http://intellidzine.blogspot.in/2014/01/cassandra-data-modelling-primary-keys.html?m=1
Thanks
Anuj
Sent from Yahoo Mail on Android
From:"Anuj Wadehra"
Date:Thu, 19 Nov, 2015 at 5:31 pm
Subject:Re: Range scans
Hi Chandra,
I will comment on some points. Someone else can take rema
t:Range scans
Hi,
I would like to run a range scan on timestamp column b with secondary indexes
without passing the partition key. I'm aware that Cassandra does not support
range scans on secondary indexes unless one more column (primary/secondary
index) clause with an = operator is suppli
Thanks for both your help, greatly appreciated.
We'll proceed down the path of putting the filtering into the application
logic for the time being.
Matt.
On Tue, Jul 15, 2014 at 1:20 AM, DuyHai Doan wrote:
> Exact Ken, I get bitten again by the semantics of composite tuples.
>
> This kind of
Exact Ken, I get bitten again by the semantics of composite tuples.
This kind of query won't be possible until something like wide row end
slice predicate is available (
https://issues.apache.org/jira/browse/CASSANDRA-6167), if it will one day
On Mon, Jul 14, 2014 at 5:02 PM, Ken Hancock
wro
I don't think your query is doing what he wants. Your query will correctly
set the starting point, but will also return larger interval_id's but with
lower skill_levels:
cqlsh:test> select * from skill_count where skill='Complaints' and
(interval_id, skill_level) >= (140235930, 5);
skill
or :
select * from skill_count where skill='Complaints'
and (interval_id,skill_level) >= (140235930,5)
and (interval_id) < (140235990)
Strange enough, when starting using tuple notation you'll need to stick to
it even if there is only one element in the tuple
On Mon, Jul 14, 2014 at 1:4
Sorry, I've just checked, the correct query should be:
select * from skill_count where skill='Complaints' and
(interval_id,skill_level) >= (140235930,5) and
(interval_id,skill_level) < (140235990,11)
On Mon, Jul 14, 2014 at 9:45 AM, DuyHai Doan wrote:
> Hello Mathew
>
> Since Cassandr
Hello Mathew
Since Cassandra 2.0.6 it is possible to query over composites:
https://issues.apache.org/jira/browse/CASSANDRA-4851
For your example:
select * from skill_count where skill='Complaints' and
(interval_id,skill_level) >= (140235930,5) and interval_id <
140235990;
On Mon, Jul
Hi,
We have a roll-up table that as follows.
CREATE TABLE SKILL_COUNT (
skill text,
interval_id bigint,
skill_level int,
skill_count int,
PRIMARY KEY (skill, interval_id, skill_level));
Essentially,
skill = a names skill i.e. "Complaints"
interval_id = a rounded epoch time (15 minu
Hi Jon,
Thanks for quick reply, I'm a newbie to Cassandra. Even though I made a
mistake in previous mail. you got it right. I'll check what you've said.
Cheers,
Rajith.
On Fri, Oct 18, 2013 at 11:47 AM, Jonathan Haddad wrote:
> I'd avoid using super columns. I don't believe they're recommend
I'd avoid using super columns. I don't believe they're recommended
anymore, and with CQL3 they aren't even supported (if you're interested in
going that route). I think it's unlikely that you'll want a column family
per company either.
How many "ticker" entries do you plan on writing per company
Hi all,
I have a problem like this,
I have stock transaction data, as follows.
Ticker data:
Company name:
timestamp:
closing price (N): (V)
trades (N) : (V)
..
.
..
In my model : I want to execute ra
his way.
>
>
> On Sun, Aug 25, 2013 at 3:38 PM, John Sanda wrote:
>
>> How is conflict resolution done with range scans? I understand when
>> reading a single column, the latest timestamp wins. Is the timestamp for
>> each column compared with a range scan such that so
See that last part on this page:
http://wiki.apache.org/cassandra/ReadRepair
This doc is dated, but I'm pretty sure it still works this way.
On Sun, Aug 25, 2013 at 3:38 PM, John Sanda wrote:
> How is conflict resolution done with range scans? I understand when
> reading a single
How is conflict resolution done with range scans? I understand when reading
a single column, the latest timestamp wins. Is the timestamp for each
column compared with a range scan such that some columns in the result
could come from one replica while other columns come from another?
- John
See http://wiki.apache.org/cassandra/FAQ#range_ghosts
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 19/09/2011, at 9:11 PM, Radim Kolar wrote:
> Is there good reason why cassandra is returning empty rows (no columns) to
> clien
Is there good reason why cassandra is returning empty rows (no columns)
to client on rangeslicequery? (list command in CLI). They should be
hidden from user because it confuses applications.
They are not returned if get CLI command is used.
ocs: "Why do deleted keys show up during range scans?"
I am pretty sure how Cassandra works will make sense to you if you think
of it that way, that rows do not get deleted, columns get deleted.
While you can delete a row, if I understand correctly, what happens is a
tombstone is crea
gt; sure they go into SSTables etc the exact same way regular columns do.
>
> -Original Message-
> From: Jeremiah Jordan [mailto:jeremiah.jor...@morningstar.com]
> Sent: Tuesday, June 14, 2011 11:22 AM
> To: user@cassandra.apache.org
> Subject: RE: Docs: "Why do deleted
rdan [mailto:jeremiah.jor...@morningstar.com]
Sent: Tuesday, June 14, 2011 11:22 AM
To: user@cassandra.apache.org
Subject: RE: Docs: "Why do deleted keys show up during range scans?"
I am pretty sure how Cassandra works will make sense to you if you think
of it that way, that rows do not get deleted,
...@dude.podzone.net]
Sent: Monday, June 13, 2011 12:11 PM
To: user@cassandra.apache.org
Subject: Re: Docs: "Why do deleted keys show up during range scans?"
On 6/13/2011 10:14 AM, Stephen Connolly wrote:
>
> store the query inverted.
>
> that way empty -> deleted
>
I don&#
On 6/13/2011 10:14 AM, Stephen Connolly wrote:
store the query inverted.
that way empty -> deleted
I don't know what that means... get the other columns? Can you
elaborate? Is there docs for this or is this a hack/workaround?
the tombstones are stored for each column that had data IIRC.
On 13 June 2011 17:09, AJ wrote:
> On 6/13/2011 9:25 AM, Stephen Connolly wrote:
>>
>> On 13 June 2011 16:14, AJ wrote:
>>>
>>> On 6/13/2011 7:03 AM, Stephen Connolly wrote:
It returns the set of columns for the set of rows... how do you
determine the difference between a completel
On 6/13/2011 9:25 AM, Stephen Connolly wrote:
On 13 June 2011 16:14, AJ wrote:
On 6/13/2011 7:03 AM, Stephen Connolly wrote:
It returns the set of columns for the set of rows... how do you
determine the difference between a completely empty row and a row that
just does not have any of the matc
On 13 June 2011 16:14, AJ wrote:
> On 6/13/2011 7:03 AM, Stephen Connolly wrote:
>>
>> It returns the set of columns for the set of rows... how do you
>> determine the difference between a completely empty row and a row that
>> just does not have any of the matching columns?
>
> I would expect it
On 6/13/2011 7:03 AM, Stephen Connolly wrote:
It returns the set of columns for the set of rows... how do you
determine the difference between a completely empty row and a row that
just does not have any of the matching columns?
I would expect it to not return anything (no row at all) for both
It returns the set of columns for the set of rows... how do you
determine the difference between a completely empty row and a row that
just does not have any of the matching columns?
Well the answer is that Cassandra does not go and check whether there
are any columns outside of the range you are
http://wiki.apache.org/cassandra/FAQ#range_ghosts
"So to special case leaving out result entries for deletions, we would
have to check the entire rest of the row to make sure there is no
undeleted data anywhere else either (in which case leaving the key out
would be an error)."
The above doe
28 matches
Mail list logo
