Re: A question to 'paging' support in DataStax java driver

I didn't read the whole thread last time around, please disregard my comment about the java driver jira. One other thought (hopefully relevant this time). Once we have https://issues.apache.org/jira/browse/CASSANDRA-10783, you could write a write a (*start*, *rows*) style paging UDF which would

RE: A question to 'paging' support in DataStax java driver

I think this request belongs in the java driver jira not the Cassandra jira. https://datastax-oss.atlassian.net/projects/JAVA/ all the best, Sebastián On May 10, 2016 1:09 AM, "Lu, Boying" wrote: > I filed a JIRA https://issues.apache.org/jira/browse/CASSANDRA-11741 to >

RE: A question to 'paging' support in DataStax java driver

I filed a JIRA https://issues.apache.org/jira/browse/CASSANDRA-11741 to track this. From: DuyHai Doan [mailto:doanduy...@gmail.com] Sent: 2016年5月10日 12:47 To: user@cassandra.apache.org Subject: Re: A question to 'paging' support in DataStax java driver I guess it's technically possible but then

Re: A question to 'paging' support in DataStax java driver

I guess it's technically possible but then we'll need to update the binary protocol. Just create a JIRA and ask for this feature On Tue, May 10, 2016 at 5:00 AM, Lu, Boying wrote: > Thanks very much. > > > > I understand that the data needs to be read from the DB to get the

RE: A question to 'paging' support in DataStax java driver

Thanks very much. I understand that the data needs to be read from the DB to get the next ‘PagingState’. But is it possible not to return those data to the client side, just returning the ‘PagingState’? I.e. the data is read on the server side, but not return to client side, this can save

Re: A question to 'paging' support in DataStax java driver

In a truly consistent world (should I say "snapshot isolation" world instead), re-reading the same page should yield the same results no matter how many new inserts have occurred since the last page read. Caching previous page at app level can be a solution but not viable if the amount of data is

Re: A question to 'paging' support in DataStax java driver

Hi Doan, What does it have to do being eventual consistency? Lets assume a scenario with complete consistency and we are at page X, and at the same time some inserts/updates happened at page X-2 and we jumped to that. User will see inconsistent page in that case as well, right? Also in such cases

Re: A question to 'paging' support in DataStax java driver

"Is it possible to just return PagingState object without returning data?" --> No Simply because before reading the actual data for each page of N rows, you cannot know at which token value a page of data starts... And it is worst than that, with paging you don't have any isolation. Let's