We're still using a fork unfortunately. Jeremy is referencing the on in
trunk as far as I know though. Here we're waiting for when we switch
from our weird version of hbase (0.89somethingsomething) to 0.90 to make
the switch.
--jacob
On Thu, 2011-03-24 at 15:10 -0700, Dmitriy Ryaboy wrote:
> That
That's a good point about HBaseStorage not using the caster. I don't use it
in prod so forgot to put it in.
Jacob, are you guys using a fork or are you back on the official loader
version?
On Thu, Mar 24, 2011 at 12:03 PM, Jeremy Hanna
wrote:
> Hmmm, that never calls the bytesToLong method even w
Hmmm, that never calls the bytesToLong method even with that specified in the
schema. I wonder if it's that when using a Cassandra validator on a column,
Cassandra tries its best to make the best guess about the value's type which
may not be compatible with the pig basic types (in this case Cas
Hmm. I bet I know what the issue is. It's not fun though. I'm thinking
that loadcaster probably isn't even called unless you explicitly name
the types at in the schema declaration.
Try loading with:
rows = load 'cassandra://MyKeyspace/MyColumnFamily' using
CassandraStorage() as (key:chararray, co
I see that there are a few LoadCaster implementations in pig 0.8. There's the
Utf8StorageConverter, the HBaseBinaryConverter, and a couple of others.
The HBaseStorage class uses the Utf8StorageConverter by default but can be
configured to use the HBaseBinaryConverter. Also it's just used as a
