Ok, got it. Many thanks for your help.
Regards,
Rajeswari
From: Harikrishnan Pillai [mailto:hpil...@walmartlabs.com]
Sent: 02 February 2017 11:30
To: user@cassandra.apache.org
Subject: Re: Is it possible to have a column which can hold any data type (for
inserting as json)
When you run a cql
When you run a cql query like select Json from table where pk=? , you will get
the value which is a full Json .but if you have a requirement to query the Json
by using some fields inside Json ,you have to create additional columns for
that fields and create a secondary index on it .
Then you
Ok, got it. Many thanks for your help.
Regards,
Rajeswari
From: Benjamin Roth [mailto:benjamin.r...@jaumo.com]
Sent: 02 February 2017 11:09
To: user@cassandra.apache.org
Subject: RE: Is it possible to have a column which can hold any data type (for
inserting as json)
This has to be done in
This has to be done in your app. You can store your data as JSON in a text
column. You can use your favourite serializer. You can cast floats to
strings. You can even build a custom type. You can store it serialized as
blob. But there is no all purpose store all data in a magic way field.
Am
Sorry for the red color in my question. It happened by mistake.
Regards,
Rajeswari.
From: Rajeswari Menon
Sent: 02 February 2017 10:47
To: 'user@cassandra.apache.org'
Subject: RE: Is it possible to have a column which can hold any data type (for
inserting as json)
Could you please help me on
Could you please help me on this. I am a newbie in Cassandra. So If I need to
add json as a String, I can define the table as below.
create table data
(
id int primary key,
json text
);
The insert query will be as follows:
insert into data (id, json) values (1, '{
You can create additional columns and create secondary index based on fields
you want to query .
Best option is store full Json in Cassandra and index fields you want to query
on in solr .
Sent from my iPhone
On Feb 1, 2017, at 8:41 PM, Rajeswari Menon
Yes. I know that. My intension is to do an aggregate query on value field (in
json). Will that be possible if I store the entire json as String? I will have
to parse it according to my need right?
Regards,
Rajeswari
From: Harikrishnan Pillai [mailto:hpil...@walmartlabs.com]
Sent: 02 February
You can use text type in Cassandra and store the full Json string .
Sent from my iPhone
On Feb 1, 2017, at 8:30 PM, Rajeswari Menon
> wrote:
Yes. Is there any way to define value to accept any data type as the json value
data may
Yes. Is there any way to define value to accept any data type as the json value
data may vary? Or is there any way to do the same without defining a schema?
Regards,
Rajeswari
From: Benjamin Roth [mailto:benjamin.r...@jaumo.com]
Sent: 01 February 2017 15:36
To: user@cassandra.apache.org
Awsome to know this!
Thanks Jon and DuyHai!
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Love your data
rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
*linkedin.com/in/carlosjuzarterolo
Adding dev only for this thread.
On Wed, Feb 1, 2017 at 4:39 AM, Kant Kodali wrote:
> What is the difference between accepting a value and committing a value?
>
>
>
> On Wed, Feb 1, 2017 at 4:25 AM, Kant Kodali wrote:
>
>> Hi,
>>
>> Thanks for the
The optimization is there. The entire sstable can be dropped but it's not
because of the default TTL. The default TTL only applies if a TTL isn't
specified explicitly. The default TTL can't be used to drop a table
automatically since it can be overridden at insert time. Check out this
example.
I was referring to this JIRA
https://issues.apache.org/jira/browse/CASSANDRA-3974 when talking about
dropping entire SSTable at compaction time
But the JIRA is pretty old and it is very possible that the optimization is
no longer there
On Wed, Feb 1, 2017 at 6:53 PM, Jonathan Haddad
This is incorrect, there's no optimization used that references the table
level TTL setting. The max local deletion time is stored in table
metadata.
See org.apache.cassandra.io.sstable.metadata.StatsMetadata#maxLocalDeletionTime
in the Cassandra 3.0 branch.The default ttl is stored
here:
Example:
cqlsh> use dc_god_emperor ;
cqlsh:dc_god_emperor> create table data ( id int primary key, value text ) ;
cqlsh:dc_god_emperor> insert into data JSON'{"id": 1, "value": "hello
world"}'
... ;
cqlsh:dc_god_emperor> select * from data;
id | value
+-
1 |
Global TTL is better than dynamic runtime TTL
Why ?
Because Global TTL is a table property and Cassandra can perform
optimization when compacting.
For example if it can see than the maxTimestamp of an SSTable is older than
the table Global TTL, the SSTable can be entirely dropped during
Thank you all, for your answers.
On 02/01/2017 01:06 PM, Carlos Rolo wrote:
> To reinforce Alain statement:
>
> "I would say that the unsafe part is more about using C* 3.9" this is
> key. You would be better on 3.0.x unless you need features on the 3.x
> series.
>
> Regards,
>
> Carlos Juzarte
To reinforce Alain statement:
"I would say that the unsafe part is more about using C* 3.9" this is key.
You would be better on 3.0.x unless you need features on the 3.x series.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Love your
What is the difference between accepting a value and committing a value?
On Wed, Feb 1, 2017 at 4:25 AM, Kant Kodali wrote:
> Hi,
>
> Thanks for the response. I finished watching this video but I still got
> few questions.
>
> 1) The speaker seems to suggest that there are
Hi,
Thanks for the response. I finished watching this video but I still got few
questions.
1) The speaker seems to suggest that there are different consistency levels
being used in different phases of paxos protocol. If so, what is right
consistency level to set on these phases?
2) Right now,
Hi,
I believe that this talk from Christopher Batey at the Cassandra Summit
2016 might answer most of your questions around LWT:
https://www.youtube.com/watch?v=wcxQM3ZN20c
He explains a lot of stuff including consistency considerations. My
understanding is that the quorum read can only see the
Value is defined as text column and you try to insert a double. That's
simply not allowed
Am 01.02.2017 09:02 schrieb "Rajeswari Menon" :
> Given below is the sql query I executed.
>
>
>
> *insert* *into* data JSON'{
>
> "id": 1,
>
>"address":"",
>
>
When you initiate a LWT(write) and do a QUORUM read is there a chance that
one might not see the LWT write ? If so, can someone explain a bit more?
Thanks!
>
> Is it safe to use TWCS in C* 3.9?
I would say that the unsafe part is more about using C* 3.9 than using TWCS
in C*3.9 :-). I see no reason to say 3.9 would be specifically unsafe in
C*3.9, but I might be missing something.
Going from STCS to TWCS is often smooth, from LCS you might expect
Given below is the sql query I executed.
insert into data JSON'{
"id": 1,
"address":"",
"datatype":"DOUBLE",
"name":"Longitude",
"attributes":{
"ID":"1"
},
"category":"REAL",
"value":1.390692,
"timestamp":1485923271718,
"quality":"GOOD"
}';
Regards,
26 matches
Mail list logo