[jira] [Comment Edited] (PHOENIX-6067) (5.x) Global Secondary Index Parity with 4.x

["Lars Hofhansl (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190808#comment-17190808 ] 

Lars Hofhansl edited comment on PHOENIX-6067 at 9/4/20, 4:13 PM:
-----------------------------------------------------------------

After a quick sweep there are "only" 23 issues marked this way. Some of them have a forward port jira.
Do you think still think this approach is best? You could also do one forward port jira/patch for these and link all the ported jiras there.
Not saying this is wrong, just wondering what's more work/risk in the end.



was (Author: lhofhansl):
After a quick sweep there are "only" 23 issues marked this way. Some of them have a forward port jira.
Do you think still think this approach is best?


> (5.x) Global Secondary Index Parity with 4.x
> --------------------------------------------
>
>                 Key: PHOENIX-6067
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6067
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Swaroopa Kadam
>            Assignee: Geoffrey Jacoby
>            Priority: Blocker
>             Fix For: 5.1.0
>
>         Attachments: PHOENIX-6067.v1.patch, PHOENIX-6067.v2.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> A large number of indexing JIRAs were done for Phoenix 4.16 but were originally unable to be ported to 5.x because of the lack of HBase 2.x support for PHOENIX-5645, max lookback age. This was eventually fixed in HBASE-24321 and PHOENIX-5881. Because some JIRAs later than the missing ones _were_ ported to 5.x, applying them all one-by-one and testing each intermediate version would be impractical.
> This JIRA will import the 4.16 global index implementation into 5.1.0, then fix HBase API usage to conform to HBase 2.x standards and Phoenix's HBase 2.x compatibility shim between minor versions. (For example, max lookback age features aren't supported in 2.1 and 2.2 because they lack HBASE-24321, and incremental index validation will be deactivated when running against HBase 2.1, because of the lack of HBASE-22710 to use raw Filters.) 



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