Re: Accessing dynamic columns via cqlsh

a cassandra cluster from pre-cql era and I am having problems accessing data via cqlsh. As you can see below, I can not reach dynamic columns via cqlsh but they are accessible via cassandra-cli. How can I make the data shown on cqlsh? cqlsh:automation> sele

RE: Accessing dynamic columns via cqlsh

I do not think that cqlsh provides a way to get internal data. I hope I am wrong... -Original Message- From: Onur Yalazı [mailto:onur.yal...@8digits.com] Sent: Thursday, October 15, 2015 10:54 AM To: user@cassandra.apache.org Subject: Accessing dynamic columns via cqlsh Hello, I have a

Re: Accessing dynamic columns via cqlsh

ing problems > accessing data via cqlsh. > As you can see below, I can not reach dynamic columns via cqlsh but they > are accessible via cassandra-cli. > > How can I make the data shown on cqlsh? > > > cqlsh:automation> select * from "Ev

Accessing dynamic columns via cqlsh

Hello, I have a cassandra cluster from pre-cql era and I am having problems accessing data via cqlsh. As you can see below, I can not reach dynamic columns via cqlsh but they are accessible via cassandra-cli. How can I make the data shown on cqlsh? cqlsh:automation> select * f

Re: Thrift to cql : mixed static and dynamic columns with secondary index

Thanks for your answer Tyler. Unfortunately, I can't wait for 3.x to be released. I think I will update my schema to declare explicitely all columns with predictive names and I will migrate only the dynamic ones to a new table. This will reduce drastically the amount of data to migrate and I'll b

Re: Thrift to cql : mixed static and dynamic columns with secondary index

This schema is something that we're providing a better CQL conversion for in 3.0. The one column you defined will become a "static" column, meaning there is only one copy of it per partition. The schema will look something like this: CREATE TABLE ref_file ( key text, folder text static,

Thrift to cql : mixed static and dynamic columns with secondary index

Hi, I'm trying to migrate from Cassandra 1.1 and Hector to a more up-to-date stack like Cassandra 1.2+ and CQL3. I have read http://www.datastax.com/dev/blog/thrift-to-cql3

Re: Re: Dynamic Columns

be on > different nodes. Thankfully with composite keys, Cassandra will use the > first column as the partition key. > > In terms of adding dynamic_column_name as part of the composite key, that > isn't ideal in my use case for several reasons. > > 1. a record might not ha

Re: Re: Dynamic Columns

> Where we differ that I feel the coverage for existing thrift use cases isn't > 100%. That may be right or wrong, but it is my impression. Here's my problem: either CQL covers all existing thrift use cases or it does not (in which case the non supported use case should be pointed out). It's a tec

Re: Re: Dynamic Columns

des. Thankfully with composite keys, Cassandra will use the first column as the partition key. In terms of adding dynamic_column_name as part of the composite key, that isn't ideal in my use case for several reasons. 1. a record might not have any dynamic columns at all. The user decides this.

Re: Re: Dynamic Columns

er of clustering columns can be specified, so more structured "dynamic columns" can be supported. For example, you could have a timestamp as a separate clustering column to maintain temporal state of the database. The partition key can also be structured from multiple columns as a composite partit

Re: Re: Dynamic Columns

I've written my fair share of crappy code, which became legacy. then I or someone else was left with supporting it and something newer. Isn't that the nature of software development. I forget who said this quote first, but I'm gonna borrow it "only pretty code is code that is in your head. once it

Re: Re: Dynamic Columns

On Wed, Jan 21, 2015 at 2:09 PM, Peter Lin wrote: > on the topic of multiple incompatible API's I recommend you look at > SqlServer and Sybase. Most of the legacy RDBMS have multiple incompatible > API. Though in some cases, it is/was unavoidable. > My bet is that the small development team resp

Re: Re: Dynamic Columns

everyone is different. I also recommend users take time to understanding every tool they use as much as time allows. We don't always have the luxury of time, but I see no point recommending laziness. I'm probably insane, since I also spend time reading papers on CRDT, paxos, query compilers, machi

Re: Re: Dynamic Columns

I apologize if I've offended you, but I clearly stated CQL3 supports dynamic columns. How it supports dynamic columns is different. If I'm reading you correctly, I believe we agree both thrift and CQL3 support dynamic columns. Where we differ that I feel the coverage for existing thrift

Re: Re: Dynamic Columns

On Wed, Jan 21, 2015 at 9:19 AM, Peter Lin wrote: > > I consistently recommend new users learn and understand both Thrift and > CQL. > FWIW, I consider this a disservice to new users. New users should use CQL, and not deploy against a deprecated-in-all-but-name API. Understanding non-CQL *storag

