You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Part of #1404. This is for generate_nested_dictionary_case, C++ producing, Rust consuming case.
Currently we take the schema of uploaded data as expected schema, using it when reading dictionary and record batches. But it causes some errors when integrating with C++ producing cases. After uploading data, the received schema from flight data could be different in dictionary ids. So it looks like C++ assigns different dictionary ids, although the actual dictionary encoded batches are the same.
Because we use dictionary ids to find correspond dictionary encoded data, incorrect dictionary ids cause unexpected error. As the scenarios is to test flight client, we should use the schema received from flight data too.
After #1635 and #1646, this is the last piece for fully enabling generate_nested_dictionary_case in archery --debug integration --run-flight --with-cpp=true --with-rust=true.
Describe the solution you'd like generate_nested_dictionary_case should be passed.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Part of #1404. This is for
generate_nested_dictionary_case
, C++ producing, Rust consuming case.Currently we take the schema of uploaded data as expected schema, using it when reading dictionary and record batches. But it causes some errors when integrating with C++ producing cases. After uploading data, the received schema from flight data could be different in dictionary ids. So it looks like C++ assigns different dictionary ids, although the actual dictionary encoded batches are the same.
Because we use dictionary ids to find correspond dictionary encoded data, incorrect dictionary ids cause unexpected error. As the scenarios is to test flight client, we should use the schema received from flight data too.
After #1635 and #1646, this is the last piece for fully enabling
generate_nested_dictionary_case
inarchery --debug integration --run-flight --with-cpp=true --with-rust=true
.Describe the solution you'd like
generate_nested_dictionary_case
should be passed.Describe alternatives you've considered
Additional context
#1404
The text was updated successfully, but these errors were encountered: