On Thu, Oct 24, 2013 at 4:58 PM, Jayadev Jayaraman wrote:
> Or do queries return only the columns with the most recent timestamp for
> each name regardless? (I would guess at the latter but I wanted to make
> sure)
>
This.
=Rob
Thanks for the reply. I have one more question. If multiple columns with
identical names but with different timestamps are bulk loaded (with
sstableloader) into a CF, and we had LCS running in the background, would a
slice predicate query retrieve multiple columns with the same name assuming
compac
Before CASSANDRA-1337 [1] (Cassandra 2.1 line) secondary indexes + vnodes
can have very slow performance due to the potentially large number of
splits/nodes sequentially scanned.
=Rob
[1] https://issues.apache.org/jira/browse/CASSANDRA-1337
On 24.10.2013, at 22:00, Petter von Dolwitz (Hem)
wrote:
> I have defined the secondary index on a field that is part of the primary
> key. This should be ok. Maybe you missed the CREATE INDEX bit in my original
> post.
Yes I did - despite actually looking for it :-) Sorry.
Then I am curiou
On Thu, Oct 24, 2013 at 3:13 PM, rash aroskar wrote:
> I have a column family created with strategy of leveled compaction. If I
> execute nodetool compact command, will the columnfamily be compacted using
> size tiered compaction strategy?
>
No.
> If yes, after the major size tiered compaction
Hi,
I have a column family created with strategy of leveled compaction. If I
execute nodetool compact command, will the columnfamily be compacted using
size tiered compaction strategy?
If yes, after the major size tiered compaction finishes will it at any
point trigger leveled compaction back on th
I have defined the secondary index on a field that is part of the primary
key. This should be ok. Maybe you missed the CREATE INDEX bit in my
original post. I might end up not using secondary indexes but since the
feature is there and I need the functionality I would like to know its
limitations an
On 24.10.2013, at 15:13, Petter von Dolwitz (Hem)
wrote:
> >You cannot use a part in a where clause unless you specify the preceeding
> >parts also.
> But the statement SELECT * FROM mytable WHERE c='myvalue'; works?
>
> What are secondary indexes for then if you can't use them in this way?
The key is this line:
Read 827 live and 6948 tombstoned cells
That means you either have a lot of deleted or TTLed columns in that row.
One option to help with that is to set a lower gc_grace for the table and
repair more frequently; this will help tombstones get purged more quickly.
Another opt
>You cannot use a part in a where clause unless you specify the preceeding
parts also.
But the statement SELECT * FROM mytable WHERE c='myvalue'; works?
What are secondary indexes for then if you can't use them in this way?
Forgot to mention that I am on Cassandra 2.0.1
/Petter
2013/10/24 Jan
Petter,
On 24.10.2013, at 14:38, Petter von Dolwitz (Hem)
wrote:
> Hi,
>
> I have a table that (in simplified version) looks like this:
>
> CREATE TABLE mytable (
> a varchar,
> b varchar,
> c varchar
> d timstamp,
> e varchar,
> PRIMARY KEY (a, b, c, d)
> );
>
> CREATE INDEX myt
Hi,
I have a table that (in simplified version) looks like this:
CREATE TABLE mytable (
a varchar,
b varchar,
c varchar
d timstamp,
e varchar,
PRIMARY KEY (a, b, c, d)
);
CREATE INDEX mytable_c_idx ON mytable ( c );
After populating I execute:
SELECT * FROM mytable WHERE c='myvalue
On 23 October 2013 21:25, Aaron Morton wrote:
> Is there ever a time when the pending count is non zero but nodetool
> compactionstats does not show any running tasks ?
No - but there are times when the number of running compaction
processes is less than concurrent_compactors, which is confusing.
Hello aaron,
I hope you had a nice flight.
>Any information on how you are using cassandra, does the zero columns no
row delete idea sound like something you are doing ?
I do not know what I could do, but we use an old versions of phpcassa
(0.8.a.2) that are not explictly compatible with cassand
Yes it's included under commit 639c01a3504b
--
Cyril SCETBON
On 23 Oct 2013, at 19:33, Janne Jalkanen wrote:
>
> Question - is https://issues.apache.org/jira/browse/CASSANDRA-6102 in 1.2.11
> or not? CHANGES.txt says it's not, JIRA says it is.
>
> /Janne (temporarily unable to check out the
Hi,
I'm very new with and trying out cassandra. I have couple of question
regarding the design of the database.
We have an API to store time series sensor data in millisecond precision.
user can do CRUD operation through the Restful API. When user retrieve
data, by default they can specify `start
Hi,
In my new project, I want to create a wide row CF with indexes in CQL3.
In my project, users can store multipurpose data and backed to Cassandra.
For example, my Profile CF has some user-defined properties as wide row.
And users can add indexes on columns which they want.
Of cource, we can c
17 matches
Mail list logo
