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

rajeshbabu commented on PHOENIX-1314:
-------------------------------------

Upload backport patch for 3.0 to check seek hint order with in column family 
which I will commit this after some time.

[~lhofhansl]
bq. I meant RegionScanner, sorry. (unless we have multiple column families 
Region == Store as far as this discussion is concerned).
Ohh. no problem.
bq. Why are we seeking to seemingly the same position again? 
(prev=varchar7//LATEST_TIMESTAMP/Maximum/vlen=0/mvcc=0, 
next=varchar7//LATEST_TIMESTAMP/Maximum/vlen=0/mvcc=0) Do you have multiple 
column families in your case?
Yes Lars there are two column families in the table. Currently reseek happening 
on only one store scanner at a time so even after first store scanner reseek to 
varchar7 second store scanner still scans kvs less than hint, that's why same 
hint given by filter. In latest patch checking seek hint order  column family 
wise.

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

Reply via email to