RE: auto_bootstrap=false broken?

[aeljami.ext]

I had problems with write_survey.
I opened a bug :  https://issues.apache.org/jira/browse/CASSANDRA-9934

De : horschi [mailto:hors...@gmail.com]
Envoyé : mardi 4 août 2015 15:20
À : user@cassandra.apache.org
Objet : Re: auto_bootstrap=false broken?

Hi Paulo,

thanks for your feedback, but I think this is not what I am looking for.

Starting with join_ring does not take any tokens in the ring. And the nodetool 
join afterwards will again do token-selection and data loading in one step.

I would like to separate these steps:
1. assign tokens
2. have the node in a joining state, so that I can copy in data
3. mark the node as ready


I just saw that perhaps write_survey could be misused for that.

Did anyone ever use write_survey for such a partial bootstrapping?
Do I have to worry about data-loss when using multiple write_survey nodes in 
one cluster?

kind regards,
Christian



On Tue, Aug 4, 2015 at 2:24 PM, Paulo Motta 
pauloricard...@gmail.commailto:pauloricard...@gmail.com wrote:
Hello Christian,
You may use the start-up parameter -Dcassandra.join_ring=false if you don't 
want the node to join the ring on startup. More about this parameter here: 
http://docs.datastax.com/en/cassandra/2.0/cassandra/tools/toolsCUtility_t.html

You can later join the ring via nodetool join command: 
http://docs.datastax.com/en/cassandra/2.0/cassandra/tools/toolsJoin.html
auto_bootstrap=false is typically used to bootstrap new datacenters or 
clusters, or nodes with data already on it before starting the process.
Cheers,
Paulo

2015-08-04 8:50 GMT-03:00 horschi hors...@gmail.commailto:hors...@gmail.com:
Hi everyone,

I'll just ask my question as provocative as possible ;-)

Isnt't auto_bootstrap=false broken the way it is currently implemented?

What currently happens:
New node starts with auto_bootstrap=false and it starts serving reads 
immediately without having any data.

Would the following be more correct:
- New node should stay in a joining state
- Operator loads data (e.g. using nodetool rebuild or putting in backupped 
files or whatever)
- Operator has to manually switch from joining into normal state using nodetool 
(only then it will start serving reads)

Wouldn't this behaviour more consistent?

kind regards,
Christian



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

RE: problem with write_survey

[aeljami.ext]

Do you see this log message?

logger.infohttp://logger.info(Startup complete, but write survey mode is 
active, not becoming an active ring member. Use JMX 
(StorageService-joinRing()) to finalize ring joining.);



ð  Yes !


Log : INFO [main] 2015-07-29 15:29:35,697 StorageService.java (line 853) 
Startup complete, but write survey mode is active, not becoming an active ring 
member. Use JMX (StorageService-joinRing()) to finalize ring joining.


De : Robert Coli [mailto:rc...@eventbrite.com]
Envoyé : mercredi 29 juillet 2015 21:03
À : user@cassandra.apache.org
Objet : Re: problem with write_survey

On Wed, Jul 29, 2015 at 8:04 AM, 
aeljami@orange.commailto:aeljami@orange.com wrote:
but the node allows read:

cqlsh select * from myTable  where id = 1745;

id   | fname | lname
--+---+---
1745 |  john | smith

This is unexpected. Does the node show up in eg nodetool ring? If so, you are 
probably failing to properly use write_survey.

Do you see this log message?

logger.infohttp://logger.info(Startup complete, but write survey mode is 
active, not becoming an active ring member. Use JMX 
(StorageService-joinRing()) to finalize ring joining.);

(Key 1745 exists on node with the the write survey = true)
Then, when attempting a transition a node from write survey to normal mode, the 
nodetool join invocation fails as the node is already joined.

Do you have any idea ?

Cassandra Version: 2.0.10

https://issues.apache.org/jira/browse/CASSANDRA-9740

Is fixed in most recent 2.0.x, 2.0.17.

=Rob


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

problem with write_survey

[aeljami.ext]

Hello,

I start a node with the write survey = true

-Dcassandra.write_survey=true

Log:

