[
https://issues.apache.org/jira/browse/TINKERPOP-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088384#comment-15088384
]
ASF GitHub Bot commented on TINKERPOP-1033:
-------------------------------------------
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/192#issuecomment-169840450
Yeah - they shouldn't be using them, but we know how that goes....make a
class public and someone is gonna use it to their detriment or otherwise.
anyway, i'd say just do one of the following then:
1. bring them back and deprecate
2. add something to upgrade docs to explain their removal - you already
have the section - perhaps just a WARNING that explicitly mentions the classes.
> 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)
