You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2020/07/28 00:13:00 UTC

[jira] [Resolved] (HBASE-24780) Index rebuilds should record scan timestamp to job counter

     [ https://issues.apache.org/jira/browse/HBASE-24780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby resolved HBASE-24780.
-------------------------------------
    Resolution: Invalid

(sigh) Wrong project, apologies for the noise. 

> Index rebuilds should record scan timestamp to job counter
> ----------------------------------------------------------
>
>                 Key: HBASE-24780
>                 URL: https://issues.apache.org/jira/browse/HBASE-24780
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>
> The index tool output tables (PHOENIX_INDEX_TOOL and PHOENIX_INDEX_TOOL_RESULT) are both keyed on the effective scan time of the index rebuild. This makes the table quite difficult to query if you know the index you're interested in but not the exact millisecond it was last rebuilt. 
> Short term: record this timestamp in the Phoenix index rebuild job counters (this JIRA)
> Longer term: we might want to consider reversing the PK to both cut down on hotspotting and make the table easier to query. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)