[
https://issues.apache.org/jira/browse/HADOOP-17402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240941#comment-17240941
]
Steve Loughran edited comment on HADOOP-17402 at 11/30/20, 6:04 PM:
--------------------------------------------------------------------
done because it's separate.
If the GCS connector adds the right service-info entry it becomes
self-declaring.
There's a cost to that if the implementation class has complex dependencies
* slower to load
* if something off the classpath then it doesn't load
We've really hoped to sit down and implement HADOOP-14132, which enhances
discovery, nobody has though.
What's the status of the GCS connector's service declaration? Does it have one?
was (Author: [email protected]):
done because it's separate.
If the GCS connector adds the right service-info entry it becomes
self-declaring.
There's a cost to that if the implementation class has complex dependencies
* slower to load
* if something off the classpath then it doesn't load
We've really hoped to sit down and implement HADOOP-14132, which enhances
discovery, nobody has though.
Does
> Add GCS FS defaults to core-default.xml
> ---------------------------------------
>
> Key: HADOOP-17402
> URL: https://issues.apache.org/jira/browse/HADOOP-17402
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Reporter: Rafal Wojdyla
> Priority: Major
>
> Akin to current S3 default configuration add GCS configuration, specifically
> to declare the GCS implementation. [GCS
> connector|https://cloud.google.com/dataproc/docs/concepts/connectors/cloud-storage].
> Has this not been done since the GCS connector is not part of the hadoop/ASF
> codebase, or is there any other blocker?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]