Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dictionary versus Get next #4

Open
funazonki opened this issue Nov 20, 2010 · 0 comments
Open

Dictionary versus Get next #4

funazonki opened this issue Nov 20, 2010 · 0 comments

Comments

@funazonki
Copy link

Seems like using a dictionary as the return result for GetRangeSlices makes it impossible for the client to do a sensible get next as the client has no way to know which KeySlice was the last one returned and so can't know which key to use as the start key for the next call.

Maybe GetRangeSlices should return IList<KeyValuePair<string, IList>> with the last entry guaranteed to be the last one returned by Cassandra.

Same issue with the other get functions that return a dictionary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant