Managed to solve this problem to an extent. I used the thrift api just for this client and did a thread sleep until the schema comes into agreement.
The addColumnFamily(CF, boolean) is not available in the Hector I use. Anyway, I checked the code in Hector trunk. The approach is almost identical, so it should be good.
Sometimes still the schema does not come into agreement... I wonder whether this issue is solved the newer versions?
Anyway, Aaron has given a workaround in another thread for this problem.
Thanks for all the help folks.
Hi!Maybe I didn't understand, but if you use Hector'saddColumnFamily(CF, true);it should wait for schema agreement.Will that solve your problem?ThanksTamar Fraenkel†
Senior Software Engineer, TOK Media†
On Tue, Mar 6, 2012 at 7:55 PM, Jeremiah Jordan <email@example.com> wrote:
That is the best one I have found.
On 03/01/2012 03:12 PM, Tharindu Mathew wrote:There are 2. I'd like to wait till there are one, when I insert the value.
Going through the code, calling client.describe_schema_versions() seems to give a good answer to this. And I discovered that if I wait till there is only 1 version, I will not get this error.
Is this the best practice if I want to check this programatically?
On Thu, Mar 1, 2012 at 11:15 PM, aaron morton <firstname.lastname@example.org> wrote:
use describe cluster in the CLI to see how many schema versions there are.†
On 2/03/2012, at 12:25 AM, Tharindu Mathew wrote:
On Thu, Mar 1, 2012 at 11:47 AM, Tharindu Mathew <email@example.com> wrote:
Thanks for the reply.
This is what we have been doing, but it's not reliable as we don't know a definite time that the schema would get replicated. Is there any way I can know for sure that changes have propagated?
[Edit: corrected to a question]
Then I can block the insertion of data until then.
On Thu, Mar 1, 2012 at 4:33 AM, Jeremiah Jordan <JEREMIAH.JORDAN@morningstar.com> wrote:
The error is that the specified colum family doesnít exist.† If you connect with the CLI and describe the keyspace does it show up?† Also, after adding a new column family programmatically you canít use it immediately, you have to wait for it to propagate.† You can use calls to describe schema to do so, keep calling it until every node is on the same schema.
I have a 3 node cluster and I'm dynamically updating a keyspace with a new column family. Then, when I try to write records to it I get the following exception shown at .
How do I avoid this. I'm using Hector and the default consistency level of QUORUM is used. Cassandra version 0.7.8. Replication Factor is 1.
How can I solve my problem?
me.prettyprint.hector.api.exceptions.HInvalidRequestException: InvalidRequestException(why:unconfigured columnfamily proxySummary)