[
https://issues.apache.org/jira/browse/ATLAS-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494758#comment-17494758
]
Ashutosh Mestry commented on ATLAS-3057:
----------------------------------------
We have tested this only with HBase + Solr.
Having said that, we have only used JanusGraph APIs. Which means that if
appropriate configurations are added, HBase + ES should function.
Hope that helps.
> 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: New Feature
> Reporter: Ashutosh Mestry
> Assignee: Nikhil P Bonte
> Priority: Major
> Fix For: 2.0.0, trunk
>
> 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
(v8.20.1#820001)
