Right now it is not easy to do the below simple testing steps:
- Write some SQL, manually query into Pinot cluster
- Record the response JSON into a resource file in Java
- use that JSON as test fixtures to mock response
The major issue is that our TestableResultTableResultSet.java file is not public.
So right now in our code we basically copy that file into our test project.
It is reasonable to avoid exposing as less as possible in public client, but on the other hand it also make sense to help client side testing easier.
Not sure how the best solution will be but we can think of a good way to avoid support but still provide testing support.
On top of my mind I am thinking of a new "pinot-java-client-test" module dedicated to test only.
Right now it is not easy to do the below simple testing steps:
The major issue is that our TestableResultTableResultSet.java file is not public.
So right now in our code we basically copy that file into our test project.
It is reasonable to avoid exposing as less as possible in public client, but on the other hand it also make sense to help client side testing easier.
Not sure how the best solution will be but we can think of a good way to avoid support but still provide testing support.
On top of my mind I am thinking of a new "pinot-java-client-test" module dedicated to test only.