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 Aug 4, 2020. It is now read-only.
Maybe we need CompositeTypes and DynamicCompositeTypes classes (http://www.slideshare.net/edanuff/indexing-in-cassandra) instead of array. Am I right about this: a key_validation_class can have only 2 types/datafields and a comparator as much as you'd like, when using DynamicCompositeType?
The text was updated successfully, but these errors were encountered:
DynamicCompositeType will definitely need its own class (in terms of phpcassa\Schema\DataType\CompositeType), but that should still be able to be represented as an array (that maps component names to values). In any case, DynamicCompositeType is not yet supported.
There's no restriction on the number of components you can include in key_validation_class. From Cassandra's perspective, it's just doing a little bit of validation on a binary string.
Maybe we need CompositeTypes and DynamicCompositeTypes classes (http://www.slideshare.net/edanuff/indexing-in-cassandra) instead of array. Am I right about this: a key_validation_class can have only 2 types/datafields and a comparator as much as you'd like, when using DynamicCompositeType?
The text was updated successfully, but these errors were encountered: