So to summarize, yes, you can do that with CQL, but it's a little more
of a pain if your comparator is BytesType since you'll need to convert
to hex.
On Thu, Jul 28, 2011 at 9:48 AM, Ikeda Anthony
wrote:
> Thanks Jonathan,
>
> I just had one of our devs playing around with it and he said he had p
Thanks Jonathan,
I just had one of our devs playing around with it and he said he had problems
with some of the column names of which we delimit using a dash (-) using the
JDBC drivers e.g.
SELECT m--hash(value) FROM column_family…..
If this is not a problem then I have my questions answered.
You can quote CQL column names to allow any column name that Thrift
would allow (suitably encoded for ascii).
For instance, CQL knows that UUIDs are represented as strings like
12345678-1234-5678-1234-567812345678 and will parse them correctly.
If you mean the official CompositeType, that should
For our current project we have decided to use Hector as the client API,
however, with the introduction of CQL I need to understand a few things.
Firstly, CQL use SQL like constructs. Column names seem to be limited to the
same constraints of SQL (restricted use of delimiters) and yet the strength
