[
https://issues.apache.org/jira/browse/PHOENIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468196#comment-16468196
]
Vincent Poon commented on PHOENIX-4726:
---------------------------------------
I think we can call it "INDEX_CREATED_DATE", or even just "CREATED_DATE" to
keep with the existing naming convention. This is the base case, and async
differentiates with prepending ASYNC_
> save index build timestamp -- for SYNC case only.
> -------------------------------------------------
>
> Key: PHOENIX-4726
> URL: https://issues.apache.org/jira/browse/PHOENIX-4726
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Xu Cang
> Priority: Minor
> Attachments: PHOENIX-4726.patch.1, PHOENIX-4726.patch.2
>
>
> save index build timestamp, similar to ASYNC_REBUILD_TIMESTAMP, or
> ASYNC_CREATED_DATE
> ("SYNC_INDEX_CREATED_DATE" is my proposed name for SYNC case.)
>
> Check IndexUtil.java for related code.
> The reason this can be useful is: We saw a case index state stuck in 'b' for
> quite some long time. And without a timestamp to indicate where it started,
> it's hard to tell if this is a legit running task or stuck...
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
