You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@giraph.apache.org by "Dionysios Logothetis (Jira)" <ji...@apache.org> on 2020/05/12 18:31:00 UTC

[jira] [Resolved] (GIRAPH-348) Create GiraphContext

     [ https://issues.apache.org/jira/browse/GIRAPH-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dionysios Logothetis resolved GIRAPH-348.
-----------------------------------------
    Resolution: Abandoned

> Create GiraphContext
> --------------------
>
>                 Key: GIRAPH-348
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-348
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Priority: Major
>
> I was thinking about this after GIRAPH-337 and we have a lot of places where we provide both Context and ImmutableClassesGiraphConfiguration.  The reason is because Context provides Configuration, but not ImmutableClassesGiraphConfiguration.
> Note that the input/output formats do not handle this properly right now, requiring that they create ImmutableClassesGiraphConfiguration and store it.  To fix this, I am suggesting a GiraphContext object that can provide ImmutableClassesGiraphConfiguration, Progressable (for progress), and Status (for status).  What do you think?  This is an API change.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)