Re: Is it possible to have a column which can hold any data type (for inserting as json)

2017-01-31 Thread Benjamin Roth
You should post the whole CQL query you try to execute! Why don't you use a native JSON type for your JSON data? 2017-02-01 7:51 GMT+01:00 Rajeswari Menon : > Hi, > > > > I have a json data as shown below. > > > > { > >

Is it possible to have a column which can hold any data type (for inserting as json)

2017-01-31 Thread Rajeswari Menon
Hi, I have a json data as shown below. { "address":"127.0.0.1", "datatype":"DOUBLE", "name":"Longitude", "attributes":{ "Id":"1"

Re: Global TTL vs Insert TTL

2017-01-31 Thread Cogumelos Maravilha
Hi Alain, Thanks for your response and the links. I've also checked "Time series data model and tombstones". Is it safe to use TWCS in C* 3.9? Thanks in advance. On 31-01-2017 11:27, Alain RODRIGUEZ wrote: > > Is there a overhead using line by line option or wasted disk space? > > There

Re: [External] Re: Cassandra ad hoc search options

2017-01-31 Thread Justin Cameron
+1 On Tue, 31 Jan 2017 at 10:04 Jonathan Haddad wrote: > With regards to having DCs for specific workloads, it would be nice to > have per DC indexes. See > https://issues.apache.org/jira/browse/CASSANDRA-12663. > > On Tue, Jan 31, 2017 at 9:52 AM Justin Cameron

Re: [External] Re: Cassandra ad hoc search options

2017-01-31 Thread Jonathan Haddad
With regards to having DCs for specific workloads, it would be nice to have per DC indexes. See https://issues.apache.org/jira/browse/CASSANDRA-12663. On Tue, Jan 31, 2017 at 9:52 AM Justin Cameron wrote: > Lucene/Elassandra and Spark serve different purposes. > >

Re: [External] Re: Cassandra ad hoc search options

2017-01-31 Thread Justin Cameron
Lucene/Elassandra and Spark serve different purposes. Lucene & Elassandra are designed for real-time queries that have predicates on columns not in the Cassandra primary key (i.e. searches). For example if you have a "person" table with person_id as the primary key but you want to allow users of

Re: Global TTL vs Insert TTL

2017-01-31 Thread Alain RODRIGUEZ
> > Is there a overhead using line by line option or wasted disk space? > > There is a very recent topic about that in the mailing list, look for "Time series data model and tombstones". I believe DuyHai answer your question there with more details :). *tl;dr:* Yes, if you know the TTL in

Global TTL vs Insert TTL

2017-01-31 Thread Cogumelos Maravilha
Hi I'm just wondering what option is fastest: Global:***create table xxx (.|AND |**|default_time_to_live = |**|XXX|**|;|**||and**UPDATE xxx USING TTL XXX;* Line by line: *INSERT INTO xxx (...USING TTL xxx;* Is there a overhead using line by line option or wasted disk

Re: [External] Re: Cassandra ad hoc search options

2017-01-31 Thread vincent gromakowski
You can also have a look at https://github.com/strapdata/elassandra 2017-01-31 9:50 GMT+01:00 vincent gromakowski : > The problem with adhoc queries on casssandra (with spark or not) is the > partition model of cassandra that needs to be respected to avoid full

Re: [External] Re: Cassandra ad hoc search options

2017-01-31 Thread vincent gromakowski
The problem with adhoc queries on casssandra (with spark or not) is the partition model of cassandra that needs to be respected to avoid full scan queries (the link you mentioned explains all of them). With FiloDB, which works on cassandra, you can pushdown predicates of the partition key and