As mentioned in the article you linked, index creation happens
asynchronously: when you perform the schema update call to add an index, the
index starts building in the background, and will not be completely valid
until it finishes building. I believe there is a JMX call to check the
status of this
> ERROR [main] 2011-01-14 15:37:49,965 DatabaseDescriptor.java (line 388) Fatal
> error: null; mapping values are not allowed here
This indicates there is a problem with the configuration file; that
error is coming from the YAML parser. Double-check what changes you
have made relative to the vers
Same here, Hector with Java.
Shimi
On Fri, Jan 14, 2011 at 9:13 PM, Dan Kuebrich wrote:
> We've done hundreds of gigs in and out of cassandra 0.6.8 with pycassa 0.3.
> Working on upgrading to 0.7 and pycassa 1.03.
>
> I don't know if we're using it wrong, but the "connection object is tied to
>
python + pycassa
scala + Hector
On Fri, Jan 14, 2011 at 6:24 PM, Ertio Lew wrote:
> Hey,
>
> If you have a site in production environment or considering so, what
> is the client that you use to interact with Cassandra. I know that
> there are several clients available out there according to the
>
Perl using the thrift interface directly.
On Sat, Jan 15, 2011 at 6:10 AM, Daniel Lundin wrote:
> python + pycassa
> scala + Hector
>
> On Fri, Jan 14, 2011 at 6:24 PM, Ertio Lew wrote:
> > Hey,
> >
> > If you have a site in production environment or considering so, what
> > is the client that
