The error reported on the list a few days ago with streaming not working properly when grouping on multiple columns should also probably qualify as a blocker since streaming is a key feature of hive.
On Sat, Aug 31, 2013 at 10:31 AM, Edward Capriolo <edlinuxg...@gmail.com>wrote: > I do not think we should consider too many not done items for 12.0. I do > not think releases should be a wish-list. If trunk is working with no > blockers we should build a release, anything not done and not committed > goes in next release. I do not like cherry picking issues and then waiting > for them. Historically adding types is much more complicated then people > think. Generally there are three or more follow on issues for things people > did not consider in the initial patch, it worked this way for binary, > decimal, date, so I am not super eager to announce and release a large > feature that was just committed and not heavily battle tested. The npath > thing is a blocker and we can not release without that. > > Committers should review the other blockers as well, and either mark them > not as blockers, or work to get them committed, because if we have > blockers, we should dealing with them. > > > On Fri, Aug 30, 2013 at 11:21 PM, Eugene Koifman <ekoif...@hortonworks.com > > wrote: > >> Because this change includes moving/renaming 300 files and then adding >> about 200 more with the same name (but contents from 0.11 branch) as the >> file had before the move. The first part is necessary to change the >> package name, the second to ensure backwards compatibility. I described >> this in detail the mail "RFC: Major HCatalog refactoring". >> >> Given the complexity of the changes I think creating and applying a patch >> could end up with a lot of conflicts. So doing this after the branch adds >> complexity but does not add anything useful. >> >> Eugene >> >> >> >> On Fri, Aug 30, 2013 at 5:57 PM, Thejas Nair <the...@hortonworks.com> >> wrote: >> >> > Hi Eugene, >> > Can you please elaborate on why you would like to have this in before >> > branching and not commit it after branching in trunk and the branch ? >> > Thanks, >> > Thejas >> > >> > >> > >> > On Thu, Aug 29, 2013 at 10:31 PM, Eugene Koifman >> > <ekoif...@hortonworks.com>wrote: >> > >> > > I think we should make sure that several items under HIVE-4869 get >> > checked >> > > in before branching. >> > > >> > > Eugene >> > > >> > > >> > > On Thu, Aug 29, 2013 at 9:18 PM, Thejas Nair <the...@hortonworks.com> >> > > wrote: >> > > >> > > > It has been more than 3 months since 0.11 was released and we >> already >> > > have >> > > > 294 jiras in resolved-fixed state for 0.12. This includes several >> new >> > > > features such as date data type, optimizer improvements, ORC format >> > > > improvements and many bug fixes. There are also many features look >> > ready >> > > to >> > > > get committed soon such as the varchar type. >> > > > I think it is time to start preparing for a 0.12 release by >> creating a >> > > > branch later next week and start stabilizing it. What do people >> think >> > > about >> > > > it ? >> > > > >> > > > As we get closer to the branching, we can start discussing any >> > additional >> > > > features/bug fixes that we should add to the release and start >> > monitoring >> > > > their progress. >> > > > >> > > > 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. >> > >> >> -- >> 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. >> > >
