You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Ashutosh Mestry (Jira)" <ji...@apache.org> on 2019/08/20 17:38:00 UTC
[jira] [Commented] (ATLAS-3381) Atlas Patch Handler: Patch Handlers
Not Committing Changes
[ https://issues.apache.org/jira/browse/ATLAS-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911580#comment-16911580 ]
Ashutosh Mestry commented on ATLAS-3381:
----------------------------------------
Addresses:
* Commit problem.
* _EntityGraphMapper.updateClassificationTextAndNames_ performance problem. The entity retrieval is now moved after the vertex is checked for existence of classification.
> 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)