[jira] [Resolved] (CASSANDRA-7129) Consider allowing clients to make the Paging State available to users

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne resolved CASSANDRA-7129.
-----------------------------------------
    Resolution: Invalid

As far as the native protocol is concerned, the paging state is some bytes that the driver should return to continue paging as is (you definitively should not try to decode those bytes in one way or another if you don't want trouble for sure). This is not extremely different from say the prepared statement ID in that respect. What the drivers want to do with the paging state is their business and I don't see what more we can do.

> Consider allowing clients to make the Paging State available to users
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-7129
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7129
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>            Reporter: Michaël Figuière
>
> This is a follow up to a ticket that has been opened on the DataStax Java Driver JIRA (https://datastax-oss.atlassian.net/browse/JAVA-323).
> Currently the Paging State is described as an internal data structure that might change in any upcoming version. As a consequence it isn't safe to make it available to users of the Cassandra Drivers.
> It would be and interesting feature to work on making Cassandra safe against all the situation that might happen after unleashing paging states in the wild on the client side: they could end up being included in some web cookies, allowing malicious users to forge some, we might also have some compatibility issues as some paging states might come back to Cassandra after an upgrade of the cluster,...
> If the discussion in this ticket turns out to conclude that the paging state SHOULD NOT be made available to users, at least it will be a clarification of something that was mostly implicit (AFAIK) so far.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)