[ 
https://issues.apache.org/jira/browse/ATLAS-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791458#comment-16791458
 ] 

ASF subversion and git services commented on ATLAS-3057:
--------------------------------------------------------

Commit 3ed1f5a082ed665ce54f7dffc683b0f7b191e44d in atlas's branch 
refs/heads/master from nikhilbonte
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3ed1f5a ]

ATLAS-3057:- Atlas Index Repair tool for JanusGraph

Signed-off-by: nixonrodrigues <[email protected]>


> Index Repair Tool: Add JanusGraph-Specific Index Repair Tool
> ------------------------------------------------------------
>
>                 Key: ATLAS-3057
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3057
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Ashutosh Mestry
>            Assignee: Nikhil Bonte
>            Priority: Major
>         Attachments: ATLAS-3057-Atlas-Index-Repair-tool-for-JanusGraph.patch, 
> ATLAS-3057-Atlas-Index-Repair-tool-for-JanusGraph.patch
>
>
> *Background*
> For Atlas version that uses _HBase_ and _Solr_, occasionally if Solr is down 
> and entities get created, then there is no record of the created entities 
> within Solr. Basic search does not indicate presence of such entities.
> *Solution*
> Index Repair Tool (which was present in branch-0.8) should be implemented for 
> JanusGraph.
> *Implementation Guidance*
>  * Create Java-based implementation rather than Groovy script that needs 
> graphdb-specific shell to be installed. 
>  * Use JanusGraph APIs for restore instead of custom per-vertex logic.
>  * Investigate possibility of using MapReduce for higher throughput.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to