aiguofer opened a new issue, #208: URL: https://github.com/apache/arrow-java/issues/208
### Describe the enhancement requested From an infrastructure perspective, it would be easier for us to do path based routing for our Flight server instead of sub-domain based routing. For example, `https://mydomain.com/grpc/flight`. A model like this would allow us to create routing rules for all grpc services we expose within our company using shared architecture. Looking around at `getUrlsArgs` , there seems to be no use for the `path` part of the JDBC URI, so I see a few ways this could be implemented: ``` jdbc:arrow-flight-sql://mydomain.com/grpc/flight:443 jdbc:arrow-flight-sql://https://mydomain.com/grpc/flight:443 jdbc:arrow-flight-sql://mydomain.com:443/grpc/flight jdbc:arrow-flight-sql://https://mydomain.com:443/grpc/flight ``` This seems to be fairly uncommon, but there's at least one other driver that does this. For example, the Simba BigQuery connection looks like this: ``` jdbc:bigquery://https://www.googleapis.com/bigquery/v2:443;ProjectId=<Your Project ID>;OAuthType=0;OAuthServiceAcctEmail=<Service Email Address>;OAuthPvtKeyPath=<Path to Key File>; ``` I'm not sure if this is already supported by the `Avatica` driver, so it may also need some changes there. ### Component(s) Java -- 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: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
