Saladi
>
> --
> *From:* Sebastian Estevez
> *To:* user@cassandra.apache.org; Saladi Naidu
> *Sent:* Friday, July 10, 2015 5:25 PM
> *Subject:* Re: DROP Table
>
> #1 The cause of this problem is a CREATE TABLE statement collision. Do
> *not*
erride the current file right?
>>
>> 3. Do we have to rename the directory name to remove CFID i.e. just
>> column family name without CFID? After that, update the System table as
>> well?
>>
>>
>> Naidu Saladi
>>
>> --
t; --
> *From:* Sebastian Estevez
> *To:* user@cassandra.apache.org; Saladi Naidu
> *Sent:* Friday, July 10, 2015 5:25 PM
> *Subject:* Re: DROP Table
>
> #1 The cause of this problem is a CREATE TABLE statement collision. Do
> *not* generate tab
user@cassandra.apache.org; Saladi Naidu
Sent: Friday, July 10, 2015 5:25 PM
Subject: Re: DROP Table
#1 The cause of this problem is a CREATE TABLE statement collision. Do notÂ
generate tables dynamically from multiple clients, even with IF NOT EXISTS.
First thing you need to do is fix your code so that
#1 The cause of this problem is a CREATE TABLE statement collision. Do
*not* generate
tables dynamically from multiple clients, even with IF NOT EXISTS. First
thing you need to do is fix your code so that this does not happen. Just
create your tables manually from cqlsh allowing time for the schema
On Fri, Jul 4, 2014 at 10:31 AM, Simon Chemouil wrote:
> Hi,
>
> I just encountered a bug with 2.1-rc1 (didn't have the chance to update
> to rc2 yet), and wondering if it's known or if I should report the issue
> on JIRA.
FWIW I think this issue might be related to what you are seeing:
https://i
On Fri, Jul 4, 2014 at 2:31 AM, Simon Chemouil wrote:
> I just encountered a bug with 2.1-rc1 (didn't have the chance to update
> to rc2 yet), and wondering if it's known or if I should report the issue
> on JIRA.
>
For issues in pre-release versions of Cassandra, JIRA is almost certainly
the ri
