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
Describe the bug, including details regarding any error messages, version, and platform.
As part of writing a Flight integration test client for .NET (#44361) I ran into a limitation where the C# client can't handle the primitive_no_batches test case because it doesn't send the schema until you write the first record batch.
…44377)
### Rationale for this change
See #44361. This allows testing compatibility of the .NET Flight implementation with other Flight implementations.
### What changes are included in this PR?
* Adds a new `Apache.Arrow.Flight.IntegrationTest` project that can run in server or client mode for Flight integration tests.
* Includes the integration tests that send then retrieve data defined in JSON files, but doesn't add any of the named scenarios
* Configures archery to include C# in the Flight integration tests, but skip all the named scenarios
* Also skips tests that use dictionary data due to #38045, and the empty data test due to #44363
### Are these changes tested?
These changes are tests.
### Are there any user-facing changes?
No
* GitHub Issue: #44361
Authored-by: Adam Reeve <adreeve@gmail.com>
Signed-off-by: Curt Hagenlocher <curt@hagenlocher.org>
Describe the bug, including details regarding any error messages, version, and platform.
As part of writing a Flight integration test client for .NET (#44361) I ran into a limitation where the C# client can't handle the
primitive_no_batches
test case because it doesn't send the schema until you write the first record batch.For comparison, the PyArrow and C++ implementations require passing the schema when calling
do_put
, and always send the schema even if no batches are sent: https://arrow.apache.org/docs/python/generated/pyarrow.flight.FlightClient.html#pyarrow.flight.FlightClient.do_putComponent(s)
C#
The text was updated successfully, but these errors were encountered: