indigophox commented on PR #34817: URL: https://github.com/apache/arrow/pull/34817#issuecomment-1868167035
> I'm not sure what you're asking; runner.py just executes binaries supplied to it. The existing C++ tests are the best reference for what is available to you. @lidavidm So I think the gotcha I was expecting to hit (and did) with Flight SQL is that it appears that the existing integration test infra is built around a FlightServer (that can only be modified by calls to its builder), whereas a lot of the Flight SQL handlers are built into the server rather than the producer... so implementing those as part of the test fixtures is probably impossible as things stand right now? Do you see any straightforward way to implement and use a customized FlightSqlServerBase implementation, or is the only way what @kou did by cutting in at doAction in a NoOpFlightProducer subclass? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
