[
https://issues.apache.org/jira/browse/PHOENIX-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634852#comment-16634852
]
Geoffrey Jacoby commented on PHOENIX-4519:
------------------------------------------
[~vincentpoon] - Found something weird.
I changed the test to use ALTER INDEX...REBUILD ASYNC, but it failed on the
assertion that the ALTER statement successfully set the index state to REBUILD.
It said the index was in BUILDING.
I looked in the MetaDataClient, and it appears that the alterIndex code
automatically replaces requests to alter an index to REBUILD state with
BUILDING. This code is from [~jamestaylor]'s original giant 2014 checkin.
See MetaDataClient:4041:
{code:java}
if (newIndexState == PIndexState.REBUILD) { newIndexState =
PIndexState.BUILDING; }
{code}
> Index rebuild MR jobs not created for "alter index rebuild async" rebuilds
> --------------------------------------------------------------------------
>
> Key: PHOENIX-4519
> URL: https://issues.apache.org/jira/browse/PHOENIX-4519
> Project: Phoenix
> Issue Type: Bug
> Reporter: Vincent Poon
> Assignee: Geoffrey Jacoby
> Priority: Major
> Attachments: PHOENIX-4519-v2.patch, PHOENIX-4519.patch
>
>
> It seems we have two ASYNC flags for index rebuilds:
> ASYNC_CREATED_DATE - when an index is created async
> ASYNC_REBUILD_TIMESTAMP - created by "alter index ... rebuild async"
> The PhoenixMRJobSubmitter only submits MR jobs for the former. We should
> also submit jobs for the latter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
