[
https://issues.apache.org/jira/browse/TINKERPOP-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324195#comment-15324195
]
ASF GitHub Bot commented on TINKERPOP-1331:
-------------------------------------------
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/334
Note that the travis integration is broken here because of the migration
from incubator (i.e. the link is just broken). One job passed and one failed -
here's the passing run:
https://travis-ci.org/apache/tinkerpop/builds/136484066
The failing run was due to a failure in the gremlin server tests, but i'm
guessing that to be an internal failure of travis and not something related to
this PR since we did get a green build out of this.
VOTE +1
> HADOOP_GREMLIN_LIBS can only point to local file system
> -------------------------------------------------------
>
> Key: TINKERPOP-1331
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1331
> Project: TinkerPop
> Issue Type: Improvement
> Components: hadoop
> Affects Versions: 3.2.0-incubating, 3.1.2-incubating
> Reporter: Daniel Kuppitz
> Assignee: Daniel Kuppitz
>
> These two lines in {{SparkGraphComputer}} assume that {{HADOOP_GREMLIN_LIBS}}
> will only contain local file system references (although it seems that the
> rest of the code could handle DFS references):
> {code}
> final String[] paths = hadoopGremlinLocalLibs.split(":");
> final FileSystem fs = FileSystem.get(hadoopConfiguration);
> {code}
> If, for example, {{HADOOP_GREMLIN_LIBS}} would be set to
> {{hdfs:///spark-gremlin-libs:/foo/bar}}, the {{split(":")}} call would
> obviously separate the file system scheme ({{hdfs://}}) from the path
> ({{/spark-gremlin-libs}}).
> Next, {{FileSystem.get(hadoopConfiguration)}} will always only return a
> reference to the {{FileSystem}} that is defined as the default file system.
> The same is probably true for {{GiraphGraphComputer}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
