The problem was that utf8 representation of the string was confusing emacs buffer for some reason by nicely removing the metadata part at the correct place. Emacs is really nice, isn't it! It became obvious once I tried to look at the binary. Thanks for providing the clue.
Yes, I am writing a ODM client for node.js. By the way, where is is type information for the clustering column stored. The type information all the other columns are available in system.schema_columnfamilies and system.columns. I sure it is somewhere, because DESCIBE shows it. Thanks. -- Mosfeq At Thu, 15 Aug 2013 10:43:38 -0500, Tyler Hobbs <ty...@datastax.com> wrote: > > [1 <text/plain; ISO-8859-1 (7bit)>] > Can you also describe the query you're running and paste the actual entire > binary response (from the header to the end)? > > By the way, are you writing a new client? > > > On Wed, Aug 14, 2013 at 6:37 PM, Mosfeq Rashid <mosfeq-cassan...@madrose.net > > wrote: > > > > > Thanks for the quick response. > > > > This is what I am getting: > > > > <row-count><value-col1-len><value-col1><value-col2-len><value-col2><value-col1-len><value-col1>... > > > > As you see, there is no metadata before the row-count. > > > > All the others messages I have tried like create, error, etc. are sending > > response as expected in the spec. > > > > By I am running Ubuntu 13.04 and the binary distribution. > > > > -- > > Mosfeq > > > > At Wed, 14 Aug 2013 18:09:39 -0500, > > Tyler Hobbs <ty...@datastax.com> wrote: > > > > > > Can you provide more details on exactly what's being returned? As far > > as I > > > know, ResultMessages of type "ROWS" should always start with metadata, > > and > > > I haven't seen a case where it's missing in 1.2. > > > > > > > > > On Wed, Aug 14, 2013 at 6:05 PM, Mosfeq Rashid < > > mosfeq-cassan...@madrose.net > > > > wrote: > > > > > > > > > > > The response to the Select query is supposed to have metadata before > > row > > > > data is provided. But in case of C* 1.2.5 and 1.2.8, I only get the > > row > > > > data. As far as I understand binary protocol, the message should have > > all > > > > the data to parse it. Does anyone know what I am missing? > > > > > > > > -- > > > > Mosfeq > > > > > > > > > > > > > > > > > -- > > > Tyler Hobbs > > > DataStax <http://datastax.com/> > > > > > > -- > Tyler Hobbs > DataStax <http://datastax.com/>
