phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4703) Provide an option to fully rebuild indexes asynchronously through SQL
Date Fri, 31 May 2019 01:02:00 GMT

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

Hudson commented on PHOENIX-4703:
---------------------------------

ABORTED: Integrated in Jenkins build PreCommit-PHOENIX-Build #2616 (See [https://builds.apache.org/job/PreCommit-PHOENIX-Build/2616/])
PHOENIX-4703 Make indextool changes to drop before rebuild (gjacoby: rev 94d840562e56b63aa9dfda21c6ed73ef791afb7e)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexToolForDeleteBeforeRebuildIT.java
PHOENIX-4703 Make indextool changes to drop before rebuild (gjacoby: rev d218e6135b3f02487b906d031ebefc160ae78ea7)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexToolForDeleteBeforeRebuildIT.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java


> Provide an option to fully rebuild indexes asynchronously through SQL
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-4703
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4703
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Vincent Poon
>            Assignee: Gokcen Iskender
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0
>
>         Attachments: PHOENIX-4703-4.x.patch, PHOENIX-4703.patch
>
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> Currently if we run "ALTER INDEX ... REBUILD" , all the rows in the index are deleted
and the index is rebuilt synchronously.
> "ALTER INEX ... REBUILD ASYNC" seems to be used for the IndexTool's partial rebuild option,
rebuilding from ASYNC_REBUILD_TIMESTAMP (PHOENIX-2890)
> So it seems currently the only way to fully rebuild is the drop the index, and recreate
it.  This is burdensome as it requires have the schema DDL.
> We should have an option to fully rebuild asynchronously, that has the same semantics
as dropping and recreating the index.  A further advantage of this is we can maintain the
splits of the index table while dropping its data.  We are currently seeing issues where
rebuilding a large table via a MR job results in hotspotting due to all data regions writing
to the same index region at the start.
>  



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

Mime
View raw message