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

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

Commit 4aed8279a8e15c12d6403e8aae766023da202c21 in atlas's branch 
refs/heads/ATLAS-5227 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4aed8279a ]

ATLAS-5227: Support disabling composite index


> Support disabling composite index
> ---------------------------------
>
>                 Key: ATLAS-5227
>                 URL: https://issues.apache.org/jira/browse/ATLAS-5227
>             Project: Atlas
>          Issue Type: Task
>            Reporter: Pinal Shah
>            Assignee: Pinal Shah
>            Priority: Major
>
> *Description:*
> This Jira is to support disabling the active index in janusgraph.
> For Example : For ddl.queryText , isIndexable=true.
> *This patch handles the support to make any attribute to isIndexable=false.*
> *Possible Improvement to Disable unnecessary Indexes:*
>  # *Write Latency* will drop significantly because JanusGraph no longer has 
> to create a secondary index entry for that massive string.
>  # *HBase Stability* will improve because we might stop hitting "Key Size 
> Limit" exceptions.
>  # *Storage Savings:* It will not create indexes
> *Explanation:*
> To properly remove an index, we need to follow below updated in sequence
>  # *DISABLE_INDEX:* Sets state to {{{}DISABLED{}}}. The index is no longer 
> used for queries and stops receiving updates.
>  # *DISCARD_INDEX:* Removes all data from the index storage. The index state 
> becomes {{{}DISCARDED{}}}.
>  # *DROP_INDEX:* Removes the index definition from the JanusGraph schema 
> entirely.
> But performing *DISCARD_INDEX* and *DROP_INDEX actions* can be too expensive 
> when there is huge indexed data. Hence this patch only handles  
> *DISABLE_INDEX*



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to