Hive bylaws<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Voting>say the mailing list is used for voting, but as I recall bylaws have some wiggle room.
Decisions regarding the project are made by votes on the primary project > development mailing list (u...@hive.apache.org <u...@pig.apache.org>). > Where necessary, PMC voting may take place on the private Hive PMC mailing > list. Votes are clearly indicated by subject line starting with [VOTE]. > Votes may contain multiple items for approval and these should be clearly > separated. Voting is carried out by replying to the vote mail. (Hm, the text says "primary project development mailing list" but then user@hive is shown in parentheses -- is that a typo in the bylaws?) Would people be willing to vote simultaneously by mail and on a jira? It's inconvenient but shouldn't be necessary after this release. -- Lefty On Sat, May 17, 2014 at 7:30 PM, Sushanth Sowmyan <khorg...@gmail.com>wrote: > There is a technical issue as well now, as raised by Prashant. But > there is also the issue that people aren't reliably able to > respond/object/approve, and not knowing if/when it'll go through. > > I think I like Lefty's jira proposal - we could open out a jira for it > and address votes there, I think I'll do that for RC2. > > On Fri, May 16, 2014 at 2:53 PM, Alan Gates <ga...@hortonworks.com> wrote: > > So this isn’t a technical issue, just concern about the delays in the > mailing list? Why not just extend the voting period then, until say Monday? > > > > Alan. > > > > On May 15, 2014, at 3:17 PM, Sushanth Sowmyan <khorg...@gmail.com> > wrote: > > > >> Hi Folks, > >> > >> I'm canceling this vote and withdrawing the RC1 candidate for the > >> following reasons: > >> > >> a) I've talked to a couple of other people who haven't seen my mail > >> updates to this thread, and saw my initial vote mail a bit late too. > >> b) There's at least one other person that has attempted to reply to > >> this thread, and I don't see the replies yet. > >> > >> Thus, when the mailing list channel isn't reliably working, the > >> ability for people to +1 or -1 is taken away, and this does not work. > >> (We don't want a situation where 3 people go ahead and +1, and that > >> arrives before today evening, thus making the release releasable, > >> while someone else discovers a breaking issue that should stop it, but > >> is not able to have their objection or -1 appear in time.) > >> > >> I'm open to suggestions on how to proceed with the voting process. We > >> could wait out this week and hope the ASF mailing list issues are > >> resolved, but if it takes too much longer than that, we also have the > >> issue of delaying an important bugfix release. > >> > >> Thoughts? > >> > >> -Sushanth > >> (3:15PM PDT, May 15 2014) > >> > >> > >> > >> On Thu, May 15, 2014 at 11:46 AM, Sushanth Sowmyan <khorg...@gmail.com> > wrote: > >>> The apache dev list seems to still be a little wonky, Prasanth mailed > >>> me saying he'd replied to this thread with the following content, that > >>> I don't see in this thread: > >>> > >>> "Hi Sushanth > >>> > >>> https://issues.apache.org/jira/browse/HIVE-7067 > >>> This bug is critical as it returns wrong results for min(), max(), > >>> join queries that uses date/timestamp columns from ORC table. > >>> The reason for this issue is, for these datatypes ORC returns java > >>> objects whereas for all other types ORC returns writables. > >>> When get() is performed on their corresponding object inspectors, > >>> writables return a new object where as java object returns reference. > >>> This will cause issue when any operator perform comparison on > >>> date/timestamp values (references will be overwritten with next > >>> values). > >>> More information is provided in the description of the jira. > >>> > >>> I think the severity of this bug is critical and should be included as > >>> part of 0.13.1. Can you please include this patch in RC2?” > >>> > >>> I think this meets the bar for criticality(actual bug in core feature, > >>> no workaround) and severity( incorrect results, effectively data > >>> corruption when used as source for other data), and I'm willing to > >>> spin an RC2 for this, but I would still like to follow the process I > >>> set up for jira inclusion though, to make sure I'm not being biased > >>> about this, so I would request two other +1s to champion this bug's > >>> inclusion into the release. > >>> > >>> Also, another thought here is whether it makes sense for us to try to > >>> have a VOTE with a 72 hour deadline when the mailing list still seems > >>> iffy and delaying mails by multiple hours. Any thoughts on how we > >>> should proceed? (In case this mail goes out much later than I send it > >>> out, I'm sending it out at 11:45AM PDT, Thu May 15 2014) > >>> > >>> > >>> > >>> On Thu, May 15, 2014 at 10:06 AM, Sushanth Sowmyan <khorg...@gmail.com> > wrote: > >>>> Eugene, do you know if these two failures happen on 0.13.0 as well? > >>>> > >>>> I would assume that TestHive_7 is an issue on 0.13.0 as well, given > >>>> that the fix for it went into trunk. What is your sense for how > >>>> important it is that we fix this? i.e., per my understanding, (a) It > >>>> does not cause a crash or adversly affect the ability for webhcat to > >>>> continue operating, and (b) It means that the feature does not work > >>>> (at all, but in isolation), and that there is no work around for it. > >>>> This means I treat it as critical(valid bug without workaround) but > >>>> not severe(breaks product, affects other features from being used). > >>>> Thus, I'm willing to include HIVE-6521 in an RC2 if we have 2 more > >>>> committers +1 an inclusion request for this. > >>>> > >>>> As for TestHeartbeat_1, that's an interesting failure. Do you have > >>>> logs on what commandline options > >>>> org.apache.hive.hcatalog.templeton.LauncherDelegator sent along that > >>>> caused it to break? Would that affect other job launches? > >>>> > >>>> > >>>> On Tue, May 13, 2014 at 8:14 PM, Eugene Koifman > >>>> <ekoif...@hortonworks.com> wrote: > >>>>> TestHive_7 is explained by > https://issues.apache.org/jira/browse/HIVE-6521, > >>>>> which is in trunk but not 13.1 > >>>>> > >>>>> > >>>>> On Tue, May 13, 2014 at 6:50 PM, Eugene Koifman < > ekoif...@hortonworks.com>wrote: > >>>>> > >>>>>> I downloaded src tar, built it and ran webhcat e2e tests. > >>>>>> I see 2 failures (which I don't see on trunk) > >>>>>> > >>>>>> TestHive_7 fails with > >>>>>> "got percentComplete map 100% reduce 0%, expected map 100% reduce > 100%" > >>>>>> > >>>>>> TestHeartbeat_1 fails to even launch the job. This looks like the > root > >>>>>> cause > >>>>>> > >>>>>> ERROR | 13 May 2014 18:24:00,394 | > >>>>>> org.apache.hive.hcatalog.templeton.CatchallExceptionMapper | > >>>>>> java.lang.NullPointerException > >>>>>> at > >>>>>> > org.apache.hadoop.util.GenericOptionsParser.processGeneralOptions(GenericOptionsParser.java:312) > >>>>>> at > >>>>>> > org.apache.hadoop.util.GenericOptionsParser.parseGeneralOptions(GenericOptionsParser.java:479) > >>>>>> at > >>>>>> > org.apache.hadoop.util.GenericOptionsParser.<init>(GenericOptionsParser.java:170) > >>>>>> at > >>>>>> > org.apache.hadoop.util.GenericOptionsParser.<init>(GenericOptionsParser.java:153) > >>>>>> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:64) > >>>>>> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > >>>>>> at > >>>>>> > org.apache.hive.hcatalog.templeton.LauncherDelegator$1.run(LauncherDelegator.java:107) > >>>>>> at > >>>>>> > org.apache.hive.hcatalog.templeton.LauncherDelegator$1.run(LauncherDelegator.java:103) > >>>>>> at java.security.AccessController.doPrivileged(Native Method) > >>>>>> at javax.security.auth.Subject.doAs(Subject.java:396) > >>>>>> at > >>>>>> > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1557) > >>>>>> at > >>>>>> > org.apache.hive.hcatalog.templeton.LauncherDelegator.queueAsUser(LauncherDelegator.java:103) > >>>>>> at > >>>>>> > org.apache.hive.hcatalog.templeton.LauncherDelegator.enqueueController(LauncherDelegator.java:81) > >>>>>> at > >>>>>> > org.apache.hive.hcatalog.templeton.JarDelegator.run(JarDelegator.java:55) > >>>>>> at > >>>>>> > org.apache.hive.hcatalog.templeton.Server.mapReduceJar(Server.java:711) > >>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > >>>>>> at > >>>>>> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > >>>>>> at > >>>>>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > >>>>>> at java.lang.reflect.Method.invoke(Method.java:597) > >>>>>> at > >>>>>> > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1480) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1411) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1360) > >>>>>> at > >>>>>> > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1350) > >>>>>> at > >>>>>> > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416) > >>>>>> at > >>>>>> > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538) > >>>>>> at > >>>>>> > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:716) > >>>>>> at > javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > >>>>>> at > >>>>>> > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:565) > >>>>>> at > >>>>>> > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1360) > >>>>>> at > >>>>>> > org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:392) > >>>>>> at > >>>>>> org.apache.hadoop.hdfs.web.AuthFilter.doFilter(AuthFilter.java:87) > >>>>>> at > >>>>>> > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331) > >>>>>> at > >>>>>> > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:477) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031) > >>>>>> at > >>>>>> > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:47) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111) > >>>>>> at org.eclipse.jetty.server.Server.handle(Server.java:349) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:449) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:925) > >>>>>> at > org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:857) > >>>>>> at > >>>>>> > org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) > >>>>>> at > >>>>>> > org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:76) > >>>>>> at > >>>>>> > org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609) > >>>>>> at > >>>>>> > org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45) > >>>>>> at > >>>>>> > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599) > >>>>>> at > >>>>>> > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534) > >>>>>> at java.lang.Thread.run(Thread.java:680) > >>>>>> > >>>>>> > >>>>>> > >>>>>> On Mon, May 12, 2014 at 7:30 PM, Sushanth Sowmyan < > khorg...@apache.org>wrote: > >>>>>> > >>>>>>> > >>>>>>> Apache Hive 0.13.1 Release Candidate 1 is available here: > >>>>>>> > >>>>>>> http://people.apache.org/~khorgath/releases/0.13.1_RC1/artifacts/ > >>>>>>> > >>>>>>> Maven artifacts are available here: > >>>>>>> > >>>>>>> > https://repository.apache.org/content/repositories/orgapachehive-1013/ > >>>>>>> > >>>>>>> Source tag for RC1 is at : > >>>>>>> https://svn.apache.org/viewvc/hive/tags/release-0.13.1-rc1/ > >>>>>>> > >>>>>>> Voting will conclude in 72 hours. > >>>>>>> > >>>>>>> Hive PMC Members: Please test and vote. > >>>>>>> > >>>>>>> Thanks. > >>>>>>> -Sushanth > >>>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> > >>>>>> Thanks, > >>>>>> Eugene > >>>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> > >>>>> Thanks, > >>>>> Eugene > >>>>> > >>>>> -- > >>>>> 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. >
