cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michaël Figuière (JIRA) <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-7129) Consider allowing clients to make the Paging State available to users
Date Thu, 01 May 2014 14:16:15 GMT
Michaël Figuière created CASSANDRA-7129:
-------------------------------------------

             Summary: 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.2#6252)

Mime
View raw message