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

Swaroopa Kadam updated PHOENIX-5804:
------------------------------------
    Description: 
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. 

  was:In case of the initial rebuild, empty column value will be x and for 
other unverified rows it will be x02 so we want to make sure that the 
appropriate counts are reflected when inline verification is run for an index 
with BEFORE/AFTER/ONLY/BOTH options. 


> 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
>
> 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)

Reply via email to