RE: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread aeljami.ext
: 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

Re: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Jean Carlo
@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 We

Re: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Carlos Alonso
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 |

Re: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Laing, Michael
fyi the list of reserved keywords is at: https://cassandra.apache.org/doc/cql3/CQL.html#appendixA ml On Wed, Mar 30, 2016 at 9:41 AM, 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 > >

Re: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Jean Carlo
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"*,

Re: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Eric Evans
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 thi

Re: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Jean Carlo
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 desc table table1; CREATE TABLE pns_fr_2_jean.table1 ( bill_id text

Re: Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Carlos Alonso
Try surrounding it with quotes. Didn't know about the reserved keyword full though. Regards Carlos Alonso | Software Engineer | @calonso On 30 March 2016 at 10:36, Jean Carlo wrote: > Hi! > > I am creating my new tables on cassandra 2.1.12 and I have this one > >

Migration from 2.0.10 to 2.1.12

2016-03-30 Thread Jean Carlo
Hi! I am creating my new tables on cassandra 2.1.12 and I have this one CREATE TABLE table1 ( bill_id text, full text, name text, provider_date timestamp, total text, PRIMARY KEY ( bill_id) ) And cassandra tells me this error SyntaxException: Is the word "full" reserve