joellubi commented on issue #1107: URL: https://github.com/apache/arrow-adbc/issues/1107#issuecomment-1738913442
Thanks for the suggestion, it makes sense to include those fields. Regarding your question about db-specific parameters, I can see the following options: 1. Add each option explicitly to the spec, but this would probably only work for parameters that generalize across many backends (i.e. not db-specific). 2. Add a single field capable of storing arbitrary key-value pairs, like `app_metadata`. 3. Use the existing `app_metadata` field of the initial FlightData sent as part of DoPut to include db-specific kv pairs. I would appreciate your perspective on these options (or any others) @lidavidm. -- 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]
