[ https://issues.apache.org/jira/browse/HIVE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984400#action_12984400 ]
Edward Capriolo commented on HIVE-1817: --------------------------------------- Arge. This is a major buzzkill, our shims, build, eclipse generation processes can not deal easily with lib changes for minor versions. Option 1. This angers me. Pushed into an update by a CLI jar, but it seems like the right think to do. Option 2. More bash scripting is only going to make the problem worse As an option 3 we do have a ticket for a hive JobShell. Which would be some perfect new shell that is not so married to bash and hadoop, I imagine this new job shell would do explicit class loading and would reference nothing except HIVE_HOME from the environment. Option 4. We use some other CLI library. +1 option 1. Push forward at all costs including forcing someone with 0.20.0 to upgrade just for hive. > Remove Hive dependency on unrelease commons-cli 2.0 Snapshot > ------------------------------------------------------------ > > Key: HIVE-1817 > URL: https://issues.apache.org/jira/browse/HIVE-1817 > Project: Hive > Issue Type: Task > Components: Build Infrastructure, CLI > Reporter: Carl Steinbach > Assignee: Carl Steinbach > Priority: Blocker > Fix For: 0.7.0 > > Attachments: HIVE-1817.wip.1.patch.txt > > > The Hive CLI depends on commons-cli-2.0-SNAPSHOT. This branch of of the > commons-cli project is dead. > Hive needs to use commons-cli-1.2 instead. See MAPREDUCE-767 for more > information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.