INFO [main] 2015-07-29 15:29:35,697 StorageService.java (line 853) Startup 
complete, but write survey mode is active, not becoming an active ring member. 
Use JMX (StorageService-joinRing()) to finalize ring joining.

but the node allows read:

cqlsh select * from myTable  where id = 1745;

id   | fname | lname
--+---+---
1745 |  john | smith

(Key 1745 exists on node with the the write survey = true)
Then, when attempting a transition a node from write survey to normal mode, the 
nodetool join invocation fails as the node is already joined.

Do you have any idea ?

Cassandra Version: 2.0.10



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

RE: Replication Factor Change

[aeljami.ext]

Hello,

If current CL = ONE, Be careful on production at the time of change replication 
factor, 3 nodes will be queried while data is being transformed ==> So data 
read errors!
De : Yulian Oifa [mailto:oifa.yul...@gmail.com]
Envoyé : jeudi 5 novembre 2015 16:02
À : user@cassandra.apache.org
Objet : Replication Factor Change

Hello to all.
I am planning to change replication factor from 1 to 3.
Will it cause data read errors in time of nodes repair?
Best regards
Yulian Oifa

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

RE: management and monitoring nodetool repair

[aeljami.ext]

Thx Carlos,

How can I get information on error during repair ?

Thx.
De : Carlos Alonso [mailto:i...@mrcalonso.com]
Envoyé : lundi 19 octobre 2015 11:09
À : user@cassandra.apache.org
Objet : Re: management and monitoring nodetool repair

So repair process has two phases:

First one is all about calculating Merkel trees and that comparing it with 
others. This phase can be monitored with nodetool compactionstats
Second one is about streaming files of data. That one can be monitored with 
nodetool netstats.

Hope it helps.
Cheers!

Carlos Alonso | Software Engineer | @calonso

On 16 October 2015 at 14:09, 
> wrote:
Hi,
I'm looking for a tool for management and monitoring of the status of nodetool 
repair.

Currently I am trying to test cassandra-reaper, but if you tested other tools 
thank you to share.

Thanks

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

management and monitoring nodetool repair

[aeljami.ext]

Hi,
I'm looking for a tool for management and monitoring of the status of nodetool 
repair.

Currently I am trying to test cassandra-reaper, but if you tested other tools 
thank you to share.

Thanks

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

cassandra-stress 2.1: Generating data

[aeljami.ext]

Hi,

I'm trying to insert data with Cassandra-stress into cluster C* with 6 nodes: 
node001006

The stress-tool is executed on a different machine (gen01) specifying one of 6 
nodes: tools/bin/cassandra-stress  user profile=cf.yml ops\(insert=1\) 
n=500 -mode thrift -node node001  -rate threads=50

My question : The data generation of data is done on  gen01 and then inserted 
on nodes Cassandra OR ALL (generation and insertion) is running on nodes 
Cassandra ?

Thanks.






_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete 
altere, deforme ou falsifie. Merci

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorization.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, France Telecom - Orange shall not be liable if this 
message was modified, changed or falsified.
Thank you.

Compaction And Write performance

[aeljami.ext]

Hi all,

Does compaction throughput impact write performance ?

Increasing the value of compaction_throughput_mb_per_sec can improve the insert 
data ? If yes, is it possible to explain to me the concept ?

Thanks.

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete 
altere, deforme ou falsifie. Merci

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorization.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, France Telecom - Orange shall not be liable if this 
message was modified, changed or falsified.
Thank you.

RE: Cassandra data modeling for a social network

[aeljami.ext]

Hello,

  > First, Is this data modeling correct for follow base (follower, 
following actions) social network?

For social network, I advise you to see Graph Databases, over Cassandra

Example : https://academy.datastax.com/resources/getting-started-graph-databases

De : Mohammad Kermani [mailto:98kerm...@gmail.com]
Envoyé : lundi 30 mai 2016 13:42
À : user@cassandra.apache.org
Objet : Cassandra data modeling for a social network

We are using Cassandra for our social network and we are designing/data 
modeling tables we need, it is confusing for us and we don't know how to design 
some tables and we have some little problems!