Re: Re: Dynamic Columns

M, Sylvain Lebresne > wrote: > >> On Wed, Jan 21, 2015 at 4:44 PM, Peter Lin wrote: >> >>> I don't remember other people's examples in detail due to my shitty >>> memory, so I'd rather not misquote. >>> >> >> Fair enough, but maybe yo

Re: Re: Dynamic Columns

. Doing this type of stuff is basically transparent for me, since >> I'm using thrift and our data modeler generates helper classes. Our tooling >> seamlessly convert the bytes back to the target object. We have a few >> standard static columns related to temporal metadata. At an

Re: Re: Dynamic Columns

s argument then. Those examples might be wrong or outdated and that kind of stuff creates confusion for everyone. > > In my case, I mix static and dynamic columns in a single column family > with primitives and objects. The objects are temporal object graphs with a > known type. Doing th

Re: Re: Dynamic Columns

I don't remember other people's examples in detail due to my shitty memory, so I'd rather not misquote. In my case, I mix static and dynamic columns in a single column family with primitives and objects. The objects are temporal object graphs with a known type. Doing this t

Re: Re: Dynamic Columns

> I've chatted with several long time users of Cassandra and there's things > CQL3 doesn't support. > Would you care to elaborate then? Maybe a simple example of something (or multiple things since you used plural) in thrift that cannot be supported in CQL? And please note that I'm *not* saying th

Re: Re: Dynamic Columns

I've studied the source code and I don't believe that statement is true. I've chatted with several long time users of Cassandra and there's things CQL3 doesn't support. Like I've said before. Thrift and CQL3 compliment each other. I totally understand some committers don't want the overhead due to

Re: Re: Dynamic Columns

On Wed, Jan 21, 2015 at 3:46 AM, Peter Lin wrote: > > I don't understand why people [...] pretend it supports 100% of the use > cases. > Have you consider the possibly that it's actually true and you're just wrong by lack of knowledge? -- Sylvain

Re: Re: Dynamic Columns

0, 2015 at 9:46 PM, Peter Lin wrote: > > the thing is, CQL only handles some types of dynamic column use cases. > There's plenty of examples on datastax.com that shows how to do CQL style > dynamic columns. > > based on what was described by Chetan, I don't feel CQL3 is a

Re: Dynamic Columns

ow to do CQL style dynamic columns. based on what was described by Chetan, I don't feel CQL3 is a perfect fit for what he wants to do. To use CQL3, he'd have to change his approach. In my temporal database, I use both Thrift and CQL. They compliment each other very nice. I don't

Re: Re: Dynamic Columns

the thing is, CQL only handles some types of dynamic column use cases. There's plenty of examples on datastax.com that shows how to do CQL style dynamic columns. based on what was described by Chetan, I don't feel CQL3 is a perfect fit for what he wants to do. To use CQL3, he'd hav

Re:Re: Dynamic Columns

I approximate dynamic columns by data_key and data_value columns. Is there a better way to get dynamic columns in CQL 3? At 2015-01-21 09:41:02, "Peter Lin" wrote: I think that table example misses the point of chetan's functional requirement. he actually needs dynamic col

Re: Dynamic Columns

I think that table example misses the point of chetan's functional requirement. he actually needs dynamic columns. On Tue, Jan 20, 2015 at 8:12 PM, Xu Zhongxing wrote: > Maybe this is the closest thing to "dynamic columns" in CQL 3. > > create table reivew (

Re: Dynamic Columns

Maybe this is the closest thing to "dynamic columns" in CQL 3. create table reivew ( product_id bigint, created_at timestamp, data_key text, data_tvalue text, data_ivalue int, primary key ((priduct_id, created_at), data_key) ); data_tvalue and data_ivalue i

Re: Dynamic Columns

this challenge. The more details >> around your use case that you can provide, the easier it will be for this >> group to offer advice. >> >> A few follow-up questions: >> - How will you query this data? >> - Do your queries require filtering on specific

Re: Dynamic Columns

s > group to offer advice. > > A few follow-up questions: > - How will you query this data? > - Do your queries require filtering on specific columns other than > product_id and created_at, i.e. the dynamic columns? > > Depending on the answers to these questions, you have

Re: Dynamic Columns

other than product_id and created_at, i.e. the dynamic columns? Depending on the answers to these questions, you have several options, of which here are a few: - Cassandra efficiently stores sparse data, so you could create columns and not populate them, without much of a penalty - Could

