[
https://issues.apache.org/jira/browse/ATLAS-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911998#comment-16911998
]
ASF subversion and git services commented on ATLAS-3381:
--------------------------------------------------------
Commit f000237a3caad91a77bacdba5e6dbd5fd1ce41f3 in atlas's branch
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f000237 ]
ATLAS-3381: Addressed ConcurrentPatchProcessor not calling commit.
Signed-off-by: nixonrodrigues <[email protected]>
(cherry picked from commit 6fbda5bcee4d9a06fc83cd80533a9971b88bb417)
> Atlas Patch Handler: Patch Handlers Not Committing Changes
> ----------------------------------------------------------
>
> Key: ATLAS-3381
> URL: https://issues.apache.org/jira/browse/ATLAS-3381
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 2.0.0, trunk, 3.0.0
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Fix For: trunk
>
> Attachments:
> ATLAS-3381-Addressed-ConcurrentPatchProcessor-not-ca.patch
>
>
> ***Background*
> Atlas patch handler is a framework that applies changes made to the structure
> of the data. Latest update to the _ConcurrentPatchProcessor_ is missing the
> commit statement. This causes changes not to get applied.
> *Solution*
> Since _ConcurrentPatchHandler_ uses the _PC_ framework, calling the
> _ConcurrentPatchProcessor_.doCommit after
> _individualItemProcessor.processVertexItem_ will address the problem.
> *Impact*
> The _commit_ is finally called when the data is exhausted, only that until
> then the data is held in memory. This may be OK for really small data but
> does not work for medium to large size data. The result is out of memory
> exception, since _JanusGraph_ holds all these changes in memory waiting for
> commit to be called.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
