[
https://issues.apache.org/jira/browse/HIVE-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766693#comment-13766693
]
Edward Capriolo commented on HIVE-5112:
---------------------------------------
{quote}
The upgrade is inevitable. With it being in trunk, it is in its way into the
0.13 release.
{quote}
Yes but this will give users time to prepare for it. Which is what rushing the
upgrade will take away.
{quote}
I don't consider it feasible to stop upgrading jars in hive because the old
version of jar was used by some udf/serde/inputformat.
{quote}
You want this upgrade because it effects the OCR input formats you care about.
It effects new beta version that you want to support.
Q. Why don't we remove the dependency from hive all together? A. We can't
because it's baked via an input format.
{quote}
But I do think that in long term we need to explore ways of isolating the hive
jars/classes vs user jars/classes.
{quote}
But why do that? We can just bake in all the things we care about! Then
whenever it screws someone up we can just say "long term we might research a
way not to inconvenience people, but for now your inconvenienced"
I don't care really take away my -1. I would not want the to inconvenience the
0 people running future-ware versions in production.
> Upgrade protobuf to 2.5 from 2.4
> --------------------------------
>
> Key: HIVE-5112
> URL: https://issues.apache.org/jira/browse/HIVE-5112
> Project: Hive
> Issue Type: Improvement
> Reporter: Brock Noland
> Assignee: Owen O'Malley
> Fix For: 0.13.0
>
> Attachments: HIVE-5112.2.patch, HIVE-5112.D12429.1.patch
>
>
> Hadoop and Hbase have both upgraded protobuf. We should as well.
--
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
