You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ning Zhang (JIRA)" <ji...@apache.org> on 2011/03/18 06:28:29 UTC
[jira] Created: (HIVE-2061) Create a hive_contrib.jar symlink to
hive-contrib-{version}.jar for backward compatibility
Create a hive_contrib.jar symlink to hive-contrib-{version}.jar for backward compatibility
------------------------------------------------------------------------------------------
Key: HIVE-2061
URL: https://issues.apache.org/jira/browse/HIVE-2061
Project: Hive
Issue Type: Bug
Reporter: Ning Zhang
Assignee: Ning Zhang
Priority: Minor
We have seen a use case where in the user's script, it run 'add jar hive_contrib.jar'. Since Hive has moved the jar file to be hive-contrib-{version}.jar, it introduced backward incompatibility. If we as the user to change the script and when Hive upgrade version again, the user need to change the script again. Creating a symlink seems to be the best solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-2061) Create a hive_contrib.jar symlink to
hive-contrib-{version}.jar for backward compatibility
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-2061:
-----------------------------
Attachment: HIVE-2061.patch
> Create a hive_contrib.jar symlink to hive-contrib-{version}.jar for backward compatibility
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-2061
> URL: https://issues.apache.org/jira/browse/HIVE-2061
> Project: Hive
> Issue Type: Bug
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Priority: Minor
> Attachments: HIVE-2061.patch
>
>
> We have seen a use case where in the user's script, it run 'add jar hive_contrib.jar'. Since Hive has moved the jar file to be hive-contrib-{version}.jar, it introduced backward incompatibility. If we as the user to change the script and when Hive upgrade version again, the user need to change the script again. Creating a symlink seems to be the best solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2061) Create a hive_contrib.jar symlink to
hive-contrib-{version}.jar for backward compatibility
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2061:
---------------------------------
Component/s: Build Infrastructure
> Create a hive_contrib.jar symlink to hive-contrib-{version}.jar for backward compatibility
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-2061
> URL: https://issues.apache.org/jira/browse/HIVE-2061
> Project: Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: HIVE-2061.patch
>
>
> We have seen a use case where in the user's script, it run 'add jar hive_contrib.jar'. Since Hive has moved the jar file to be hive-contrib-{version}.jar, it introduced backward incompatibility. If we as the user to change the script and when Hive upgrade version again, the user need to change the script again. Creating a symlink seems to be the best solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVE-2061) Create a hive_contrib.jar symlink to
hive-contrib-{version}.jar for backward compatibility
Posted by "Paul Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008363#comment-13008363 ]
Paul Yang commented on HIVE-2061:
---------------------------------
Looks good, will test and commit.
> Create a hive_contrib.jar symlink to hive-contrib-{version}.jar for backward compatibility
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-2061
> URL: https://issues.apache.org/jira/browse/HIVE-2061
> Project: Hive
> Issue Type: Bug
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Priority: Minor
> Attachments: HIVE-2061.patch
>
>
> We have seen a use case where in the user's script, it run 'add jar hive_contrib.jar'. Since Hive has moved the jar file to be hive-contrib-{version}.jar, it introduced backward incompatibility. If we as the user to change the script and when Hive upgrade version again, the user need to change the script again. Creating a symlink seems to be the best solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2061) Create a hive_contrib.jar symlink to
hive-contrib-{version}.jar for backward compatibility
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach resolved HIVE-2061.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.8.0
Hadoop Flags: [Reviewed]
Committed to trunk.
> Create a hive_contrib.jar symlink to hive-contrib-{version}.jar for backward compatibility
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-2061
> URL: https://issues.apache.org/jira/browse/HIVE-2061
> Project: Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: HIVE-2061.patch
>
>
> We have seen a use case where in the user's script, it run 'add jar hive_contrib.jar'. Since Hive has moved the jar file to be hive-contrib-{version}.jar, it introduced backward incompatibility. If we as the user to change the script and when Hive upgrade version again, the user need to change the script again. Creating a symlink seems to be the best solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVE-2061) Create a hive_contrib.jar symlink to
hive-contrib-{version}.jar for backward compatibility
Posted by "Paul Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008585#comment-13008585 ]
Paul Yang commented on HIVE-2061:
---------------------------------
Committed. Thanks Ning!
> Create a hive_contrib.jar symlink to hive-contrib-{version}.jar for backward compatibility
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-2061
> URL: https://issues.apache.org/jira/browse/HIVE-2061
> Project: Hive
> Issue Type: Bug
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Priority: Minor
> Attachments: HIVE-2061.patch
>
>
> We have seen a use case where in the user's script, it run 'add jar hive_contrib.jar'. Since Hive has moved the jar file to be hive-contrib-{version}.jar, it introduced backward incompatibility. If we as the user to change the script and when Hive upgrade version again, the user need to change the script again. Creating a symlink seems to be the best solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira