Re: CQL 3 Binary protocol spec mismatch

2013-08-15 Thread Mosfeq Rashid
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 O

Re: CQL 3 Binary protocol spec mismatch

2013-08-15 Thread Tyler Hobbs
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 wrote: > > Thanks for the quick response. > > This is what I am getting: > > ... > >

Re: CQL 3 Binary protocol spec mismatch

2013-08-14 Thread Mosfeq Rashid
Thanks for the quick response. This is what I am getting: ... 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

Re: CQL 3 Binary protocol spec mismatch

2013-08-14 Thread Tyler Hobbs
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 wrote: > > The response to the Select query is s

CQL 3 Binary protocol spec mismatch

2013-08-14 Thread Mosfeq Rashid
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