Re: Dynamic Columns

reviews for a given product will reside on same node) and clustering key as created_at and id (Desc) so that reviews will be sorted by time. I can have more column and that requirement I want to fulfil by dynamic columns but there are limitations to it explained above. Could you please let me know

Re: Dynamic Columns

ustering key as created_at and id (Desc) so that reviews will be > sorted by time. > > I can have more column and that requirement I want to fulfil by dynamic > columns but there are limitations to it explained above. > Could you please let me know the best way. > > On Tue, J

Re: Dynamic Columns

com/+Datastax/about> <http://feeds.feedburner.com/datastax> <https://github.com/datastax/> On Tue, Jan 20, 2015 at 1:24 PM, chetan verma wrote: > Hi, > > I am starting a new project with cassandra as database. > I have unstructured data so I need dynamic columns, > though

Dynamic Columns

Hi, I am starting a new project with cassandra as database. I have unstructured data so I need dynamic columns, though in CQL3 we can achive this via Collections but there are some downsides to it. 1. Collections are used to store small amount of data. 2. The maximum size of an item in a

Re: are dynamic columns supported at all in CQL 3?

ug 27, 2014 at 11:31 AM, Deepak Shetty wrote: > " Using the post's example, consider the query of "get all readings for > sensor 1". With dynamic columns, the query is just "select * from data > where sensor_id=1". In CQL, not only does this take N differen

Re: are dynamic columns supported at all in CQL 3?

" Using the post's example, consider the query of "get all readings for sensor 1". With dynamic columns, the query is just "select * from data where sensor_id=1". In CQL, not only does this take N different queries (one per sample) but you have to explicitly know th

Re: are dynamic columns supported at all in CQL 3?

Unfortunately, no. I've read that and the solution presented only works in limited scenarios. Using the post's example, consider the query of "get all readings for sensor 1". With dynamic columns, the query is just "select * from data where sensor_id=1". In

Re: are dynamic columns supported at all in CQL 3?

On Tue, Aug 26, 2014 at 12:14 PM, Shane Hansen wrote: > Does this answer your question Ian? > http://www.datastax.com/dev/blog/does-cql-support-dynamic-columns-wide-rows > If dissembling can be considered to answer a question... "A common misunderstanding is that CQL does not s

Re: are dynamic columns supported at all in CQL 3?

Does this answer your question Ian? http://www.datastax.com/dev/blog/does-cql-support-dynamic-columns-wide-rows On Tue, Aug 26, 2014 at 1:12 PM, Ian Rose wrote: > Is it possible in CQL to create a table that supports dynamic column > names? I am using C* v2.0.9, which I assume impli

are dynamic columns supported at all in CQL 3?

Is it possible in CQL to create a table that supports dynamic column names? I am using C* v2.0.9, which I assume implies CQL version 3. This page appears to show that this was supported in CQL 2 with the 'with comparator' and 'with default_validation' options but that CQL 3 does not support this:

Re: Dynamic Columns in Cassandra 2.X

>>> For point 2) this is a small trade-off to have access to a query >>> language and being able to do slice queries using the WHERE clause. Some >>> like it, other hate it, it's just a question of taste. Please note that >>> the "waste" in disk space

Re: Dynamic Columns in Cassandra 2.X

note that the "waste" >> in disk space is somehow mitigated by compression. >> >> Long story short I think Thrift may have appropriate usage but only in very >> few use cases. Recently a lot of improvement and features have been added to >> CQL3 so that

Re: Dynamic Columns in Cassandra 2.X

on. >> >> Long story short I think Thrift may have appropriate usage but only in >> very few use cases. Recently a lot of improvement and features have been >> added to CQL3 so that it shoud be considered as the first choice for most >> users and if they fall into

Re: Dynamic Columns in Cassandra 2.X

mprovement and features have been > added to CQL3 so that it shoud be considered as the first choice for most > users and if they fall into those few use cases then switch back to Thrift > > My 2 cents > > > > > > > On Fri, Jun 13, 2014 at 11:43 PM, Peter Lin wro

Re: Dynamic Columns in Cassandra 2.X

hen switch back to Thrift > > My 2 cents > > > > > > > On Fri, Jun 13, 2014 at 11:43 PM, Peter Lin wrote: > > With text based query approach like CQL, you loose the type with dynamic > columns. Yes, we're storing it as bytes, but it is simpler

Re: Dynamic Columns in Cassandra 2.X

and features have been added to CQL3 so that it shoud be considered as the first choice for most users and if they fall into those few use cases then switch back to Thrift My 2 cents On Fri, Jun 13, 2014 at 11:43 PM, Peter Lin wrote: > > With text based query approach like CQL, yo

Re: Dynamic Columns in Cassandra 2.X

With text based query approach like CQL, you loose the type with dynamic columns. Yes, we're storing it as bytes, but it is simpler and easier with Thrift to do these types of things. I like CQL3 and what it does, but text based query languages make certain dynamic schema use cases pa

Re: Dynamic Columns in Cassandra 2.X

"the validation type is set to bytes, and my code is type safe, so it knows which serializers to use. Those dynamic columns are driven off the types in Java." --> Correct. However, you are still bound by the column comparator type which should be fixed (unless again you set it to b

Re: Dynamic Columns in Cassandra 2.X

the validation type is set to bytes, and my code is type safe, so it knows which serializers to use. Those dynamic columns are driven off the types in Java. Having said that, CQL3 does have a new custom type feature, but the documentation is basically non-existent on how that actually works. One

Re: Dynamic Columns in Cassandra 2.X

ne of the defined > datatypes. > > with thrift I use the appropriate serializer to handle these dynamic > columns. > > > On Fri, Jun 13, 2014 at 4:55 PM, DuyHai Doan wrote: > >> Well, before talking and discussing about "dynamic columns", we should >>

Re: Dynamic Columns in Cassandra 2.X

when I say dynamic column, I mean non-static columns of different types within the same row. Some could be an object or one of the defined datatypes. with thrift I use the appropriate serializer to handle these dynamic columns. On Fri, Jun 13, 2014 at 4:55 PM, DuyHai Doan wrote: > W

Re: Dynamic Columns in Cassandra 2.X

Well, before talking and discussing about "dynamic columns", we should first define it clearly. What do people mean by "dynamic columns" exactly ? Is it the ability to add many columns "of same type" to an existing physical row? If yes then CQL3 does support it wit

Re: Dynamic Columns in Cassandra 2.X

e others around a hybrid of CQL and Thrift (where necssary). But from a newb's perspective, I sense the community is unsettled around this concept of truly dynamic columns. Coming from an HBase background, it's a consideration I didn't anticipate having to evaluate. -- about.me <

Re: Dynamic Columns in Cassandra 2.X

> >>> This strikes me as bad practice in the world of multi tenant systems. I >>> don't want to create a table per customer. So I'm wondering if dynamically >>> modifying the table is an accepted practice? >>> >>> -- >>> about.me <

Re: Dynamic Columns in Cassandra 2.X

Like you, I make extensive use of dynamic columns for similar reasons. In our project, one of the goals is to give "end users" the ability to design their own schema without having to alter a table. If people really want strong schema, then just use old Sql or NewSql. RDB gives you the

Re: Dynamic Columns in Cassandra 2.X

multi tenant systems. I >> don't want to create a table per customer. So I'm wondering if dynamically >> modifying the table is an accepted practice? >> >> -- >> about.me <http://about.me/markgreene> >> >> >> On Fri, Jun 13, 2014 at 2

Re: Dynamic Columns in Cassandra 2.X

>> modifying the table is an accepted practice? >> >> -- >> about.me <http://about.me/markgreene> >> >> >> On Fri, Jun 13, 2014 at 2:54 PM, DuyHai Doan >> wrote: >> >>> Hello Mark >>> >>> Dynamic columns, as you

Re: Dynamic Columns in Cassandra 2.X

t.me <http://about.me/markgreene> > > > On Fri, Jun 13, 2014 at 2:54 PM, DuyHai Doan wrote: > >> Hello Mark >> >> Dynamic columns, as you said, are perfectly supported by CQL3 via >> clustering columns. And no, using collections for storing dynamic data is

Re: Dynamic Columns in Cassandra 2.X

On Fri, Jun 13, 2014 at 11:54 AM, DuyHai Doan wrote: > Dynamic columns, as you said, are perfectly supported by CQL3 via > clustering columns. > "Perfectly supported" seems a bit expansive as a claim. They are not quite the same thing as actual dynamic columns and are me

Re: Dynamic Columns in Cassandra 2.X

ifying the table is an accepted practice? -- about.me <http://about.me/markgreene> On Fri, Jun 13, 2014 at 2:54 PM, DuyHai Doan wrote: > Hello Mark > > Dynamic columns, as you said, are perfectly supported by CQL3 via > clustering columns. And no, using collections for stor

Re: Dynamic Columns in Cassandra 2.X

Hello Mark Dynamic columns, as you said, are perfectly supported by CQL3 via clustering columns. And no, using collections for storing dynamic data is a very bad idea if the cardinality is very high (>> 1000 elements) 1) Is using Thrift a valid approach in the era of CQL? --> Less

