You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2021/01/15 12:19:01 UTC

[jira] [Updated] (PHOENIX-5804) Implement strong verification with -v ONLY option for old design of secondary indexes

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

Istvan Toth updated PHOENIX-5804:
---------------------------------
    Fix Version/s: 5.1.0

> Implement strong verification with -v ONLY option for old design of secondary indexes
> -------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5804
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5804
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Swaroopa Kadam
>            Assignee: Swaroopa Kadam
>            Priority: Major
>             Fix For: 5.1.0
>
>         Attachments: PHOENIX-5804.4.x.v1.patch, PHOENIX-5804.4.x.v2.patch, PHOENIX-5804.4.x.v3.patch, PHOENIX-5804.4.x.v4.patch, PHOENIX-5804.4.x.v5.patch, PHOENIX-5804.v1.patch, PHOENIX-5804.v2.patch
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Currently, with -v ONLY option we get weak verification i.e. we find out if index row is present or not. It does not provide information on if the values have mismatch when executed with old design.
> We attempt to provide scrutiny like implementation but way faster. The verification will be done only one the latest version of the row.  
> This will help us in quantifying the success of new self-consistent secondary indexes design. 



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