Thanks. Take 2 attached.
On Sat, Oct 16, 2010 at 3:37 PM, Wayne wrote:
> ERROR [pool-1-thread-64] 2010-10-16 20:27:55,396 Cassandra.java (line 1280)
> Internal error processing get_slice
> java.lang.AssertionError
> at
> org.apache.cassandra.service.ReadResponseResolver.resolve(ReadResponseR
Ah nice, even better, thanks!
On Sat, Oct 16, 2010 at 2:31 PM, Brandon Williams wrote:
> On Sat, Oct 16, 2010 at 3:55 PM, Eric Lee wrote:
>
>> I have this working now with the following:
>>
>> rows = LOAD 'cassandra://TwitterExample/User' using CassandraStorage();
>> *cols = FOREACH rows GENERA
On Sat, Oct 16, 2010 at 3:55 PM, Eric Lee wrote:
> I have this working now with the following:
>
> rows = LOAD 'cassandra://TwitterExample/User' using CassandraStorage();
> *cols = FOREACH rows GENERATE
> FLATTEN((bag{tuple(chararray,chararray)})$1);*
> users = FOREACH cols GENERATE $1;
>
> Not s
I have this working now with the following:
rows = LOAD 'cassandra://TwitterExample/User' using CassandraStorage();
*cols = FOREACH rows GENERATE FLATTEN((bag{tuple(chararray,chararray)})$1);*
users = FOREACH cols GENERATE $1;
Not sure if that operation with *cols *is correct or not, but it appea
ERROR [pool-1-thread-64] 2010-10-16 20:27:55,396 Cassandra.java (line 1280)
Internal error processing get_slice
java.lang.AssertionError
at
org.apache.cassandra.service.ReadResponseResolver.resolve(ReadResponseResolver.java:88)
at
org.apache.cassandra.service.ReadResponseResolver.resolve(Re
Frank,
Things are a bit clearer now. Think I had the wrong idea to start with.
The server side error means this cassandra node does not know about the
column family it was asked to read. I guess either the schema are out of sync
on the nodes or there is a bug. How did you add
Stack trace from cassandra log?
On Sat, Oct 16, 2010 at 6:50 AM, Wayne wrote:
> While doing a read I get a TApplicationException: Internal Error processing
> get_slice.
>
> On Fri, Oct 15, 2010 at 5:49 PM, Jonathan Ellis wrote:
>>
>> On Fri, Oct 15, 2010 at 2:21 PM, Wayne wrote:
>> > The optimi
> I have a query regarding the insert operation. The insert operation by
> default inserts an new row or updates an existing row. Is it possible to
> prevent an update but allow only inserts automatically ( especially when
> multiple clients are writing to cassandra)? I was wondering if there is
> 2. What we really want for small users is just a replicated data store with
> some caching. Each of our application instances would have all the data
> available to it. If one application instance goes down, the other nodes
> should continue to function just fine.
Sounds reasonable, but make
While doing a read I get a TApplicationException: Internal Error processing
get_slice.
On Fri, Oct 15, 2010 at 5:49 PM, Jonathan Ellis wrote:
> On Fri, Oct 15, 2010 at 2:21 PM, Wayne wrote:
> > The optimization definitely shaved off some time. Now it is running about
> 3x
> > CFSTATS reported t
10 matches
Mail list logo
