You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 12, 2020. It is now read-only.
The document actually uses a composited CF in its example. You can use Components() with one or more values for composite components in Query, and leave the others free to range over them, and Between() to make a range query over the last composite component value. As for the struct mapping you use cols to tell Gossie which struct fields are part of the composite column name. This minimal interface actually exposes all the available functionality in (non-dynamic) composite column names circa Cassandra 1.0, but I believe "fat" clients like Astyanax go a lot farther than this and build higher level abstractions that hide those details to the developer.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would it be possible to update the docs to show how to save/query composite columns and how to do column range queries on composite columns?
We do this all the time in Astyanax on Java, so we are trying to find out how to do the same thing in gossie
thank you
The text was updated successfully, but these errors were encountered: