[
https://issues.apache.org/jira/browse/PHOENIX-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101039#comment-17101039
]
Geoffrey Jacoby commented on PHOENIX-5876:
------------------------------------------
To give some context: PHOENIX-5645, adding max lookback age, can't currently be
ported to master because of coprocessor changes in HBase 2.0 and up. (I'm
currently working HBASE-24321 to fix that, but even once it and HBase 2.3 are
out, there's going to be some not-fun compatibility shim work in Phoenix
because it can't be backported to 2.0, 2.1 or 2.2.)
[~wangweiming800], [~swaroopa], and I had to do a bunch of changes to the
IndexTool and IndexScrutinyTool to work with max lookback age, and then I did
PHOENIX-5799 on top of them to do a broad refactor that allows external tools
to parse the IndexTool results.
So at this point, the IndexTool code is really different between 4.x and
master. One of the next things on my to-do list (probably going to start in the
next day or so) is trying to get them as close together as I can _without_
porting max lookback to master, since that's still impossible.
> IndexTool updates the index state when it runs with ONLY option
> ---------------------------------------------------------------
>
> Key: PHOENIX-5876
> URL: https://issues.apache.org/jira/browse/PHOENIX-5876
> Project: Phoenix
> Issue Type: Bug
> Reporter: Weiming Wang
> Assignee: Weiming Wang
> Priority: Minor
> Fix For: 4.16.0
>
> Attachments: PHOENIX-5876.4.x.001.patch, PHOENIX-5876.4.x.001.patch,
> PHOENIX-5876.4.x.001.patch
>
>
> When IndexTool runs with ONLY option, it is NOT supposed to update the index
> state, since it never rebuild the index. However current code is working the
> opposite way.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
