The problem continues. I posted a few more examples on INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221> of issues with either complete or incomplete messages in the issues@hive mailing list. Commits to trunk seem to be the main problem, while branch commits usually have complete records. But both have exceptions.
I've changed the status of INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221> from waiting for user to waiting for infra. Perhaps that was needed to get their attention. But I didn't set a review date, not knowing what's appropriate. Should I bump the priority to critical? Hive's archives are incomplete! -- Lefty On Fri, Apr 3, 2015 at 9:22 PM, Szehon Ho <sze...@cloudera.com> wrote: > Yea I added some for what its worth, +1 for bumping it if it helps as its > quite annoying. > > Thanks > Szehon > > On Fri, Apr 3, 2015 at 2:00 PM, Lefty Leverenz <leftylever...@gmail.com> > wrote: > > > Thanks Szehon, if you could add some examples on INFRA-9221 > > <https://issues.apache.org/jira/browse/INFRA-9221> then maybe we'd see > > some > > action. > > > > Should we bump the priority too? It seemed a small matter at first, but > > the Apache way requires complete archives and we haven't had that for > > several weeks. > > > > -- Lefty > > > > On Fri, Apr 3, 2015 at 2:51 PM, Szehon Ho <sze...@cloudera.com> wrote: > > > > > Hi Lefty > > > > > > I am also seeing this, whenever I resolve the JIRA after commit to > > trunk, I > > > never get the email, and probably the contributor doesn't get the email > > > either. > > > > > > Did you find any resolution to this (is it going to different mail > list)? > > > If not I can add my examples tool. > > > > > > Thanks > > > Szehon > > > > > > On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz < > leftylever...@gmail.com > > > > > > wrote: > > > > > > > This is still a problem. I'm working around it but the archives are > > > > incomplete, and that's not good. > > > > > > > > I updated INFRA-9221 < > https://issues.apache.org/jira/browse/INFRA-9221 > > > > > > with > > > > a few more examples. Can someone corroborate please (so INFRA > doesn't > > > > think I'm a nut-case)? > > > > > > > > Thanks. > > > > > > > > -- Lefty > > > > > > > > On Tue, Mar 3, 2015 at 4:12 AM, Lefty Leverenz < > > leftylever...@gmail.com> > > > > wrote: > > > > > > > >> Good call Alan, the messages are also missing from the archives so I > > > >> filed INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221 > >. > > > >> > > > >> By the way, we need to add issues@hive to the Mailing Lists > > > >> <http://hive.apache.org/mailing_lists.html> page. I'll file a Hive > > > JIRA > > > >> for that. > > > >> > > > >> -- Lefty > > > >> > > > >> On Thu, Feb 26, 2015 at 6:40 PM, Alan Gates <alanfga...@gmail.com> > > > wrote: > > > >> > > > >>> The issues list should be getting all JIRA notifications except > > CREATE, > > > >>> you shouldn't need to watch it. You can go look at the mail > archives > > > to > > > >>> see if the issue is with the list or on your end. If they aren't > all > > > >>> showing up in the list we should file an INFRA JIRA. > > > >>> > > > >>> Alan. > > > >>> > > > >>> Lefty Leverenz <leftylever...@gmail.com> > > > >>> February 26, 2015 at 14:03 > > > >>> Being a watcher could explain why I got the last two messages for > > > >>> HIVE-9731 > > > >>> <https://issues.apache.org/jira/browse/HIVE-9731> > > > >>> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc > > > >>> comment) > > > >>> but then why did I get all the messages before the commit, when I > > > wasn't > > > >>> a > > > >>> watcher yet? And I'm not a watcher for HIVE-9509 > > > >>> <https://issues.apache.org/jira/browse/HIVE-9509> > > > >>> <https://issues.apache.org/jira/browse/HIVE-9509> although I got > all > > > the > > > >>> messages up to Ashutosh's +1. > > > >>> > > > >>> This is something I can work around, but if others have the same > > > problem > > > >>> we > > > >>> might need to figure it out and get it fixed. > > > >>> > > > >>> -- Lefty > > > >>> > > > >>> > > > >>> Xuefu Zhang <xzh...@cloudera.com> > > > >>> February 26, 2015 at 13:12 > > > >>> I think you get subsequent messages only if you're a watcher. You > > > become > > > >>> a > > > >>> watcher after you comment or make changes for a JIRA. Is this your > > > case? > > > >>> > > > >>> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz > > > >>> <leftylever...@gmail.com> <leftylever...@gmail.com> > > > >>> > > > >>> Lefty Leverenz <leftylever...@gmail.com> > > > >>> February 26, 2015 at 13:05 > > > >>> Is it just me, or has JIRA email been flaky since the issues > mailing > > > list > > > >>> went into effect? > > > >>> > > > >>> For example, although I got a commit message for HIVE-9731 > > > >>> <https://issues.apache.org/jira/browse/HIVE-9731> > > > >>> <https://issues.apache.org/jira/browse/HIVE-9731> on the > > commits@hive > > > >>> mailing list, I didn't get either the change of Resolution or the > > > comment > > > >>> about the commit -- not on dev@hive nor on issues@hive. However I > > did > > > >>> get > > > >>> two subsequent messages on issues@hive when I added a TODOC1.2 > label > > > and > > > >>> doc comment. > > > >>> > > > >>> Another example: for HIVE-9509 > > > >>> <https://issues.apache.org/jira/browse/HIVE-9509> > > > >>> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit > > > >>> comment > > > >>> and Fix Version change for branch-1.0.1 on the issues@hive list > but > > > not > > > >>> the > > > >>> prior commit comment and Resolved - Fix Version for 1.2.0. > > > >>> > > > >>> Does anyone else have this problem? > > > >>> > > > >>> -- Lefty > > > >>> > > > >>> > > > >> > > > > > > > > > >
