Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 27 Mar 2013 13:15:25 +0000 (UTC)
From: "Cyril Scetbon (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12631394.1360311211535.63315.1364390125441@arcas>
In-Reply-To: <JIRA.12631394.1360311211535@arcas>
References: <JIRA.12631394.1360311211535@arcas>
Subject: [jira] [Commented] (CASSANDRA-5234) Table created through CQL3 are
 not accessble to Pig 0.10
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-5234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615231#comment-13615231 ] 

Cyril Scetbon commented on CASSANDRA-5234:
------------------------------------------

It means that CQL3 column families are not accessible through thrift and for me it's an issue (I do not agree with your Resolution label). That's why Pig 0.11 cannot use it. Is there a way to solve it ?
I can help you if necessary
                
> Table created through CQL3 are not accessble to Pig 0.10
> --------------------------------------------------------
>
>                 Key: CASSANDRA-5234
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5234
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>    Affects Versions: 1.2.1
>         Environment: Red hat linux 5
>            Reporter: Shamim Ahmed
>             Fix For: 1.2.2
>
>
> Hi,
>   i have faced a bug when creating table through CQL3 and trying to load data through pig 0.10 as follows:
> java.lang.RuntimeException: Column family 'abc' not found in keyspace 'XYZ'
> 	at org.apache.cassandra.hadoop.pig.CassandraStorage.initSchema(CassandraStorage.java:1112)
> 	at org.apache.cassandra.hadoop.pig.CassandraStorage.setLocation(CassandraStorage.java:615).
> This effects from Simple table to table with compound key. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira