[
https://issues.apache.org/jira/browse/CASSANDRA-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302779#comment-14302779
]
Philip Thompson edited comment on CASSANDRA-8725 at 2/3/15 5:14 AM:
--------------------------------------------------------------------
[~iamaleksey], AbstractCassandraStorage is using key_aliases to determine if
the table was created via cql or thrift. Is there still a way to do that
without key_aliases?
{code}
String keyAliases = ByteBufferUtil.string(cqlRow.columns.get(5).value);
if (FBUtilities.fromJsonList(keyAliases).size() > 0)
cql3Table = true;
{code}
was (Author: philipthompson):
[~iamaleksey], AbstractCassandraStorage is using key_aliases to determine if
the table was created via cql or thrift. Is there still a way to do that
without key_aliases?
> CassandraStorage erroring due to system keyspace schema changes
> ---------------------------------------------------------------
>
> Key: CASSANDRA-8725
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8725
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Reporter: Philip Thompson
> Assignee: Philip Thompson
> Fix For: 3.0
>
>
> CassandraStorage will be deprecated in 3.0, but is currently not working
> because it is selecting {{key_aliases}} from the system.schema_columnfamilies
> table, and the column no longer exists. This is causing about half of the
> pig-tests to fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
