Need a mechanism to handle schema changes due to dictionary hydration in FlightSQL server implementations
What changes are included in this PR?
With this change is now possible to inspect the encoded schema of the encoded Flight data, which may differ from the input schema based on dictionary hydration handling.
Are there any user-facing changes?
Yes, and example motivating the new API has been given.
alamb
commented
1 week ago
Which issue does this PR close?
Fixes #6672
Rationale for this change
Need a mechanism to handle schema changes due to dictionary hydration in FlightSQL server implementations
What changes are included in this PR?
With this change is now possible to inspect the encoded schema of the encoded Flight data, which may differ from the input schema based on dictionary hydration handling.
Are there any user-facing changes?
Yes, and example motivating the new API has been given.