You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metamodel.apache.org by "Kasper Sørensen (JIRA)" <ji...@apache.org> on 2015/12/14 11:02:46 UTC
[jira] [Resolved] (METAMODEL-220) Add dynamic scheme name to
HdfsResource
[ https://issues.apache.org/jira/browse/METAMODEL-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kasper Sørensen resolved METAMODEL-220.
---------------------------------------
Resolution: Fixed
Assignee: Kasper Sørensen
Fix Version/s: 4.5.0
> Add dynamic scheme name to HdfsResource
> ---------------------------------------
>
> Key: METAMODEL-220
> URL: https://issues.apache.org/jira/browse/METAMODEL-220
> Project: Apache MetaModel
> Issue Type: Improvement
> Affects Versions: 4.4.1
> Reporter: Kasper Sørensen
> Assignee: Kasper Sørensen
> Fix For: 4.5.0
>
>
> We should offer a way to use other scheme's than "hdfs" for Hadoop FileSystem based resources.
> NOTE: This issue is blocked by/dependent on METAMODEL-219 because the file system configuration would need to be loaded from configuration files.
> I have heard of at least a few variants that supposedly support the same API:
> * OpenStack Swift (swift://...)
> * Amazon EMR FS (emrfs://...)
> * MapR file system (maprfs://...)
> And there are probably more.
> Today "hdfs://" is hardcoded into HdfsResource and clearly it should be a field which the user can select a different value for. I suggest to keep it simply as a string and to also add a couple of constants in the class to make it easy for users to pick between the usual candidates.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)