As we understood for every query we have to have different tables, and for 
example user A is following user C and B.

Now, in Cassandra we have a table that is posts_by_user:

user_id  |  post_id   |  text  |  created_on  |  deleted  |  view_count



likes_count  |  comments_count  |  user_full_name

And we have a table according to the followers of users, we insert the post's 
info to the table called user_timeline that when the follower users are 
visiting the first web page we get the post from database from user_timeline 
table.
And here is user_timeline table:

follower_id  |  post_id  | user_id (who posted)  |  likes_count  |



comments_count   |   location_name   |  user_full_name

First, Is this data modeling correct for follow base (follower, following 
actions) social network?

And now we want to count likes of a post, as you see we have number of likes in 
both tables(user_timeline, posts_by_user), and imagine one user has 1000 
followers then by each like action we have to update all 1000 rows in 
user_timeline and 1 row in posts_by_users; And this is not logical!
Then, my second question is How should it be? I mean how should like (favorite) 
table be?

Thank you
I wish I can get answer

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

Atomic Batch: Maintaining consistency between tables

[aeljami.ext]

Hello,

I read in the documentation DataStax :

"The coordinator node might also need to work hard to process a logged batch 
while maintaining consistency between tables"

It means that the coordinator send the mutations  to all replica nodes and 
waits for RF acknowledgements ? or only one node of set of replica ?

thx

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

RE: Modeling nested collection with C* 2.0

[aeljami.ext]

I need to query all columns by the userid.

For example: Select * from users where userid  = 123;

frozen UDT don’t exist in Cassandra 2.0 ☹

De : Jack Krupansky [mailto:jack.krupan...@gmail.com]
Envoyé : jeudi 28 janvier 2016 16:38
À : user@cassandra.apache.org
Objet : Re: Modeling nested collection with C* 2.0

Generally, you should use clustering columns to model nested structures, unless 
they really are simply list/map structures.

But, first, as with all data modeling in Cassandra, start by looking at how you 
intend to query the data. Do you need to query individual addresses, email 
addresses, streets, etc.? If so, separate rows for each address is a better way 
to go. On the flip side, if the full address is just a blob that you will 
interpret in the app, a frozen UDT or JSON blob is a reasonable way to go. In 
any case, tell us about your query needs first.

-- Jack Krupansky

On Thu, Jan 28, 2016 at 10:29 AM, Carlos Alonso 
> wrote:
Hi Ahmed,

I think modelling them as a map where you can 'label' your emails or addresses 
sounds like a good option.

More info here: 
https://docs.datastax.com/en/cql/3.1/cql/cql_using/use_map_t.html

Regards

Carlos Alonso | Software Engineer | @calonso

On 28 January 2016 at 13:36, Ryan Svihla 
> wrote:
Ahmed,

Just using text and serializing as Json is the easy way and a common approach.

However, this list is for Cassandra commiter discussion, please be so kind as 
to use the regular user list for data modeling questions or for any future 
responses to this email thread.


Regards,
Ryan Svihla

On Jan 28, 2016, at 7:28 AM, Ahmed Eljami 
> wrote:
​Hi,

I need your help for modeling a nested collection with cassanrda2.0 (UDT no,
no fozen)

My users table contains emails by type, each type of email contains multiple
emails.

Example:
Type: pro. emails: {a...@mail.com, 
b...@mail.com ...}

Type: private. emails: {c...@mail.com, 
d...@mail.com}
.

The user table also contains addresses, address type with fields.

Example:

Type: Pro. address {Street= aaa, number = 123, apartment = bbb}

Type: Private. address {Street = bbb, number = 123, apartment = kkk }

I am looking for a solution to store all these columns in one table.

Thank you.



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

RE: [C*2.1]memtable_allocation_type: offheap_objects

[aeljami.ext]

Thank you !

