[
https://issues.apache.org/jira/browse/CASSANDRA-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911171#comment-13911171
]
Edward Capriolo commented on CASSANDRA-6757:
--------------------------------------------
Also take this into account:
https://developers.google.com/protocol-buffers/docs/cpptutorial
{quote}
Required Is Forever You should be very careful about marking fields as
required. If at some point you wish to stop writing or sending a required
field, it will be problematic to change the field to an optional field – old
readers will consider messages without this field to be incomplete and may
reject or drop them unintentionally. You should consider writing
application-specific custom validation routines for your buffers instead. Some
engineers at Google have come to the conclusion that using required does more
harm than good; they prefer to use only optional and repeated. However, this
view is not universal.
{quote}
Having done protobuf and thrift Objects and methods/services I completely agree
with this advice. Leave yourself the maximum flexibility and limit required
fields.
> SliceQueryFilter can accept multiple ColumnSlice but not exposed to thrift
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-6757
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6757
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Attachments: Cassandra-6757.1.diff
>
>
> Thrift has getSlice() which takes a key and a predicate. SliceQueryFilter can
> accept multiple ColumnSlice(s). Users should have access to this capability
> already found in Cassandra.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
