You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@s2graph.apache.org by "Chul Kang (JIRA)" <ji...@apache.org> on 2018/04/10 09:25:00 UTC
[jira] [Assigned] (S2GRAPH-205) too many initialize S2Graph when
writeBatchMutate on S2GraphSink
[ https://issues.apache.org/jira/browse/S2GRAPH-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chul Kang reassigned S2GRAPH-205:
---------------------------------
Assignee: Chul Kang
> too many initialize S2Graph when writeBatchMutate on S2GraphSink
> ----------------------------------------------------------------
>
> Key: S2GRAPH-205
> URL: https://issues.apache.org/jira/browse/S2GRAPH-205
> Project: S2Graph
> Issue Type: Sub-task
> Components: s2jobs
> Reporter: Chul Kang
> Assignee: Chul Kang
> Priority: Minor
>
> When call the function S2GraphHelper.initS2Graph() , S2Graph is initialized every time.
> It causes initialize the Model class, so many connections can be created to DB.
> In especially, when you call writeBatchWithMutate on the S2graphSink class, the following code initializes S2Graph on each task.
> ```
> df.foreachPartition { iters =>
> val config = ConfigFactory.parseString(serializedConfig)
> val s2Graph = S2GraphHelper.initS2Graph(config)
> ...
> }
> ```
> I think it would be better, if we can re-use S2Graph instance on the same executor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)