cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6073) Changes for Pig collections break CQL prepared statements
Date Wed, 25 Sep 2013 15:42:06 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777632#comment-13777632
] 

Jeremiah Jordan commented on CASSANDRA-6073:
--------------------------------------------

While I totally agree stuff shouldn't just change, this interface was added in 1.2.7, the
original method of encoding the select in the URL was discovered to have issues, so it was
switch in 1.2.10 to a new encoding scheme.

It had the old way for ~2 months before being changed, and it is a fairly trivial task to
update for the new way.  Since CQL3 is the way forward in Cassandra, I think it is better
to get the interface right and working for all cases, and have some rework up front, rather
than leave the original not working way in place because we don't want to break existing scripts
that are less than 2 months old

If this happened a year from now, I would be yelling right along with you.  This is a brand
new interface, the first pass at it didn't work as well as expected, we should fix it now
while it is still new.
                
> Changes for Pig collections break CQL prepared statements
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-6073
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6073
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>         Environment: 1.2.10-tentative branch
>            Reporter: Chad Johnston
>            Assignee: Alex Liu
>
> I've checked out and built the 1.2.10-tentative branch, and I've noticed that all of
my CQL prepared statements are now broken.
> Looking into the code, it looks like the "#" -> "=" and "@" -> "?" translations
were removed. I tried to replace these in one of my scripts with "=" and "?", but there's
other code that splits the query string on "=", causing the prepared statement to be malformed.
> If I look at the comments on https://issues.apache.org/jira/browse/CASSANDRA-5867, where
this change was made, I see a single mention of URL encoding the CQL query. Is this the expectation
going forward? Was there a reason that the "#" and "@" mappings were removed?

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

Mime
View raw message