[
https://issues.apache.org/jira/browse/PHOENIX-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rajeshbabu updated PHOENIX-1314:
--------------------------------
Attachment: PHOENIX-1314_3.0_v2.patch
[~lhofhansl]
bq. They seek to the same KV, no?
Yes they seek to same KV one after other while filtering their kvs.
bq. Could we instead just change the assert to only enforce the row-key of the
new hint is >= the row-key of the previous one?
Row key of new hint should strictly greater than previous hint so just > check
is fine.
And added the test case for the above failed scenario.
Thanks.
> Assertion tripped for skip scan with two unit tests
> ---------------------------------------------------
>
> Key: PHOENIX-1314
> URL: https://issues.apache.org/jira/browse/PHOENIX-1314
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.1
> Reporter: James Taylor
> Assignee: rajeshbabu
> Attachments: PHOENIX-1314.patch, PHOENIX-1314_3.0.patch,
> PHOENIX-1314_3.0_v2.patch, PHOENIX-1314_v3.patch, Phoenix-1314_3.0.patch
>
>
> After checking in a pretty sizeable change
> (https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=d018cc1c6e01d9836de6e67af4f8b91de3269bfd),
> the assert in SkipScanFilter.setNextCellHint() started getting tripped for
> the following unit tests:
> - DeleteIT.testDeleteAllFromTableWithIndexNoAutoCommitNoSalting()
> - MutableIndexIT.testCoveredColumnUpdatesWithLocalIndex()
> The tests seem to pass without this assert (not sure what HBase does if the
> seek next hint is the same as the current row), but it would be good to get
> to the bottom of this. Would you mind taking a look, [~rajesh23]? It's
> possibly related to PHOENIX-1313.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
