Thanks! This has solved the problem!
On Wed, Mar 24, 2010 at 5:50 PM, gabriele renzi wrote:
> On Wed, Mar 24, 2010 at 3:36 PM, Oleg Mürk wrote:
> > Hi Jonathan,
> >
> > On Wed, Mar 24, 2010 at 4:32 PM, Jonathan Ellis
> wrote:
> >>
> >> probably 0.5.1 is allowing an invalid query and erroring o
Ah, you're right.
So it is a validation problem that 0.6 catches, just not the one I
thought at first. :)
On Wed, Mar 24, 2010 at 10:50 AM, gabriele renzi wrote:
> On Wed, Mar 24, 2010 at 3:36 PM, Oleg Mürk wrote:
>> Hi Jonathan,
>>
>> On Wed, Mar 24, 2010 at 4:32 PM, Jonathan Ellis wrote:
>>>
On Wed, Mar 24, 2010 at 3:36 PM, Oleg Mürk wrote:
> Hi Jonathan,
>
> On Wed, Mar 24, 2010 at 4:32 PM, Jonathan Ellis wrote:
>>
>> probably 0.5.1 is allowing an invalid query and erroring out when it
>> actually runs it.
>
> I am pretty sure that the same query works OK when I initially start
> Ca
Hi Jonathan,
On Wed, Mar 24, 2010 at 4:32 PM, Jonathan Ellis wrote:
> probably 0.5.1 is allowing an invalid query and erroring out when it
> actually runs it.
I am pretty sure that the same query works OK when I initially start
Cassandra.
The problems occur after restarting.
Oleg
probably 0.5.1 is allowing an invalid query and erroring out when it
actually runs it. 0.6 beta3 should catch the problem earlier.
On Wed, Mar 24, 2010 at 9:28 AM, Oleg Mürk wrote:
> Hello,
> I am having the following problem with Cassandra. When I first start
> Cassandra, it works fine and I in
Hello,
I am having the following problem with Cassandra. When I first start
Cassandra, it works fine and I insert some data, but when I kill cassandra
and then start it again, it starts throwing NullPointerException (into
log4j). When I restart Cassandra once more, it doesn't throw the exception
(