[
https://issues.apache.org/jira/browse/CASSANDRA-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-13138:
------------------------------------
Component/s: sasi
> SASI tries to fetch an extra page when resultset size is same size as page
> size
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-13138
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13138
> Project: Cassandra
> Issue Type: Bug
> Components: sasi
> Reporter: Alex Petrov
> Assignee: Alex Petrov
>
> For example, in a dataset that would return 10 rows, SASI would try (and
> return an empty page) to fetch the next page, while filtering and 2i will
> return results correctly:
> {code}
> pk | ck1 | ck2 | reg1 | reg2 | reg3
> ----+-----+-----+------+------+------
> 6 | 5 | 5 | 5 | 5 | 10
> 7 | 5 | 5 | 5 | 5 | 10
> 9 | 5 | 5 | 5 | 5 | 10
> 4 | 5 | 5 | 5 | 5 | 10
> 3 | 5 | 5 | 5 | 5 | 10
> 5 | 5 | 5 | 5 | 5 | 10
> 0 | 5 | 5 | 5 | 5 | 10
> 8 | 5 | 5 | 5 | 5 | 10
> 2 | 5 | 5 | 5 | 5 | 10
> 1 | 5 | 5 | 5 | 5 | 10
> ---MORE---
> (10 rows)
> {code}
> (that {{--MORE--}} shouldn't have been there)
> This might be an inherent limitation, although even if it is we can opt out
> for fetching limit+1 if the data limits aren't exhausted. Although it seems
> that there should be a solution for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
