You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2013/09/24 21:45:07 UTC
[jira] [Resolved] (CASSANDRA-6085) Pig CqlStorage read schema
changes to (value, value ... value) from ((name,value), (name, value) ...
(name, value)) . Do we need make it backward compatible?
[ https://issues.apache.org/jira/browse/CASSANDRA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams resolved CASSANDRA-6085.
-----------------------------------------
Resolution: Won't Fix
CqlStorage is new enough that I don't see the need to take on extra code to make it backward-compatible.
> Pig CqlStorage read schema changes to (value, value ... value) from ((name,value), (name, value) ... (name, value)) . Do we need make it backward compatible?
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6085
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6085
> Project: Cassandra
> Issue Type: Bug
> Reporter: Alex Liu
> Assignee: Alex Liu
> Priority: Minor
>
> Since the pushdown needs the schema change from (name, value) tuple to value
> {code}
> schema: (value, value, value) where keys are in the front. Each has its name in the column schema
> {code}
> Doesn't anyone needs backward compatible which will block filter push down?
> The new schema is much concise than the old one, and It still keeps the column name in the column schema.
--
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