https://issues.apache.org/jira/browse/CASSANDRA-12654
On Thu, Oct 27, 2016 at 9:59 PM, Ali Akhtar wrote:
> I have the following table schema:
>
> *CREATE TABLE ticket_by_member (*
> * project_id text,*
> * member_id text,*
> * ticket_id text,*
> * ticket ticket,*
> *
I have the following table schema:
*CREATE TABLE ticket_by_member (*
* project_id text,*
* member_id text,*
* ticket_id text,*
* ticket ticket,*
*assigned_members list,*
* votes list,*
*labels list,*
* PRIMARY KEY ( project_id, member_id, ticket_id )*
*);*
I have
please see CASSANDRA-12654
On Sat, Oct 22, 2016 at 3:12 AM, DuyHai Doan wrote:
> So the commit on this restriction dates back to 2.2.0 (CASSANDRA-7981).
>
> Maybe Benjamin Lerer can shed some light on it.
>
> On Fri, Oct 21, 2016 at 11:05 PM, Jeff Carpenter <
>
So the commit on this restriction dates back to 2.2.0 (CASSANDRA-7981).
Maybe Benjamin Lerer can shed some light on it.
On Fri, Oct 21, 2016 at 11:05 PM, Jeff Carpenter <
jeff.carpen...@choicehotels.com> wrote:
> Hello
>
> Consider the following schema:
>
> CREATE TABLE rates_by_code (
>
Hello
Consider the following schema:
CREATE TABLE rates_by_code (
hotel_id text,
rate_code text,
rates set,
description text,
PRIMARY KEY ((hotel_id), rate_code)
);
When executing the query:
select rates from rates_by_code where hotel_id='AZ123' and rate_code IN ('ABC',
'DEF',