I am interested in building a Go client to query the phoenix query
server using protocol buffers.
The query server is running on http://localhost:8765, so I tried POSTing
to localhost:8765 with the marshalled protocol buffer as the body.
Unfortunately, the server responds with:
We have designed a few tables where our application does the construction of
the composite row key and derive it as a Primary key field before writing to
Phoenix. Given that Phoenix uses a null byte character as a separator for the
row key construction, we went with the same separator in our
Our only public APIs are JDBC and our various integrations with Spark, MR,
etc. Though it's unlikely these APIs will change as Sergey mentioned, it's
possible. The actual binary format won't change, though (at least for
existing tables).
Thanks,
James
On Wed, Mar 23, 2016 at 1:05 PM, Sergey
Mohammad,
Honestly speaking, I'm not sure. Possible other guys have a definitive
answer. All I can say is that this API didn't change for last 1.5
years.
Thanks,
Sergey
On Wed, Mar 23, 2016 at 1:07 AM, Mohammad Adnan Raza
wrote:
> Thank you Sergey for quick response. I was
Hey Nick, at least as far as PHOENIX-2607 is concerned, traveling back in time
to insert data is the fundamental cause of the issue; that is, even after we
insert the correct data in cache, we ignore whats in the cache next time
around, and start rebuilding every time. This is by design and