Feat: Add queryId to TableResult#3106
Conversation
|
Please let me know if it's not advisable to update the constructor for TableResult. |
I recommend asking on a Java chat. This may be considered a breaking change. |
Just verified, since the constructors are annotated with |
| */ | ||
| @InternalApi("Exposed for testing") | ||
| public TableResult(Schema schema, long totalRows, Page<FieldValueList> pageNoSchema) { | ||
| public TableResult( |
There was a problem hiding this comment.
Rather than solely extending the existing constructor, should we just provide an second signature or a builder? It would mean you can avoid having to touch all the callsites where queryId isn't relevant for construction.
There was a problem hiding this comment.
As discussed offline. I think creating a builder would be the preferred option. I'll follow up with another PR to switch to using a builder.
This PR adds queryId to TableResult by changing its public constructors. It should be fine to update TableResult constructors to include QueryId since it is used to return results to the user and users should not directly construct TableResult objects.
Fixes #3105 ☕️