Auth
Sent: Tuesday, November 10, 2020 11:50 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Last stored value metadata table
Hi,
On Tue, Nov 10, 2020 at 5:29 PM Durity, Sean R
mailto:sean_r_dur...@homedepot.com>> wrote:
Updates do not create tombstones. Deletes create tombstone
Hi,
On Tue, Nov 10, 2020 at 6:29 PM Alex Ott wrote:
> What about using "per partition limit 1" on that table?
>
Oh, it is almost a good solution, but actually the key is ((epoch_day,
name), timestamp), to support more distributed partitioning, so... it is
not good... :/
--
Bye,
Auth Gábor (h
e`.
>
> Is there a Cassandra friendly solution to store the last value of every
> `name` in a separate metadata table? It will come with a lot of
> tombstones... any other solution? :)
>
> --
> Bye,
> Auth Gábor
>
--
With best wishes,Alex Ott
http://alexott.net/
Twitter: alexott_en (English), alexott (Russian)
Hi,
On Tue, Nov 10, 2020 at 5:29 PM Durity, Sean R
wrote:
> Updates do not create tombstones. Deletes create tombstones. The above
> scenario would not create any tombstones. For a full solution, though, I
> would probably suggest a TTL on the data so that old/unchanged data
> eventually gets re
Hi,
On Tue, Nov 10, 2020 at 3:18 PM Durity, Sean R
mailto:sean_r_dur...@homedepot.com>> wrote:
My answer would depend on how many “names” you expect. If it is a relatively
small and constrained list (under a few hundred thousand), I would start with
something like:
At the moment, the number o
Hi,
On Tue, Nov 10, 2020 at 3:18 PM Durity, Sean R
wrote:
> My answer would depend on how many “names” you expect. If it is a
> relatively small and constrained list (under a few hundred thousand), I
> would start with something like:
>
At the moment, the number of names is more than 10,000 but
are, I would look at something time-series
related with a short TTL.)
Sean Durity
From: Gábor Auth
Sent: Tuesday, November 10, 2020 2:39 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Last stored value metadata table
Hi,
Short story: storing time series of measurements (key(name
Hi,
Short story: storing time series of measurements (key(name, timestamp),
value).
The problem: get the list of the last `value` of every `name`.
Is there a Cassandra friendly solution to store the last value of every
`name` in a separate metadata table? It will come with a lot of
tombstones
, it’s possible a bad disk or bit flip could have corrupted
some of your data, but hard to say much beyond that.
--
Jeff Jirsa
> On May 30, 2018, at 3:42 PM, Charulata Sharma (charshar)
> wrote:
>
> Hi,
>
> I am observing a very strange behavior in our cluster. Metadata is
Hi,
I am observing a very strange behavior in our cluster. Metadata is being
prefixed in some rows.
This metadata cannot be sent by application primarily because application
writing to C* will not have this data,
and also applications use custom Java objects and this metadata doesn’t fall
Hey
Thanks for response, i accidently decommissioned the seed node which was
causing this.
I promoted another node as seed node and restartwd all nodes with new seed
nodes , follwed by full nodetool repair and cleanup and it fixed the issue.
On Thursday, May 17, 2018, kurt greaves wrote:
> Can
Can you post the stack trace and you're version of Cassandra?
On Fri., 18 May 2018, 09:48 Abdul Patel, wrote:
> Hi
>
> I had to decommission one dc , now while adding bacl the same nodes ( i
> used nodetool decommission) they both get added fine and i also see them im
> nodetool status but i am
Hi
I had to decommission one dc , now while adding bacl the same nodes ( i
used nodetool decommission) they both get added fine and i also see them im
nodetool status but i am unable to login in them .gives invalid mwtadat
error, i ran repair and later cleanup as well.
Any ideas?
-src-1 pre-scrub-1464981676212]$ java -jar
sstablemetadata.jar vt1-table_1-ka-12-Data.db | grep "timestamp"
Minimum timestamp: -9223372036854775808
Maximum timestamp: 146438090618
>From the sstablemetadata tool source code, I know that it parses only the
Statistics.db component to p
variable bound in this prepare statement.
- is defined exactly as but correspond to the
metadata for the resultSet that execute this query will yield. Note that
may be empty (have the No_metadata flag and 0
columns, See
section 4.2.5.2) and will be for any query that is not
On Wed, Jul 23, 2014 at 11:14 AM, Ben Hood <0x6e6...@gmail.com> wrote:
> But I was wondering if we were doing something wrong by not returning
> the result meta data from the PREPARE result (if it does indeed
> exist).
Looking into this a bit further, it looks like the client driver needs
to deser
Hi all,
I'm looking at the specification of statement preparation (section
4.2.5.4 of the CQL protocol) and I'm wondering whether the metadata
result of the PREPARE query only returns column information for the
query arguments, and not for the columns of the actual query result.
The
user@cassandra.apache.org
Subject: Re: Rollback question regarding system metadata change
On Tue, Oct 1, 2013 at 3:45 PM, Chris Wirt wrote:
Yep they still work. They dont acutally have any of the new system CF
created for 2.0, paxos, etc.. but they do have new rows in the
schema_columns table preventing st
actually happens is that you automatically create a snapshot in the
snapshots dir when you drop, so you would have to move (or (better) hard
link) those files back into place.
> - create schema (will create all the metadata and leave my data
> directories alone?)
> - on each node run nodeto
mess for a couple minutes while i recreate the
schema and load the sstables.
But anyway, actions to do this would be:
- drop schema (wont actually delete data?)
- create schema (will create all the metadata and leave my data
directories alone?)
- on each node run nodetool refresh (will load my exi
On Tue, Oct 1, 2013 at 10:51 AM, Christopher Wirt wrote:
> Moving back to 1.2.10. What is the procedure roll back from 2.0.1?
>
> ** **
>
> Changes in the system schema seem to make this quite difficult.
>
> ...
First, unfortunately downgrade is not, in my understanding, a supported
oper
Moving back to 1.2.10. What is the procedure roll back from 2.0.1?
Changes in the system schema seem to make this quite difficult.
We have:
DC1 - 10 x 1.2.10
DC2 - 4 x 1.2.10
DC3 - 3 x 2.0.1 -> ran this for a couple days and have decided to roll back
In my efforts I've now completel
Any points on the same.
- Rishabh
- Reply message -
From: "Rishabh Agrawal"
To: "user@cassandra.apache.org"
Subject: Accessing Metadata of Column Familes
Date: Mon, Jan 28, 2013 5:56 pm
I found following issues while working on Cassandra version 1.2, CQL 3 and
Thr
gt;
>
>
>
>
> From: Harshvardhan Ojha [mailto:harshvardhan.o...@makemytrip.com]
> Sent: Monday, January 28, 2013 12:57 PM
>
>
> To: user@cassandra.apache.org
> Subject: RE: Accessing Metadata of Column Familes
>
>
>
> You can get storage attributes fr
deemed as correct or consistent?
* How to access meta data on the same?
Thanks and Regards
Rishabh Agrawal
From: Harshvardhan Ojha [mailto:harshvardhan.o...@makemytrip.com]
Sent: Monday, January 28, 2013 12:57 PM
To: user@cassandra.apache.org
Subject: RE: Accessing Metadata of Column
You can get storage attributes from /data/system/ keyspace.
From: Rishabh Agrawal [mailto:rishabh.agra...@impetus.co.in]
Sent: Monday, January 28, 2013 12:42 PM
To: user@cassandra.apache.org
Subject: RE: Accessing Metadata of Column Familes
Thank for the reply.
I do not want to go by API route
amilyDefinition.
>
>
>
> Regards
>
> Harshvardhan OJha
>
>
>
> *From:* Rishabh Agrawal [mailto:rishabh.agra...@impetus.co.in]
> *Sent:* Monday, January 28, 2013 12:16 PM
> *To:* user@cassandra.apache.org
> *Subject:* Accessing Metadata of Column Familes
>
>
Metadata of Column Familes
Which API are you using?
If you are using Hector use ColumnFamilyDefinition.
Regards
Harshvardhan OJha
From: Rishabh Agrawal [mailto:rishabh.agra...@impetus.co.in]
Sent: Monday, January 28, 2013 12:16 PM
To: user@cassandra.apache.org
Subject: Accessing Metadata of Column
Which API are you using?
If you are using Hector use ColumnFamilyDefinition.
Regards
Harshvardhan OJha
From: Rishabh Agrawal [mailto:rishabh.agra...@impetus.co.in]
Sent: Monday, January 28, 2013 12:16 PM
To: user@cassandra.apache.org
Subject: Accessing Metadata of Column Familes
Hello,
I wish
Hello,
I wish to access metadata information on column families. How can I do it? Any
ideas?
Thanks and Regards
Rishabh Agrawal
NOTE: This message may contain information that is confidential, proprietary,
privileged or otherwise protected by law. The
>
> user ,
>
> cc
>
> Objet
>
> Need help in updating metadata of an existing column family
>
> Hi,
>
> I have an existing column family that is created with comparator
> BytesType. I want to add a built-in index to this column
Is it possible to update the column-metadata of a column family definition
programmatically? If yes, can someone please point me to the right classes
to use?
Thanks.
On Thu, Nov 29, 2012 at 3:58 PM, Roshan Dawrani wrote:
> Hi,
>
> I have an existing column family that is cre
s becomes significant.
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Wednesday, November 14, 2012 6:00 PM
> To: user@cassandra.apache.org
> Subject: Re: CF metadata syntax for an array
>
> database a hint that this will be an array?
> Things are going t
? While
for a small data set this would be no big deal. But for millions or billions
of orders this becomes significant.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Wednesday, November 14, 2012 6:00 PM
To: user@cassandra.apache.org
Subject: Re: CF metadata syntax for an array
lues this basically gives the
>> database a hint that this will be an array? Is there an implicit INDEX on id
>> and item_id? Thanks again.
>>
>> -Original Message-
>> From: aaron morton [mailto:aa...@thelastpickle.com]
>> Sent: Wednesday, November 14, 2012
: user@cassandra.apache.org
> Subject: Re: CF metadata syntax for an array
>
> Like this?
>
> cqlsh:dev> CREATE TABLE my_orders(
>... id int,
>... item_id int,
>... price decimal,
>... title text,
>... PRIMARY
[mailto:aa...@thelastpickle.com]
Sent: Wednesday, November 14, 2012 4:08 PM
To: user@cassandra.apache.org
Subject: Re: CF metadata syntax for an array
Like this?
cqlsh:dev> CREATE TABLE my_orders(
... id int,
... item_id int,
... price deci
> 2 $8.00 “This is another example”
> 3 $6.00 “This is the last example”
>
> So in this case the array would be the three items listed above. So the
> “column” is repeated three times for this order.
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Wednesda
.@thelastpickle.com]
Sent: Wednesday, November 14, 2012 3:05 PM
To: user@cassandra.apache.org
Subject: Re: CF metadata syntax for an array
In both cases the array is the PRIMARY_KEY.
I'm not sure what you mean by the "array"
The vector_name and list_name columns are used
list_name text
> ….
>
> In both cases the array is the PRIMARY_KEY. In order for an array to work
> does the array have to be a KEY?
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Tuesday, November 13, 2012 10:18 PM
> To:
2012 10:18 PM
To: user@cassandra.apache.org
Subject: Re: CF metadata syntax for an array
Would this syntax be the same for CREATE COLUMNFAMILY (as an aside what is a
'TABLE' in Cassandra)?
Yes, CQL 2 uses COLUMN FAMILY or Table and CQL 3 uses TABLE
http://www.datastax.com/dev/blog/
list_name text
> ….
>
> Does the array have to be a KEY? Finally, what would be the syntax for
> inserting data into the CF?
>
> Thanks again.
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent
ron morton [mailto:aa...@thelastpickle.com]
Sent: Tuesday, November 13, 2012 4:09 AM
To: user@cassandra.apache.org
Subject: Re: CF metadata syntax for an array
While this solves the problem for an array of 'primitive' types. What if I
want an array or collection of an arbitrary type like
://www.thelastpickle.com
>>
>> On 12/11/2012, at 8:35 PM, Kevin Burton wrote:
>>
>>> I am sorry if this is an FAQ. But I was wondering what the syntax for
>>> describing an array? I have gotten as far as feeling a need to understand a
>>> ‘super-column’ but I fail after that. Once I have the metadata in place to
>>> describe an array how do I insert data into the array? Get data from the
>>> array? Thank you.
>>>
>>
ng a need to understand a
>> ‘super-column’ but I fail after that. Once I have the metadata in place to
>> describe an array how do I insert data into the array? Get data from the
>> array? Thank you.
>
PM, Kevin Burton wrote:
> I am sorry if this is an FAQ. But I was wondering what the syntax for
> describing an array? I have gotten as far as feeling a need to understand a
> ‘super-column’ but I fail after that. Once I have the metadata in place to
> describe an array how do I i
I am sorry if this is an FAQ. But I was wondering what the syntax for
describing an array? I have gotten as far as feeling a need to understand a
'super-column' but I fail after that. Once I have the metadata in place to
describe an array how do I insert data into the array? Get dat
> Bloom filter is stored in RAM, but what about metadata?
> Is disk seek required to access it?
No, it's loaded in RAM when the sstable is loaded.
--
Sylvain
Setting the metadata will set the validation. If you insert to a
column that is supposed to only INT values Cassandra will reject non
INT data on insert time.
Also comparator can not be changed, you only get once chance to set
the column sorting.
On Tue, Aug 28, 2012 at 3:34 PM, A J wrote
For static column family what is the advantage in pre-defining column metadata ?
I can see ease of understanding type of values that the CF contains
and that clients will reject incompatible insertion.
But are there any major advantages in terms of performance or
something else that makes it
gt; bloom filter and may have an index of columns. This is not cached.
>
> See http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/ or
> http://www.slideshare.net/aaronmorton/cassandra-sf-2012-technical-deep-dive-query-performance
>
>> and Metadata?
>
> This is
2-technical-deep-dive-query-performance
>
> and Metadata?
>
> This is the meta data we hold in memory for every open sstable
>
> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/SSTableMetadata.java
>
> Cheers
>
>
> ---
012-technical-deep-dive-query-performance
> and Metadata?
This is the meta data we hold in memory for every open sstable
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/SSTableMetadata.java
Cheers
-
Aaron Morton
Freelance Dev
Hi all,
bloom filter for row keys is always in RAM. What about SSTable index, and
Metadata?
Is it cached by Cassandra, or it relays on memory mapped files?
Thanks,
Maciej
Hi all,
older Cassandra versions had to read columns from each SSTable with
positive bloom filter in order to find recent value.
This was optimized with: Improve read performance in update-intensive
workload <https://issues.apache.org/jira/browse/CASSANDRA-2498>
Now each SSTable has me
When you set comparator = LexicalUUIDType, you're saying that column names
are UUIDs. In your column metadata, you need to use a UUID for column_name
if that's what you want.
I suspect that you either don't want LexicalUUIDType for your column names
or you're looking for defa
Hi,
I have a columnfamily like that:
CREATE COLUMN FAMILY Clients
WITH key_validation_class = 'CompositeType(LexicalUUIDType,UTF8Type)'
AND comparator = LexicalUUIDType
AND column_metadata = [
{column_name: name, validation_class: UTF8Type}
];
My metadata
rsion of the
> schema on a new node? Is there a reason to apply the migrations?
>
> - Mike
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Tuesday, March 06, 2012 4:14 AM
> To: user@cassandra.apache.org
> Subject: Re: Secondary indexes don't go away afte
on of the schema on a
new node? Is there a reason to apply the migrations?
- Mike
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Tuesday, March 06, 2012 4:14 AM
To: user@cassandra.apache.org
Subject: Re: Secondary indexes don't go away after metadata change
When the new node co
elastpickle.com]
> Sent: Monday, March 05, 2012 3:58 AM
> To: user@cassandra.apache.org
> Subject: Re: Secondary indexes don't go away after metadata change
>
> The secondary index CF's are marked as no longer required / marked as
> compacted. under 1.x they would then be delet
2012 3:58 AM
To: user@cassandra.apache.org
Subject: Re: Secondary indexes don't go away after metadata change
The secondary index CF's are marked as no longer required / marked as
compacted. under 1.x they would then be deleted reasonably quickly, and
definitely deleted after a restart
The secondary index CF's are marked as no longer required / marked as
compacted. under 1.x they would then be deleted reasonably quickly, and
definitely deleted after a restart.
Is there a zero length .Compacted file there ?
> Also, when adding a new node to the ring the new node will build i
I have a few column families that I decided to get rid of the secondary indexes
on. I see that there aren't any new index SSTables being created, but all of
the old ones remain (some from as far back as September). Is it safe to just
delete then when the node is offline? Should I run clean-up
Hi,
I tried the assume and column metadata's column name still not right. I think
CLI shouldn't use comparator type to convert the column meta string. It should
all use UTF8 to convert column name metadata.
Regards,
Arsene
-Original Message-
From: Brandon Williams [
On Mon, Nov 7, 2011 at 7:36 PM, Arsene Lee
wrote:
> Hi,
>
> Thanks for the replay. I'm not talking about the column name. I'm talking
> about the column metadata's column name. Right now cli can't not display the
> column's meta name correctly if the comparator type is not UTF8.
Try 'help assum
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Friday, November 04, 2011 11:09 PM
To: user
Subject: Re: Using Cli to create a column family with column name metadata
question
[Moving to user@]
Because Cassandra's sparse data model supports using rows as "materialized
views,"
Hi,
I'm trying to use Column Family's metadata to do some validation. I found out
that in Cassandra's CLI CliClient.java code when trying to create a column
family with column name metadata. It is based on CF's comparator type to
convert the name String to ByteBuffer. I
[Moving to user@]
Because Cassandra's sparse data model supports using rows as
"materialized views," having non-UTF8 column names is common and
totally valid.
On Fri, Nov 4, 2011 at 5:19 AM, Arsene Lee
wrote:
> Hi,
>
> I'm trying to use Column Family's metad
Then you'll want to create an issue:
https://issues.apache.org/jira/browse/CASSANDRA
On Fri, Sep 2, 2011 at 10:08 AM, Radim Kolar wrote:
>> Is this 0.8.4?
> yes
>
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://w
> Is this 0.8.4?
yes
Is this 0.8.4?
2011/9/2 Radim Kolar :
> I cant find way how to remove all columns definitions without CF
> import/export.
>
> [default@int4] update column family sipdb with column_metadata = [];
> Syntax error at position 51: required (...)+ loop did not match anything at
> input ']'
>
> [default@
I cant find way how to remove all columns definitions without CF
import/export.
[default@int4] update column family sipdb with column_metadata = [];
Syntax error at position 51: required (...)+ loop did not match anything
at input ']'
[default@int4] update column family sipdb with column_meta
rote:
>
>> Dear all,
>>
>> I'm wondering what's the advantage of assigning column metadata when NOT
>> using secondary indices.
>>
>> I've gone through the SSTable internal and found out it won't do such
>> conversion.Thus I think the only advantage we got via column metadata is
>> a data validation type, am I correct?
>>
>> Thanks.
>> Steve
>
rmation it feels a
little like additional coupling that's not needed .
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 6 Aug 2011, at 11:58, Yi Yang wrote:
> Dear all,
>
> I'm wondering what's the adva
Dear all,
I'm wondering what's the advantage of assigning column metadata when NOT using
secondary indices.
I've gone through the SSTable internal and found out it won't do such
conversion.Thus I think the only advantage we got via column metadata is a
data validatio
If I wish to find name of all the keys in all the column families
along with other related metadata (such as last updated, size of
column value field), is there an additional solution that caches this
metadata OR do I have to always perform range queries and get the
information ?
I am not
Eventually, but I think this requires moving to
partitioner-per-columnfamily which as discussed before is a ton of
work.
On Fri, Oct 29, 2010 at 7:07 AM, Jim Ancona wrote:
> In 0.7, Cassandra now supports column metadata
> CfDef.default_validation_class and ColumnDef.validation_class. Is
&
On Fri, Oct 29, 2010 at 10:07 AM, Jim Ancona wrote:
> In 0.7, Cassandra now supports column metadata
> CfDef.default_validation_class and ColumnDef.validation_class. Is
> there any plan to provide similar metadata for keys, at the key space
> or column family level?
Sorry to respo
In 0.7, Cassandra now supports column metadata
CfDef.default_validation_class and ColumnDef.validation_class. Is
there any plan to provide similar metadata for keys, at the key space
or column family level?
Jim
79 matches
Mail list logo