Dynamic Columns in Cassandra 2.X

I'm looking for some best practices w/r/t supporting arbitrary columns. It seems from the docs I've read around CQL that they are supported in some capacity via collections but you can't exceed 64K in size. For my requirements that would cause problems. So my questions are: 1) Is using Thrift a

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

wrote an more in-depth >> answer: >> http://www.datastax.com/dev/blog/does-cql-support-dynamic-columns-wide-rows >> >> On Thu, Jun 6, 2013 at 8:02 AM, Joe Greenawalt >> wrote: >> > Hi, >> > I'm having some problems figuring out how to append a

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

ing something of a FAQ, so I wrote an more in-depth > answer: > http://www.datastax.com/dev/blog/does-cql-support-dynamic-columns-wide-rows > > On Thu, Jun 6, 2013 at 8:02 AM, Joe Greenawalt > wrote: > > Hi, > > I'm having some problems figuring out how to append a dy

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

sandra Rule 2: ROWS CAN HAVE 2 BILLION COLUMNS > Collection Rule 1: DON'T STORE MORE THEN 100 THINGS IN A COLLECTION > > Why does are user confused? Its simple. > > > > > > > > > > On Thu, Jun 6, 2013 at 10:51 AM, Eric Stevens wrote: > >> CQL3 does

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

This is becoming something of a FAQ, so I wrote an more in-depth answer: http://www.datastax.com/dev/blog/does-cql-support-dynamic-columns-wide-rows On Thu, Jun 6, 2013 at 8:02 AM, Joe Greenawalt wrote: > Hi, > I'm having some problems figuring out how to append a dynamic column on

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

ule 2: ROWS CAN HAVE 2 BILLION COLUMNS Collection Rule 1: DON'T STORE MORE THEN 100 THINGS IN A COLLECTION Why does are user confused? Its simple. On Thu, Jun 6, 2013 at 10:51 AM, Eric Stevens wrote: > CQL3 does now support dynamic columns. For tags or metadata values you &g

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

> > CQL3 does now support dynamic columns. For tags or metadata values you > could use a Collection: > This should probably be clarified. A collection is a super useful tool, but it is *not* the same thing as a dynamic column. It has many advantages, but there is one huge disadvan

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

Hi, CQL3 does now support dynamic columns. For tags or metadata values you could use a Collection: http://www.datastax.com/dev/blog/cql3_collections For wide rows there's the enhanced primary keys, which I personally prefer over the composite columns of yore: http://www.datastax.com/dev

Re: Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

Dynamic columns are not supported in CQL3. We just had a discussion a day or two ago about this where Eric Stevens explained it. Please see this: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/CQL-3-returning-duplicate-keys-td7588181.html Regards, Shahab On Thu, Jun 6, 2013 at

Dynamic Columns Question Cassandra 1.2.5, Datastax Java Driver 1.0

Hi, I'm having some problems figuring out how to append a dynamic column on a column family using the datastax java driver 1.0 and CQL3 on Cassandra 1.2.5. Below is what i'm trying: *cqlsh:simplex> create table user (firstname text primary key, lastname text); cqlsh:simplex> insert into user (fir

Re: Performance impact of static vs dynamic columns and mixing the two in the same CF

ading of the docs the advantage is that the data will be validated > on write and that the various dev tools can deserialize into a human readable > form easily. Thats about it. > 2. Is there any impact to mixing static and dynamic columns in the same > column family? (Follow-up que

Performance impact of static vs dynamic columns and mixing the two in the same CF

Hi all, A question has come up in our team about the performance impact of static vs dynamic columns. We'd like to ask two questions: Quick background: We are using a custom app to write to Cassandra using Hector. Production is Solaris and pre-prod is generally Centos. We're curren

Re: Dynamic columns in a column family?

Yes. (Please keep these to the user list rather than dev.) On Fri, Jan 6, 2012 at 11:59 AM, Frank Yang wrote: > Hi everyone, > > I am wondering whether it is possible to not to define the column > metadata when creating a column family, but to specify the column when > client updates data, for e

Dynamic columns in a column family?

Hi everyone, I am wondering whether it is possible to not to define the column metadata when creating a column family, but to specify the column when client updates data, for example: CREATE COLUMN FAMILY products WITH default_validation_class= UTF8Type AND key_validation_class=UTF8Type AND compa