Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 14 Jun 2013 05:55:21 +0000 (UTC)
From: "Alex Liu (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12631394.1360311211535.113997.1371189321481@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=13683125#comment-13683125 ] 

Alex Liu commented on CASSANDRA-5234:
-------------------------------------

The patch resolves the following issues.

1. allow access to cql3 type table through CassandraStorage.

2. create new CqlStorage to easy access cql3 tables.
                
> 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
>
>         Attachments: 5234-1.2-patch.txt, 5234.tx
>
>
> 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