Cassandra large objects:

nosql database
  • All header information variables become static attached to your primary key.
  • Parcel information will become non-static variables.
  • Your clustering column will identify each parcel data object.
  • This way you should get all parcel information belonging to a header with just one lookup. (There are many examples out there in the web, describing this pattern).
  • Generally speaking, it’s never a good idea to build relationships in Cassandra with the use of multiple tables.
  • If there’s no way out use data duplication to achieve “single read get’s all” queries.
storing lists of large objects in cassandra

Categorized in:

Tagged in:

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,