You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex Liu (JIRA)" <ji...@apache.org> on 2013/09/23 23:49:03 UTC

[jira] [Created] (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?

Alex Liu created CASSANDRA-6085:
-----------------------------------

             Summary: 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