ility, extremely low
>>> latency queries (on known access patterns), high volume/low latency writes,
>>> easy scalability, etc. then you are going to have to rethink how you model
>>> the data.
>>>
>>>
>>>
>>>
>>>
>>>
gt;> scalability, etc. then you are going to have to rethink how you model the
>> data.
>>
>>
>>
>>
>>
>> Sean Durity
>>
>>
>>
>> *From:* Kenneth Brotman
>> *Sent:* Thursday, February 07, 2019 7:01 AM
>> *To:* us
, easy
> scalability, etc. then you are going to have to rethink how you model the
> data.
>
>
>
>
>
> Sean Durity
>
>
>
> *From:* Kenneth Brotman
> *Sent:* Thursday, February 07, 2019 7:01 AM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] R
] RE: SASI queries- cqlsh vs java driver
Peter,
Sounds like you may need to use a different architecture. Perhaps you need
something like Presto or Kafka as a part of the solution. If the data from the
legacy system is wrong for Cassandra it’s an ETL problem? You’d have to
transform the data
that a proper data model
for Cassandra can be used.
From: Peter Heitman [mailto:pe...@heitman.us]
Sent: Wednesday, February 06, 2019 10:05 PM
To: user@cassandra.apache.org
Subject: Re: SASI queries- cqlsh vs java driver
Yes, I have read the material. The problem is that the application has a
ved=2ahUKEwi0n-nWzajgAhXnHzQIHf6jBJIQ6AEwAXoECAgQAQ#v=onepage&q=jeff%20carpenter%20chapter%205&f=false>
> .
>
>
>
> Kenneth Brotman
>
>
>
> *From:* Peter Heitman [mailto:pe...@heitman.us]
> *Sent:* Wednesday, February 06, 2019 6:33 PM
>
>
> *To:*
itman.us]
Sent: Wednesday, February 06, 2019 6:33 PM
To: user@cassandra.apache.org
Subject: Re: SASI queries- cqlsh vs java driver
Yes, I "know" that allow filtering is a sign of a (possibly fatal) inefficient
data model. I haven't figured out how to do it correctly yet
On Thu,
se ALLOW FILTERING in the queries. That is not recommended.
>
>
>
> Kenneth Brotman
>
>
>
> *From:* Peter Heitman [mailto:pe...@heitman.us]
> *Sent:* Wednesday, February 06, 2019 6:09 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: SASI queries- cqlsh vs java
seems like a lot.
Kenneth Brotman
From: Peter Heitman [mailto:pe...@heitman.us]
Sent: Tuesday, February 05, 2019 6:59 PM
To: user@cassandra.apache.org
Subject: Re: SASI queries- cqlsh vs java driver
The table and secondary indexes look generally like this. Note that I have
changed the nam
>
> Kenneth Brotman
>
>
>
> *From:* Peter Heitman [mailto:pe...@heitman.us]
> *Sent:* Tuesday, February 05, 2019 6:59 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: SASI queries- cqlsh vs java driver
>
>
>
> The table and secondary indexes look generally lik
PM
To: user@cassandra.apache.org
Subject: Re: SASI queries- cqlsh vs java driver
The table and secondary indexes look generally like this. Note that I have
changed the names of many of the columns to be generic since they aren't
important to the question as far as I know. I left the a
The table and secondary indexes look generally like this. Note that I have
changed the names of many of the columns to be generic since they aren't
important to the question as far as I know. I left the actual names for
those columns that I've created SASI indexes for. The query I use to try to
cre
Could you post full table schema (names obfuscated, if required) with index
creation statements and queries?
On Mon, Feb 4, 2019 at 10:04 AM Jacques-Henri Berthemet <
jacques-henri.berthe...@genesys.com> wrote:
> I’m not sure why it`s not allowed by the Datastax driver, but maybe you
> could try
I’m not sure why it`s not allowed by the Datastax driver, but maybe you could
try to use OR instead of IN?
SELECT blah FROM foo WHERE = :val1 OR = :val2
ALLOW FILTERING
It should be the same as IN query, but I don’t if it makes a difference for
performance.
From: Peter Heitman
Reply-To: "us
14 matches
Mail list logo
