Just wish that an error like: "Table x not found in keyspace y"
You are welcome to open JIRA with type Improvement.
Best regards, Vladimir Yudovin,
Winguzone - Cloud Cassandra Hosting
On Sun, 26 Mar 2017 13:31:33 -0400 S G sg.online.em...@gmail.com
wrote
Thanks, got
Prefixing with the ks is best practice, since it allows you to use a single
session for multiple keyspaces. Otherwise you'd have to have a desicated
session and set the keyspace by calling cluster.connect(ks)
On Sun, Mar 26, 2017 at 19:39 S G wrote:
> Thanks, got it
Thanks, got it working now :)
Just wish that an error like:
"Table x not found in keyspace y"
would have been much better than:
"Table x not configured".
On Sat, Mar 25, 2017 at 6:13 AM, Arvydas Jonusonis <
arvydas.jonuso...@gmail.com> wrote:
> Make sure to prefix the table with the
Make sure to prefix the table with the keyspace.
On Sat, Mar 25, 2017 at 13:28 Anuj Wadehra wrote:
> Ensure that all the nodes are on same schema version such that table2
> schema is replicated properly on all the nodes.
>
> Thanks
> Anuj
>
> Sent from Yahoo Mail on
Ensure that all the nodes are on same schema version such that table2 schema is
replicated properly on all the nodes.
ThanksAnuj
Sent from Yahoo Mail on Android
On Sat, Mar 25, 2017 at 3:19 AM, S G wrote: Hi,
I have a keyspace with two tables.
I run a different