[
https://issues.apache.org/jira/browse/PHOENIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475144#comment-16475144
]
Hudson commented on PHOENIX-4726:
---------------------------------
ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1890 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1890/])
PHOENIX-4726 save index build timestamp -- for SYNC case only (vincentpoon: rev
1907f74a61542d993245e9a9849dc2d9b148f6e1)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDatabaseMetaData.java
> 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
> Assignee: Xu Cang
> Priority: Minor
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4726.4.patch, PHOENIX-4726.patch.1,
> PHOENIX-4726.patch.2, PHOENIX-4726.patch.3
>
>
> 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)
