[jira] [Updated] (PHOENIX-5866) IndexTool verification marks a timestamp column as not matching even though they match

["Gokcen Iskender (Jira)" <ji...@apache.org>]

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

Gokcen Iskender updated PHOENIX-5866:
-------------------------------------
    Description: 
This is a False Negative report from IndexTool verification.

The data table is an immutable table and index table has the include column with timestamp.

When indexTool -v Only runs, it marks this row as invalid sometimes saying the ActualValue is different than Index tool table value. The data table and index table have the same rows with same values when we query. The IndexTool's actual value is similar to data table value but it is not the same one. We suspect that the timestamp differ by a few millisecods and it is a value from memory not from the data table.

> IndexTool verification marks a timestamp column as not matching even though they match 
> ---------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5866
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5866
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Gokcen Iskender
>            Priority: Major
>
> This is a False Negative report from IndexTool verification.
> The data table is an immutable table and index table has the include column with timestamp.
> When indexTool -v Only runs, it marks this row as invalid sometimes saying the ActualValue is different than Index tool table value. The data table and index table have the same rows with same values when we query. The IndexTool's actual value is similar to data table value but it is not the same one. We suspect that the timestamp differ by a few millisecods and it is a value from memory not from the data table.



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