[
https://issues.apache.org/jira/browse/TINKERPOP-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088267#comment-15088267
]
ASF GitHub Bot commented on TINKERPOP-1033:
-------------------------------------------
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/192#issuecomment-169827767
This PR drops a few "internal" classes - folks shouldn't have been using
those directly, but would it have been better to deprecate those as opposed to
just removing completely?
Seems like deprecation would have worked for:
*
[HadoopLoader](https://github.com/apache/incubator-tinkerpop/pull/192/files#diff-*
55e3610726b342e666b34223b8270526)
*
[HDFSTools](https://github.com/apache/incubator-tinkerpop/pull/192/files#diff-88ec5bbe9a2817117d62799b9e91a20a)
*
[SparkLoader](https://github.com/apache/incubator-tinkerpop/pull/192/files#diff-0c5aa03b09c929fa6440edb9bacc7e76)
even though these are pretty low-level classes, it would be nice to stick
to "not breaking (even if they are doing stuff they are not supposed to)" plan
imo.
> Store sideEffects as a persisted RDD
> ------------------------------------
>
> Key: TINKERPOP-1033
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1033
> Project: TinkerPop
> Issue Type: Improvement
> Components: hadoop
> Affects Versions: 3.1.0-incubating
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
> Fix For: 3.1.1-incubating
>
>
> I think we can completely get away from HDFS for {{SparkGraphComputer}}. We
> will need something like {{PesistedSideEffectsRDD}}. Once we do that, if the
> user wants to use Spark without Hadoop, its possible.
> This would beg the question -- do we go all the way and support
> {{SparkGraph}} ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
