[
https://issues.apache.org/jira/browse/CASSANDRA-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777768#comment-13777768
]
Jeremy Hanna commented on CASSANDRA-6073:
-----------------------------------------
Having been on the user's side of a lot of the changes (in CassandraStorage)
from 0.7 to 1.0, I can appreciate where you're coming from.
I wonder if it's possible to use the macro feature of pig to URL encode the URL
so that it could still be readable but it would send it to CqlStorage like
that. I opened CASSANDRA-6096 to explore that possibility.
Pig isn't really a second class citizen as much as feedback is needed such as
this. I think it's great that you spoke out so the project contributors know
who is using it and know who they may be affecting.
As CqlStorage solidifies, I think the only major changes will really be to add
features from Cassandra. I would think CqlStorage will be more rigid in terms
of backwards compatibility starting in 2.0.
> 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
