[
https://issues.apache.org/jira/browse/CALCITE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690858#comment-17690858
]
Istvan Toth commented on CALCITE-5534:
--------------------------------------
Instead of adding new properties, IMO wo should transparently relay all
non-Avatica properties to the server, and let the proxied driver handle them.
That would solve both this problem, and add the ability to set any driver
specific properties from the Avatica client.
(We could also introduce a special property where the relayed properties could
be set instead)
i.e
_jdbc:avatica:remote:url=remoteserver;driverspecific1=a;driverspecifc2=b_
or
_jdbc:avatica:remote:url=remoteserver;relayoption=driverspecifc1ESCEQaESCCOMMAdrivespecific2ESCEQb_
and these would be set for the proxied connection as
as jdbc:proxied?driverspecific1=a&driverspecific2=b
See https://issues.apache.org/jira/browse/CALCITE-4121
> Add `userAgent` JDBC param to Avatica
> -------------------------------------
>
> Key: CALCITE-5534
> URL: https://issues.apache.org/jira/browse/CALCITE-5534
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: TJ Banghart
> Assignee: TJ Banghart
> Priority: Minor
>
> It could be beneficial to add a {{userAgent}} parameter to the JDBC URL
> recognized options. This {{userAgent}} value would be passed from the client
> to server as a {{User-Agent}} HTTP header overriding Avatica's current
> default of {{Apache-HttpClient/<version> (<java_version>)}}. This would allow
> Avatica servers to more easily identify requesting applications.
> Here's [Denodo's {{userAgent}}
> |https://community.denodo.com/docs/html/browse/6.0/vdp/administration/monitoring_the_virtual_dataport_server/monitoring_with_a_java_management_extensions_jmx_agent/setting_the_user_agent_of_an_application]
> as an example.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
