[
https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740666#comment-16740666
]
Sean Mackrory commented on HADOOP-16041:
----------------------------------------
In the case of CDH (and I believe Hortonworks / HDInsight) the version number
includes an identification of the vendor and the vendor release. For example
"3.0.0-cdh6.0.0". That's how the vendor has been identified in the other
connectors as far as I'm aware - that's definitely all we did for ADLS Gen1 and
I know the required information was still collected. In these Hadoop distros
the user-configurable prefix is also modifiable by the user, and has been used
(not on Azure specifically in the cases I'm thinking of) to identify workloads
from a particular large user or something like that. It's not as good a fit for
identifying the vendor. With the Databricks model where it's more of a service,
then it does make sense to identify themselves using the configured prefix
(which is actually a suffix right now) unless their version string embeds
enough information.
+1 to ABFS/<version string>, if that allows you to identify Hadoop vendors
sufficiently well.
> UserAgent string for ABFS
> -------------------------
>
> Key: HADOOP-16041
> URL: https://issues.apache.org/jira/browse/HADOOP-16041
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.0
> Reporter: Shweta
> Assignee: Shweta
> Priority: Major
> Fix For: 3.3.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
