[jira] [Commented] (CASSANDRA-8725) CassandraStorage erroring due to system keyspace schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303558#comment-14303558
]
Philip Thompson commented on CASSANDRA-8725:
Fair. If that is the case then, should I push the java driver changes back up
to ACS, make CNS a subclass of ACS again, and just be mixing thrift/native
inside ACS (Because of CS)?
> 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)
[jira] [Commented] (CASSANDRA-8725) CassandraStorage erroring due to system keyspace schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303126#comment-14303126
]
Aleksey Yeschenko commented on CASSANDRA-8725:
--
That code is wrong either way - it does NOT tell you if the table is a
'cql3table'. It's a bug.
> 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)
[jira] [Commented] (CASSANDRA-8725) CassandraStorage erroring due to system keyspace schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302805#comment-14302805
]
Philip Thompson commented on CASSANDRA-8725:
If not, the only way to handle using CassandraStorage against cql tables after
8358 would be to push the java driver changes up to AbstractCassandraStorage.
> 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)
[jira] [Commented] (CASSANDRA-8725) CassandraStorage erroring due to system keyspace schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302779#comment-14302779
]
Philip Thompson commented on CASSANDRA-8725:
[~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)
