We did merge the cleared IP into a branch:
https://github.com/apache/arrow/tree/flight-sql-jdbc
James then took it and filed a PR, which we can review:
https://github.com/apache/arrow/pull/13800
So long as further changes build on top of that commit, I guess we can just
include them in the exis
If you want to merge the cleared IP into a new branch rather than
master, that is fine, too. It's not necessary to land it in the main
branch
On Tue, Aug 2, 2022 at 4:18 PM David Li wrote:
>
> Would it be OK to get what's there into the main branch first? i.e., open a
> PR from the apache/flight
Would it be OK to get what's there into the main branch first? i.e., open a PR
from the apache/flight-jdbc-driver (or a contributor's clone of it, that would
make it easier to address review comments). I'd like to get through the review
of what we currently have since the PR will be large. And t
Hi,
We have a few additional important changes for the Flight SQL JDBC Driver:
- Avoid sending headers for built-in properties such as hostname, port.
- Make handling of connection URI key names and Properties keys
case-insensitive.
- Create separate FlightClients for each new endpoint returned by
