On Sun 03 Feb 2013 07:36:58 AM CST, Paul van Hoven wrote:
I've got a table that has a column called date. I created an index on
the column date with the following command:
CREATE INDEX date_key ON ola (date);
Now, I can perform the following command:
select * from ola where date = '2013-01-01'
On Sun 03 Feb 2013 05:45:56 AM CST, Daning Wang wrote:
I'd like to upgrade from 1.1.6 to 1.2.1, one big feature in 1.2 is
that it can have multiple tokens in one node. but there is only one
token in 1.1.6.
how can I upgrade to 1.2.1 then breaking the token to take advantage
of this feature? I we
Thanks for the answer. If I understand that correctly I had to do the
following to repair my query:
cqlsh:demodb> select * from ola where date < '2013-01-01' and date =
'2013-01-01' limit 10;
Bad Request: datum cannot be restricted by more than one relation if
it includes an Equal
Perhaps you mean
Hi Aaron,
Thanks for your answers. That helped me get a big picture.
Yes, it contains a big row that goes up to 2GB with more than a million of
columns.
Let me confirm if I correctly understand.
- The stack trace is from Slice By Names query. And the deserialization is
at the step 3, "Read the
On Sun 03 Feb 2013 08:19:08 PM CST, Paul van Hoven wrote:
Thanks for the answer. If I understand that correctly I had to do the
following to repair my query:
cqlsh:demodb> select * from ola where date < '2013-01-01' and date =
'2013-01-01' limit 10;
Bad Request: datum cannot be restricted by mor
After figuring out how to use the ">" operator on an secondary index I
noticed that in a column family of about 5.5 million datasets I get a
rpc_timeout when trying to read data from this table. In the concrete
situation I want to request data younger than January 1 2013. The
number of rows that sh
It is interesting the press c* got about having 2 billion columns in a
row. You *can* do it but it brings to light some realities of what
that means.
On Sun, Feb 3, 2013 at 8:09 AM, Takenori Sato wrote:
> Hi Aaron,
>
> Thanks for your answers. That helped me get a big picture.
>
> Yes, it contain
Without seeing your schema it is hard to say, but in some cases "ALLOW
FILTERING" might be considered "EXPECT THIS COULD BE SLOW". It could
mean the query is not hitting and index and is going to page through
large amounts of data.
On Sun, Feb 3, 2013 at 9:42 AM, Paul van Hoven
wrote:
> After fig
Okay, here is the schema (actually it is in german, but I translated
the column names such that it is easier to read for an international
audience):
cqlsh:demodb> describe table offerten_log_archiv;
CREATE TABLE offerten_log_archiv (
offerte_id int PRIMARY KEY,
aktionen int,
angezeigt bigin
Secondary indexes need at least one equality. If you want to do this
at scale you might need a different design.
Using WITH FILTERING and LIMIT 10 is simply grabbing the first few
random rows that match your criteria.
When you have GB or TB of data any query that adds "WITH FILTERING"
will not wo
I'm not sure if I understood your answer.
> When you have GB or TB of data any query that adds "WITH FILTERING"
> will not work at scale.
1. You mean any query that requires "with filtering" is slow?
> Secondary indexes need at least one equality. If you want to do this
> at scale you might need
This was the issue that prompted the "WITH FILTERING ALLOWED":
https://issues.apache.org/jira/browse/CASSANDRA-4915
Cassandra's storage system can only optimize certain queries.
On Sun, Feb 3, 2013 at 2:07 PM, Paul van Hoven
wrote:
> I'm not sure if I understood your answer.
>
>> When you have
Thanks for the answer. Can anybody else answer my other two questions,
because my problem is not solved yet?
2013/2/3 Edward Capriolo :
> This was the issue that prompted the "WITH FILTERING ALLOWED":
>
> https://issues.apache.org/jira/browse/CASSANDRA-4915
>
> Cassandra's storage system can only
On Mon 04 Feb 2013 04:42:12 AM CST, Paul van Hoven wrote:
Thanks for the answer. Can anybody else answer my other two questions,
because my problem is not solved yet?
2013/2/3 Edward Capriolo :
This was the issue that prompted the "WITH FILTERING ALLOWED":
https://issues.apache.org/jira/browse
If querying by a date inequality is an important access paradigm you
probably want a column that represents some time bucket (a month?) And
have that column be part of the cql primary key. Thus when a query is
requested you can make c* happy by specifying a date bucket to pick the
c* row and th
15 matches
Mail list logo
