I don't know if an IN query already does this without source diving,
but it could certainly do so without needing extra syntax.
On Wed, Mar 12, 2014 at 7:16 PM, Nicolas Favre-Felix wrote:
>> If any new use cases
>> come to light that can be done with Thrift but not CQL, we will commit
>> to suppo
> If any new use cases
> come to light that can be done with Thrift but not CQL, we will commit
> to supporting those in CQL.
Hello,
(going back to the original topic...)
I just wanted to point out that there is in my opinion an important
use case that is doable in Thrift but not in CQL, which i
I am glad the project has is adoptimg unambigious language of their
position. It is nice to have the clarity that volunteer efforts to add
features to thrift will be rejected.
This is a shining example of how a volunteer apache software foundation
project should be run. if users are attempting to
On Wed, Mar 12, 2014 at 1:38 PM, Edward Capriolo wrote:
> ", I don't know of any use cases for Thrift that can't be
> > done in CQL"
>
> Can dynamic composites be used from CQL?
>
Sure, you can use any AbstractType Class you want as type in CQL the same
way you
would do it with the thrift API.
-
", I don't know of any use cases for Thrift that can't be
> done in CQL"
Can dynamic composites be used from CQL?
On Wed, Mar 12, 2014 at 4:44 AM, Sylvain Lebresne wrote:
> +1 to Jonathan's proposal.
>
>
> On Tue, Mar 11, 2014 at 6:00 PM, Jonathan Ellis wrote:
>
> > CQL3 is almost two years ol
+1 to Jonathan's proposal.
On Tue, Mar 11, 2014 at 6:00 PM, Jonathan Ellis wrote:
> CQL3 is almost two years old now and has proved to be the better API
> that Cassandra needed. CQL drivers have caught up with and passed the
> Thrift ones in terms of features, performance, and usability. CQL
