Through CQL, you see the logical schema. Through CLI, you see the physical schema.
This may help: http://www.datastax.com/dev/blog/cql3-for-cassandra-experts -brian On Mon, Jan 28, 2013 at 7:26 AM, Rishabh Agrawal <rishabh.agra...@impetus.co.in> wrote: > I found following issues while working on Cassandra version 1.2, CQL 3 and > Thrift protocol 19.35.0. > > > > Case 1: > > Using CQL I created a table t1 with columns col1 and col2 with col1 being my > primary key. > > > > When I access same data using CLI, I see col1 gets adopted as rowkey and > col2 being another column. Now I have inserted value in another column > (col3) in same row using CLI. Now when I query same table again from CQL I > am unable to find col3. > > > > Case 2: > > > > Using CLI, I have created table t2. Now I added a row key row1 and two > columns (keys) col1 and col2 with some values in each. When I access t2 > from CQL I find following resultset with three columns: > > > > key | column1 | value > > row1| col1 | val1 > > row1| col2 | val2 > > > > > > This behavior raises certain questions: > > > > · What is the reason for such schema anomaly or is this a problem? > > · Which schema should be deemed as correct or consistent? > > · How to access meta data on the same? > > > > > > Thanks and Regards > > Rishabh Agrawal > > > > > > From: Harshvardhan Ojha [mailto:harshvardhan.o...@makemytrip.com] > Sent: Monday, January 28, 2013 12:57 PM > > > To: user@cassandra.apache.org > Subject: RE: Accessing Metadata of Column Familes > > > > You can get storage attributes from /data/system/ keyspace. > > > > From: Rishabh Agrawal [mailto:rishabh.agra...@impetus.co.in] > Sent: Monday, January 28, 2013 12:42 PM > To: user@cassandra.apache.org > Subject: RE: Accessing Metadata of Column Familes > > > > Thank for the reply. > > > > I do not want to go by API route. I wish to access files and column families > which store meta data information > > > > From: Harshvardhan Ojha [mailto:harshvardhan.o...@makemytrip.com] > Sent: Monday, January 28, 2013 12:25 PM > To: user@cassandra.apache.org > Subject: RE: Accessing Metadata of Column Familes > > > > Which API are you using? > > If you are using Hector use ColumnFamilyDefinition. > > > > Regards > > Harshvardhan OJha > > > > From: Rishabh Agrawal [mailto:rishabh.agra...@impetus.co.in] > Sent: Monday, January 28, 2013 12:16 PM > To: user@cassandra.apache.org > Subject: Accessing Metadata of Column Familes > > > > Hello, > > > > I wish to access metadata information on column families. How can I do it? > Any ideas? > > > > Thanks and Regards > > Rishabh Agrawal > > > > > > ________________________________ > > > > > > > > NOTE: This message may contain information that is confidential, > proprietary, privileged or otherwise protected by law. The message is > intended solely for the named addressee. If received in error, please > destroy and notify the sender. Any use of this email is prohibited when > received in error. Impetus does not represent, warrant and/or guarantee, > that the integrity of this communication has been maintained nor that the > communication is free of errors, virus, interception or interference. > > The contents of this email, including the attachments, are PRIVILEGED AND > CONFIDENTIAL to the intended recipient at the email address to which it has > been addressed. If you receive it in error, please notify the sender > immediately by return email and then permanently delete it from your system. > The unauthorized use, distribution, copying or alteration of this email, > including the attachments, is strictly forbidden. Please note that neither > MakeMyTrip nor the sender accepts any responsibility for viruses and it is > your responsibility to scan the email and attachments (if any). No contracts > may be concluded on behalf of MakeMyTrip by means of email communications. > > > > ________________________________ > > > > > > > > NOTE: This message may contain information that is confidential, > proprietary, privileged or otherwise protected by law. The message is > intended solely for the named addressee. If received in error, please > destroy and notify the sender. Any use of this email is prohibited when > received in error. Impetus does not represent, warrant and/or guarantee, > that the integrity of this communication has been maintained nor that the > communication is free of errors, virus, interception or interference. > > The contents of this email, including the attachments, are PRIVILEGED AND > CONFIDENTIAL to the intended recipient at the email address to which it has > been addressed. If you receive it in error, please notify the sender > immediately by return email and then permanently delete it from your system. > The unauthorized use, distribution, copying or alteration of this email, > including the attachments, is strictly forbidden. Please note that neither > MakeMyTrip nor the sender accepts any responsibility for viruses and it is > your responsibility to scan the email and attachments (if any). No contracts > may be concluded on behalf of MakeMyTrip by means of email communications. > > > ________________________________ > > > > > > > NOTE: This message may contain information that is confidential, > proprietary, privileged or otherwise protected by law. The message is > intended solely for the named addressee. If received in error, please > destroy and notify the sender. Any use of this email is prohibited when > received in error. Impetus does not represent, warrant and/or guarantee, > that the integrity of this communication has been maintained nor that the > communication is free of errors, virus, interception or interference. -- Brian ONeill Lead Architect, Health Market Science (http://healthmarketscience.com) mobile:215.588.6024 blog: http://brianoneill.blogspot.com/ twitter: @boneill42