Another question please : In the blog post 
(http://www.datastax.com/dev/blog/off-heap-memtables-in-Cassandra-2-1), it is 
noted that offheap_objects it effective for small values like ints or uuids as 
well. offheap_buffers for the tables with string or blobs.

in my case, the tables contains many columns with string type. But in  
cassandra.yaml, it is noted that offheap_objects is: native memory, heap buffer 
nio Eliminating overhead.

I must in all cases use offheap_objects?

Thanks.
De : Jeff Jirsa [mailto:jeff.ji...@crowdstrike.com]
Envoyé : mercredi 9 mars 2016 17:13
À : user@cassandra.apache.org
Objet : Re: [C*2.1]memtable_allocation_type: offheap_objects

We use them. No signs of stability problems in 2.1 that we’ve attributed to 
offheap objects.


From: "aeljami@orange.com"
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, March 9, 2016 at 1:54 AM
To: user
Subject: [C*2.1]memtable_allocation_type: offheap_objects

Hi,

offheap_objects was removed in releases 3.2.x then reintroduced  in release 
3.4: I vould like to know if someone has used offheap_objects in Cassandra 2.1: 
stable or not, improvementobservedor not…

Thanks.
Ahmed


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

C*2.1 using timestamp with same timestamp

[aeljami.ext]

Hello,

I try to insert two lines for the same partition with the same timestamp. 
prmiere the line without TTL. the 2nd line with TTL.
As shown in the example below:

INSERT INTO tab1 (a,b) VALUES ('YYY','') USING TIMESTAMP 1460088862025940
INSERT INTO tab1 (a,b) VALUES ('YYY','') USING TIMESTAMP 1460088862025940 
AND TTL 1000

With C*2.0, when I select from the table, I get the row with the TTL (), 
therefore the second row

a| b | ttl(b) | writetime(b)
++-+---
YYY | | 999 |  1460088862025940

but with C*2.1 for the same insertions I get the row without TTL, therefore the 
first row.

a| b | ttl(b) | writetime(b)
++-+---
YYY | | null |  1460088862025940

I know it is related to the WriteTime except that I do not understand the 
difference between 2.0 and 2.1 in this case

Any idea ?

Thx.

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

[C*2.1]memtable_allocation_type: offheap_objects

[aeljami.ext]

Hi,

offheap_objects was removed in releases 3.2.x then reintroduced  in release 
3.4: I vould like to know if someone has used offheap_objects in Cassandra 2.1: 
stable or not, improvement observed or not...

Thanks.
Ahmed


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

RE: Migration from 2.0.10 to 2.1.12

[aeljami.ext]

full is a reserved word in apache Cassandra / cql 3.1

https://cassandra.apache.org/doc/cql3/CQL.html#appendixA

*Reserved keywords cannot be used as identifier , they are truly reserved for 
the language (but one can enclose a reserved keyword by double-quotes to use it 
as an identifier)

De : Jean Carlo [mailto:jean.jeancar...@gmail.com]
Envoyé : mercredi 30 mars 2016 16:08
À : user@cassandra.apache.org
Objet : Re: Migration from 2.0.10 to 2.1.12

@Laing thx for the info.
@Carlos I also check that page and I did not find it. I was asking to know if 
someone has done smth to avoid change the column name everytime cassandra adds 
new words to the list.



Saludos

Jean Carlo

"The best way to predict the future is to invent it" Alan Kay

On Wed, Mar 30, 2016 at 4:02 PM, Carlos Alonso 
> wrote:
Well...

I guess that if full is a reserved word there's nothing you can do to change 
that but then, checking which are the keywords for that version it turns out 
that full is not there!!
https://docs.datastax.com/en/cql/3.1/cql/cql_reference/keywords_r.html

Maybe a bug?

Regards

Carlos Alonso | Software Engineer | @calonso

On 30 March 2016 at 15:41, Jean Carlo 
> wrote:
Yes we did some reads and writes, the problem is that adding double quotes 
force us to modify our code to change and insert like that

INSERT INTO table1 (bill_id, full, name,provider_date ,total) values 
('qs','full','name','2015-02-23','toltal');
to this

INSERT INTO table1 (bill_id, "full", name,provider_date ,total) values 
('qs','full','name','2015-02-23','toltal');
this last one is ok, but obviously the first one makes an error:

cqlsh:pns_fr_2_jean> INSERT INTO table1 (bill_id, full, name,provider_date 
,total) values ('qs','full','name','2015-02-23','toltal');
SyntaxException: 
and it is because the name of the column is not longer full, is "full"


Best regards

Jean Carlo

"The best way to predict the future is to invent it" Alan Kay

On Wed, Mar 30, 2016 at 3:26 PM, Eric Evans 
> wrote:
On Wed, Mar 30, 2016 at 8:08 AM, Jean Carlo 
> wrote:
> With double quotes it doesn't show error
>
> CREATE TABLE table1 ( bill_id text, "full" text, name text,
> provider_date timestamp, total text, PRIMARY KEY ( bill_id) ) ;
>
> but it changes the name of the column

I don't think it does though; You're meant to be able to use the
output of DESC TABLE to (re)create these tables, so it's quoted below
for the same reason you did so above.

Obviously it would be better to have column names that parse without
needing to be double quoted, but it should work.  Have you tried some
reads and writes?

> desc table table1;
>
> CREATE TABLE pns_fr_2_jean.table1 (
> bill_id text PRIMARY KEY,
> "full" text,
> name text,
> provider_date timestamp,
> total text
> )
>
> instead of
>
> CREATE TABLE pns_fr_2_jean.table1 (
> bill_id text PRIMARY KEY,
> full text,
> name text,
> provider_date timestamp,
> total text
> )

--
Eric Evans
eev...@wikimedia.org




_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

[C* 2.1.14] Not enough bytes exception during compaction

[aeljami.ext]

Hi,

We recently got an exception during  compaction on some nodes (Cassandra 
2.1.14):

ERROR [CompactionExecutor:14065] 2016-12-30 14:45:07,245 
CassandraDaemon.java:229 - Exception in thread 
Thread[CompactionExecutor:14065,1,main]
java.lang.IllegalArgumentException: Not enough bytes. Offset: 5. Length: 20275. 
Buffer size: 12594
at 
org.apache.cassandra.db.composites.AbstractCType.checkRemaining(AbstractCType.java:378)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.composites.AbstractCompoundCellNameType.fromByteBuffer(AbstractCompoundCellNameType.java:100)
 ~[apache-cassandra-2.1.14.ja
r:2.1.14]
at 
org.apache.cassandra.db.composites.AbstractCType$Serializer.deserialize(AbstractCType.java:398)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.composites.AbstractCType$Serializer.deserialize(AbstractCType.java:382)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.OnDiskAtom$Serializer.deserializeFromSSTable(OnDiskAtom.java:75)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.AbstractCell$1.computeNext(AbstractCell.java:52) 
~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.AbstractCell$1.computeNext(AbstractCell.java:46) 
~[apache-cassandra-2.1.14.jar:2.1.14]
at 
com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
 ~[guava-16.0.jar:na]
at 
com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) 
~[guava-16.0.jar:na]
at 
org.apache.cassandra.io.sstable.SSTableIdentityIterator.hasNext(SSTableIdentityIterator.java:171)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.utils.MergeIterator$OneToOne.computeNext(MergeIterator.java:202)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
 ~[guava-16.0.jar:na]
at 
com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) 
~[guava-16.0.jar:na]
at 
com.google.common.collect.Iterators$7.computeNext(Iterators.java:645) 
~[guava-16.0.jar:na]
at 
com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
 ~[guava-16.0.jar:na]
at 
com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) 
~[guava-16.0.jar:na]
at 
org.apache.cassandra.db.ColumnIndex$Builder.buildForCompaction(ColumnIndex.java:166)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.compaction.LazilyCompactedRow.write(LazilyCompactedRow.java:121)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:193) 
~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.io.sstable.SSTableRewriter.append(SSTableRewriter.java:127)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:197)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) 
~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:73)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:59)
 ~[apache-cassandra-2.1.14.jar:2.1.14]
at 
org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:264)
 ~[apache-cassandra-2.1.14.jar:2
.1.14]

My colleague has already opened an issue 
(https://issues.apache.org/jira/browse/CASSANDRA-13087), it's also seems 
closely related to 
CASSANDRA-10961.

Can anyone has an idea about the reason for this exception ?

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.