y, September 30, 2010 4:38am
To: user@cassandra.apache.org
Subject: Re: LongType from user input
I just read through the tickets on Jira, and it appears that indices are
implemented in the 0.7 source tree, but I cannot find any pointer on how to
use them. I'll be trying to create a custom Ca
r"
> Sent: Thursday, September 30, 2010 4:38am
> To: user@cassandra.apache.org
> Subject: Re: LongType from user input
>
> I just read through the tickets on Jira, and it appears that indices are
> implemented in the 0.7 source tree, but I cannot find any pointer on how to
&g
Take a look at the get_indexed_slices method in the 0.7.0-beta Thrift interface.
-Original Message-
From: "Christian Decker"
Sent: Thursday, September 30, 2010 4:38am
To: user@cassandra.apache.org
Subject: Re: LongType from user input
I just read through the tickets on Ji
BTW is there an official Roadmap which states when the 0.7 release is to be
expected?
On Thu, Sep 30, 2010 at 11:38 AM, Christian Decker <
decker.christ...@gmail.com> wrote:
> I just read through the tickets on Jira, and it appears that indices are
> implemented in the 0.7 source tree, but I cann
I just read through the tickets on Jira, and it appears that indices are
implemented in the 0.7 source tree, but I cannot find any pointer on how to
use them. I'll be trying to create a custom CassandraStorage that loads data
through the indices, anyone else interested?
Regards,
Chris
On Thu, Sep
AFAIK indexes are still in dev. The only example is in the system_tests.py in
the source tree.
Aaron
On 30 Sep 2010, at 20:10, Christian Decker wrote:
> Apparently I have blanked the 0.7 completely out of my memory. I was trying
> to implement application layer indices and ignored the fact th
Apparently I have blanked the 0.7 completely out of my memory. I was trying
to implement application layer indices and ignored the fact that Cassandra
0.7 is implementing them by default. I found ticket CASSANDRA-749 about the
indices and am reading through the code right now, but is there a higher
The only thing I can think of is that values need to be in the correct byte format when used in indexes in 0.7. Take a look at the types.py module in the pycassa client http://github.com/pycassa/pycassa for an example of which values need to be byte packed. How is your pig function working against
Hi Aaron,
what changes can I expect in the 0.7 release regarding Comparison and
Parameters? My problem is mainly that I want to take Strings from stdin (or
Pig Scripts for that matter) and convert them in such a way that they are
interpreted correctly and converted to the corresponding byte repres
Things a changing in v0.7, the row keys are byte arrays.
Not sure I understand your other concerns.
Aaron
On 25 Sep 2010, at 08:10, Christian Decker wrote:
> Thanks for your quick answer, I think I'll use an affix to sort of cast the
> keys, ranges and others from their textual representatio
Thanks for your quick answer, I think I'll use an affix to sort of cast the
keys, ranges and others from their textual representation (from Pig) to the
desired byte representation, since I just noticed that the keys for the rows
themselfs are always UTF8 interpreted, and since I want to make key-ra
Yes, you can use describe_keyspace() and then look through the results.
It's a little ugly in 0.6, but it works.
- Tyler
On Fri, Sep 24, 2010 at 11:25 AM, Christian Decker <
decker.christ...@gmail.com> wrote:
> Well I'm writing a loading function for Pig, and as it happens I want to be
> able to
Well I'm writing a loading function for Pig, and as it happens I want to be
able to load slices from cassandra which are specified in the pig script
(thus the input from stdin) but the ColumnFamily from which to read the data
is another parameter and some of the CFs have UTF8, UUID, TimeUUID or Lon
I'm not sure I understand why using this with multiple column families
prevents you from converting it. Could you clarify this?
On Fri, Sep 24, 2010 at 10:56 AM, Christian Decker <
decker.christ...@gmail.com> wrote:
> Hi all,
>
> I'm having quite a dilemma with the CompareWith attribute. The Pro
14 matches
Mail list logo
