I would like to have https://issues.apache.org/jira/browse/HIVE-6953 also as part 0.13.1. I still could not figure out the reason for test failures, when all tests are running, the CompactorTests fail.
Thanks Amareshwari On Sun, Apr 27, 2014 at 2:49 AM, Sushanth Sowmyan <khorg...@gmail.com>wrote: > Added. > > If others have difficulty editing( I can't figure out how to change editing > privileges, but it seems to indicate that others can edit) the page, I'll > accept replies to this thread as well and can add it in. > On Apr 25, 2014 6:25 PM, "Sergey Shelukhin" <ser...@hortonworks.com> > wrote: > > > I don't have access to edit this page (or cannot figure out the UI). > > Username sershe. > > Can you add > > HIVE-6961 : Drop partitions treats partition columns as strings (area - > > metastore) > > > > > > On Fri, Apr 25, 2014 at 4:20 PM, Sushanth Sowmyan <khorg...@gmail.com > > >wrote: > > > > > I've created the following wiki link : > > > > > > > > > https://cwiki.apache.org/confluence/display/Hive/Hive+0.13.1+Release+tracking > > > > > > People should be able to request additional jiras by adding it to the > > > list. I think it might make sense to halt addition of requests to the > > > list 3 days before the RC is cut, so as to prevent an endless-tail > > > scenario, unless the bug in question is a breaking severe issue, > > > where, yes, after discussion, we can vote to add it to the list. That > > > also gives us time to run a full suite of tests on a stable build > > > before we cut the RC. > > > > > > I propose that the first RC (RC0) be built on Monday May 5th at 6pm > > > PDT, and the jira list on the wiki be closed to open/easy additions at > > > 6pm PDT on Friday May 2nd. > > > > > > > > > On Fri, Apr 25, 2014 at 2:40 PM, Gunther Hagleitner > > > <ghagleit...@hortonworks.com> wrote: > > > > Sorry - HIVE-6824 isn't needed. Just the other 3. My bad. > > > > > > > > Thanks, > > > > Gunther. > > > > > > > > > > > > On Fri, Apr 25, 2014 at 2:10 PM, Gunther Hagleitner < > > > > ghagleit...@hortonworks.com> wrote: > > > > > > > >> I'd like to request to include these Tez fixes: > > > >> > > > >> HIVE-6824, HIVE-6826, HIVE-6828, HIVE-6898 > > > >> > > > >> Thanks, > > > >> Gunther. > > > >> > > > >> > > > >> On Fri, Apr 25, 2014 at 11:59 AM, Sushanth Sowmyan < > > khorg...@gmail.com > > > >wrote: > > > >> > > > >>> True, I was counting two weeks from today, but 0.13 has already > been > > > >>> out for a week. I'm amenable to having an RC1 out on May 5th. If > any > > > >>> further issues appear that block, then we can deal with them in an > > > >>> RC2/etc modification to that. > > > >>> > > > >>> On Fri, Apr 25, 2014 at 11:45 AM, Thejas Nair < > > the...@hortonworks.com> > > > >>> wrote: > > > >>> > On Fri, Apr 25, 2014 at 11:33 AM, Sushanth Sowmyan < > > > khorg...@gmail.com > > > >>> >wrote: > > > >>> > > > > >>> >> > > > >>> >> I think it's important to get a bugfix/stabilization release > > > >>> >> reasonably quickly, but it's also important to give people a > > little > > > >>> >> time to try out 0.13, discover/report bugs and fix them. So I > > think > > > >>> >> about two weeks is a good point? And instead of releasing an RC > > on a > > > >>> >> friday, I'm thinking of pushing it out to Monday - does 12th May > > > sound > > > >>> >> good to everyone? > > > >>> >> > > > >>> > > > > >>> > I think we can aim for an earlier date. Most of these issues seem > > to > > > be > > > >>> > already committed to trunk or have patches available. So the > > > remaining > > > >>> ones > > > >>> > also might get committed to trunk by early next week. How about > > > shooting > > > >>> > for May 5th (Monday) ? > > > >>> > By then 0.13 would also have been out for 2 weeks. If we have any > > new > > > >>> > critical bug reported that needs a fix, we can hold off on the RC > > for > > > >>> few > > > >>> > days. > > > >>> > What do you think ? > > > >>> > > > > >>> > Thanks, > > > >>> > Thejas > > > >>> > > > > >>> > -- > > > >>> > CONFIDENTIALITY NOTICE > > > >>> > NOTICE: This message is intended for the use of the individual or > > > >>> entity to > > > >>> > which it is addressed and may contain information that is > > > confidential, > > > >>> > privileged and exempt from disclosure under applicable law. If > the > > > >>> reader > > > >>> > of this message is not the intended recipient, you are hereby > > > notified > > > >>> that > > > >>> > any printing, copying, dissemination, distribution, disclosure or > > > >>> > forwarding of this communication is strictly prohibited. If you > > have > > > >>> > received this communication in error, please contact the sender > > > >>> immediately > > > >>> > and delete it from your system. Thank You. > > > >>> > > > >> > > > >> > > > > > > > > -- > > > > CONFIDENTIALITY NOTICE > > > > NOTICE: This message is intended for the use of the individual or > > entity > > > to > > > > which it is addressed and may contain information that is > confidential, > > > > privileged and exempt from disclosure under applicable law. If the > > reader > > > > of this message is not the intended recipient, you are hereby > notified > > > that > > > > any printing, copying, dissemination, distribution, disclosure or > > > > forwarding of this communication is strictly prohibited. If you have > > > > received this communication in error, please contact the sender > > > immediately > > > > and delete it from your system. Thank You. > > > > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > > >
