[
https://issues.apache.org/jira/browse/CALCITE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690676#comment-17690676
]
Julian Hyde commented on CALCITE-5534:
--------------------------------------
Is this for the remote driver or would it make sense for all connections? It
would be a new value in BuiltInConnectionProperty or
AvaticaRemoteConnectionProperty, depending.
Would people be allowed to add extra information (e.g. the client process ID)
to the string?
Should the property be masked or hidden (as the password property is) when
tracing etc.
> 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)
