[
https://issues.apache.org/jira/browse/CASSANDRA-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474751#comment-13474751
]
Jeremy Hanna edited comment on CASSANDRA-4749 at 10/12/12 3:00 AM:
-------------------------------------------------------------------
I was looking at 1.1.5 that didn't yet have the URL location for Cassandra
accepting the widerows or use_secondary flags. That's in there in the 1.1
branch.
in other words +1 :)
was (Author: jeromatron):
I was looking at 1.1.5 that didn't yet have the URL location for Cassandra
accepting the widerows or use_secondary. That's in there in 1.1-branch.
in other words +1 :)
> Possible problem with widerow in Pig URI
> -----------------------------------------
>
> Key: CASSANDRA-4749
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4749
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Affects Versions: 1.1.5
> Environment: AWS running Centos 5.6 using Sun build 1.6.0_24-b07
> Reporter: Will Oberman
> Assignee: Brandon Williams
> Attachments: 4749.txt
>
>
> I don't have a good way to test this directly, but I'm concerned the Uri
> parsing for widerows isn't going to work. setLocation
> 1.) calls setLocationFromUri (which sets widerows to the Uri value)
> 2.) sets widerows to a static value (which is defined as false)
> 3.) sets widerows to the system setting if it exists.
> That doesn't seem right...
> But setLocationFromUri also gets called from setStoreLocation, and I don't
> really know the difference between setLocation and setStoreLocation in terms
> of what is going on in terms of the integration between cassandra/pig/hadoop.
--
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
