[ https://issues.apache.org/jira/browse/CASSANDRA-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125979#comment-13125979 ]
Hudson commented on CASSANDRA-3320: ----------------------------------- Integrated in Cassandra-0.8 #368 (See [https://builds.apache.org/job/Cassandra-0.8/368/]) Fix pig script to only pick up a single pig jar. Patch by Brian Oneill, reviewed by brandonwilliams for CASSANDRA-3320 brandonwilliams : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1182456 Files : * /cassandra/branches/cassandra-0.8/contrib/pig/bin/pig_cassandra > pig_cassandra script errors when running against pig 0.9.1 tar ball because > there are multiple jars. > ---------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-3320 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3320 > Project: Cassandra > Issue Type: Bug > Components: Contrib > Affects Versions: 0.8.6 > Environment: Running on mac os x. PIG_HOME set to a fresh download > of pig 0.9.1. > Reporter: Brian ONeill > Assignee: Brian ONeill > Priority: Minor > Fix For: 0.8.8 > > Attachments: trunk-3320.txt > > > The pig_cassandra script in contrib/pig/bin assumes there is only one pig jar > file in $PIG_HOME. However, the latest release of pig 0.9.1 has two jar > files: one for hadoop and one without hadoop. See below: > bone@zen:~/tools/pig-0.9.1-> ls -al *.jar > -rw-r--r-- 1 bone staff 5130595 Sep 29 18:55 pig-0.9.1-withouthadoop.jar > -rw-r--r-- 1 bone staff 12430153 Sep 29 18:55 pig-0.9.1.jar > This breaks the shell script with: > bin/pig_cassandra: line 42: [: > /Users/bone/tools/pig/pig-0.9.1-withouthadoop.jar: binary operator expected > Unrecognized option: -x > Attached is a patch for the shell script that takes the last jar file listed > in the directory. This fixes the problem. I also add an "echo" to notify the > user which jar file they are using. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira