Re: [DISCUSS] 1.10.2 release with reload4j

[Michael Wall]

I have some GC fixes I am working on that I would like to get into the
1.10.2 release.

https://github.com/apache/accumulo/issues/1377
https://github.com/apache/accumulo/issues/2322

On Thu, Feb 3, 2022 at 4:25 PM Christopher  wrote:
>
> That PR adds a new feature that is currently forward-incompatible in
> behavior with 1.10.0 and 1.10.1. New features are supposed to go into the
> next release, not patched into a bugfix on a release line that is intended
> to be stable long term.
>
> While our semver and LTM guidelines are just guidelines, and we can break
> them when we want/need to, I think the project is better served if that
> were rare. Every time we stretch/break those guidelines, we normalize
> violating them, and the resulting reduced confidence in our software's
> stability can create a feedback loop where the instability creates upgrade
> aversion, and the upgrade aversion increases the demand for backporting
> features. That's not sustainable, and it creates an unnecessary burden on
> the development side of things. I think having boundaries that resist
> against backporting features to stable branches creates a healthier
> relationship between the devs and the users.
>
> At this point, I'm a "soft" (not yet a veto) -1 to including that in 1.10.
> I could be convinced if it were A) 100% forward compatible with
> 1.10.0/1.10.1 *and* either B) there was greater consensus for it among the
> PMC or C) a good argument was made to justify adding the feature to a patch
> release [A&(B|C)].
>
> As for the schedule, I was thinking about creating a release candidate on
> Monday if there weren't any issues.
>
>
> On Thu, Feb 3, 2022 at 2:56 PM Dave Marion  wrote:
>
> > I'd like to try and include https://github.com/apache/accumulo/pull/2221.
> > A
> > little more testing needs to be done, do you have a schedule for the 1.10.2
> > release?
> >
> > On Thu, Feb 3, 2022 at 1:55 PM Christopher  wrote:
> >
> > > I'm interested in putting together a 1.10.2 release with the changes in
> > > https://github.com/apache/accumulo/pull/2458 so that the 1.10 line no
> > > longer requires log4j1, which has several vulnerabilities. Reload4j was
> > > created as a fork from log4j1 from Apache by its original author in order
> > > to provide a transition away from the CVE-riddled log4j1 jars.
> > >
> > > I'm sure we have a couple of other small bugfixes and improvements in
> > 1.10
> > > that could benefit from being released as well.
> > >
> > > If there are any objections or last-minute tweaks that should be included
> > > in 1.10.2, please discuss here.
> > >
> > > Thanks,
> > > Christopher
> > >
> >

Re: Accumulo quarterly report. Due 10/13/2021

[Michael Wall]

I think links 3 and 4 have a space that is breaking up the url.

Are we doing Hacktoberfest again this year?  Could mention that.

Thanks Ed

On Tue, Sep 28, 2021 at 2:50 PM Mike Miller  wrote:

> Other than the typo Dave found, LGTM.
>
> On Tue, Sep 28, 2021 at 9:01 AM Dave Marion  wrote:
>
> > Typo in last line, "Jira to Gibhub"
> >
> > On Tue, Sep 28, 2021 at 8:10 AM dev1  wrote:
> >
> > > The Accumulo community quarterly report for October is due Wednesday
> > > 10/13/2021.  The community decided to publicly prepare the report on
> the
> > > dev mailing list.  Below is the current draft.
> > >
> > > Ed Coleman
> > >
> > > --- Draft report ---
> > >
> > > ## Description:
> > > The Apache Accumulo is a robust, scalable, distributed key/value store
> > > with cell-based access control and customizable server-side processing.
> > >
> > > ## Issues:
> > > There are no new issues requiring board attention.
> > >
> > > The trademark issue with http:www.accumulodata.com is still open.
> > > Although the domain owner does not have access to the domain
> > registration,
> > > the domain appears to have automatically renewed, and the expiration is
> > now
> > > 2022-06-28.  Email from the private list discussing this are at [1],
> [2]
> > > and [3]. No action has been required and allowing the domain to expire
> > was
> > > deemed a viable option by Brand Management VP in Jan-2021 (private)[4]
> to
> > > minimize volunteer efforts.
> > >
> > > ## Membership Data:
> > > Apache Accumulo was founded 2012-03-21 (10 years ago)
> > > There are currently 40 committers and 40 PMC members in this project.
> > > The Committer-to-PMC ratio is 1:1.
> > >
> > > Community changes, past quarter:
> > > - Dominic Garguilo was added to the PMC on 2021-07-29
> > > - Dominic Garguilo was added as committer on 2021-07-29
> > >
> > > ## Project Activity:
> > > No new releases this reporting period. Last release dates:
> > > - accumulo-2.0.1 was released on 2020-12-24.
> > > - accumulo-1.10.1 was released on 2020-12-22.
> > >
> > > Project activity on the next release remains active with significant
> > > improvements to the current baseline. The remaining issues are being
> > > actively worked.
> > >
> > > ## Community Health:
> > > Overall community health is good and GitHub activity remains
> consistent.
> > >
> > > - Community participation remains healthy with discussions on the
> mailing
> > > lists and GitHub issues and pull-requests.
> > > - Accumulo continues to transition from Jira to GibHub issues. Jira
> > > activity reflects transition to using GitHub issues as obsolete issues
> > are
> > > closed and open issues are transitioned to GitHub issues.
> > >
> > >
> > > ## Links
> > > (private) [1]:
> > >
> >
> https://lists.apache.org/thread.html/r8c8ef5575b14accb6fc00d670764a313b91d76033f761c6e5c7eb29d%40%3Cprivate.accumulo.apache.org%3E
> > > (private) [2]:
> > >
> >
> https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
> > > (private) [3]:https://lists.apache.org/thread.html/rcc8c07db43222e0
> > > 8b9992fd739b8f24d18569ba9af3decfdb52c4a3e%40%
> > 3Cprivate.accumulo.apache.org
> > > %3E
> > > (private) [4]:https://lists.apache.org/thread.html/r408e3eed907e3ad
> > > 24a7c84b5247f51973a4c965c891b01215e45ee17%40%
> > 3Cprivate.accumulo.apache.org
> > > %3E
> > > ~
> > >
> >
>

Re: Re: Cannot run program "make"

[Michael Wall]

As much as I love make, I had the thought that maybe we shouldn't require
devs to have it installed to build and contribute to Accumulo.  Didn't see
an existing ticket, can write one tonight.

On Thu, Jul 1, 2021 at 11:10 AM Christine Buss 
wrote:

>
>
> Thanks so much! Yes that was the problem. And thanks to everyone else that
> took their time to help me.
>
>
> Gesendet: Donnerstag, 01. Juli 2021 um 16:38 Uhr
> Von: "Christopher" 
> An: "accumulo-dev" 
> Betreff: Re: Cannot run program "make"
> The error message looks like it's saying you don't have the `make`
> command installed on your machine. Based on the word "ubuntu" in your
> OpenJDK build version, I think you're on an Ubuntu-based machine. I
> found a StackOverflow answer (https://askubuntu.com/a/272020) that
> said you can do:
>
> sudo apt-get install build-essential
>
> On Thu, Jul 1, 2021 at 10:24 AM Christine Buss 
> wrote:
> >
> > the directory does exist:
> >
> >
> >
> accumulo/server/native/target/accumulo-native-2.1.0-SNAPSHOT/accumulo-native-2.1.0-SNAPSHOT$
> ls
> > javah LICENSE Makefile nativeMap NOTICE testNativeMap
> >
> > So why can the program "make" not be run?
> > What file or directory is missing?
> >
> >
> > Hello,
> > I am trying to learn how to contribute.
> > However I cloned and forked the accumulo repository.
> > When I run the command :
> > mvn clean verify -DskipITs
> > I am getting this Error:
> >
> > [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:3.0.0:exec (test-native-libs) on
> project accumulo-native: Command execution failed.: Cannot run program
> "make" (in directory
> "/home/christine/accumulo/server/native/target/accumulo-native-2.1.0-SNAPSHOT/accumulo-native-2.1.0-SNAPSHOT"):
> error=2, No such file or directory -> [Help 1]
> >
> > I can't find the reason. How can I solve this?
> > Thanks so much in advanve for any and all help.
> >
> >
> > I am using Java 11
> > >java -version
> > openjdk version "11.0.11" 2021-04-20
> > OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)
> > OpenJDK 64-Bit Server VM (build 11.0.11+9-Ubuntu-0ubuntu2.20.04, mixed
> mode, sharing)
> >
>

Re: Quarterly Community Report due July 14th

[Michael Wall]

Looks good to me Ed.  Formatting is a little off, maybe that is just my
gmail.  One typo in the Jira Activity section (66$ increase)

Mike



On Tue, Jun 29, 2021 at 8:42 AM  wrote:

> The Accumulo community has agreed to draft the quarterly reports using  the
> mailing list.  The report is due July 14th.
>
>
>
> --- current draft ---
>
>
>
> ## Description:
>
> The Apache Accumulo is a robust, scalable, distributed key/value store with
> cell-based access control and customizable server-side processing.
>
>
>
> ## Issues:
>
> There are no new issues requiring board attention.
>
>
>
> The trademark issue with http:www.accumulodata.com is still open. The
> domain
>
> appears to have expired on 2021-06-28 and has entered the grace period.
>
> Initial emails are at [1] and follow-up discussions at [2] No action has
> been
>
> required and allowing the domain to expire was deemed a viable option by
>
> Brand Management VP in Jan-2021 [3] to minimize volunteer efforts.
>
>
>
> ## Membership Data:
>
> Apache Accumulo was founded 2012-03-20 (9 years ago)
>
> There are currently 39 committers and 39 PMC members in this project.
>
> The Committer-to-PMC ratio is 1:1.
>
>
>
> Community changes, past quarter:
>
> - No new PMC members. Last addition was Karthick Narendran on 2021-01-21.
>
> - No new committers. Last addition was Karthick Narendran on 2021-01-22.
>
>
>
> ## Project Activity:
>
> No new releases this reporting period. Last release dates:
>
> - accumulo-2.0.1 was released on 2020-12-24.
>
> - accumulo-1.10.1 was released on 2020-12-22.
>
>
>
> Project activity on the next release remains active with significant
>
> improvements to the current baseline. The remaining issues are being
> actively
>
> worked.
>
>
>
> ## Community Health:
>
> Overall community health is good and GitHub activity remains consistent.
>
>
>
> - Increase in code contributor 81% (21 individuals) Driven by successful
>
>   participation in an Open Source Hackathon for Diversity (April 29-30) The
>
>   goal of the Hackathon was to kick-start involvement in the OSS community
> and
>
>   foster an environment for contributions and increase the diversity of the
>
>   OSS communities.  Overall, 6 new contributors successfully submitted code
>
>   contributions as part of the Hackathon.
>
> - Mailing list / GitHub activity.  The continued decreases in mailing list
>
>   activity reflect the community leveraging GitHub for community
>
>   collaboration.
>
> - Jira Activity (65 issues closed, 66$ increase). The increase in Jira
>
>   activity reflects transition to using GitHub issues as obsolete issues
> are
>
>   closed and open issues are transitioned to GitHub issues.
>
>
>
> ## Links
>
> [1]:
> https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999f
> c83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
>
> [2]:
> https://lists.apache.org/thread.html/rcc8c07db43222e08b9992fd739b8f24d18
> 569ba9af3decfdb52c4a3e%40%3Cprivate.accumulo.apache.org%3E
>
> [3]:
> https://lists.apache.org/thread.html/r408e3eed907e3ad24a7c84b5247f51973a
> 4c965c891b01215e45ee17%40%3Cprivate.accumulo.apache.org%3E
>
>

Re: Quarterly Community Report due 4/16.

[Michael Wall]

thoughts and comments inline

Mike

On Wed, Apr 14, 2021 at 5:10 PM Ed Coleman  wrote:

> The Accumulo community has agreed to draft the quaterly reports using the
> maling list.
>
> Sorry for the late notice on this - I had a vague notion that this was
> upcoming, but didn't realize until the first email today from Apache that
> it was due so soon.  Please, if you have any suggestions on Project
> Activity or Community Health - I find writing those sections particularly
> difficult. I go from things are fine to writing release notes and have
> trouble striking the right balance or even if I've included the relevant
> info.
>
> I'll incorporate comments as received and will submit on Friday to meet
> the deadline.
>
> Thanks.
>
> Ed Coleman
>
>  begin report 
>
> ## Description:
> The mission of Apache Accumulo is the creation and maintenance of software
> related to a robust, scalable, distributed key/value store with cell-based
> access control and customizable server-side processing.
>
> ## Issues:
> There are no new issues requiring board attention.
>
> The trademark issue with http:www.accumulodata.com is still open until the
> domain expires on 2021-06-28.  No action has been required and allowing the
> domain to expire was deemed a viable option by Brand Management VP to
> minimize
> volunteer efforts.
>

Probably want to link to the mailing list.  There are new boards members
that haven't seen this and those that have may not remember


>
> ## Membership Data:
> Apache Accumulo was founded 2012-03-21 (9 years ago)
> There are currently 39 committers and 39 PMC members in this project.
> The Committer-to-PMC ratio is 1:1.
>
> Community changes, past quarter:
> - Karthick Narendran was added to the PMC on 2021-01-22
> - Karthick Narendran was added as committer on 2021-01-22
>
> ## Project Activity:
> No new releases this reporting period. Last release dates:
> - accumulo-2.0.1 was released on 2020-12-24.
> - accumulo-1.10.1 was released on 2020-12-22.
>
> Project activity on the next release remains active with significant
> improvements to the current baseline. The remaining issues are being
> actively
> worked.  Highlights of changes this reporting period:
> - Removal of problematic process names to more inclusive terms.
> - Formalization of public API. Previously, certain internal classes were
>   necessary for users for some functions (iterators) - the interface has
> been
>   extracted and formally declared as part of the Accumulo public API.
> - Internal improvements handling threads and exceptions to improve
> reliability
> - Accumulo community agreed to participate in an upcoming OSS virtual
>   hackathon (April 29-30) The goal of the hackathon is to kick-start
>   involvement in the OSS community and foster an environment for
> contributions
>   and increase the diversity of the OSS communities.
>

I would highlight the diversity part, maybe using the subject from Billie's
email and start with something like
"- The Apache Accumulo PMC agreed to participate in an Open Source
Hackathon for Diversity..."
and then again include a link (https://tiny.cc/osshack)


> ## Community Health:
> Overall community health is good and activity remains consistent.
> Decreases
> in Jira (-65%) and dev mailing list activity (-53%) reflect the community
> transition to using GitHub as a focal point for development.  This is
> reflected in the increased activity for PRs and GotHub issues.
> - contributions from 14 individuals reflecting continued community
> involvement
>   and consistent participation.


s/GotHub/Github

Most of the time the board is going to say they don't want statistics from
issues and lists, they want our interpretation of those statistics.  When I
look at the reporter stats at
https://reporter.apache.org/wizard/statistics?accumulo, what I see is a
decrease in mailing list traffic to dev and user, but a marked increase in
commits, issues closed and a slight increase in PRs.  Clearly work is
happening, so the conversations must be in the github tickets and pull
requests.  I believe we setup that to go to notifications@accumulo.a.o, and
the reporter shows a 42% increase in that mailing list

Re: New committer/PMC member: Karthick Narendran

[Michael Wall]

congrats and welcome

On Fri, Jan 22, 2021 at 8:35 AM Jeffrey Manno  wrote:
>
> Congrats Karthick!
>
> On Fri, Jan 22, 2021 at 8:26 AM Tushar Dhadiwal 
> wrote:
>
> > Congratulations Karthick!
> >
> > On Fri, Jan 22, 2021 at 13:43, Christopher  wrote:
> >
> > > The Project Management Committee (PMC) for Apache Accumulo
> > > has invited Karthick Narendran to become a committer and PMC
> > > member and we are pleased to announce that they have accepted.
> > >
> > > Karthick has contributed several bug fixes and quality improvements
> > > to Accumulo, has written blog posts for our website, has been very
> > > helpful in engaging users with questions on various issues, and
> > > has helped in testing and providing feedback on release candidates.
> > > We are happy to have them contributing to the Accumulo
> > > community!
> > >
> > > Being a committer enables easier contribution to the
> > > project since there is no need to go via the patch
> > > submission process. This should enable better productivity.
> > > Being a PMC member enables assistance with the management
> > > and to guide the direction of the project.
> > >
> > > Welcome Karthick!
> > >
> >

Re: [DRAFT][REPORT] Apache Accumulo - Jan 2021

[Michael Wall]

Report LGTM.  Couple of thoughts.

1 - The github metrics as pasted are not useful to the board without
context.  Is this normal, is an increase in activity etc.
2 - Adding the name of contributors and their affiliations is new,
wonder if you would speak a little about your thoughts on this.

I agree with Christopher on not using github for this collaboration

Thanks Ed

On Thu, Jan 7, 2021 at 5:21 AM Ed Coleman  wrote:
>
> The Apache Accumulo PMC decided to draft its quarterly board reports on the 
> dev list. Here is a draft of our report which is due Wednesday, Jan 13, 1 
> week before the board meeting on Wednesday, Oct 20.
>
> To facilitate collaboration, this report is also a draft PR at 
> https://github.com/apache/accumulo-website/pull/256.
>
> Please let me know if you have any feedback and your thoughts on using PRs as 
> an approach for drafting these reports.
>
> Some more detailed metrics are at 
> https://reporter.apache.org/wizard/statistics?accumulo, which appears to 
> require a committer login.
>
> Ed Coleman
>
> 
> [REPORT] Apache Accumulo - January 2021
>
> ## Description:
>
> The Apache Accumulo sorted, distributed key/value store is a robust, scalable,
> high performance data storage system that features cell-based access control
> and customizable server-side processing. It is based on Google's BigTable
> design and is built on top of Apache Hadoop, Zookeeper, and Thrift.
>
> ## Issues:
>
> No change since last report, Oct 2020.  Still waiting for the owner of
> http://www.accumulodata.com to work with Amazon to reactive the account used 
> for
> hosting, so it can be pointed to https://accumulo.apache.org or shutdown. 
> Initial emails are at [1].
>
> ## Membership Data:
>
> Apache Accumulo was founded 2012-03-20 (9 years ago)
> There are currently 38 committers and 38 PMC members in this project.
> The Committer-to-PMC ratio is 1:1.
>
> Community changes, past quarter:
> - Jeffrey Manno was added to the PMC on 2020-11-01
> - Jeffrey Manno was added as committer on 2020-11-02
>
> ## Project Release Activity
>
> - accumulo-1.10.1 was released on 2020-12-22 [2]
> - accumulo-2.0.1 was released on 2020-12-24. [3]
>
> ## Project Activity:
>
> - 
> [CVE-2020-17533](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17533),
>  authenticated
>   users could perform certain administrative operations without having the 
> appropriate permissions,
>   was reported on 2020-12-09 and resolved with the accumulo-2.0.1 
> (2020-12-24) and accumulo-1.10.1
>   (2020-12-22) releases.
> - GitHub activity summary over the past quarter (as of 2021-01-07)
>   - 48 GitHub issues created / 44 issues closed.
>   - 120 GitHib PRs opened / 97 PRs closed.
>   - 145 commits from 18 committers.
>
> ## Community Health:
>
> - Mailing list participation and github issues are consistent.
> - 3 new contributors:
>   - Szabolcs Bukros [Cloudera](https://www.cloudera.com/)
>   - Seth Falco [Elypia](https://elypia.org/en-US/)
>   - Dominic Garguilo [Arctic Slope Regional Corp](https://www.asrc.com/)
>
> [1]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
> [2]:https://lists.apache.org/thread.html/r947a56c98d0a8e009fa93df3b19e93761bfea8b236f30fb0c21b1992%40%3Cuser.accumulo.apache.org%3E
> [3]:https://lists.apache.org/thread.html/r38b0920499c9c88de282ca783debb9fbb8dc8ed88f5fc0ad9981bf97%40%3Cuser.accumulo.apache.org%3E
>

Re: [ANNOUNCE] New PMC Chair and VP Apache Accumulo

[Michael Wall]

Thanks for the clarification and well wishes Niclas.

Mike

On Wed, Nov 18, 2020 at 4:40 PM Niclas Hedhman  wrote:
>
> A small nitpick; The PMC "recommends" and the Board "appoints", although in
> practical terms the Board approves the resolution laid before it, that
> records the transition of Chairs.
>
> Nevertheless; Well done for past and future work at Accumulo  (Chairs, PMC
> members and others)...
>
>
> Niclas
>
> On Wed, Nov 18, 2020 at 9:52 PM Michael Wall  wrote:
>
> > I am happy to announce the PMC recently voted Ed Coleman as the new
> > PMC Chair and Vice President of Apache Accumulo.  Ed was unanimously
> > approved at today's board meeting.
> >
> > I want to thank the community for your support over the past 3+ years.
> > It was a great experience and I learned a lot.
> >
> > Congrats Ed and may it be a prosperous journey.
> >
> > Mike
> >

[ANNOUNCE] New PMC Chair and VP Apache Accumulo

[Michael Wall]

I am happy to announce the PMC recently voted Ed Coleman as the new
PMC Chair and Vice President of Apache Accumulo.  Ed was unanimously
approved at today's board meeting.

I want to thank the community for your support over the past 3+ years.
It was a great experience and I learned a lot.

Congrats Ed and may it be a prosperous journey.

Mike

Re: New committer/PMC member: Jeffrey Manno

[Michael Wall]

Congratulations Jeff.

Mike

On Mon, Nov 2, 2020 at 2:40 PM Keebler, Holly I
 wrote:
>
> Congrats Jeff!!!
> 
> From: Laura Schanno 
> Sent: Monday, November 2, 2020 1:03 PM
> To: dev@accumulo.apache.org 
> Subject: Re: New committer/PMC member: Jeffrey Manno
>
> [External Email]
>
> --
> Congrats Jeff!
>
> Laura Schanno
> 
> Senior Software Engineer
> ASRC Federal
> M: 301-693-3583
> W: www.asrcfederal.com
>
>
> On Mon, Nov 2, 2020 at 12:48 PM Jeffrey Manno 
> wrote:
>
> > Thanks for the kind words, everyone!
> >
> > On Mon, Nov 2, 2020 at 12:32 PM karthick rn 
> > wrote:
> >
> > > Well done & Congrats Jeff!
> > >
> > > Thanks,
> > > Karthick
> > >
> > > On Mon, 2 Nov 2020 at 17:20, Owens, Mark  wrote:
> > >
> > > > Congratulations, Jeff!
> > > >
> > > > -Original Message-
> > > > From: Mike Miller 
> > > > Sent: Monday, November 2, 2020 11:50 AM
> > > > To: dev@accumulo.apache.org
> > > > Subject: New committer/PMC member: Jeffrey Manno
> > > >
> > > > The Project Management Committee (PMC) for Apache Accumulo has invited
> > > > Jeffrey Manno to become a committer/PMC member and we are pleased to
> > > > announce that he accepted.
> > > > In Accumulo, Jeff has fixed multiple bugs with the integration tests,
> > > made
> > > > a critical change to tablet location tracking and recently made
> > > > improvements to compex internal code.
> > > >
> > > > Please join me in welcoming Jeff.  Welcome Jeff!
> > > >
> > >
> >
>
> 
>
> The preceding message (including attachments) is covered by the Electronic 
> Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for 
> the person or entity to which it is addressed, and may contain information 
> that is confidential, protected by attorney-client or other privilege, or 
> otherwise protected from disclosure by law. If you are not the intended 
> recipient, you are hereby notified that any retention, dissemination, 
> distribution, or copying of this communication is strictly prohibited. Please 
> reply to the sender that you have received the message in error and destroy 
> the original message and all copies.

[REPORT] Apache Accumulo - Oct 2020

[Michael Wall]

## Description:
The Apache Accumulo sorted, distributed key/value store is a robust, scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:
We continue to track the redirect or shutdown of http://www.accumulodata.com.
The owner is still trying to reach an actual person at Amazon to figure out the
appropriate account that was used and reactivate it.  Initial emails are at [1].

## Membership Data:
Apache Accumulo was founded 2012-03-20 (9 years ago)
There are currently 37 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Arvind Shyamsundar on 2020-04-15.
- No new committers. Last addition was Arvind Shyamsundar on 2020-04-16.


## Project Activity:
- We completed our rename of our git branch to 'main' [2] and have begun
making changes to transition away from other potentially harmfully terminology
such as renaming out 'master' component to 'manager' [3].  This effort will
take some time and potentially several releases to complete.
- Apache Accumulo 1.10 was completed, our first LTM or Long Term Maintenance
release [4].

## Community Health:
- Christopher Tubbs updated all our projects [5] with the tag #hacktober to
increase community participation as part of Digital Ocean's Hacktoberfest [6].
Hard to track actual metrics as a result of this change, but we have added 5
new contributors since the last report and 2 in the past week [7].
- Mailing list particpation and github issues are at least consistent, perhaps
slightly increased.

[1]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
[2]:https://lists.apache.org/thread.html/ra4b972e27eef1d21a33b9e64a8be5ffd7bbef30b8cd965465e32bdc8%40%3Cdev.accumulo.apache.org%3E
[3]:https://lists.apache.org/thread.html/rb68e1264d49b98a06719c0954f5a99732d21fbbafd8030fa226a976e%40%3Cdev.accumulo.apache.org%3E
[4]:https://lists.apache.org/thread.html/ra5aed36cf93e62f3110ce94193a098c3710f26e64584f6e1d1f9bca3%40%3Cuser.accumulo.apache.org%3E
[5]:https://lists.apache.org/thread.html/ra5aed36cf93e62f3110ce94193a098c3710f26e64584f6e1d1f9bca3%40%3Cuser.accumulo.apache.org%3E
[6]:https://hacktoberfest.digitalocean.com/
[7]:https://github.com/apache/accumulo-website/commits/main/pages/people.md

Re: [DRAFT][REPORT] Apache Accumulo - Oct 2020

[Michael Wall]

Thanks Christopher.  I'll include your suggestions before I post it in
a few minutes.

Regarding the github actions, I haven't really been tracking it but I
did see 
https://lists.apache.org/thread.html/r1708881f52adbdae722afb8fea16b23325b739b254b60890e72375e1%40%3Cbuilds.apache.org%3E.
Ignore it if is unrelated.

Mike

On Mon, Oct 12, 2020 at 10:56 PM Christopher  wrote:
>
> Looks good, Mike. A few additional things that we did in the last quarter:
>
> * CI changes: moved to GitHub Actions (instead of Travis CI)
> * CI changes: moved Jenkins jobs from builds.apache.org to
> ci-builds.apache.org, with Slack integration
> * have begun making other changes to transition away from potentially
> harmful terminology, such as renaming our "master" component to
> "manager", but this will take time and probably several versions
> before it is eventually complete.
> * established a "Long Term Maintenance (LTM)" release strategy (I know
> you mentioned LTM above, but this expands on what it stands for).
>
> It might be nice to *try* to track "brand new contributors" as well.
> One easy thing is to check who has added themselves to our people
> page: I count 5 using `git log --since '3 months ago'
> pages/people.md`.
>
> On Mon, Oct 12, 2020 at 5:13 PM Michael Wall  wrote:
> >
> > The Apache Accumulo PMC decided to draft its quarterly board
> > reports on the dev list. Here is a draft of our report which is due
> > Wednesday, Oct 14, 1 week before the board meeting on
> > Wednesday, Oct 21. Please let me know if you have any feedback.
> >
> > Some more detailed metrics are at
> > https://reporter.apache.org/wizard/statistics?accumulo,
> > which appears to require a committer login.
> >
> > Mike
> >
> > 
> > [REPORT] Accumulo - Oct 2020
> >
> > ## Description:
> >
> > The Apache Accumulo sorted, distributed key/value store is a robust, 
> > scalable,
> > high performance data storage system that features cell-based access control
> > and customizable server-side processing. It is based on Google's BigTable
> > design and is built on top of Apache Hadoop, Zookeeper, and Thrift.
> >
> > ## Issues:
> >
> > Still waiting for the owner of http://www.accumulodata.com to work with 
> > Amazon
> > to reactive the account used for hosting so it can be pointed to
> > https://accumulo.apache.org or shutdown.  Initial emails are at [1].
> >
> > ## Membership Data:
> >
> > Apache Accumulo was founded 2012-03-20 (9 years ago)
> > There are currently 37 committers and 37 PMC members in this project.
> > The Committer-to-PMC ratio is 1:1.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Arvind Shyamsundar on 2020-04-15.
> > - No new committers. Last addition was Arvind Shyamsundar on 2020-04-16.
> >
> > ## Project Activity:
> >
> > - We completed our rename of our git branch to 'main' [2]
> > - Apache Accumulo 1.10 was completed, our first LTM release [3].
> >
> > ## Community Health:
> >
> > - Christopher Tubbs updated all our projects [4] with tag #hacktober to 
> > increase
> > community participation as part of Digital Ocean's Hacktoberfest [5].
> > - Mailing list particpation and github issues are consistent.
> >
> > [1]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
> > [2]:https://lists.apache.org/thread.html/ra4b972e27eef1d21a33b9e64a8be5ffd7bbef30b8cd965465e32bdc8%40%3Cdev.accumulo.apache.org%3E
> > [3]:https://lists.apache.org/thread.html/ra5aed36cf93e62f3110ce94193a098c3710f26e64584f6e1d1f9bca3%40%3Cuser.accumulo.apache.org%3E
> > [4]:https://lists.apache.org/thread.html/ra5aed36cf93e62f3110ce94193a098c3710f26e64584f6e1d1f9bca3%40%3Cuser.accumulo.apache.org%3E
> > [5]:https://hacktoberfest.digitalocean.com/

[DRAFT][REPORT] Apache Accumulo - Oct 2020

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
Wednesday, Oct 14, 1 week before the board meeting on
Wednesday, Oct 21. Please let me know if you have any feedback.

Some more detailed metrics are at
https://reporter.apache.org/wizard/statistics?accumulo,
which appears to require a committer login.

Mike


[REPORT] Accumulo - Oct 2020

## Description:

The Apache Accumulo sorted, distributed key/value store is a robust, scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

Still waiting for the owner of http://www.accumulodata.com to work with Amazon
to reactive the account used for hosting so it can be pointed to
https://accumulo.apache.org or shutdown.  Initial emails are at [1].

## Membership Data:

Apache Accumulo was founded 2012-03-20 (9 years ago)
There are currently 37 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Arvind Shyamsundar on 2020-04-15.
- No new committers. Last addition was Arvind Shyamsundar on 2020-04-16.

## Project Activity:

- We completed our rename of our git branch to 'main' [2]
- Apache Accumulo 1.10 was completed, our first LTM release [3].

## Community Health:

- Christopher Tubbs updated all our projects [4] with tag #hacktober to increase
community participation as part of Digital Ocean's Hacktoberfest [5].
- Mailing list particpation and github issues are consistent.

[1]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
[2]:https://lists.apache.org/thread.html/ra4b972e27eef1d21a33b9e64a8be5ffd7bbef30b8cd965465e32bdc8%40%3Cdev.accumulo.apache.org%3E
[3]:https://lists.apache.org/thread.html/ra5aed36cf93e62f3110ce94193a098c3710f26e64584f6e1d1f9bca3%40%3Cuser.accumulo.apache.org%3E
[4]:https://lists.apache.org/thread.html/ra5aed36cf93e62f3110ce94193a098c3710f26e64584f6e1d1f9bca3%40%3Cuser.accumulo.apache.org%3E
[5]:https://hacktoberfest.digitalocean.com/

Re: [DRAFT][ANNOUNCE] Apache Accumulo 1.10.0

[Michael Wall]

LGTM Christopher.  Thanks to everyone who contributed to this release.

On Sat, Sep 5, 2020 at 10:40 PM Christopher  wrote:
>
> Accumulo Devs,
>
> Please provide feedback on the following draft announcement for the
> 1.10 release. I expect to send it out on Tuesday, after updating the
> website, as discussed in my email earlier today.
>
> ***
> The Apache Accumulo project is pleased to announce the
> release of Apache Accumulo 1.10.0!
>
> Apache Accumulo 1.10.0 is a continuation of our 1.x series,
> and contains a few major bug fixes since 1.9.3, and several
> performance enhancements and other improvements. This
> release is expected to be the last of our 1.x versions,
> which can be used with either Hadoop 2 or Hadoop 3 (2.0.0
> and later versions require Hadoop 3). This version requires
> Java 8 or later.
>
> With this release, we have adopted a "Long Term Maintenance
> (LTM)" strategy, and this will be our first LTM release. As
> such, we intend to continue to provide 1.10.patch releases
> until a year after our next LTM release. However, no new
> features are expected to be developed on the 1.x series.
> Please see the release notes linked below for more details
> about our LTM strategy.
>
> This release is primarily intended for existing 1.x users
> who are not yet ready to upgrade to Accumulo 2.x, and want
> the latest bug fixes and performance improvements on a
> stable release series. All existing users of any prior 1.x
> version are encouraged to upgrade to this version as soon as
> possible to be on the most stable and best supported 1.x
> release available, or to upgrade to 2.0.0. 1.9 and earlier
> will no longer receive patch releases.
>
> New users are encouraged to consider starting with the
> existing 2.0.0 release instead of this release, as new
> development is expected to have a greater focus on the 2.x
> series moving forward. A new 2.x LTM release is also
> anticipated in the near future that will support upgrades
> from either 2.0.0 or from the latest 1.10 release available
> at the time of its release.
>
> ***
>
> Apache Accumulo® is a sorted, distributed key/value store
> that provides robust, scalable data storage and retrieval.
> With Apache Accumulo, users can store and manage large data
> sets across a cluster. Accumulo uses Apache Hadoop's HDFS to
> store its data and Apache ZooKeeper for consensus.
>
> This version is now available in Maven Central, and at:
> https://accumulo.apache.org/downloads/
>
> The full release notes can be viewed at:
> https://accumulo.apache.org/release/accumulo-1.10.0/
>
> --
> The Apache Accumulo Team

Re: [VOTE] "Manager" as new name for "master" service

[Michael Wall]

+1

On Mon, Aug 3, 2020 at 12:28 PM Billie Rinaldi  wrote:
>
> +1
>
> On Mon, Aug 3, 2020, 9:55 AM Christopher  wrote:
>
> > Based on the feedback on
> > https://github.com/apache/accumulo/issues/1638 , the following two
> > names have taken a clear lead in popularity for the new name for the
> > service currently known as "master": Manager and Coordinator. Of the
> > two, "Manager" is more popular by a very narrow margin.
> >
> > Please vote on whether to accept "Manager" as the new name for the
> > service currently known as "master" to work towards. Remember, we're
> > only voting on a target name at this time, not a migration path,
> > release plan, or any specific code changes. Those details can be
> > worked out in future actions.
> >
> > My vote is +1
> >
> > This vote will end after Thu 06 Aug 2020 02:00:00 PM UTC
> > (Thu 06 Aug 2020 10:00:00 AM EDT / Thu 06 Aug 2020 07:00:00 AM PDT)
> >
> > Thanks,
> >
> > Christopher
> >

Re: [LAZY][VOTE] change default branch to 'main'

[Michael Wall]

+1

On Mon, Aug 3, 2020 at 12:27 PM Billie Rinaldi  wrote:
>
> +1
>
> On Mon, Aug 3, 2020, 7:58 AM Christopher  wrote:
>
> > As a follow-up from our previous conversation on this issue, I have
> > already started a new branch named 'main' for my own future
> > contributions (that name because it appears to be the trending
> > alternative to 'master'), and for others who wish to use it as an
> > alternative to the current 'master' branch. I intend to discontinue
> > merging contributions (my own or others) to any 'master' branch owned
> > by the Accumulo PMC.
> >
> > In conjunction with that practice that I intend to follow, I would
> > like to propose the following as a lazy vote (by that, I mean I'm just
> > going to do it if nobody votes; if somebody objects, this turns into a
> > majority vote):
> >
> > 1. Submit an INFRA ticket to change the default branch to 'main' for
> > all our repos (I'll make sure one is created in each before then), and
> > 2. Update all our PRs against 'master' to be based on 'main' instead, and
> > 3. Delete the branch currently named 'master' (after the first two
> > steps and ensuring 'main' contains all of its commits)
> >
> > This effectively results in a rename of our primary development
> > branches. Upon completion of these steps, I would send an email
> > reminder to update any forks or local clones.
> >
> > This vote will end after Thu 06 Aug 2020 12:00:00 PM UTC
> > (Thu 06 Aug 2020 08:00:00 AM EDT / Thu 06 Aug 2020 05:00:00 AM PDT)
> >
> > Thanks,
> > Christopher
> >

[REPORT] Apache Accumulo July 2020

[Michael Wall]

I made one typo change, here is what I reported.



## Description:

The Apache Accumulo sorted, distributed key/value store is a robust, scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

The Apr report listed a discussion about a trademark issue at
http://www.accumulodata.com [1], but the link was incorrect. The owner is
actively working with Amazon to reactivate the account that managed that
domain and is awaiting a response. The site will either be shutdown or
repointed to https://accumulo.apache.org.

## Membership Data:

Apache Accumulo was founded 2012-03-20 (8 years ago) There are currently 37
committers and 37 PMC members in this project. The Committer-to-PMC ratio is
1:1.

Community changes, past quarter:
- Arvind Shyamsundar was added to the PMC on 2020-04-15
- Arvind Shyamsundar was added as committer on 2020-04-16

## Project Activity:

- No new releases this quarter, although 1.10 is still in the works.
The 1.10 releases will also be our first LTS release [2].
- There was a public chat on slack on May 13 [3].
- The PMC started a discussion about renaming the Accumulo Master server [4].

## Community Health:

- Activity in the community is consistent.  There is less activity on
the user mailing lists but more on the dev mailing list [5].

[1]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
[2]:https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
[3]:https://lists.apache.org/thread.html/r5c5e87461b6e0a6e6e904a8725b8604d29b6ba4d720ceef1039873af%40%3Cdev.accumulo.apache.org%3E
[4]:https://lists.apache.org/thread.html/redcea10fc3c705491b9792b2b0bafa12b9bd246b64394c4dea2d9be0%40%3Cdev.accumulo.apache.org%3E
[5]:https://reporter.apache.org/wizard/statistics?accumulo

[DRAFT][REPORT] Apache Accumulo July 2020

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
Wednesday, Jul 8, 1 week before the board meeting on
Wednesday, Jul 15. Please let me know if you have any feedback, I'll
submit it Wed morning.

Some more detailed metrics are at
https://reporter.apache.org/wizard/statistics?accumulo,
which appears to require a committer login.

Mike


[REPORT] Apache Accumulo July 2020

## Description:

The Apache Accumulo sorted, distributed key/value store is a robust, scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

The Apr report listed a discussion about a trademark issue at
http://www.accumulodata.com
[1], but the link was incorrect. The owner is actively working with
Amazon to reactive the
account that managed that domain and is awaiting a response. The site
will either be
shutdown or repointed to https://accumulo.apache.org.

## Membership Data:

Apache Accumulo was founded 2012-03-20 (8 years ago)
There are currently 37 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- Arvind Shyamsundar was added to the PMC on 2020-04-15
- Arvind Shyamsundar was added as committer on 2020-04-16

## Project Activity:

- No new releases this quarter, although 1.10 is still in the works.
The 1.10 releases
will also be our first LTS release [2].
- There was a public chat on slack on May 13 [3].
- The PMC started a discussion about renaming the Accumulo Master server [4].

## Community Health:

- Activity in the community is consistent.  There is less activity on
the user mailing lists but more on the dev mailing list [5].

[1]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
[2]:https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
[3]:https://lists.apache.org/thread.html/r5c5e87461b6e0a6e6e904a8725b8604d29b6ba4d720ceef1039873af%40%3Cdev.accumulo.apache.org%3E
[4]:https://lists.apache.org/thread.html/redcea10fc3c705491b9792b2b0bafa12b9bd246b64394c4dea2d9be0%40%3Cdev.accumulo.apache.org%3E
[5]:https://reporter.apache.org/wizard/statistics?accumulo

Re: [DISCUSS] Rename Accumulo master

[Michael Wall]

On Wed, Jun 17, 2020 at 3:44 PM Brian Loss  wrote:

> I agree—things have changed in the world since this was last discussed,
> and I think it’s time to make the change even though it will be disruptive.
> I support changing both the master branch and Accumulo master service names
> as well, and am willing to help out with the work to get it done.
>
> Mike, do we need to have some consensus on the names before the vote? That
> is, can the vote select a name from a list, or must it purely be a +/- vote
> for a specific choice? It might be better to have more discussion in this
> discuss thread (or in a ticket) before a vote is held


Brian, good question. I was thinking the name choice would be separate from
whether we should make the change.  But happy to have 1 vote instead of 2.

> .
>
> > On Jun 17, 2020, at 3:37 PM, Michael Wall  wrote:
> >
> > I support changing both the name of the Accumulo master service and the
> > master branch name.  Should we start a vote?  Maybe we need to understand
> > the full scope of what will be required before we can do that.  Billie,
> do
> > you want to start the ticket you mentioned?
> >
> > On Wed, Jun 17, 2020 at 3:18 PM Owens, Mark 
> wrote:
> >
> >> Sounds like GitHub is considering changing 'master' to 'main'. That
> could
> >> also be a possibility.
> >>
> >> -Original Message-
> >> From: Billie Rinaldi 
> >> Sent: Wednesday, June 17, 2020 3:07 PM
> >> To: Accumulo Dev List 
> >> Subject: [DISCUSS] Rename Accumulo master
> >>
> >> Hi Accumulo folks! I would like to start a discussion about renaming the
> >> Accumulo master. Previous discussions were held a few years ago [1].
> Some
> >> things have changed since we started that discussion, in the world and
> in
> >> our project governance, so I think it is worth revisiting this topic.
> >>
> >> If people agree that a rename would be worthwhile, we can start
> >> identifying the many changes that would need to be made (probably a
> GitHub
> >> issue would be a good place for that). This will be a big change and I
> am
> >> happy to help work on it. If anyone else is interested in helping out
> too,
> >> I think we should be able to break the work down into several discrete
> >> tasks.
> >>
> >> I believe the best replacement names we came up with on the original
> >> ticket were Coordinator and Conductor. I also wanted to suggest another
> >> possibility that I don't think we considered: Admin / AdminServer.
> Admin is
> >> generic, but at least it's short. Feel free to share your thoughts and
> >> other ideas, if you have them.
> >>
> >> Billie
> >>
> >> [1]: https://issues.apache.org/jira/browse/ACCUMULO-2844
> >>
>
>

Re: [DISCUSS] Rename Accumulo master

[Michael Wall]

I support changing both the name of the Accumulo master service and the
master branch name.  Should we start a vote?  Maybe we need to understand
the full scope of what will be required before we can do that.  Billie, do
you want to start the ticket you mentioned?

On Wed, Jun 17, 2020 at 3:18 PM Owens, Mark  wrote:

> Sounds like GitHub is considering changing 'master' to 'main'. That could
> also be a possibility.
>
> -Original Message-
> From: Billie Rinaldi 
> Sent: Wednesday, June 17, 2020 3:07 PM
> To: Accumulo Dev List 
> Subject: [DISCUSS] Rename Accumulo master
>
> Hi Accumulo folks! I would like to start a discussion about renaming the
> Accumulo master. Previous discussions were held a few years ago [1]. Some
> things have changed since we started that discussion, in the world and in
> our project governance, so I think it is worth revisiting this topic.
>
> If people agree that a rename would be worthwhile, we can start
> identifying the many changes that would need to be made (probably a GitHub
> issue would be a good place for that). This will be a big change and I am
> happy to help work on it. If anyone else is interested in helping out too,
> I think we should be able to break the work down into several discrete
> tasks.
>
> I believe the best replacement names we came up with on the original
> ticket were Coordinator and Conductor. I also wanted to suggest another
> possibility that I don't think we considered: Admin / AdminServer. Admin is
> generic, but at least it's short. Feel free to share your thoughts and
> other ideas, if you have them.
>
> Billie
>
> [1]: https://issues.apache.org/jira/browse/ACCUMULO-2844
>

Re: FileSystem API (was: Slack call notes)

[Michael Wall]

Yeah, I agree the docs are not clear.  I didn't actually run it myself,
just took a peek at the source at
https://github.com/minio/minio/blob/master/cmd/gateway/hdfs/gateway-hdfs.go

On Tue, Apr 28, 2020 at 9:43 PM Christopher  wrote:

> The page seemed to describe an S3 gateway, as well as a separate HDFS
> gateway, but I only took a superficial reading of the docs, and did
> not look at the code at all.
>
> On Tue, Apr 28, 2020 at 4:19 PM Michael Wall  wrote:
> >
> > That HDFS gateway appears to be an S3 layer on top of HDFS, not and HDFS
> > layer on top of S3/Minio.  It allows you to write code to use Minio and
> > pull existing data from HDFS as you migrate it into Minio.  As far as I
> can
> > tell, it would not work without changes to Accumulo.
> >
> > In the next week or so I'll look at actually putting interfaces around
> the
> > HDFS interactions for RFiles and WALs as a first step.  I will report
> back
> > with my findings and hopefully some code.
> >
> > Thanks
> >
> > Mike
> >
> > On Fri, Apr 24, 2020 at 10:32 PM Christopher 
> wrote:
> >
> > > I'm not familiar with it, but the website says it can replace HDFS.
> > > There appears to be an "HDFS Gateway"
> > > (https://github.com/minio/minio/blob/master/docs/gateway/hdfs.md) that
> > > might be useful. At a glance, it looks like no abstraction is needed
> > > in Accumulo code is needed for it... you just run the gateway and
> > > Accumulo believes it is using HDFS, but it is really using MinIO
> > > instead.
> > >
> > > There also might be a Hadoop FileSystem implementation for it to use
> > > it directly without a Gateway, but I didn't have any luck with a quick
> > > search for one.
> > >
> > > In either case, there shouldn't need to be any changes to Accumulo
> itself.
> > >
> > > If changes to Accumulo do become necessary (or desired), I'd be
> > > interested in collaborating on that part. If it's just a matter of
> > > trying it with the Gateway or existing Hadoop FileSystem
> > > implementation, I'd also be interested in testing any step-by-step
> > > HOWTO guides somebody might want to write as a blog post.
> > >
> > > On Fri, Apr 24, 2020 at 11:20 AM Mike Miller 
> wrote:
> > > >
> > > > I have no experience with MinIO but would be interested in learning
> more
> > > > and collaborating.
> > > >
> > > > On Fri, Apr 24, 2020 at 10:57 AM Michael Wall 
> wrote:
> > > >
> > > > > Resurrecting this thread on the File System API.  I have been
> thinking
> > > > > about giving Minio [1] a try for both WALs and RFiles.  Seems to me
> > > like
> > > > > step one is to abstract internal interfaces for both targeted
> against
> > > 2.1?
> > > > > Couple of questions
> > > > >
> > > > > 1 - Anyone have experience with minio?
> > > > > 2 - Anyone interested in collaborating?  Thinking anything from
> > > providing
> > > > > input to helping to test once we get a prototype to actually doing
> some
> > > > > development.
> > > > >
> > > > > Thanks, hope everyone is staying safe and healthy.
> > > > >
> > > > > [1] - https://min.io/
> > > > >
> > > > > On Wed, Mar 25, 2020 at 6:08 PM Christopher 
> > > wrote:
> > > > >
> > > > > > Only 705 across 280 files, if you exclude Text, though :)
> > > > > >
> > > > > > grep -rP 'org[.]apache[.]hadoop(?![.]io[.]Text)'
> --include='*.java' *
> > > > > > | grep -v test/ | wc -l
> > > > > >
> > > > > > On Wed, Mar 25, 2020 at 3:34 PM Mike Miller 
> > > wrote:
> > > > > > >
> > > > > > > I think we have come a long way removing any external types
> from
> > > the
> > > > > API,
> > > > > > > for reasons other than de-coupling from Hadoop.  While we don't
> > > have
> > > > > many
> > > > > > > dependencies on the other components of Hadoop, we are still
> very
> > > > > tightly
> > > > > > > coupled to HDFS.
> > > > > > > For example, some quick grep'ing of the code shows:
> > > > > > > "grep -r "import org.apache.hadoop" --include=*.java * | wc -l"
> > > > > > >

Re: FileSystem API (was: Slack call notes)

[Michael Wall]

That HDFS gateway appears to be an S3 layer on top of HDFS, not and HDFS
layer on top of S3/Minio.  It allows you to write code to use Minio and
pull existing data from HDFS as you migrate it into Minio.  As far as I can
tell, it would not work without changes to Accumulo.

In the next week or so I'll look at actually putting interfaces around the
HDFS interactions for RFiles and WALs as a first step.  I will report back
with my findings and hopefully some code.

Thanks

Mike

On Fri, Apr 24, 2020 at 10:32 PM Christopher  wrote:

> I'm not familiar with it, but the website says it can replace HDFS.
> There appears to be an "HDFS Gateway"
> (https://github.com/minio/minio/blob/master/docs/gateway/hdfs.md) that
> might be useful. At a glance, it looks like no abstraction is needed
> in Accumulo code is needed for it... you just run the gateway and
> Accumulo believes it is using HDFS, but it is really using MinIO
> instead.
>
> There also might be a Hadoop FileSystem implementation for it to use
> it directly without a Gateway, but I didn't have any luck with a quick
> search for one.
>
> In either case, there shouldn't need to be any changes to Accumulo itself.
>
> If changes to Accumulo do become necessary (or desired), I'd be
> interested in collaborating on that part. If it's just a matter of
> trying it with the Gateway or existing Hadoop FileSystem
> implementation, I'd also be interested in testing any step-by-step
> HOWTO guides somebody might want to write as a blog post.
>
> On Fri, Apr 24, 2020 at 11:20 AM Mike Miller  wrote:
> >
> > I have no experience with MinIO but would be interested in learning more
> > and collaborating.
> >
> > On Fri, Apr 24, 2020 at 10:57 AM Michael Wall  wrote:
> >
> > > Resurrecting this thread on the File System API.  I have been thinking
> > > about giving Minio [1] a try for both WALs and RFiles.  Seems to me
> like
> > > step one is to abstract internal interfaces for both targeted against
> 2.1?
> > > Couple of questions
> > >
> > > 1 - Anyone have experience with minio?
> > > 2 - Anyone interested in collaborating?  Thinking anything from
> providing
> > > input to helping to test once we get a prototype to actually doing some
> > > development.
> > >
> > > Thanks, hope everyone is staying safe and healthy.
> > >
> > > [1] - https://min.io/
> > >
> > > On Wed, Mar 25, 2020 at 6:08 PM Christopher 
> wrote:
> > >
> > > > Only 705 across 280 files, if you exclude Text, though :)
> > > >
> > > > grep -rP 'org[.]apache[.]hadoop(?![.]io[.]Text)' --include='*.java' *
> > > > | grep -v test/ | wc -l
> > > >
> > > > On Wed, Mar 25, 2020 at 3:34 PM Mike Miller 
> wrote:
> > > > >
> > > > > I think we have come a long way removing any external types from
> the
> > > API,
> > > > > for reasons other than de-coupling from Hadoop.  While we don't
> have
> > > many
> > > > > dependencies on the other components of Hadoop, we are still very
> > > tightly
> > > > > coupled to HDFS.
> > > > > For example, some quick grep'ing of the code shows:
> > > > > "grep -r "import org.apache.hadoop" --include=*.java * | wc -l"
> > > > > 1734
> > > > > Without tests it is slightly more feasible...
> > > > > grep -r "import org.apache.hadoop" --include=*.java * | grep -v
> "test"
> > > |
> > > > wc
> > > > > -l
> > > > > 858
> > > > >
> > > > >
> > > > > On Wed, Mar 25, 2020 at 3:19 PM David Mollitor 
> > > > wrote:
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I too have been thinking about this for a pet project.  There is
> > > > already
> > > > > > Apache Commons VFS that, with some investment, could probably
> serve
> > > all
> > > > > > these requirements.
> > > > > >
> > > > > > On Wed, Mar 25, 2020, 3:16 PM Christopher 
> > > wrote:
> > > > > >
> > > > > > > (Forking this thread, as it's a distinct topic)
> > > > > > >
> > > > > > > I've thought about it. The idea has driven me to try to reduce
> our
> > > > use
> > > > > > > of Hadoop-specific code, and to isolate Hadoop-specific stuff
> > > behind
> > &

Re: FileSystem API (was: Slack call notes)

[Michael Wall]

Resurrecting this thread on the File System API.  I have been thinking
about giving Minio [1] a try for both WALs and RFiles.  Seems to me like
step one is to abstract internal interfaces for both targeted against 2.1?
Couple of questions

1 - Anyone have experience with minio?
2 - Anyone interested in collaborating?  Thinking anything from providing
input to helping to test once we get a prototype to actually doing some
development.

Thanks, hope everyone is staying safe and healthy.

[1] - https://min.io/

On Wed, Mar 25, 2020 at 6:08 PM Christopher  wrote:

> Only 705 across 280 files, if you exclude Text, though :)
>
> grep -rP 'org[.]apache[.]hadoop(?![.]io[.]Text)' --include='*.java' *
> | grep -v test/ | wc -l
>
> On Wed, Mar 25, 2020 at 3:34 PM Mike Miller  wrote:
> >
> > I think we have come a long way removing any external types from the API,
> > for reasons other than de-coupling from Hadoop.  While we don't have many
> > dependencies on the other components of Hadoop, we are still very tightly
> > coupled to HDFS.
> > For example, some quick grep'ing of the code shows:
> > "grep -r "import org.apache.hadoop" --include=*.java * | wc -l"
> > 1734
> > Without tests it is slightly more feasible...
> > grep -r "import org.apache.hadoop" --include=*.java * | grep -v "test" |
> wc
> > -l
> > 858
> >
> >
> > On Wed, Mar 25, 2020 at 3:19 PM David Mollitor 
> wrote:
> >
> > > Hello,
> > >
> > > I too have been thinking about this for a pet project.  There is
> already
> > > Apache Commons VFS that, with some investment, could probably serve all
> > > these requirements.
> > >
> > > On Wed, Mar 25, 2020, 3:16 PM Christopher  wrote:
> > >
> > > > (Forking this thread, as it's a distinct topic)
> > > >
> > > > I've thought about it. The idea has driven me to try to reduce our
> use
> > > > of Hadoop-specific code, and to isolate Hadoop-specific stuff behind
> > > > some abstraction, wherever possible. Though, I'll admit, we're
> nowhere
> > > > close to where we'd want to be to be fully decoupled from Hadoop.
> > > >
> > > > I've also been looking a lot at our VolumeManager code lately, to try
> > > > to improve it a bit, and to create better abstractions for Volumes,
> > > > that could aid future work in this area.
> > > >
> > > > But, I haven't directly been working on new FileSystem API
> > > > abstraction... just trying to lay some groundwork for that
> possibility
> > > > in future.
> > > >
> > > > It'd be nice to get to a point where we have a Hadoop-specific
> > > > implementation isolated to a jar that can be swapped out at runtime
> > > > for other file system implementations, as needed. I see that as a
> > > > somewhat long-way off.
> > > >
> > > > On Wed, Mar 25, 2020 at 2:08 PM  wrote:
> > > > >
> > > > >
> > > > >   I couldn't make the call today, but am curious if anyone has
> > > > previously brought up creating a FileSystem API for Accumulo so that
> we
> > > > could use implementations other than Hadoop. I realize that Hadoop
> > > provides
> > > > implementations for things other than HDFS but that doesn't
> necessarily
> > > > mean that all filesystem implementations are covered.
> > > > >
> > > > > -Original Message-
> > > > > From: Christopher 
> > > > > Sent: Wednesday, March 25, 2020 1:45 PM
> > > > > To: accumulo-dev 
> > > > > Subject: Slack call notes
> > > > >
> > > > > Several committers/contributors in the community joined a call in
> Slack
> > > > on Wednesday, at 1130-1230, New York (Eastern) time. Here are my
> notes of
> > > > the call. Please feel free to add to them.
> > > > >
> > > > > I shared the overall philosophy and backstory to some of the script
> > > > improvements in 2.x to help guide current/future work on the scripts.
> > > > >
> > > > > * bin/accumulo is inspired by old jpackage.org standards which are
> > > > still in use in RPM macros for Java packaging in Fedora/RHEL/etc.
> The key
> > > > idea is that scripts are simple... set up environment (class path,
> etc.),
> > > > locate java, and exec a single process with the provided args.
> > > > > * bin/accumulo-service is inspired by old SysVInit scripts for
> > > > start/stop/restart/status of a single service
> > > > > * behavior of bin/accumulo and bin/accumulo-service can be
> manipulated
> > > > through launch environment
> > > > > * bin/accumulo-cluster uses bin/accumulo-service, and is provided
> as a
> > > > simple, out-of-the-box cluster management tool
> > > > > * bin/accumulo-cluster and bin/accumulo-service are replaceable;
> they
> > > > are useful for out-of-the-box, but one would expect them to be
> > > unnecessary
> > > > if using systemd, or a vendor-provided cluster management system
> > > > > * we discussed possibly moving bin/accumulo-cluster and
> > > > bin/accumulo-service to contrib/ in the tarball, or some subdir of
> bin/,
> > > > but it was suggested to not make too many disruptive changes there
> > > > > * we discussed the possibility of adding a config file for
> > > > 

Re: accumulo-docker

[Michael Wall]

Thanks Brian, you bring up a good point on the latest tag.  I would be fine
with this proposal as well.

On Mon, Apr 20, 2020 at 9:41 AM Brian Loss  wrote:

> Another possibility is to push all of that extra info into the tag. E.g.,
>
> accumulo:1.9.3-1
> accumulo:2.0.0-1
> accumulo:2.0.0-1-alpine
>
> That seems to be the basic pattern used by projects such as openjdk. It’s
> true that you couldn’t then have a latest tag for Accumulo 1.9.3 and
> Accumulo 2.0, but I don’t believe that’s the intent of the latest tag. I
> believe that’s supposed to be the single latest available stable release so
> that if I did “docker pull accumulo” I’d get the current version.
>
> > On Apr 20, 2020, at 9:20 AM, Michael Wall  wrote:
> >
> > Just now following this.  Looking at dockerhub, many project do something
> > like accumulo:1.9.3, accumulo:2.0.0 and then
> > have a tag accumulo:latest that is the latest version.  So if you run
> > `docker pull accumulo`, it uses
> > latest by default.  I have always found this a little lacking because if
> > you need to update the Dockerfile for say
> > accumulo:1.9.3, you must overwrite the previous images.  If someone used
> > that prior image as a base image, it is
> > then really hard to recreate their image from scratch if they clear out
> > their docker cache.
> >
> > Numbers are free, so another option is to do something thing like
> > accumulo-1.9.3:1, accumulo-2.0.0:4 and tag
> > accumulo-2.0.0:latest with the last version of accumulo-2.0.0.  This is
> > what I tend to do.
> >
> > If we wanted to provide images running on different OS's, we might also
> > consider names like accumulo-1.9.3-centos7:1
> > and accumulo-2.0.0-ubuntu16:2.  Not sure that is necessary.
> >
> > Mike
> >
> > On Mon, Apr 20, 2020 at 9:03 AM Vincent Russell <
> vincent.russ...@gmail.com>
> > wrote:
> >
> >> Most projects, that I've seen anyway,  keep their Dockerfile in the same
> >> repository as their source code so that it's versioned with the software
> >> that its loading.
> >>
> >> Please consider doing this for accumulo.
> >>
> >> Thanks,
> >> Vincent
> >>
> >> On Mon, Apr 20, 2020 at 8:05 AM karthick rn <
> karthick.narend...@gmail.com>
> >> wrote:
> >>
> >>> Hi Christopher,
> >>>
> >>>> Before we vote, I'd like to us to have some idea of how we will label
> >>>> versions of accumulo-docker releases. Any opinions?
> >>> Could we label the 'accumulo-docker' versions based on the Accumulo
> >> version
> >>> used in it? I thought it would be simple by just relying on Accumulo
> >>> version & not having to maintain a separate versioning for
> >>> 'accumulo-docker'. However, I'm not sure if this would be an acceptable
> >>> practice in Apache, others might chime if they have any ideas?
> >>>
> >>> Found this JIRA https://issues.apache.org/jira/browse/INFRA-17518,
> that
> >>> suggests 2 options for publishing images to dockerhub, the 2nd option
> >> looks
> >>> more apt for our case & like you mentioned, we'll have to engage INFRA
> &
> >>> start a discussion on "bui...@apache.org".
> >>>
> >>> Thanks,
> >>> Karthick
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Fri, 10 Apr 2020 at 13:49, Ed Coleman  wrote:
> >>>
> >>>> Does the NiFi community have an established process or procedure that
> >>> they
> >>>> follow that we could copy as a guide?  (
> >>>> https://hub.docker.com/r/apache/nifi/)
> >>>>
> >>>> -Original Message-
> >>>> From: Christopher [mailto:ctubb...@apache.org]
> >>>> Sent: Friday, April 10, 2020 12:23 AM
> >>>> To: accumulo-dev 
> >>>> Subject: Re: accumulo-docker
> >>>>
> >>>> First, I don't know much about how Docker or Dockerhub works. I don't
> >> use
> >>>> docker often, and have never used Dockerhub. So that is a gap in my
> >>>> knowledge that will need to be filled by somebody else's expertise.
> >>>>
> >>>> Before we distribute accumulo-docker code, we need to vote on a
> >> release.
> >>>> Any PMC member can prepare a release candidate and initiate that vote.
> >>&g

Re: accumulo-docker

[Michael Wall]

Just now following this.  Looking at dockerhub, many project do something
like accumulo:1.9.3, accumulo:2.0.0 and then
have a tag accumulo:latest that is the latest version.  So if you run
`docker pull accumulo`, it uses
latest by default.  I have always found this a little lacking because if
you need to update the Dockerfile for say
accumulo:1.9.3, you must overwrite the previous images.  If someone used
that prior image as a base image, it is
then really hard to recreate their image from scratch if they clear out
their docker cache.

Numbers are free, so another option is to do something thing like
accumulo-1.9.3:1, accumulo-2.0.0:4 and tag
accumulo-2.0.0:latest with the last version of accumulo-2.0.0.  This is
what I tend to do.

If we wanted to provide images running on different OS's, we might also
consider names like accumulo-1.9.3-centos7:1
and accumulo-2.0.0-ubuntu16:2.  Not sure that is necessary.

Mike

On Mon, Apr 20, 2020 at 9:03 AM Vincent Russell 
wrote:

> Most projects, that I've seen anyway,  keep their Dockerfile in the same
> repository as their source code so that it's versioned with the software
> that its loading.
>
> Please consider doing this for accumulo.
>
> Thanks,
> Vincent
>
> On Mon, Apr 20, 2020 at 8:05 AM karthick rn 
> wrote:
>
> > Hi Christopher,
> >
> > > Before we vote, I'd like to us to have some idea of how we will label
> > > versions of accumulo-docker releases. Any opinions?
> > Could we label the 'accumulo-docker' versions based on the Accumulo
> version
> > used in it? I thought it would be simple by just relying on Accumulo
> > version & not having to maintain a separate versioning for
> > 'accumulo-docker'. However, I'm not sure if this would be an acceptable
> > practice in Apache, others might chime if they have any ideas?
> >
> > Found this JIRA https://issues.apache.org/jira/browse/INFRA-17518, that
> > suggests 2 options for publishing images to dockerhub, the 2nd option
> looks
> > more apt for our case & like you mentioned, we'll have to engage INFRA &
> > start a discussion on "bui...@apache.org".
> >
> > Thanks,
> > Karthick
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Fri, 10 Apr 2020 at 13:49, Ed Coleman  wrote:
> >
> > > Does the NiFi community have an established process or procedure that
> > they
> > > follow that we could copy as a guide?  (
> > > https://hub.docker.com/r/apache/nifi/)
> > >
> > > -Original Message-
> > > From: Christopher [mailto:ctubb...@apache.org]
> > > Sent: Friday, April 10, 2020 12:23 AM
> > > To: accumulo-dev 
> > > Subject: Re: accumulo-docker
> > >
> > > First, I don't know much about how Docker or Dockerhub works. I don't
> use
> > > docker often, and have never used Dockerhub. So that is a gap in my
> > > knowledge that will need to be filled by somebody else's expertise.
> > >
> > > Before we distribute accumulo-docker code, we need to vote on a
> release.
> > > Any PMC member can prepare a release candidate and initiate that vote.
> > > (I'm willing to do it, once we figure out how the distribution should
> > go.)
> > >
> > > Before we vote, I'd like to us to have some idea of how we will label
> > > versions of accumulo-docker releases. Any opinions?
> > >
> > > After we figure out release versioning and vote, I don't know what
> comes
> > > next.
> > >
> > > I believe INFRA has an "organization" for Apache on Dockerhub... but
> we'd
> > > probably have to put in a ticket.
> > > A search on JIRA shows some previous similar issues:
> > >
> > >
> >
> https://issues.apache.org/jira/browse/INFRA-18167?jql=project%3DINFRA%20AND%20text~dockerhub
> > >
> > > Those might be a good starting point for researching how to publish.
> > >
> > > On Thu, Apr 9, 2020 at 2:25 PM karthick rn <
> karthick.narend...@gmail.com
> > >
> > > wrote:
> > > >
> > > > Hi Christopher,
> > > >
> > > > Following the conversation from PR#12
> > > > , I'm interested
> to
> > > > drive this forward and publish the image to Dockerhub. Let me know
> how
> > > > do I get in touch with INFRA?
> > > >
> > > > Thanks,
> > > > Karthick
> > >
> > >
> >
>

Re: New committer/PMC member: Arvind Shyamsundar

[Michael Wall]

Congrats and welcome Arvind.

Mike

On Thu, Apr 16, 2020 at 2:33 PM Billie Rinaldi 
wrote:

> Welcome, Arvind! Thanks for your contributions.
>
> Billie
>
> On Thu, Apr 16, 2020 at 2:32 PM Keith Turner  wrote:
>
> > The Apache Accumulo Project Management Committee (PMC) invited Arvind
> > Shyamsundar to become a committer/PMC member and we are pleased to
> > announce that he accepted.  Arvind has fixed multiple bugs in Accumulo
> > recently and added support for running multiple tservers per node to
> > the scripts.
> >
> > Welcome Arvind!
> >
>

[REPORT] Apache Accumulo Apr 2020

[Michael Wall]

## Description:
The Apache Accumulo sorted, distributed key/value store is a robust,
scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:
The Oct report listed a discussion about a trademark issue at
http://www.accumulodata.com [1]. The owner has acknowledged and agreed to
repoint to https://accumulo.apache.org.  The PMC is waiting on that change
by
the owner.

## Membership Data:
Apache Accumulo was founded 2012-03-20 (8 years ago)
There are currently 36 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Holly Keebler on 2019-08-08.
- No new committers. Last addition was Holly Keebler on 2019-08-09.
- Ongoing discussion about adding a new member.

## Project Activity:
- No new releases this quarter, although 1.10 is still in the works. The
1.10
  releases will also be our first LTS release [2].
- There was work done to improve the website generation using github actions
  [3].
- The monthly "Hack Day" continues in Columbia MD. There was nothing of note
  posted from the meetings in Jan[4] and Feb[5]. The March Hack Day had a
few
  notes[6].
- Some of the developers participated in a slack call[7] on Mar 24, notes
were
  written to the mailing list[8].

## Community Health:
- Activity in the community is consistent.  There is less activity on the
  mailing lists but more on github issues and and PRs [9].

[1]:
https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org
[2]:
https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
[3]:
https://lists.apache.org/thread.html/rc9dacacb7bafd1d2289cdfa67ab31d5f4c0c1c47eb1afc905d62ef77%40%3Cdev.accumulo.apache.org%3E
[4]:
https://lists.apache.org/thread.html/r873b186740d0c1c078edafbf0af4fab0158f85aabc74348cfdf8acc8%40%3Cdev.accumulo.apache.org%3E
[5]:
https://lists.apache.org/thread.html/r0c43fdc622d446a0f5cbec79085de86e8ad098a173a73739e86c98fd%40%3Cdev.accumulo.apache.org%3E
[6]:
https://lists.apache.org/thread.html/r3753f5ee8caba67fc00a4a6af36c75018349085f9c5fd7892ba7d7aa%40%3Cdev.accumulo.apache.org%3E
[7]:
https://lists.apache.org/thread.html/r494ba26ee4e8f16fc1b865bb363f3e4a9035738d8c49f10505d6e4f5%40%3Cdev.accumulo.apache.org%3E
[8]:
https://lists.apache.org/thread.html/r2ae8f3375fc2c2e36b11e576456b8697f29057c06d0bf89c6e165d14%40%3Cdev.accumulo.apache.org%3E
[9]:https://reporter.apache.org/wizard/statistics?accumulo

Re: [REPORT][DRAFT] Apache Accumulo April 2020

[Michael Wall]

Thanks for the review Josh and Marc.  I will make the adjustment.
Submitting tomorrow morning so if anyone else has feedback let me know.

Mike

On Mon, Apr 6, 2020 at 8:36 PM Marc  wrote:

> Agreed with Josh, but looks good otherwise. thanks, Michael!
>
> On Mon, Apr 6, 2020 at 8:16 PM Josh Elser  wrote:
> >
> > Maybe clarify on the "issues" section that a resolution in sight but
> > it's not done yet. You imply this in other words, but being clear that
> > the trademark issue is "acknowledged by the owner and the PMC is waiting
> > on a fix by that owner" is helpful for someone who is moving through the
> > report quickly.
> >
> > On 4/6/20 1:43 PM, Michael Wall wrote:
> > > The Apache Accumulo PMC decided to draft its quarterly board
> > > reports on the dev list. Here is a draft of our report which is due
> > > Wednesday, Apr 8, 1 week before the board meeting on
> > > Wednesday, Apr 15. Please let me know if you have any feedback.  I'll
> post
> > > it on Wed.
> > >
> > > Some more detailed metrics are at
> > > https://reporter.apache.org/wizard/statistics?accumulo,
> > > which appears to require a committer login.
> > >
> > > Mike
> > >
> > > 
> > > [REPORT] Accumulo - Jan 2020
> > >
> > > ## Description:
> > >
> > > The Apache Accumulo sorted, distributed key/value store is a robust,
> > > scalable,
> > > high performance data storage system that features cell-based access
> control
> > > and customizable server-side processing. It is based on Google's
> BigTable
> > > design and is built on top of Apache Hadoop, Zookeeper, and Thrift.
> > >
> > > ## Issues:
> > >
> > > The Oct report listed a discussion about a trademark issue at
> > > http://www.accumulodata.com
> > > [1]. The owner is still looking for the right account used for that
> site to
> > > repoint to https://accumulo.apache.org.
> > >
> > > ## Membership Data:
> > >
> > > Apache Accumulo was founded 2012-03-20 (8 years ago)
> > > There are currently 36 committers and 36 PMC members in this project.
> > > The Committer-to-PMC ratio is 1:1.
> > >
> > > Community changes, past quarter:
> > > - No new PMC members. Last addition was Holly Keebler on 2019-08-08.
> > > - No new committers. Last addition was Holly Keebler on 2019-08-09.
> > > - Ongoing discussion about adding a new member.
> > >
> > > ## Project Activity:
> > >
> > > - No new releases this quarter, although 1.10 is still in the works.
> The
> > > 1.10 releases
> > > will also be our first LTS release [2].
> > > - There was work done to improve the website generation using github
> > > actions [3].
> > > - The monthly "Hack Day" continues in Columbia MD. There was nothing
> of note
> > > posted from the meetings in Jan[4] and Feb[5]. The March Hack Day had
> a few
> > > notes[6].
> > > - Some of the developers participated in a slack call[7] on Mar 24,
> notes
> > > were written to the mailing list[8].
> > >
> > > ## Community Health:
> > >
> > > - Activity in the community is consistent.  There is less activity on
> the
> > > mailing lists but more on github issues and and PRs [9].
> > >
> > > [1]:
> > >
> https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org
> > > [2]:
> > >
> https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
> > > [3]:
> > >
> https://lists.apache.org/thread.html/rc9dacacb7bafd1d2289cdfa67ab31d5f4c0c1c47eb1afc905d62ef77%40%3Cdev.accumulo.apache.org%3E
> > > [4]:
> > >
> https://lists.apache.org/thread.html/r873b186740d0c1c078edafbf0af4fab0158f85aabc74348cfdf8acc8%40%3Cdev.accumulo.apache.org%3E
> > > [5]:
> > >
> https://lists.apache.org/thread.html/r0c43fdc622d446a0f5cbec79085de86e8ad098a173a73739e86c98fd%40%3Cdev.accumulo.apache.org%3E
> > > [6]:
> > >
> https://lists.apache.org/thread.html/r3753f5ee8caba67fc00a4a6af36c75018349085f9c5fd7892ba7d7aa%40%3Cdev.accumulo.apache.org%3E
> > > [7]:
> > >
> https://lists.apache.org/thread.html/r494ba26ee4e8f16fc1b865bb363f3e4a9035738d8c49f10505d6e4f5%40%3Cdev.accumulo.apache.org%3E
> > > [8]:
> > >
> https://lists.apache.org/thread.html/r2ae8f3375fc2c2e36b11e576456b8697f29057c06d0bf89c6e165d14%40%3Cdev.accumulo.apache.org%3E
> > > [9]:https://reporter.apache.org/wizard/statistics?accumulo
> > >
>

[REPORT][DRAFT] Apache Accumulo April 2020

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
Wednesday, Apr 8, 1 week before the board meeting on
Wednesday, Apr 15. Please let me know if you have any feedback.  I'll post
it on Wed.

Some more detailed metrics are at
https://reporter.apache.org/wizard/statistics?accumulo,
which appears to require a committer login.

Mike


[REPORT] Accumulo - Jan 2020

## Description:

The Apache Accumulo sorted, distributed key/value store is a robust,
scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

The Oct report listed a discussion about a trademark issue at
http://www.accumulodata.com
[1]. The owner is still looking for the right account used for that site to
repoint to https://accumulo.apache.org.

## Membership Data:

Apache Accumulo was founded 2012-03-20 (8 years ago)
There are currently 36 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Holly Keebler on 2019-08-08.
- No new committers. Last addition was Holly Keebler on 2019-08-09.
- Ongoing discussion about adding a new member.

## Project Activity:

- No new releases this quarter, although 1.10 is still in the works. The
1.10 releases
will also be our first LTS release [2].
- There was work done to improve the website generation using github
actions [3].
- The monthly "Hack Day" continues in Columbia MD. There was nothing of note
posted from the meetings in Jan[4] and Feb[5]. The March Hack Day had a few
notes[6].
- Some of the developers participated in a slack call[7] on Mar 24, notes
were written to the mailing list[8].

## Community Health:

- Activity in the community is consistent.  There is less activity on the
mailing lists but more on github issues and and PRs [9].

[1]:
https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org
[2]:
https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
[3]:
https://lists.apache.org/thread.html/rc9dacacb7bafd1d2289cdfa67ab31d5f4c0c1c47eb1afc905d62ef77%40%3Cdev.accumulo.apache.org%3E
[4]:
https://lists.apache.org/thread.html/r873b186740d0c1c078edafbf0af4fab0158f85aabc74348cfdf8acc8%40%3Cdev.accumulo.apache.org%3E
[5]:
https://lists.apache.org/thread.html/r0c43fdc622d446a0f5cbec79085de86e8ad098a173a73739e86c98fd%40%3Cdev.accumulo.apache.org%3E
[6]:
https://lists.apache.org/thread.html/r3753f5ee8caba67fc00a4a6af36c75018349085f9c5fd7892ba7d7aa%40%3Cdev.accumulo.apache.org%3E
[7]:
https://lists.apache.org/thread.html/r494ba26ee4e8f16fc1b865bb363f3e4a9035738d8c49f10505d6e4f5%40%3Cdev.accumulo.apache.org%3E
[8]:
https://lists.apache.org/thread.html/r2ae8f3375fc2c2e36b11e576456b8697f29057c06d0bf89c6e165d14%40%3Cdev.accumulo.apache.org%3E
[9]:https://reporter.apache.org/wizard/statistics?accumulo

Re: Video chat this week

[Michael Wall]

I am available this week as well.

On Tue, Mar 24, 2020 at 12:05 PM Billie Rinaldi  wrote:

> Sounds good to me!
>
> Billie
>
> On Tue, Mar 24, 2020 at 9:25 AM Keith Turner  wrote:
>
> > Slack has a call feature, but I have never used it.  I can do 11 Wed
> > or Thur this week.
> >
> > On Mon, Mar 23, 2020 at 10:14 PM Christopher 
> wrote:
> > >
> > > Accumulo Devs,
> > >
> > > I happen to have some extra time on my hands this week at home, and
> > > thought it might be nice to set up a video meeting to chat with
> > > anybody who might be interested in discussing Accumulo development.
> > > This came up as part of the conversation on
> > > https://github.com/apache/accumulo/pull/1568 , but we can discuss
> > > anything.
> > >
> > > I'm most familiar with Google Hangouts, and 1100, New York time, is
> > > probably the earliest I could do it... but I can also probably do
> > > early afternoon or late evening. If somebody wants to set up using
> > > another service, that's probably fine too, but I haven't really used
> > > anything else.
> >
>

[REPORT] Apache Accumulo January 2020

[Michael Wall]

Report as published to Board agenda.  No longer sending this as an email to
the board, but wanted to get the final version out to list.

Mike

-

## Description:

The Apache Accumulo sorted, distributed key/value store is a robust, scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

The Oct report listed a discussion about a trademark issue
athttp://www.accumulodata.com [1]. We are still waiting for the owner
to repoint
to https://accumulo.apache.org.


## Membership Data:

Apache Accumulo was founded 2012-03-20 (8 years ago)
There are currently 36 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Holly Keebler on 2019-08-08.
- No new committers. Last addition was Holly Keebler on 2019-08-09.

## Project Activity:

- No new releases this quarter, although 1.10 is in discussion [2] and [3],
which is the 1.9 line with the minimum JDK moved to 1.8.  The 1.10 releases
will also be our first LTS release [4].
- The monthly "Hack Day" continues in Columbia MD. There was nothing of note
posted from the meetings in Oct[5] and Dec[6].  The Nov[7] meetup was
mirrored on the west coast and some issues labeling for 'good first issue' was
accomplished [8].

## Community Health:

- Activity in the community was lower this quarter than last, but
consistent with prior quarters.  The uptick last quarter was most likely
due the surge to release 2.0.

[1]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org
[2]:https://lists.apache.org/thread.html/ee05bb430a28dfa5f6cab0eec18be26926e7404182102667ea14cc56%40%3Cdev.accumulo.apache.org%3E
[3]:https://lists.apache.org/thread.html/266d114a0638accba6b9dc3768474cf43d6b965149572cf07bcf4cdb%40%3Cdev.accumulo.apache.org%3E
[4]:https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
[5]:https://lists.apache.org/thread.html/05b21f61ca4bd3fe2610984953990bca041dc9a7f74a3bd0f70c6f99%40%3Cdev.accumulo.apache.org%3E
[6]:https://lists.apache.org/thread.html/cc3c8b81ee1a0f946cef0b84c756f2a199a320c3f81e63054bfdb072%40%3Cdev.accumulo.apache.org%3E
[7]:https://lists.apache.org/thread.html/19dc06fa9f649adc3bb70ca6e6cbdf8c5f8d1525a57f17b6e6d315db%40%3Cdev.accumulo.apache.org%3E
[8]:https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22

Re: [REPORT][DRAFT] Apache Accumulo January 2020

[Michael Wall]

thanks Mike, Keith and Ed (who talked to me in person).  Submitting now.

On Wed, Jan 8, 2020 at 3:21 PM Keith Turner  wrote:

> This looks great.  Your project activity section is packed with useful
> information and really short.
>
> On Tue, Jan 7, 2020 at 5:51 PM Michael Wall  wrote:
> >
> > The Apache Accumulo PMC decided to draft its quarterly board
> > reports on the dev list. Here is a draft of our report which is due
> > tomorrow, Wednesday, Jan 8, 1 week before the board meeting on
> > Wednesday, Jan 15. Please let me know if you have any feedback.
> >
> > Some more detailed metrics are at
> > https://reporter.apache.org/wizard/statistics?accumulo,
> > which appears to require a committer login.
> >
> > Mike
> >
> > 
> > [REPORT] Accumulo - Jan 2020
> >
> > ## Description:
> >
> > The Apache Accumulo sorted, distributed key/value store is a robust,
> > scalable,
> > high performance data storage system that features cell-based access
> control
> > and customizable server-side processing. It is based on Google's BigTable
> > design and is built on top of Apache Hadoop, Zookeeper, and Thrift.
> >
> > ## Issues:
> >
> > The Oct report listed a discussion about a trademark issue at
> > http://www.accumulodata.com
> > [1]. We are still waiting for the owner to repoint to
> > https://accumulo.apache.org.
> >
> >
> > ## Membership Data:
> >
> > Apache Accumulo was founded 2012-03-20 (8 years ago)
> > There are currently 36 committers and 36 PMC members in this project.
> > The Committer-to-PMC ratio is 1:1.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Holly Keebler on 2019-08-08.
> > - No new committers. Last addition was Holly Keebler on 2019-08-09.
> >
> > ## Project Activity:
> >
> > - No new releases this quarter, although 1.10 is in discussion [2] and
> [3],
> > which is the 1.9 line with the minimum JDK moved to 1.8.  The 1.10
> releases
> > will also be our first LTS release [4].
> > - The monthly "Hack Day" continues in Columbia MD. There was nothing of
> note
> > posted from the meetings in Oct[5] and Dec[6].  The Nov[7] meetup was
> > mirrored on the west coast and some issues labeling for 'good first
> issue'
> > was
> > accomplished [8].
> >
> > ## Community Health:
> >
> > - Activity in the community was lower this quarter than last, but
> > consistent
> > prior quarters.  The uptick last quarter was most likely due the surge to
> > release
> > 2.0.
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org
> > [2]:
> >
> https://lists.apache.org/thread.html/ee05bb430a28dfa5f6cab0eec18be26926e7404182102667ea14cc56%40%3Cdev.accumulo.apache.org%3E
> > [3]:
> >
> https://lists.apache.org/thread.html/266d114a0638accba6b9dc3768474cf43d6b965149572cf07bcf4cdb%40%3Cdev.accumulo.apache.org%3E
> > [4]:
> >
> https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
> > [5]:
> >
> https://lists.apache.org/thread.html/05b21f61ca4bd3fe2610984953990bca041dc9a7f74a3bd0f70c6f99%40%3Cdev.accumulo.apache.org%3E
> > [6]:
> >
> https://lists.apache.org/thread.html/cc3c8b81ee1a0f946cef0b84c756f2a199a320c3f81e63054bfdb072%40%3Cdev.accumulo.apache.org%3E
> > [7]:
> >
> https://lists.apache.org/thread.html/19dc06fa9f649adc3bb70ca6e6cbdf8c5f8d1525a57f17b6e6d315db%40%3Cdev.accumulo.apache.org%3E
> > [8]:
> >
> https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
>

[REPORT][DRAFT] Apache Accumulo January 2020

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
tomorrow, Wednesday, Jan 8, 1 week before the board meeting on
Wednesday, Jan 15. Please let me know if you have any feedback.

Some more detailed metrics are at
https://reporter.apache.org/wizard/statistics?accumulo,
which appears to require a committer login.

Mike


[REPORT] Accumulo - Jan 2020

## Description:

The Apache Accumulo sorted, distributed key/value store is a robust,
scalable,
high performance data storage system that features cell-based access control
and customizable server-side processing. It is based on Google's BigTable
design and is built on top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

The Oct report listed a discussion about a trademark issue at
http://www.accumulodata.com
[1]. We are still waiting for the owner to repoint to
https://accumulo.apache.org.


## Membership Data:

Apache Accumulo was founded 2012-03-20 (8 years ago)
There are currently 36 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- No new PMC members. Last addition was Holly Keebler on 2019-08-08.
- No new committers. Last addition was Holly Keebler on 2019-08-09.

## Project Activity:

- No new releases this quarter, although 1.10 is in discussion [2] and [3],
which is the 1.9 line with the minimum JDK moved to 1.8.  The 1.10 releases
will also be our first LTS release [4].
- The monthly "Hack Day" continues in Columbia MD. There was nothing of note
posted from the meetings in Oct[5] and Dec[6].  The Nov[7] meetup was
mirrored on the west coast and some issues labeling for 'good first issue'
was
accomplished [8].

## Community Health:

- Activity in the community was lower this quarter than last, but
consistent
prior quarters.  The uptick last quarter was most likely due the surge to
release
2.0.

[1]:
https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org
[2]:
https://lists.apache.org/thread.html/ee05bb430a28dfa5f6cab0eec18be26926e7404182102667ea14cc56%40%3Cdev.accumulo.apache.org%3E
[3]:
https://lists.apache.org/thread.html/266d114a0638accba6b9dc3768474cf43d6b965149572cf07bcf4cdb%40%3Cdev.accumulo.apache.org%3E
[4]:
https://lists.apache.org/thread.html/43f051404bc5f15cde8f971ccbdc4cf7b017cc014affd914c357eaad%40%3Cdev.accumulo.apache.org%3E
[5]:
https://lists.apache.org/thread.html/05b21f61ca4bd3fe2610984953990bca041dc9a7f74a3bd0f70c6f99%40%3Cdev.accumulo.apache.org%3E
[6]:
https://lists.apache.org/thread.html/cc3c8b81ee1a0f946cef0b84c756f2a199a320c3f81e63054bfdb072%40%3Cdev.accumulo.apache.org%3E
[7]:
https://lists.apache.org/thread.html/19dc06fa9f649adc3bb70ca6e6cbdf8c5f8d1525a57f17b6e6d315db%40%3Cdev.accumulo.apache.org%3E
[8]:
https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22

Fwd: [PMCs] Launch of the 2020 ASF Community Survey

[Michael Wall]

Forwarding an email from ASF Diversity & Inclusion.  See below

Mike

---

Hello everyone,

If you have an apache.org email, you should have received an email with an
invitation to take the 2020 ASF Community Survey. Please take 15 minutes to
complete it.

If you do not have an apache.org email address or you didn’t receive a
link, please follow this link to the survey:
https://communitysurvey.limequery.org/454363

This survey is important because it will provide us with scientific
information about our community, and shed some light on how we can
collaborate better and become more diverse. Our last survey of this kind
was implemented in 2016, which means that our existing data about Apache
communities is outdated. The deadline to complete the survey is January
4th, 2020. You can find information about privacy on the survey’s
Confluence page [1].

Your participation is paramount to the success of this project! Please
consider filling out the survey, and share this news with your fellow
Apache contributors. As individuals form the Apache community, your opinion
matters: we want to hear your voice.

If you have any questions about the survey or otherwise, please reach out
to us!

Kindly,
ASF Diversity & Inclusion
https://diversity.apache.org/


[1]
https://cwiki.apache.org/confluence/display/EDI/Launch+Plan+-+The+2020+ASF+Community+Survey

Re: Getting ready to release 1.10.0

[Michael Wall]

Thanks Christopher.

On Tue, Nov 12, 2019 at 3:48 PM Christopher  wrote:

> It was pointed out to me that some of the problems I had using the
> modernizer-maven-plugin could be alleviated by adding granular
> exceptions in the modernizer config. I'll see if I can make that
> happen.
>
> On Fri, Nov 8, 2019 at 7:14 PM Christopher  wrote:
> >
> > So, one of the problems I've run into migrating the 1.x code to JDK8
> > is that we still have Mock in the API. That was removed in 2.x.
> > However, in 1.9, MockConfiguration extends a non-public API,
> > AccumuloConfiguration, which uses non-public Guava types for
> > Predicates. Code-modernization/quality checks performed by the
> > modernizer-maven-plugin catch the use of Guava's Predicate. I'm still
> > looking at this, to see if I can work around it without breaking
> > anything, but it's a bit frustrating, especially since the right fix
> > (removal of Mock) was already done in 2.x.
> >
> > I'll revisit next week after a long weekend. In the meantime, if
> > anybody is having second thoughts about a 1.10 release, or opinions
> > about what to do, feel free to express them here. One option is to
> > simply disable the modernizer-maven-plugin and ignore those checks...
> > but I don't really like the idea of disabling one of our tools that
> > does quality checks (even if these are very minor quality items).
> >
> > On Thu, Nov 7, 2019 at 4:20 PM Christopher  wrote:
> > >
> > > As agreed in the recent [VOTE] thread, we will be releasing a 1.10.0
> > > that bumps the minimum runtime Java version to 8.
> > >
> > > I am beginning to work on getting the branch (currently still named
> > > 1.9) ready for release in accordance with this plan. As such, I will
> > > be preparing a pull request that bumps the Java version and resolves
> > > any errors generated by our plugins which do quality checks
> > > (specifically modernizer, but also some compiler warnings).
> > >
> > > However, there are still a few other outstanding issues that were
> > > previously labeled for 1.9, which have not yet been resolved. At least
> > > one of these was labeled a "blocker". These are:
> > >
> https://github.com/apache/accumulo/issues?q=is%3Aopen+project%3Aapache%2Faccumulo%2F8
> > >
> > > If anybody is able to work on these, it will be very helpful in
> > > getting the 1.10.0 ready for a release vote.
> > >
> > > Thanks,
> > >
> > > Christopher
>

Re: [VOTE] Proposal to release version 1.10

[Michael Wall]

I am +1 on moving 1.10 to Java 8.

However Sean's -1 vote is a veto [1] and we can not proceed down this path
unless it is withdrawn.  I can only take the veto to mean there are
customers who would upgrade to Accumulo 1.10 but would not upgrade to Java
1.8.  Is there anything that would change your mind Sean?

Thanks

Mike

1 - https://www.apache.org/foundation/voting.html#Veto


On Fri, Nov 1, 2019 at 12:46 PM Sean Busbey 
wrote:

> Correct, it is up to every user of SemVer to define the public API and
> AFAIK we have chosen not to include things like the Java version
> needed to run Accumulo in ours[1].
>
> That doesn't mean it's not crappy to our downstream users to do things
> that have a major operational impact upon minor releases. Updating a
> JDK version is a major undertaking. It takes a long time to do in an
> environment with strict change control policies and it sucks. There
> are still shops that run JDK7. There are multiple options for
> purchasing commercial support with security updates for it still. Just
> picking two vendors out of the air[2], Oracle will still provide
> support for almost 2 more years and Azul for almost 3.
>
> That doesn't mean we have to keep supporting JDK7, but be aware that
> we are trading for a gain in developer convenience at the expense of
> operator difficulty. We will probably drive folks into the arms of
> forks that bother to maintain JDK compatibility for these release
> lines. It does inhibit our ability to draw new folks into the
> community, but that's not a fundamental problem I guess.
>
> As an aside, this comment from your cited FAQ is inaccurate on its
> face for practical considerations in the Java ecosystem as cause for
> not needing to worry about the downstream impact of changing a
> dependency.
>
> > Software that explicitly depends on the same dependencies as your
> package should have their own dependency specifications and the author will
> notice any conflicts.
>
> We've discussed this a bunch of times. We clearly have disagreement in
> the community about the priority on the tradeoff between developer
> work and operational work. That's okay.
>
> [1]: https://accumulo.apache.org/api/
> [2]: https://www.azul.com/products/azul-support-roadmap/
>
> On Fri, Nov 1, 2019 at 7:16 AM Ed Coleman  wrote:
> >
> > If I am reading semver correctly (
> https://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api)
> this proposal has no changes to the Accumulo public API, it is an update to
> our dependencies - and would not require a major version change.
> >
> > -Original Message-
> > From: Sean Busbey [mailto:bus...@cloudera.com.INVALID]
> > Sent: Friday, November 01, 2019 3:52 AM
> > To: dev@accumulo apache. org 
> > Subject: Re: [VOTE] Proposal to release version 1.10
> >
> > -1 no dropping supported java versions in a minor release. if we want
> folks to move to java 8 then we should make it easier to upgrade to
> Accumulo 2.y
> >
> > On Thu, Oct 31, 2019 at 7:37 PM Ed Coleman  wrote:
> > >
> > > As suggested in the LTS discussion ([LAZY][VOTE] A basic, but
> > > concrete, LTS proposal), I'm breaking this out to as a separate thread
> > > to keep the topic distinct.
> > >
> > >
> > > The proposal - I would like to start the formal release process for a
> > > 1.10 version that would change the java language level to java 8.  The
> > > release would be based on the current 1.9 branch and would be released
> > > instead of a 1.9.4.  The 1.10 release would not contain additional
> > > feature changes that are not present in the current 1.9 branch.
> > > Currently, this would be based on the commit SHA:
> > >
> > >
> > > 328ffa0849981e0f113dfbf539c832b447e06902 - committed Thu Oct 10.
> > >
> > >
> > > (I am unaware of any bug-fixes or issues in the pipe line that would /
> > > should be included - but hopefully this makes the intention clear.)
> > >
> > >
> > > The goal is to provide a candidate for LTS nomination that is based on
> > > the current 1.9.x code, but unifies our currently supported branches
> > > to all use java 8 as the supported language level. While this had been
> > > discussed in the past, enough time has passed that a java 8
> > > requirement now, seems to me, to be unlikely to impact any customers
> > > that would look to upgrade Accumulo past a 1.9.3 version and have them
> not running at least java 8.
> > > Having our code base with a modern, unified java language support
> > > level would greatly benefit our development and reduce the burden to
> > > support our multiple branches.
> > >
> > >
> > > This vote will be held open for at least the standard 72 hours.
> >
> >
> >
> > --
> > busbey
> >
>
>
> --
> busbey
>

[REPORT] Accumulo - October 2019

[Michael Wall]

## Description:

The Apache Accumulo sorted, distributed key/value store is a robust,
scalable, high performance data storage system that features
cell-based access control and customizable server-side processing. It
is based on Google's BigTable design and is built on top of Apache
Hadoop, Zookeeper, and Thrift.

## Issues:

There was a discussion about a trademark issue at
http://www.accumulodata.com [1]. The owner of the site is a PMC member
and has offered to repoint to https://accumulo.apache.org.

## Membership Data:

Apache Accumulo was founded 2012-03-20 (8 years ago)
There are currently 36 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- Adam Lerman was added to the PMC on 2019-08-06
- Holly Keebler was added to the PMC on 2019-08-08
- Adam Lerman was added as committer on 2019-08-08
- Holly Keebler was added as committer on 2019-08-09

## Project Activity:

- We have finally released Apache Accumulo 2.0.0 on 2019-08-02 [2].
- We also released the Apache Accumulo2 Maven Plugin on 2019-08-07 [3].
- The monthly "Hack Day" continues in Columbia MD. There was nothing
of note posted from the meetings in Jul, Sep or Aug.

## Community Health:

Activity in the community remains pretty constant. The exception is that
the user list felt like it had a little more activity over the past quarter
which is supported by the metrics showing a 195% increase in emails (59
compared to 20). Many of those emails were people new to the community
asking questions or getting support. We have also been attempting to
encourage participation among newcomers by inviting them to
subscribe and introduce themselves on the dev list.

[1]:
https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org
[2]:
https://lists.apache.org/thread.html/5421727924d60a20e20af356cda0c4f1daf685be9266d1aebc2f34fd@%3Cannounce.apache.org%
[3]:
https://lists.apache.org/thread.html/344b402281d50e62a78d4770727fd4630fe0dad6ac62584ec7236c05@%3Cdev.accumulo.apache.org%3E

Re: [DRAFT] [REPORT] Apache Accumulo - Oct 2019

[Michael Wall]

Sure, thanks Christopher.

Any other comments?  Yesterday I said I was posting it tomorrow, but I
really meant I was posting it in 2 days from yesterday, which is actually
tomorrow today.  Sorry for the confusion.

Mike

On Tue, Oct 8, 2019 at 7:51 PM Christopher  wrote:

> Oh, one thing you could mention is how we've begun attempting to more
> actively encourage participation among newcomers by inviting them to
> subscribe and introduce themselves on the dev@ list.
>
> On Tue, Oct 8, 2019 at 6:51 PM Christopher  wrote:
> >
> > LGTM. Thanks, Mike!
> >
> > On Mon, Oct 7, 2019 at 9:46 PM Michael Wall  wrote:
> > >
> > > The Apache Accumulo PMC decided to draft its quarterly board
> > > reports on the dev list. Here is a draft of our report which is due
> > > tomorrow, Wednesday, Oct 9, 1 week before the board meeting on
> > > Wednesday, Jul 16. Please let me know if you have any feedback.
> > >
> > > Note, the reporter wizard has been updated.  Much less focus on raw
> > > number, more emphasis on meaning.  I am not sure who has access to
> > > these, so pasting the rolled up metrics here
> > >
> > > dev@accumulo.apache.org had a 34% decrease in traffic in the past
> quarter
> > > (90 emails compared to 136)
> > > u...@accumulo.apache.org had a 195% increase in traffic in the past
> quarter
> > > (59 emails compared to 20)
> > > 2 issues opened in JIRA, past quarter (100% increase)
> > > 1 issue closed in JIRA, past quarter (-99% decrease)
> > > 169 commits in the past quarter (-18% decrease)
> > > 17 code contributors in the past quarter (-15% decrease)
> > > 88 PRs opened on GitHub, past quarter (-42% decrease)
> > > 87 PRs closed on GitHub, past quarter (-40% decrease)
> > > 65 issues opened on GitHub, past quarter (-35% decrease)
> > > 51 issues closed on GitHub, past quarter (-31% decrease)
> > >
> > > And the link to fuller metrics is at
> > > https://reporter.apache.org/wizard/statistics?accumulo.  Looks like
> > > committers can login to see that.
> > >
> > > Mike
> > >
> > > 
> > >
> > > ## Description:
> > >
> > > The Apache Accumulo sorted, distributed key/value store is a robust,
> > > scalable, high performance data storage system that features
> > > cell-based access control and customizable server-side processing.  It
> > > is based on Google's BigTable design and is built on top of Apache
> > > Hadoop, Zookeeper, and Thrift.
> > >
> > > ## Issues:
> > >
> > > There was a discussion about a trademark issue at
> > > http://www.accumulodata.com [1]. The owner of the site is a PMC member
> > > and has offered to repoint to https://accumulo.apache.org.
> > >
> > > ## Membership Data:
> > >
> > > Apache Accumulo was founded 2012-03-20 (8 years ago)
> > > There are currently 36 committers and 36 PMC members in this project.
> > > The Committer-to-PMC ratio is 1:1.
> > >
> > > Community changes, past quarter:
> > > - Adam Lerman was added to the PMC on 2019-08-06
> > > - Holly Keebler was added to the PMC on 2019-08-08
> > > - Adam Lerman was added as committer on 2019-08-08
> > > - Holly Keebler was added as committer on 2019-08-09
> > >
> > > ## Project Activity:
> > >
> > > - We have finally released Apache Accumulo 2.0.0 on 2019-08-02 [2].
> > > - We also released the Apache Accumulo2 Maven Plugin on 2019-08-07 [3].
> > > - The monthly "Hack Day" continues in Columbia MD.  There was nothing
> > >   of note posted from the meetings in Jul, Sep or Aug.
> > >
> > > ## Community Health:
> > >
> > > Activity in the community remains pretty constant.  The exception is
> > > that the user list felt like it had a little more activity over the
> > > past quarter which is supported by the metrics showing a 195% increase
> > > in emails (59 compared to 20).  Many of those emails were people new
> > > to the community asking questions or getting support.
> > >
> > > [1]:
> > >
> https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
> > > [2]:
> > >
> https://lists.apache.org/thread.html/5421727924d60a20e20af356cda0c4f1daf685be9266d1aebc2f34fd@%3Cannounce.apache.org%3E
> > > [3]:
> > >
> https://lists.apache.org/thread.html/344b402281d50e62a78d4770727fd4630fe0dad6ac62584ec7236c05@%3Cdev.accumulo.apache.org%3E
>

[DRAFT] [REPORT] Apache Accumulo - Oct 2019

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
tomorrow, Wednesday, Oct 9, 1 week before the board meeting on
Wednesday, Jul 16. Please let me know if you have any feedback.

Note, the reporter wizard has been updated.  Much less focus on raw
number, more emphasis on meaning.  I am not sure who has access to
these, so pasting the rolled up metrics here

dev@accumulo.apache.org had a 34% decrease in traffic in the past quarter
(90 emails compared to 136)
u...@accumulo.apache.org had a 195% increase in traffic in the past quarter
(59 emails compared to 20)
2 issues opened in JIRA, past quarter (100% increase)
1 issue closed in JIRA, past quarter (-99% decrease)
169 commits in the past quarter (-18% decrease)
17 code contributors in the past quarter (-15% decrease)
88 PRs opened on GitHub, past quarter (-42% decrease)
87 PRs closed on GitHub, past quarter (-40% decrease)
65 issues opened on GitHub, past quarter (-35% decrease)
51 issues closed on GitHub, past quarter (-31% decrease)

And the link to fuller metrics is at
https://reporter.apache.org/wizard/statistics?accumulo.  Looks like
committers can login to see that.

Mike



## Description:

The Apache Accumulo sorted, distributed key/value store is a robust,
scalable, high performance data storage system that features
cell-based access control and customizable server-side processing.  It
is based on Google's BigTable design and is built on top of Apache
Hadoop, Zookeeper, and Thrift.

## Issues:

There was a discussion about a trademark issue at
http://www.accumulodata.com [1]. The owner of the site is a PMC member
and has offered to repoint to https://accumulo.apache.org.

## Membership Data:

Apache Accumulo was founded 2012-03-20 (8 years ago)
There are currently 36 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is 1:1.

Community changes, past quarter:
- Adam Lerman was added to the PMC on 2019-08-06
- Holly Keebler was added to the PMC on 2019-08-08
- Adam Lerman was added as committer on 2019-08-08
- Holly Keebler was added as committer on 2019-08-09

## Project Activity:

- We have finally released Apache Accumulo 2.0.0 on 2019-08-02 [2].
- We also released the Apache Accumulo2 Maven Plugin on 2019-08-07 [3].
- The monthly "Hack Day" continues in Columbia MD.  There was nothing
  of note posted from the meetings in Jul, Sep or Aug.

## Community Health:

Activity in the community remains pretty constant.  The exception is
that the user list felt like it had a little more activity over the
past quarter which is supported by the metrics showing a 195% increase
in emails (59 compared to 20).  Many of those emails were people new
to the community asking questions or getting support.

[1]:
https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E
[2]:
https://lists.apache.org/thread.html/5421727924d60a20e20af356cda0c4f1daf685be9266d1aebc2f34fd@%3Cannounce.apache.org%3E
[3]:
https://lists.apache.org/thread.html/344b402281d50e62a78d4770727fd4630fe0dad6ac62584ec7236c05@%3Cdev.accumulo.apache.org%3E

Re: New committer/PMC member: Adam Lerman

[Michael Wall]

On Fri, Aug 9, 2019 at 8:52 AM Owens, Mark  wrote:

> Welcome, Adam!
>
> -Original Message-
> From: Christopher 
> Sent: Wednesday, August 7, 2019 6:22 PM
> To: accumulo-dev 
> Cc: aler...@apache.org
> Subject: New committer/PMC member: Adam Lerman
>
> Devs,
>
> The Project Management Committee (PMC) for Apache Accumulo has invited
> Adam Lerman to become a committer and we are pleased to announce that he
> has accepted.
>
> Adam has contributed several pull requests in the last year to enhance
> features in the accumulo-shell and the VolumeChooser in 1.9 and 2.0, as
> well as other user experience enhancements. Most recently, he worked with
> Keith Turner to incorporate some additional logging to help administrators
> find busy tablets causing hotspotting.
>
> Being a committer comes with write access to the Accumulo repositories, to
> accept code changes and merges from other contributors, and to merge their
> own contributions more easily. This should enable better productivity.
> Being a PMC member enables assistance with the management and direction of
> the project, such as binding votes for releases.
>
> Please join me in welcoming Adam!
>

Welcome Adam and congrats.  Feel free to introduce yourself and your
interests with this new role.

Re: New committer/PMC member: Holly Keebler

[Michael Wall]

On Fri, Aug 9, 2019 at 5:17 PM Laura Schanno  wrote:

> Congratulations Holly!
>
> Laura
>
> On Fri, Aug 9, 2019, 4:28 PM Jeffrey Zeiberg  wrote:
>
> > Congrats Holly.
> >
> > Well deserved.
> >
> >
> > On Fri, Aug 9, 2019 at 3:21 PM Christopher  wrote:
> >
> > > Devs,
> > >
> > > The Project Management Committee (PMC) for Apache Accumulo
> > > has invited Holly Keebler to become a committer and we are pleased
> > > to announce that she has accepted.
> > >
> > > Holly started with contributions fixing some smaller issues, like
> > > removing a premature "Master is down" message from the monitor during
> > > startup, and making use of NewTableConfiguration in some ITs, to
> > > improve the quality of the tests for the 2.0.0 release. Not only has
> > > she continued making changes to fix smaller issues like those, but has
> > > since also moved on to significantly more complicated issues helping
> > > refactor the metadata internals for future Accumulo 2.1.x releases.
> > >
> > > Being a committer comes with write access to the Accumulo
> > > repositories, to accept code changes and merges from other
> > > contributors, and to merge their own contributions more easily. This
> > > should enable better productivity.
> > > Being a PMC member enables assistance with the management and
> > > direction of the project, such as binding votes for releases.
> > >
> > > Please join me in welcoming Holly!
> > >
> >
>

Congrats Holly and welcome.  Feel free to introduce yourself and your
interests with this new role.

Re: [RESULT][VOTE] Apache Accumulo 2.0.0-rc2

[Michael Wall]

Congrats everyone.  This has been a long time coming.

On Thu, Aug 1, 2019, 20:40 Christopher  wrote:

> It's getting late for me. I've completed some release tasks. I can finish
> the rest tomorrow:
>
> I completed:
> merged in approved rc2-next branch to 2.0 and merged forward
> created signed git tag for rel/2.0.0
> cleaned up rc branches in git
> uploaded release artifacts to SVN/mirrors
> updated reporter.apache.org with release info
> released the Maven staging repository for rc2
> deleted old staging repositories
>
> Most of what's left is website updates, which can be done tomorrow after
> the mirrors sync up.
>
> On Thu, Aug 1, 2019 at 8:12 PM Christopher  wrote:
>
> > This vote passes with 4 binding +1s (mmiller, kturner, jmark99,
> > ctubbsii), 2 non-binding +1s (Holly Keebler, Jeffrey Manno), and no
> > other votes.
> >
> > Accumulo 2.0.0 is officially approved for release by the PMC! There's
> > still more to do, of course, and I will begin stepping through those
> > release tasks shortly. In the meantime, please feel free look over the
> > release notes to ensure they cover everything they should.
> >
> > This release has been at least 3 years in the making... so this is
> > pretty exciting! I want to especially thank those contributors who
> > aren't PMC members who contributed to, tested, and voted on this
> > release candidate. Your contributions are appreciated!
> >
> > Thanks all,
> >
> > Christopher
> > 
> >
> > On Thu, Aug 1, 2019 at 7:58 PM Christopher  wrote:
> > >
> > > +1 from me
> > >
> > > * I started up an instance in fluo-uno
> > > * I verified sigs and checksums
> > > * Javadoc and Source jars are present
> > > * Verified lib directory contains same jars in staging repo
> > > * Verified git commit matches MANIFEST.MF contents and its checkout
> > > matches source tarball contents
> > > * Verified all ITs pass on Java 11
> > > * I performed bulk import testing and some small CI builds on fluo-uno
> > > to my satisfaction between rc1 and rc2, just to ensure basic
> > > functionality (and, in the case of the bulk tests, to triage some of
> > > the issues that were fixed between rc1 and rc2)
> > >
> > > These are things I'd prefer be different, but I don't think should
> > > hold the release:
> > > I think we can remove accumulo-test-*.jar from future builds (See
> > > https://github.com/apache/accumulo/issues/1305)
> > > I think we should simplify the way we build and package the source
> > > tarball (See https://github.com/apache/accumulo/issues/1306)
> > >
> > > On Thu, Aug 1, 2019 at 3:20 PM Christopher 
> wrote:
> > > >
> > > > I'm going to assume this was supposed to be "+1", as in "I am in
> favor
> > > > of", rather than "+!", as in one of
> > > > https://www.urbandictionary.com/define.php?term=%3A%21 :)
> > > >
> > > > On Thu, Aug 1, 2019 at 3:09 PM Owens, Mark 
> > wrote:
> > > > >
> > > > > +!
> > > > >
> > > > > Verified hashes
> > > > > Successfully ran unit tests
> > > > > Successfully ran sunny tests
> > > > > Built from source and installed via Fluo.
> > > > > Exercised standard operations via shell.
> > > > >
> > > > >
> > > > > -Original Message-
> > > > > From: Christopher 
> > > > > Sent: Monday, July 29, 2019 4:10 PM
> > > > > To: accumulo-dev 
> > > > > Subject: [VOTE] Apache Accumulo 2.0.0-rc2
> > > > >
> > > > > Accumulo Developers,
> > > > >
> > > > > Please consider the following candidate for Apache Accumulo 2.0.0.
> > > > > Changes since rc1: git log 4160067813..5a6481f7c1
> > > > >
> > > > > Git Commit:
> > > > > 0b34e30c34b7c31ebb84ca6b3b686c1b3e7b19af
> > > > > Branch:
> > > > > 2.0.0-rc2
> > > > >
> > > > > If this vote passes, a gpg-signed tag will be created using:
> > > > > git tag -f -m 'Apache Accumulo 2.0.0' -s rel/2.0.0 \
> > > > > 0b34e30c34b7c31ebb84ca6b3b686c1b3e7b19af
> > > > >
> > > > > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1081
> > > > > Source (official release artifact):
> > > > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1081/org/apache/accumulo/accumulo/2.0.0/accumulo-2.0.0-src.tar.gz
> > > > > Binary:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1081/org/apache/accumulo/accumulo/2.0.0/accumulo-2.0.0-bin.tar.gz
> > > > >
> > > > > Append ".asc" to download the cryptographic signature for a given
> > artifact.
> > > > > (You can also append ".sha1" or ".md5" instead in order to verify
> > the checksums generated by Maven to verify the integrity of the Nexus
> > repository staging area.)
> > > > >
> > > > > Signing keys are available at
> > https://www.apache.org/dist/accumulo/KEYS
> > > > > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > > > >
> > > > > In addition to the tarballs and their signatures, the following
> > checksum files will be added to the dist/release SVN area after release:
> > > > > accumulo-2.0.0-src.tar.gz.sha512 will contain:
> > > > > SHA512 

Re: Encouraging introductions for new contributors

[Michael Wall]

I think this is a good idea, thanks Christopher.

On Wed, Jul 31, 2019 at 12:21 PM Keith Turner  wrote:

> On Wed, Jul 31, 2019 at 11:39 AM Christopher  wrote:
> >
> > Accumulo Devs,
> >
> > It occurs to me that with the increased use of GitHub PRs, we have a
> > number of contributors which we do not have their contact email
> > addresses, and who have never participated on the mailing lists.
> > Perhaps they are not subscribed, or merely lurking. Some of these
> > contributors have their email addresses in their git logs, but others
> > might use the github noreply address instead.
> >
> > Lacking email addresses makes it hard to send invitations to these
> > people to invite them to become committers/PMC members (if/when that
> > time comes).
> >
> > To remedy this, I suggest that whenever we have a new active
> > contributor submitting pull requests, we encourage them to introduce
> > themselves on the developer mailing list, and to subscribe there. A
> > simple comment on their PR like the following should be sufficient:
> > "Hey there, thanks for contributing. If you plan to contribute
> > regularly, please consider subscribing to the developer mailing list
> > and introducing yourself to the other developers in the community."
> >
> > Does this sound like a good idea? Let me know what you think.
>
> Yes
>
> >
> > Also, if there's anybody subscribed to this list who has been
> > contributing and would like to introduce themselves, please consider
> > doing so now.
> >
> > Christopher
>

[REPORT] Apache Accumulo - July 2019

[Michael Wall]

## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - The last release was 1.9.3 on Apr 9 2019 [1].
 - The community continues to march toward the 2.0.0 release.  This includes
   closing old issues on Jira and moving still relevant issues to github
   issues.
 - The monthly "Hack Day" continues in Columbia MD.  There was nothing of
   note posted from the May meeting, but a summary of June's meeting is at
   [2].  There was a meeting on Jul 10, but no notes from that yet.

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
 - All Committers are also PMC members, see the PMC Changes section for
   details

## Releases:
 - accumulo-1.9.3 was released on Wed Apr 10 2019

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 86 issues created [3] and 70 closed [4] across all the Accumulo repos
   since the last report.
 - 134 pull requests created [5] and 135 closed [6] across all the Accumulo
   repos since the last report.

[1]: https://accumulo.apache.org/release/accumulo-1.9.3/
[2]:
https://lists.apache.org/thread.html/953ddb7f3d621daa1cc068804dd7d813469c147b29778e68081a310f@%3Cdev.accumulo.apache.org%3E
[3]:
https://github.com/search?q=is:issue+created:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[4]:
https://github.com/search?q=is:issue+closed:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[5]:
https://github.com/search?q=is:pr+created:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[6]:
https://github.com/search?q=is:pr+closed:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp

[DRAFT][REPORT] Apache Accumulo - July 2019

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
tomorrow, Wednesday, Jul 10, 1 week before the board meeting on
Wednesday, Jul 17. Please let me know if you have any feedback.

I only saw one summary from the hack days which I included (thanks Mike).
If anyone wants to put something more in about them, let me know.

I also did not write anything about the NoSQL day.  Anyone who attended
want to add anything?

I will submit this tomorrow night.  Sorry for the short timeline.

Mike



## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - The last release was 1.9.3 on Apr 9 2019 [1].
 - The community continues to march toward the 2.0.0 release.  This includes
   closing old issues on Jira and moving still relevant issues to github
   issues.
 - The monthly "Hack Day" continues in Columbia MD.  There was nothing of
   note posted from the May meeting, but a summary of June's meeting is at
   [2].  There was a meeting on Jul 10, but no notes from that yet.

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
 - All Committers are also PMC members, see the PMC Changes section for
   details

## Releases:
 - accumulo-1.9.3 was released on Wed Apr 10 2019

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 86 issues created [3] and 70 closed [4] across all the Accumulo repos
   since the last report.
 - 134 pull requests created [5] and 135 closed [6] across all the Accumulo
   repos since the last report.

[1]: https://accumulo.apache.org/release/accumulo-1.9.3/
[2]:
https://lists.apache.org/thread.html/953ddb7f3d621daa1cc068804dd7d813469c147b29778e68081a310f@%3Cdev.accumulo.apache.org%3E
[3]:
https://github.com/search?q=is:issue+created:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[4]:
https://github.com/search?q=is:issue+closed:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[5]:
https://github.com/search?q=is:pr+created:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[6]:
https://github.com/search?q=is:pr+closed:2019-04-17..2019-07-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp

Fwd: ApacheCon EU 2019 Travel Assistance Applications now open!

[Michael Wall]

-- Forwarded message -
From: Christofer Dutz 
Date: Fri, Jun 21, 2019 at 3:56 AM
Subject: ApacheCon EU 2019 Travel Assistance Applications now open!
To: 


Hi pmcs@!,

The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon EU 2019 are now open!

This announcement serves as a purpose for you (pmcs@) to let members of
your community know about both ApacheCon EU 2019 and about the TAC
assistance available to attend. Could you please forward this announcement
to your community, along with (if possible) information on how your project
is involved in ApacheCon this year?

We will be supporting ApacheCon EU, Berlin, Germany, 22nd - 24th October
2019.

TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons. For more info on this years
applications and qualifying criteria, please visit the TAC website at <
https://www.apache.org/travel/ >. Applications are already open, so don't
delay!

*Important: Applications close on Wednesday, July 14th, 2019.*

Applicants have until the closing date above to submit their applications
(which should contain as much supporting material as required to
efficiently and accurately process their request), this will enable TAC to
announce successful awards shortly afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds; therefore, we encourage (as always) anyone thinking
about sending in an application to do so ASAP.

We look forward to greeting many of you in Berlin in Oktober, 2019!

Kind Regards,
Chris
(On behalf of the Travel Assistance Committee)

Fwd: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.

[Michael Wall]

-- Forwarded message -
From: Gavin McDonald 
Date: Fri, May 17, 2019 at 2:30 AM
Subject: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.
To: 


Hi PMCs!

Please redistribute the below to your user and dev lists, feel free to also
use social media to spread the word. Thanks!

Gav... TAC Team

---

The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon NA 2019 are now open!

We will be supporting ApacheCon NA Las Vegas, Nevada on 9th - 12th
September 2019

 TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons.
For more info on this years applications and qualifying criteria, please
visit the TAC website at < http://www.apache.org/travel/ <
http://www.apache.org/travel/> >. Applications opened today and will close
around the 21st June.

Important: Applications close on June 21st, 2019. Applicants have until the
closing date above to submit their applications (which should contain as
much supporting material as required to efficiently and accurately process
their request), this will enable TAC to announce successful awards shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.
We look forward to greeting many of you in Las Vegas!

Kind Regards,
Gavin - (On behalf of the Travel Assistance Committee)

Re: Triaging JIRA issues

[Michael Wall]

What about setting aside some time at the next hack day?  We could show
Jira on a big monitor and several of us go through the tickets one at a
time and make some decisions.  Probably should set some ground rules and
have someone facilitate to stay on track.  I don't imagine we would or
should get through them all in one sitting but we could chip away at the
800.

Mike

On Mon, Apr 22, 2019 at 9:04 PM Christopher  wrote:

> Hi Accumulo Devs,
>
> As you may have noticed (or not) from the recent barrage of emails to
> the notifications@ list, I'm trying to triage and close as many open
> JIRA issues as possible, so the ones that are left represent
> meaningful work.
> I want to do this to help complete the transition from JIRA to GitHub
> issues shortly after the 2.0 release (if not before).
>
> I'd prefer not to simply ignore all those issues, though... because
> some are actually still bugs, and some might be important, but
> forgotten. I also don't want to naively move all of those remaining to
> GitHub and create a sea of noise there.
>
> So, I'm trying to triage them, starting with the low-hanging fruit in
> the first few passes, to reduce the noise as quickly as possible. In
> the last week, we've closed about 10%, leaving around 800 left, but
> that's still only a dent. The faster the low-hanging fruit gets
> cleared out, the better off we are, but after the low-hanging fruit
> gets cleared out, the remaining issues are going to take successively
> longer to triage, fix, and/or close, so it's not like one or two
> people can keep up the 10% per week pace. Help is needed.
>
> There are at least two easy ways to help if you anybody wishes to:
> 1. Triage issues that you have reported yourself, and close ones that
> are unimportant or no longer applicable or
> 2. Find trivial/easy/fast issues to create a pull request to fix, so
> we can close them as soon as they are fixed.
>
> Any help would be appreciated.
>
> Thanks,
> Christopher
>

Re: new committer question

[Michael Wall]

Thanks, I don't disagree with anything you posted here.  So let's focus on
the specific case where an issue exists in Jira currently and someone is
going to work on it.  I will propose the following for discussion.

1 - If no further discussion needs to happen before code is written, simply
create a PR and reference the Jira issue.  When the PR is merged, we can
close the Jira issue and reference the PR.  All further discussion about
the issue happens outside of Jira on the PR.
2 - If any discussion is required before submitting code, create an issue
in github and reference the Jira issue.  Then we can close the issue in
Jira and reference the github issue.  No further discussion happens on Jira
about the issue, it happens on the github issue and the PR.

Mike

On Wed, Apr 17, 2019 at 10:55 AM Christopher  wrote:

> My opinion isn't a principled one... it's a practical one. So, if it
> makes sense in some cases, certainly, create the separate issue. For
> example, it can be useful when you want to report an issue now, but
> don't have time to fix it right away. Or, if it's a complex issue that
> requires coordination to plan, to save work. Tracking issues for
> multiple PRs for different versions or subtasks are also useful
> separate from the PR.
>
> What I've been annoyed by in the past is somebody creating an issue to
> fix a small typo (or other small issue) and then immediately creating
> a PR within 5 minutes. In such cases, they weren't created because
> discussion was needed; they were created merely to follow some
> prescribed workflow for its own sake. I just want to avoid people
> creating unnecessary work for those reviewers and release managers who
> spend all their time triaging and labeling issues, and to avoid
> unnecessary work for themselves and causing confusion for users when
> discussions are spread across multiple pages.
>
> So, sometimes it makes sense, but one shouldn't just create one out of
> habit, or because it is expected. They should do so, thoughtfully, for
> a specific and intentional reason.
>
> However, in this specific case, there's already an issue on JIRA, and
> the PR will create a second one. There's no need to create a third,
> especially for a trivial task such as creating unit tests for a few
> constructors.
>
> Also, keep in mind that discussion can occur on the mailing list for
> design and in the code review. GitHub also allows creating "Draft" PRs
> to mock up something quickly to facilitate discussion. In all cases,
> people should engage in an appropriate forum with intention, rather
> than merely following specific practices because they believe it to be
> expected by a predefined workflow.
>
> On Wed, Apr 17, 2019 at 10:26 AM Michael Wall  wrote:
> >
> > Hi Christopher,
> >
> > I'll disagree with you here.  Going straight to a PR makes sense to me
> > sometimes, but not always.  What is missing in the straight to PR model
> is
> > any discussion that would drive the development.  A ticket could be used
> to
> > hash out details like assumptions or requirements or project design
> > preferences or historical approaches that have been tried before writing
> > any code.  What I was trying to avoid is having a new contributor do work
> > to put up a PR only to have to go back and rework the solution when a
> > discussion in advance could have prevented that.  Or even worse have the
> PR
> > rejected entirely for some reason.  Maybe the idea is already implemented
> > and the contributor didn't see it in the code, or maybe the feature is
> out
> > of scope for the project  or whatever.  I don't see having an issue as
> > redundant but that is just my opinion.
> >
> > Mike
> >
> > On Wed, Apr 17, 2019 at 10:03 AM Christopher 
> wrote:
> >
> > > You don't need to create a new issue on GitHub. You can just create a
> > > Pull Request with the changes. PRs serve as their own issue. Creating
> > > an issue, and then creating a PR would be redundant.
> > >
> > > On Wed, Apr 17, 2019 at 9:45 AM Resnik, Donald J
> > >  wrote:
> > > >
> > > > Mike,
> > > >
> > > > Thanks, I will make the ticket in github and grab it.
> > > >
> > > > Don
> > > > 
> > > > From: Michael Wall 
> > > > Sent: Wednesday, April 17, 2019 8:41 AM
> > > > To: dev
> > > > Subject: Re: new committer question
> > > >
> > > > [External Email]
> > > >
> > > >
> --
> > > > Hi Don,
> > > >
> > &g

Re: [REPORT] Apache Accumulo - April 2019

[Michael Wall]

Rich Bowen (rb commented on the report, I think that is who it is) added
the Hack Day to https://events.apache.org/event/index.html.  Next report I
need to add details on

- what the event accomplished
- the turnout
- feedback from those that did not or could not attend

Mike

On Wed, Apr 10, 2019 at 12:17 PM Michael Wall  wrote:

> ## Description:
>  - The Apache Accumulo sorted, distributed key/value store is a robust,
>scalable, high performance data storage system that features cell-based
>access control and customizable server-side processing.  It is based on
>Google's BigTable design and is built on top of Apache Hadoop,
> Zookeeper,
>and Thrift.
>
> ## Issues:
>  - There are no issues requiring board attention at this time.
>
> ## Activity:
>  - There was 1 new release, Accumulo-2.0.0-alpha-2 since the last
>report [1].  Progress toward the 2.0.0 release continues.
>  - A 1.9.3 is in the works with a release soon [2].
>  - The community once again started a monthly "Hack Day" in Columbia
>MD that is open to all contributors [3].  No decisions will be made off
>list at these events and a summary will be posted to the mailing list.
>
> ## Health report:
>  - The project remains healthy.  Activity levels on mailing lists, issues
> and
>pull requests remain constant.
>
> ## PMC changes:
>  - Currently 34 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Nick Felts on Thu Mar 22 2018
>
> ## Committer base changes:
>  - All Committers are also PMC members, see the PMC Changes section for
>details
>
> ## Releases:
>  - accumulo-2.0.0-alpha-2 was released on Wed Jan 30 2019
>
> ## Mailing list activity:
>  - Nothing significant in the figures
>
> ## Issue activity:
>  - 78 issues created [4] and 55 closed [5] across all the Accumulo repos
>since the last report.
>  - 153 pull requests created [6] and 152 closed [7] across all the Accumulo
>repos since the last report.
>
> [1]: https://accumulo.apache.org/release/accumulo-2.0.0-alpha-2/
> [2]: https://accumulo.apache.org/release/accumulo-1.9.3/
> [3]:
> https://lists.apache.org/thread.html/9817962004326e233b8360f945420a3ffed4526f181098aaf4b76e66@%3Cdev.accumulo.apache.org%3E
> [4]:
> https://github.com/search?q=is:issue+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> [5]:
> https://github.com/search?q=is:issue+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> [6]:
> https://github.com/search?q=is:pr+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> [7]:
> https://github.com/search?q=is:pr+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
>
>

Re: new committer question

[Michael Wall]

Hi Christopher,

I'll disagree with you here.  Going straight to a PR makes sense to me
sometimes, but not always.  What is missing in the straight to PR model is
any discussion that would drive the development.  A ticket could be used to
hash out details like assumptions or requirements or project design
preferences or historical approaches that have been tried before writing
any code.  What I was trying to avoid is having a new contributor do work
to put up a PR only to have to go back and rework the solution when a
discussion in advance could have prevented that.  Or even worse have the PR
rejected entirely for some reason.  Maybe the idea is already implemented
and the contributor didn't see it in the code, or maybe the feature is out
of scope for the project  or whatever.  I don't see having an issue as
redundant but that is just my opinion.

Mike

On Wed, Apr 17, 2019 at 10:03 AM Christopher  wrote:

> You don't need to create a new issue on GitHub. You can just create a
> Pull Request with the changes. PRs serve as their own issue. Creating
> an issue, and then creating a PR would be redundant.
>
> On Wed, Apr 17, 2019 at 9:45 AM Resnik, Donald J
>  wrote:
> >
> > Mike,
> >
> > Thanks, I will make the ticket in github and grab it.
> >
> > Don
> > 
> > From: Michael Wall 
> > Sent: Wednesday, April 17, 2019 8:41 AM
> > To: dev
> > Subject: Re: new committer question
> >
> > [External Email]
> >
> > --
> > Hi Don,
> >
> > As Christopher mentioned, we are not using JIRA for tracking issue
> > anymore.  I would suggest creating a new issue on github with the info
> for
> > the ticket you want to work and maybe a link to the JIRA issue for
> > historical reference.  Then make a comment on the JIRA ticket that links
> > the github issue.  Discussion on the ticket can then happen on github and
> > if you create a PR you can link the github issue.
> >
> > Mike
> >
> > On Tue, Apr 16, 2019 at 8:47 PM Resnik, Donald J <
> > donald.res...@asrcfederal.com> wrote:
> >
> > > Chris,
> > >
> > > Thanks for the email.  I would be happy to take the ticket you
> suggested:
> > >
> > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO-2D4377=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=F2YcX4M_wpkeFWtlw6oBZaYIXfQ2EDwKRc_xOrI7xK0=
> > >
> > > Is there some level of Jira access I can get so I can grab the ticket,
> or
> > > is there another protocol to follow.  I was not able to assign the
> ticket
> > > to myself after I created my ASF Jira account (username: donresnik)
> > >
> > > Thanks,
> > >
> > > Don
> > > 
> > > From: Christopher 
> > > Sent: Tuesday, April 16, 2019 2:13 PM
> > > To: accumulo-dev
> > > Subject: Re: new committer question
> > >
> > > [External Email]
> > >
> > > --
> > > Hi Don! Welcome to the community.
> > >
> > > Were you looking on JIRA or GitHub?
> > > We're trying to track new issues on GitHub at
> > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_accumulo_issues=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=x0Dp6qfyi6dOk4DdBm3Mh3S9P_pMw0qwfNbStlhek8g=
> > > However, there's a backlog of issues that still exist on
> > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=WqcX-yHKvichfVFOBmwkJfniF5x3ZU_OJfepzaDlY_0=
> > > that may still be valid
> > > (uncertain, as most of them are quite old and we're slowly triaging).
> > > Looking there, I found
> > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO-2D4377=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=F2YcX4M_wpkeFWtlw6oBZaYIXfQ2EDwKRc_xOrI7xK0=
> > > that looks like a
> > > really simple starting point, to at least get used to contributing.
> > >
> > > On Mon, Apr 15, 2

Re: new committer question

[Michael Wall]

Hi Don,

As Christopher mentioned, we are not using JIRA for tracking issue
anymore.  I would suggest creating a new issue on github with the info for
the ticket you want to work and maybe a link to the JIRA issue for
historical reference.  Then make a comment on the JIRA ticket that links
the github issue.  Discussion on the ticket can then happen on github and
if you create a PR you can link the github issue.

Mike

On Tue, Apr 16, 2019 at 8:47 PM Resnik, Donald J <
donald.res...@asrcfederal.com> wrote:

> Chris,
>
> Thanks for the email.  I would be happy to take the ticket you suggested:
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO-2D4377=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=F2YcX4M_wpkeFWtlw6oBZaYIXfQ2EDwKRc_xOrI7xK0=
>
> Is there some level of Jira access I can get so I can grab the ticket, or
> is there another protocol to follow.  I was not able to assign the ticket
> to myself after I created my ASF Jira account (username: donresnik)
>
> Thanks,
>
> Don
> 
> From: Christopher 
> Sent: Tuesday, April 16, 2019 2:13 PM
> To: accumulo-dev
> Subject: Re: new committer question
>
> [External Email]
>
> --
> Hi Don! Welcome to the community.
>
> Were you looking on JIRA or GitHub?
> We're trying to track new issues on GitHub at
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_accumulo_issues=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=x0Dp6qfyi6dOk4DdBm3Mh3S9P_pMw0qwfNbStlhek8g=
> However, there's a backlog of issues that still exist on
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=WqcX-yHKvichfVFOBmwkJfniF5x3ZU_OJfepzaDlY_0=
> that may still be valid
> (uncertain, as most of them are quite old and we're slowly triaging).
> Looking there, I found
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO-2D4377=DwIFaQ=Ff2GokX4A_6S-cy_JRNEiQ=7sXp0We1OQQKRSGyjz35VSGU6op68dwzfY3c89DwDgBombhjVkfUnmcvB18wjBra=Z5TrAOFD4oAH-XefdwTiyRYuvd5C5QyLX0NPxa3ZRQk=F2YcX4M_wpkeFWtlw6oBZaYIXfQ2EDwKRc_xOrI7xK0=
> that looks like a
> really simple starting point, to at least get used to contributing.
>
> On Mon, Apr 15, 2019 at 8:13 PM Resnik, Donald J
>  wrote:
> >
> > Accumulo devs,
> >
> > I am interested in starting to contribute to Accumulo.  I was looking at
> the newbie tickets but a lot of them look pretty old so I wanted to make
> sure they were still relevant before grabbing one.
> >
> > Any info on specific newbie tickets that would be good to start with
> would be appreciated.
> >
> > Thanks,
> >
> > Don Resnik
> >
> > 
> >
> > The preceding message (including attachments) is covered by the
> Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is
> intended only for the person or entity to which it is addressed, and may
> contain information that is confidential, protected by attorney-client or
> other privilege, or otherwise protected from disclosure by law. If you are
> not the intended recipient, you are hereby notified that any retention,
> dissemination, distribution, or copying of this communication is strictly
> prohibited. Please reply to the sender that you have received the message
> in error and destroy the original message and all copies.
>
> 
>
> The preceding message (including attachments) is covered by the Electronic
> Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only
> for the person or entity to which it is addressed, and may contain
> information that is confidential, protected by attorney-client or other
> privilege, or otherwise protected from disclosure by law. If you are not
> the intended recipient, you are hereby notified that any retention,
> dissemination, distribution, or copying of this communication is strictly
> prohibited. Please reply to the sender that you have received the message
> in error and destroy the original message and all copies.
>

Re: [RESULT][VOTE] Apache Accumulo 1.9.3-rc3

[Michael Wall]

Thanks Christopher

On Wed, Apr 10, 2019 at 8:05 PM Christopher  wrote:

> Completed release tasks:
>
> In git:
> * Merge 1.9.3-rc3-next into 1.9, and 1.9 into master to preserve history
> * Create GPG-signed release tag rel/1.9.3
> * Clean up RC branches
>
> In dist-SVN:
> * Upload release artifacts, signatures, and sha512 sums to
> dist/release area for mirrors
>
> In Nexus:
> * Release the 1.9.3-rc3 staging repository to Maven Central
> * Drop old (rc1,rc2) staging repos
>
> In GitHub:
> * Updated 1.9.3 label description in GitHub issues to say "was fixed"
> * Ensured no open issues with 1.9.3 label
>
> Miscellaneous:
> * Updated release info at reporter.apache.org
>
> TODO (I'll work on these tomorrow, 2019-04-11, after the mirrors sync):
>
> On website:
> * complete release notes
> * update previous release notes (as archived or archived-critical)
> * update user manual for 1.9
> * update _config.yml
> * update _includes/nav.html
> * update doap
> * update downloads page
> * update javadocs
>
> In dist-SVN:
> * Archive 1.9.2 artifacts (after updating website)
>
> Email:
> * Draft and send announcement
>
>
> On Wed, Apr 10, 2019 at 7:30 PM Christopher  wrote:
> >
> > This vote passes with the following binding votes:
> > +1 mmiller
> > +1 edcoleman
> > +1 mjwall
> > +1 phrocker
> > +1 jmark99
> > +1 adamjshook
> > +1 ctubbsii
> >
> > And the following non-binding votes:
> > +1 Jeffrey Manno
> > +1 Jeffrey Zeiberg
> >
> > And no other votes, for a total of +7(+2)
> >
> > I'll begin working on the release tasks ASAP and report back here as I
> > complete the checklist.
> >
> > Thanks again for voting!
> >
> > --
> > Christopher
> >
> >
> > On Wed, Apr 10, 2019 at 7:23 PM Christopher  wrote:
> > >
> > > +1 for me also.
> > >
> > > * Verified all ITs pass with Hadoop 2 and Hadoop 3 profiles
> > > * Verified source tarball matches git commit
> > > * Verified all sigs and checksums
> > > * Verified binary tarball contains the same jars staged in Maven
> > > * Verified all jars have corresponding sources and javadoc jars
> > >
> > > On Wed, Apr 10, 2019 at 3:03 PM Jeffrey Zeiberg 
> wrote:
> > > >
> > > > +1
> > > >
> > > > Verified hashes
> > > > Ran 'mvn clean package -Psunny' and unit tests with success.
> > > >
> > > >
> > > >
> > > > On Wed, Apr 10, 2019 at 1:02 PM Jeffrey Manno <
> jeffreymann...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Verified hashes
> > > > > Ran 'mvn clean package -Psunny' and unit tests with success.
> > > > > Successfully ran instance with Uno and tested some of the basic
> shell
> > > > > features.
> > > > > Successfully ran a short continuous ingest and bulk ingest test
> then
> > > > > scanned data, on a local machine.
> > > > > Successfully performed compaction as well.
> > > > >
> > > > > On Wed, Apr 10, 2019 at 12:52 PM Owens, Mark 
> wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Verified hashes
> > > > > > Built from source
> > > > > > Successfully ran maven sunny profile and unit tests.
> > > > > > Used Uno to create running instance and test basic features via
> the shell
> > > > > >
> > > > > > -Original Message-
> > > > > > From: Christopher 
> > > > > > Sent: Friday, April 5, 2019 9:57 PM
> > > > > > To: accumulo-dev 
> > > > > > Subject: [VOTE] Apache Accumulo 1.9.3-rc3
> > > > > >
> > > > > > Accumulo Developers,
> > > > > >
> > > > > > Please consider the following candidate for Apache Accumulo
> 1.9.3.
> > > > > >
> > > > > > Git Commit:
> > > > > > a834aa8f36f1305b3d41abccb4eadc4f3b39302c
> > > > > > Branch:
> > > > > > 1.9.3-rc3
> > > > > >
> > > > > > If this vote passes, a gpg-signed tag will be created using:
> > > > > > git tag -f -m 'Apache Accumulo 1.9.3' -s rel/1.9.3 \
> > > > > > a834aa8f36f1305b3d41abccb4eadc4f3b39302c
> > > > > >
> > > > > > Staging repo:
> > > > > >
> > > > >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1078
> > > > > > Source (official release artifact):
> > > > > >
> > > > > >
> > > > >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1078/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-src.tar.gz
> > > > > > Binary:
> > > > > >
> > > > >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1078/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-bin.tar.gz
> > > > > >
> > > > > > Append ".asc" to download the cryptographic signature for a given
> > > > > artifact.
> > > > > > (You can also append ".sha1" or ".md5" instead in order to
> verify the
> > > > > > checksums generated by Maven to verify the integrity of the Nexus
> > > > > > repository staging area.)
> > > > > >
> > > > > > Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > > > > > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > > > > >
> > > > > > In addition to the tarballs and their signatures, the following
> checksum
> > > > > > files will be added to the dist/release SVN area after release:
> > 

[REPORT] Apache Accumulo - April 2019

[Michael Wall]

## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new release, Accumulo-2.0.0-alpha-2 since the last
   report [1].  Progress toward the 2.0.0 release continues.
 - A 1.9.3 is in the works with a release soon [2].
 - The community once again started a monthly "Hack Day" in Columbia
   MD that is open to all contributors [3].  No decisions will be made off
   list at these events and a summary will be posted to the mailing list.

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
 - All Committers are also PMC members, see the PMC Changes section for
   details

## Releases:
 - accumulo-2.0.0-alpha-2 was released on Wed Jan 30 2019

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 78 issues created [4] and 55 closed [5] across all the Accumulo repos
   since the last report.
 - 153 pull requests created [6] and 152 closed [7] across all the Accumulo
   repos since the last report.

[1]: https://accumulo.apache.org/release/accumulo-2.0.0-alpha-2/
[2]: https://accumulo.apache.org/release/accumulo-1.9.3/
[3]:
https://lists.apache.org/thread.html/9817962004326e233b8360f945420a3ffed4526f181098aaf4b76e66@%3Cdev.accumulo.apache.org%3E
[4]:
https://github.com/search?q=is:issue+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[5]:
https://github.com/search?q=is:issue+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[6]:
https://github.com/search?q=is:pr+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[7]:
https://github.com/search?q=is:pr+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp

Re: Monthly Accumulo Hack Day

[Michael Wall]

Thanks to everyone who showed up for the Hack Day yesterday.  Just a few
notes

- Christopher spent some time giving a high level overview of Accumulo to
some new contributors
- There was a discussion of resources vs complexity and about moving away
from complexity
- Another discussion on the current integration test frameworks

No decisions were made.  Please feel free to add anything I missed.

Next Hack Day will be on 14 May.  Please email [ibella|mjwall]@apache.org
if you need the address.

On Thu, Apr 4, 2019 at 8:47 AM Michael Wall  wrote:

> My company, ASRC, has offered to host the Accumulo community for a hack
> day.  Looking to do the 2nd Tues of the month, doors will be open from
> 8-5ish.  First one will be next Tues, 9 Apr.
>
> All are invited, we just need to know about how many.  If you are planning
> to attend, email ibe...@apache.org and mjw...@apache.org and we will send
> you the address.
>
> Thanks, hope to see you there.
>
> Mike
>

Re: [DRAFT] [REPORT] Apache Accumulo - April 2019

[Michael Wall]

Thanks for the review Josh.

No prospects I am aware of.  I'll acknowledge no decisions are being made
at the Hack Day.

Sending this in shortly

On Tue, Apr 9, 2019 at 2:49 PM Josh Elser  wrote:

> Some general comments that I suspect the board will ask on their own. If
> you want to proactively address them, it might keep away some
> back-and-forth, but it's up to you.
>
> * Any prospects on new C/PMC?
> * An acknowledgement that no decisions are being made at the Hack Day
> and there will be some summary of relevant discussions on the dev list
> for those who were not physically present.
>
> Looks like you covered all of the good stuff.
>
> On 4/9/19 9:58 AM, Michael Wall wrote:
> > The Apache Accumulo PMC decided to draft our quarterly board
> > reports on the dev list. Here is a draft of our report which is due
> > by Wednesday, Apr 10, 1 week before the board meeting on
> > Wednesday, Apr 17. Please let me know if you have any feedback.
> >
> > I will submit this tomorrow morning.  Sorry for the short timeline.
> >
> > Mike
> >
> > 
> >
> > ## Description:
> >   - The Apache Accumulo sorted, distributed key/value store is a robust,
> > scalable, high performance data storage system that features
> cell-based
> > access control and customizable server-side processing.  It is based
> on
> > Google's BigTable design and is built on top of Apache Hadoop,
> Zookeeper,
> > and Thrift.
> >
> > ## Issues:
> >   - There are no issues requiring board attention at this time.
> >
> > ## Activity:
> >   - There was 1 new release, Accumulo-2.0.0-alpha-2 since the last
> > report [1].  Progress toward the 2.0.0 release continues.
> >   - A 1.9.3 is in the works with a release soon [2].
> >   - The community once again started a monthly "Hack Day" in Columbia
> > MD that is open to all contributors [3].
> >
> > ## Health report:
> >   - The project remains healthy.  Activity levels on mailing lists,
> issues
> > and
> > pull requests remain constant.
> >
> > ## PMC changes:
> >   - Currently 34 PMC members.
> >   - No new PMC members added in the last 3 months
> >   - Last PMC addition was Nick Felts on Thu Mar 22 2018
> >
> > ## Committer base changes:
> >   - All Committers are also PMC members, see the PMC Changes section for
> > details
> >
> > ## Releases:
> >   - accumulo-2.0.0-alpha-2 was released on Wed Jan 30 2019
> >
> > ## Mailing list activity:
> >   - Nothing significant in the figures
> >
> > ## Issue activity:
> >   - 78 issues created [4] and 55 closed [5] across all the Accumulo repos
> > since the last report.
> >   - 153 pull requests created [6] and 152 closed [7] across all the
> Accumulo
> > repos since the last report.
> >
> > [1]: https://accumulo.apache.org/release/accumulo-2.0.0-alpha-2/
> > [2]: https://accumulo.apache.org/release/accumulo-1.9.3/
> > [3]:
> >
> https://lists.apache.org/thread.html/9817962004326e233b8360f945420a3ffed4526f181098aaf4b76e66@%3Cdev.accumulo.apache.org%3E
> > [4]:
> >
> https://github.com/search?q=is:issue+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> > [5]:
> >
> https://github.com/search?q=is:issue+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> > [6]:
> >
> https://github.com/search?q=is:pr+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> > [7]:
> >
> https://github.com/search?q=is:pr+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> >
>

Re: [VOTE] Apache Accumulo 1.9.3-rc3

[Michael Wall]

+1

Verified asc and sha512 signatures
successful 'mvn clean package -Psunny' from src tar.gz
started up built artifact on Hadoop 2.9.2 locally, inserted data and scanned


On Mon, Apr 8, 2019 at 9:50 PM Ed Coleman  wrote:

> +1
>
> Verified published commit git sha matches
> Verified binary and src tar signatures.
> Build and verify passed without failures (-Psunny) on local machine
> Ran on small cluster, 2 tservers and a master node, and performed some
> basic checks with no issues seen.
>   - performed bulk ingest.
>   - scan of data and metadata tables completed.
>   - created and dropped tables.
>   - successfully ran compactions.
>   - enabled FATE metrics and validated they published via JMX
>
>
> -Original Message-
> From: Christopher [mailto:ctubb...@apache.org]
> Sent: Friday, April 05, 2019 9:57 PM
> To: accumulo-dev 
> Subject: [VOTE] Apache Accumulo 1.9.3-rc3
>
> Accumulo Developers,
>
> Please consider the following candidate for Apache Accumulo 1.9.3.
>
> Git Commit:
> a834aa8f36f1305b3d41abccb4eadc4f3b39302c
> Branch:
> 1.9.3-rc3
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.9.3' -s rel/1.9.3 \
> a834aa8f36f1305b3d41abccb4eadc4f3b39302c
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1078
> Source (official release artifact):
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1078/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1078/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-bin.tar.gz
>
> Append ".asc" to download the cryptographic signature for a given artifact.
> (You can also append ".sha1" or ".md5" instead in order to verify the
> checksums generated by Maven to verify the integrity of the Nexus
> repository staging area.)
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>
> In addition to the tarballs and their signatures, the following checksum
> files will be added to the dist/release SVN area after release:
> accumulo-1.9.3-src.tar.gz.sha512 will contain:
> SHA512 (accumulo-1.9.3-src.tar.gz) =
>
> 0d0a9101ddf9f64e13ebc4f381ff663ffb9ac3d0826ad3cbc0e6f9da960bb8fed886b5feab643857557329c6d833abd2f561a13273d62cb877d8120c28362e06
> accumulo-1.9.3-bin.tar.gz.sha512 will contain:
> SHA512 (accumulo-1.9.3-bin.tar.gz) =
>
> dcda2ca6188314d43984282cf6fb32f53f93eb98e9c01d2988937b5c790b946ab8ced1d3a57171caaa32684cabbd2eabceaa955342fcd077bd78f1cc8fb22496
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release/accumulo-1.9.3/
>
> Release testing instructions:
> https://accumulo.apache.org/contributor/verifying-release
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.9.3 release of Apache Accumulo.
>
> This vote will remain open until at least Tue Apr  9 02:00:00 UTC 2019.
> (Mon Apr  8 22:00:00 EDT 2019 / Mon Apr  8 19:00:00 PDT 2019) Voting can
> continue after this deadline until the release manager sends an email
> ending the vote.
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1078/
> # note the trailing slash is needed
>
>

[DRAFT] [REPORT] Apache Accumulo - April 2019

[Michael Wall]

The Apache Accumulo PMC decided to draft our quarterly board
reports on the dev list. Here is a draft of our report which is due
by Wednesday, Apr 10, 1 week before the board meeting on
Wednesday, Apr 17. Please let me know if you have any feedback.

I will submit this tomorrow morning.  Sorry for the short timeline.

Mike



## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new release, Accumulo-2.0.0-alpha-2 since the last
   report [1].  Progress toward the 2.0.0 release continues.
 - A 1.9.3 is in the works with a release soon [2].
 - The community once again started a monthly "Hack Day" in Columbia
   MD that is open to all contributors [3].

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
 - All Committers are also PMC members, see the PMC Changes section for
   details

## Releases:
 - accumulo-2.0.0-alpha-2 was released on Wed Jan 30 2019

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 78 issues created [4] and 55 closed [5] across all the Accumulo repos
   since the last report.
 - 153 pull requests created [6] and 152 closed [7] across all the Accumulo
   repos since the last report.

[1]: https://accumulo.apache.org/release/accumulo-2.0.0-alpha-2/
[2]: https://accumulo.apache.org/release/accumulo-1.9.3/
[3]:
https://lists.apache.org/thread.html/9817962004326e233b8360f945420a3ffed4526f181098aaf4b76e66@%3Cdev.accumulo.apache.org%3E
[4]:
https://github.com/search?q=is:issue+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[5]:
https://github.com/search?q=is:issue+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[6]:
https://github.com/search?q=is:pr+created:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[7]:
https://github.com/search?q=is:pr+closed:2019-01-17..2019-04-17+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp

Monthly Accumulo Hack Day

[Michael Wall]

My company, ASRC, has offered to host the Accumulo community for a hack
day.  Looking to do the 2nd Tues of the month, doors will be open from
8-5ish.  First one will be next Tues, 9 Apr.

All are invited, we just need to know about how many.  If you are planning
to attend, email ibe...@apache.org and mjw...@apache.org and we will send
you the address.

Thanks, hope to see you there.

Mike

Re: [VOTE] Apache Accumulo 1.9.3-rc2

[Michael Wall]

Thanks for the clarification.  That was a much longer response than I
anticipated, so I think I am having trouble communicating over email.

I was referencing "https://www.apache.org/dev/release-distribution.html;
which says



For every artifact distributed to the public through Apache channels, the
PMC

   - MUST supply a valid
   <https://www.apache.org/dev/release-signing#verifying-signature>
OpenPGP-compatible
   ASCII-armored detached signature
   <https://www.apache.org/dev/release-signing#openpgp-ascii-detach-sig>
file
   - MUST supply at least one checksum file
   - SHOULD supply a SHA-256 and/or SHA-512
   <https://www.apache.org/dev/release-signing#sha-checksum> checksum file
   - SHOULD NOT supply a MD5 or SHA-1 checksum file (because these are
   deprecated)



Our template generates an email with the following


(Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
given artifact.)

In addition to the tarballs, and their signatures, the following checksum
files will be added to the dist/release SVN area after release:
accumulo-1.9.3-src.tar.gz.sha512 will contain:
SHA512 (accumulo-1.9.3-src.tar.gz)
=b366b89295b1835038cb242f8ad46b1d8455753a987333f0e15e3d89749540f2cd59db1bc6cf7100fc9050d3d0bc7340a3b661381549d40f2f0223d4120fd809

accumulo-1.9.3-bin.tar.gz.sha512 will contain:
SHA512 (accumulo-1.9.3-bin.tar.gz)
=cc909296d9bbd12e08064fccaf21e81b754c183a8264dfa2575762c76705fd0c580b50c2b224c60feaeec120bd618fba4d6176d0f53e96e1ca9da0d9e2556f1f

Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
(Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)

Release notes (in progress) can be found at:
https://accumulo.apache.org/release/accumulo-1.9.3/

Release testing instructions:
https://accumulo.apache.org/contributor/verifying-release


That last link has the following



OpenPGP is an asymmetric encryption scheme which lends itself well to the
globally distributed nature of Apache. Verification of a release artifact
can be done using the signature and the release-maker’s public key. Hashes
can be verified using the appropriate command (e.g. sha1sum, md5sum)


So putting that all together, I spent time verify the sha1 and md5 when I
didn't need to.  I was not suggesting we add .sha512 files.  Not suggesting
we change Maven.  The only thing I was suggesting was to make it harder for
me (and others maybe) to make the mistake of checking the sha1 and md5
again.  I do think it is wording on the template, but the inaccuracies in
my suggestion were distracting.  Maybe it is a change to
https://accumulo.apache.org/contributor/verifying-release#foundation-level-requirements
as well.  I'll look for the template in code and make some PRs there and on
the website after I give it some more thought.

Mike


On Tue, Apr 2, 2019 at 11:42 AM Christopher  wrote:

> On Tue, Apr 2, 2019 at 9:32 AM Michael Wall  wrote:
> >
> > If I understand this correctly, you are saying the sha1 and md5 are
> created
> > by nexus?  I do recall the discussion about moving to the stronger
> hashes,
> > so I was surprised to see sha1 and md5 still listed in the VOTE thread.
>
> They are actually created by one of the Maven plugins and uploaded to
> Nexus. Nexus might generate its own to compare/validate them, but that
> would be internal to Nexus. In any case, there is movement in the
> Maven community to move these from one plugin to another (from
> maven-install-plugin to maven-deploy-plugin, IIRC). Currently, Nexus
> upload validation rules require .sha1 and .md5, and the Maven
> dependency resolver uses these to validate downloads on the client.
> These aren't just requirements for ASF's Nexus, but requirements to
> sync artifacts to Maven Central also, and are core parts of the Maven2
> repository format.
>
> In order for Maven to discontinue these, 3 components need to
> simultaneously (or coordinated-ly) update: maven-deploy-plugin, maven
> dependency resolver, and Nexus. I'm sure that will happen at some
> point, but it's going to take some time, and as I've said... all that
> is outside our control.
>
> >
> > When verifying a release, I want to verify the signatures are correct
> and I
> > want to use the asc and sha512 that will show up on the downloads page at
> > https://accumulo.apache.org/downloads/.
> >
> > What about something like "Nexus generates an md5 and sha1 file but those
> > are no longer recommended by Apache for verification of artifacts.  For
> > release verification use the 512 signature below" or something.
> >
>
> Inaccuracies not withstanding (see above for clarification regarding
> which component generates these), the situation is more complex than
> merely not being recommended. First, it is currently not easy or
> reasonabl

Re: [VOTE] Apache Accumulo 1.9.3-rc2

[Michael Wall]

If I understand this correctly, you are saying the sha1 and md5 are created
by nexus?  I do recall the discussion about moving to the stronger hashes,
so I was surprised to see sha1 and md5 still listed in the VOTE thread.

When verifying a release, I want to verify the signatures are correct and I
want to use the asc and sha512 that will show up on the downloads page at
https://accumulo.apache.org/downloads/.

What about something like "Nexus generates an md5 and sha1 file but those
are no longer recommended by Apache for verification of artifacts.  For
release verification use the 512 signature below" or something.

Thanks Christopher.

On Mon, Apr 1, 2019 at 10:21 PM Christopher  wrote:

> Apologies, but I was confused because you said the template was
> wrong... but you quoted a portion of the template which was not wrong,
> and which I've already explained in my original response to Mike.
>
> Once again, those are references to files generated by the Maven
> tooling, outside our control. Granted, we don't have to mention them
> at all. However, the template merely acknowledges their existence.
> Providing information for how those files are named still has value in
> the Maven context, and is useful for any artifact downloaded from
> Maven, not just our tarballs.
>
> Would there be less confusion over this if the template was a bit more
> verbose, saying something like:
> (Append ".asc" to download an artifact's corresponding GPG signature,
> or ".sha1" or ".md5" to verify the checksums generated by Maven.)
>
> If you'd prefer this, or an alternative wording, please change it in
> the repo... or let me know and I'll change it.
>
> On Mon, Apr 1, 2019 at 2:22 PM Josh Elser  wrote:
> >
> > Again, like I included earlier:
> >
> >  > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for
> > a given artifact.)
> >
> > On 4/1/19 1:56 PM, Christopher wrote:
> > > In what way?
> > >
> > > On Mon, Apr 1, 2019 at 1:54 PM Josh Elser  wrote:
> > >>
> > >> Your email template is wrong.
> > >>
> > >> On 4/1/19 1:33 PM, Christopher wrote:
> > >>> Sorry, I don't understand what you mean by 'retelling of "checksums
> of old"'.
> > >>>
> > >>> On Mon, Apr 1, 2019 at 12:30 PM Josh Elser 
> wrote:
> > >>>>
> > >>>> I think Mike's point was your VOTE template does not reflect the
> > >>>> retelling of "checksums of old"
> > >>>>
> > >>>>> (Append ".sha1", ".md5", or ".asc" to download the
> signature/hash for
> > >>>> a given artifact.)
> > >>>>
> > >>>> On 3/31/19 10:54 PM, Christopher wrote:
> > >>>>> Mike,
> > >>>>>
> > >>>>> We already stopped using md5 and sha1 for the release artifacts on
> the
> > >>>>> mirrors. I did this some time ago, and we discussed it on list on
> > >>>>> previous vote threads (last year)... which resulted in me changing
> the
> > >>>>> release candidate build script automated tooling to embed the
> SHA512
> > >>>>> sums for the tarballs directly in the release vote message. I even
> > >>>>> went back and updated the downloads page for the previous releases
> and
> > >>>>> updated the mirrors to be SHA512 only. Because of these steps I
> took,
> > >>>>> Accumulo was one of the first projects across the entire ASF who
> were
> > >>>>> 100% compliant immediately after INFRA VP updated the release
> > >>>>> distribution policy you linked.
> > >>>>>
> > >>>>> *This is a resolved action for Accumulo.*
> > >>>>>
> > >>>>> FWIW, SHA512 was also used as the hash algorithm in the GPG
> signature
> > >>>>> (same as every RC I've ever prepped for ASF). The only remaining
> md5
> > >>>>> and sha1 reference are Maven-specific tooling, and we have no
> control
> > >>>>> over that tooling. We could change the vote template to no longer
> > >>>>> mention them, but I don't see the point since they're still
> relevant
> > >>>>> within the context of Maven artifact hosting, and that's the
> context
> > >>>>> in which they are presented in the vote email.
> > >>>>&g

Re: [RESULT][VOTE] Apache Accumulo 1.9.3-rc2

[Michael Wall]

Thanks Christopher.  I just added a comment on
https://github.com/apache/accumulo/issues/1069 and would like to get this
included in the next RC.

On Mon, Apr 1, 2019 at 10:34 PM Christopher  wrote:

> This vote fails with {-1, -1, -1, -0, +1}.
> I'll prep an RC3 once the issues identified in the thread are resolved.
>
> --
>
> On Wed, Mar 27, 2019 at 7:56 PM Christopher  wrote:
> >
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 1.9.3.
> >
> > This supersedes RC1 and contains the following change:
> > https://github.com/apache/accumulo/pull/1057
> >
> > Git Commit:
> > 94f9782242a1f336e176c282f0f90063a21e361d
> > Branch:
> > 1.9.3-rc2
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.9.3' -s rel/1.9.3 \
> > 94f9782242a1f336e176c282f0f90063a21e361d
> >
> > Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-src.tar.gz
> > Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for
> > a given artifact.)
> >
> > In addition to the tarballs, and their signatures, the following checksum
> > files will be added to the dist/release SVN area after release:
> > accumulo-1.9.3-src.tar.gz.sha512 will contain:
> > SHA512 (accumulo-1.9.3-src.tar.gz) =
> >
> b366b89295b1835038cb242f8ad46b1d8455753a987333f0e15e3d89749540f2cd59db1bc6cf7100fc9050d3d0bc7340a3b661381549d40f2f0223d4120fd809
> > accumulo-1.9.3-bin.tar.gz.sha512 will contain:
> > SHA512 (accumulo-1.9.3-bin.tar.gz) =
> >
> cc909296d9bbd12e08064fccaf21e81b754c183a8264dfa2575762c76705fd0c580b50c2b224c60feaeec120bd618fba4d6176d0f53e96e1ca9da0d9e2556f1f
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.9.3/
> >
> > Release testing instructions:
> > https://accumulo.apache.org/contributor/verifying-release
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.9.3 release of Apache Accumulo.
> >
> > This vote will remain open until at least Sun Mar 31 00:00:00 UTC 2019.
> > (Sat Mar 30 20:00:00 EDT 2019 / Sat Mar 30 17:00:00 PDT 2019)
> > Voting can continue after this deadline until the release manager
> > sends an email ending the vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/
> > # note the trailing slash is needed
>

Re: [VOTE] Apache Accumulo 1.9.3-rc2

[Michael Wall]

-1 for the issue with commons config

I check the signatures, they are good.  We should stop using md5 and sha1
though, see https://www.apache.org/dev/release-distribution#sigs-and-sums.
Has anyone looked at moving to sha256 and/org sha512?
Successful run of mvn clean verify -Psunny

On Sat, Mar 30, 2019 at 11:31 PM Keith Turner  wrote:

> I completed a continuous ingest run on a 10 node cluster running
> Centos 7.  I used the native map.  I had to rebuild Accumulo to work
> around  #1065 inorder to get the verify M/R job to run.
>
> org.apache.accumulo.test.continuous.ContinuousVerify$Counts
> REFERENCED=34417110819
> UNREFERENCED=9097524
>
> On Wed, Mar 27, 2019 at 7:57 PM Christopher  wrote:
> >
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 1.9.3.
> >
> > This supersedes RC1 and contains the following change:
> > https://github.com/apache/accumulo/pull/1057
> >
> > Git Commit:
> > 94f9782242a1f336e176c282f0f90063a21e361d
> > Branch:
> > 1.9.3-rc2
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.9.3' -s rel/1.9.3 \
> > 94f9782242a1f336e176c282f0f90063a21e361d
> >
> > Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-src.tar.gz
> > Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/org/apache/accumulo/accumulo/1.9.3/accumulo-1.9.3-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for
> > a given artifact.)
> >
> > In addition to the tarballs, and their signatures, the following checksum
> > files will be added to the dist/release SVN area after release:
> > accumulo-1.9.3-src.tar.gz.sha512 will contain:
> > SHA512 (accumulo-1.9.3-src.tar.gz) =
> >
> b366b89295b1835038cb242f8ad46b1d8455753a987333f0e15e3d89749540f2cd59db1bc6cf7100fc9050d3d0bc7340a3b661381549d40f2f0223d4120fd809
> > accumulo-1.9.3-bin.tar.gz.sha512 will contain:
> > SHA512 (accumulo-1.9.3-bin.tar.gz) =
> >
> cc909296d9bbd12e08064fccaf21e81b754c183a8264dfa2575762c76705fd0c580b50c2b224c60feaeec120bd618fba4d6176d0f53e96e1ca9da0d9e2556f1f
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.9.3/
> >
> > Release testing instructions:
> > https://accumulo.apache.org/contributor/verifying-release
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.9.3 release of Apache Accumulo.
> >
> > This vote will remain open until at least Sun Mar 31 00:00:00 UTC 2019.
> > (Sat Mar 30 20:00:00 EDT 2019 / Sat Mar 30 17:00:00 PDT 2019)
> > Voting can continue after this deadline until the release manager
> > sends an email ending the vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1077/
> > # note the trailing slash is needed
>

Re: Builds

[Michael Wall]

Yes, I agree.  Sorry, the branch was just for testing until I get it
right.  Ideally in the end all branches have 1 or more Jenkinsfiles.

Thanks for the link to that article Josh.  I honestly don't understand what
yetus gives you and I think I see a fairly simple way to make tests run in
docker with just a Jenkinsfile so I wasn't going to add complexity yet.

Thanks for the input.

Mike

On Tue, Feb 5, 2019 at 3:40 PM Josh Elser  wrote:

> I feel like trying to put the Jenkinsfile in a separate branch might
> cause more headache than it's worth.
>
> Happen to stumble on AW's write-up on a similar subject?
>
> https://effectivemachines.com/2019/01/24/using-apache-yetus-with-jenkins-and-github-part-1/
>
> On 2/5/19 2:35 PM, Michael Wall wrote:
> > I think I see a path forward using a Jenkinsfile.  Please comment on this
> > plan if something doesn't make sense or someone does not agree.
> >
> > 1 - Create a new branch off master called jenkinsfile or such and add a
> > jenkinsfile that runs only unit tests but does it in docker.
> > 2 - Create a new job on jenkins.revelc.net that only builds that branch
> > 3 - Iterate on the jenkinsfile until it works cleanly
> > 4 - Reconfigure the Accumulo-Master job on builds.apache.org to use the
> > Jenkinsfile
> >
> >  From there it will hopefully make sense about what to do next.  Maybe a
> > Jenkinsfile-IT or something.
> >
> > Christopher, looks like I already have permission on jenkins.revelc.net
> to
> > make jobs.
> >
> > Thanks
> >
> > Mike
> >
> > On Sun, Jan 6, 2019 at 10:32 PM Christopher  wrote:
> >
> >> I've seen similar problems with processes left behind on my own
> >> Jenkins instance, but my solution is to periodically log in and nuke
> >> the processes, and even occasionally reboot the instance. I don't
> >> think these options are available to us on builds.apache.org, because
> >> we don't have direct access to them. I'm also not sure why it happens
> >> or why Jenkins doesn't properly clean up child processes leftover from
> >> no-longer-running builds it launched.
> >>
> >> One suggestion was to run in Docker, but I don't know how to do that.
> >> I attempted to do it that way, and got as far as Jenkins running and
> >> connecting to the Docker instance, but the Maven versions available to
> >> configure the Maven build does not seem to match what's inside the
> >> Docker container and the job quickly fails.... so it's not clear how
> >> to do a Maven build in Jenkins with Docker given the options INFRA has
> >> made available to us. Perhaps if they had instructions, or an example
> >> Maven job we could model our jobs after?
> >>
> >>
> >> On Sun, Jan 6, 2019 at 9:34 PM Michael Wall  wrote:
> >>>
> >>> Anyone look at this yet?
> >>>
> >>
> https://lists.apache.org/thread.html/e78b1b8ccaf11eb5cb557ec29d3208c3fec0450fd2b908b3f7922c56@%3Cbuilds.apache.org%3E
> >>>
> >>> Not sure who even has karma to do anything here
> >>> https://builds.apache.org/view/A/view/Accumulo/
> >>
> >
>

Re: List project on website

[Michael Wall]

Hi Flavius,

Apache projects do not and can not endorse commercial products.  All the
projects listed on https://accumulo.apache.org/related-projects/ are open
source.  If you ever open source the Accumulo storage layer, let us know.

Mike




On Wed, Jan 23, 2019 at 6:25 AM Flavius Burca 
wrote:

> Hi,
>
>I would like to list bigconnect.io on the Related Projects section. We
> are using Accumulo as an enterprise database for storing BigConnect graph
> structures. Although BigConnect is open-source, the Accumulo storage layer
> is not and available only in the enterprise version. Can you list the
> project under these circumstances ?
>
> Thanks,
> Flavius
>

[REPORT] Accumulo - Jan 2019

[Michael Wall]

## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new release, Accumulo-2.0.0-alpha-1 since the last
   report [1] to coincide with the Accumulo Summit which was held on
   Oct 15 [2].
 - The PMC decided to stop using IRC and started a new channel on Slack
   for communication with the community [3].
 - There have been a few critical fixes warranting 1.9.3 release soon [4].

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
  - All Committers are also PMC members, see the PMC Changes section for
details

## Releases:
 - accumulo-2.0.0-alpha-1 was released on Sat Oct 13 2018

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 68 issues created [5] and 48 closed [6] across all the Accumulo repos
   since the last report.
 - 140 pull requests created [7] and 136 closed [8] across all the Accumulo
   repos since the last report.

[1]: https://accumulo.apache.org/release/accumulo-2.0.0-alpha-1/
[2]: http://accumulosummit.com/
[3]: https://the-asf.slack.com/messages/CERNB8NDC
[4]:
https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aclosed+label%3Av1.9.3
[5]:
https://github.com/search?q=is:issue+created:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[6]:
https://github.com/search?q=is:issue+closed:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[7]:
https://github.com/search?q=is:pr+created:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[8]:
https://github.com/search?q=is:pr+closed:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp

Re: [DRAFT] [REPORT] Apache Accumulo - Jan 2019

[Michael Wall]

Thanks Keith, thanks Mike. Will modify and send now.

On Tue, Jan 8, 2019 at 6:04 PM Keith Turner  wrote:

> I suspect the board is not looking for too much detail given all of
> the reports they have to read.  I think adding : "There have been a
> few critical fixes warranting 1.9.3 release soon" would be good.  I
> modified the sentence from an earlier email.
>
> On Tue, Jan 8, 2019 at 11:42 AM Mike Miller  wrote:
> >
> > I'd say either 800, 819 or 854 or all of the above.  Basically any that
> > Keith worked on haha.  Maybe he can chose his favorite if you just want
> > one... Keith?
> > https://github.com/apache/accumulo/issues/854
> > https://github.com/apache/accumulo/issues/819
> > https://github.com/apache/accumulo/issues/800
> >
> > On Tue, Jan 8, 2019 at 8:29 AM Michael Wall  wrote:
> >
> > > Thanks Mike,
> > >
> > > Perhaps something from
> > >
> > >
> https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aclosed+label%3Av1.9.3
> > > ?  Any of those you were thinking?
> > >
> > > On Mon, Jan 7, 2019 at 11:54 AM Mike Miller 
> wrote:
> > >
> > > > There have been a few critical fixes in 1.9 and 2.0, both warranting
> > > > releases soon.  You could mention something like that in the
> activity.
> > > >
> > > > On Mon, Jan 7, 2019 at 11:49 AM Josh Elser 
> wrote:
> > > >
> > > > >
> > > > > On 1/7/19 11:26 AM, Michael Wall wrote:
> > > > > > Hi Josh, thanks for reviewing.
> > > > > >
> > > > > > The "PMC Changes" was copied directly from the
> reporter.apache.org
> > > > > > template.  The "Committer base changes" was in response to
> feedback
> > > > from
> > > > > > the board several reports ago asking if all committers were PMC
> > > > > members.  I
> > > > > > could say something like "All Committers are also PMC members,
> see
> > > the
> > > > > PMC
> > > > > > Changes section for details".  Is that what you mean by more
> > > explicit?
> > > > > Or
> > > > > > do you mean something else?
> > > > >
> > > > > I had initially thought just copy/paste'ing the text from the PMC
> > > > > additions was good, but, on second thought, suggesting that readers
> > > look
> > > > > at the PMC additions section in the Committer additions section is
> just
> > > > > as good.
> > > > >
> > > > > Thanks for the careful attention, Mike!
> > > > >
> > > >
> > >
>

Re: [DRAFT] [REPORT] Apache Accumulo - Jan 2019

[Michael Wall]

Thanks Mike,

Perhaps something from
https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aclosed+label%3Av1.9.3
?  Any of those you were thinking?

On Mon, Jan 7, 2019 at 11:54 AM Mike Miller  wrote:

> There have been a few critical fixes in 1.9 and 2.0, both warranting
> releases soon.  You could mention something like that in the activity.
>
> On Mon, Jan 7, 2019 at 11:49 AM Josh Elser  wrote:
>
> >
> > On 1/7/19 11:26 AM, Michael Wall wrote:
> > > Hi Josh, thanks for reviewing.
> > >
> > > The "PMC Changes" was copied directly from the reporter.apache.org
> > > template.  The "Committer base changes" was in response to feedback
> from
> > > the board several reports ago asking if all committers were PMC
> > members.  I
> > > could say something like "All Committers are also PMC members, see the
> > PMC
> > > Changes section for details".  Is that what you mean by more explicit?
> > Or
> > > do you mean something else?
> >
> > I had initially thought just copy/paste'ing the text from the PMC
> > additions was good, but, on second thought, suggesting that readers look
> > at the PMC additions section in the Committer additions section is just
> > as good.
> >
> > Thanks for the careful attention, Mike!
> >
>

Re: [DRAFT] [REPORT] Apache Accumulo - Jan 2019

[Michael Wall]

Got it, thanks for the feedback Josh.

On Mon, Jan 7, 2019 at 11:49 AM Josh Elser  wrote:

>
> On 1/7/19 11:26 AM, Michael Wall wrote:
> > Hi Josh, thanks for reviewing.
> >
> > The "PMC Changes" was copied directly from the reporter.apache.org
> > template.  The "Committer base changes" was in response to feedback from
> > the board several reports ago asking if all committers were PMC
> members.  I
> > could say something like "All Committers are also PMC members, see the
> PMC
> > Changes section for details".  Is that what you mean by more explicit?
> Or
> > do you mean something else?
>
> I had initially thought just copy/paste'ing the text from the PMC
> additions was good, but, on second thought, suggesting that readers look
> at the PMC additions section in the Committer additions section is just
> as good.
>
> Thanks for the careful attention, Mike!
>

Re: [DRAFT] [REPORT] Apache Accumulo - Jan 2019

[Michael Wall]

Hi Josh, thanks for reviewing.

The "PMC Changes" was copied directly from the reporter.apache.org
template.  The "Committer base changes" was in response to feedback from
the board several reports ago asking if all committers were PMC members.  I
could say something like "All Committers are also PMC members, see the PMC
Changes section for details".  Is that what you mean by more explicit?  Or
do you mean something else?

I went through the mailing lists and didn't really find anything else to
add under Activity.  Last three months have been pretty light.  Anyone have
anything we can add to the report?

On Mon, Jan 7, 2019 at 11:12 AM Josh Elser  wrote:

> Thanks for putting a draft together, Mike. A few suggestions:
>
> Please be a little more explicit that Nick was added as a committer. I
> had to read it twice before realizing what you meant.
>
> The report seems fine, perhaps a little light on what the project's
> current trajectory actually is. Since 2.0.0-alpha-1, what are the
> project's goals? Bolstering up the "Activity" header would be
> appreciated by the board, I'm sure.
>
> On 1/6/19 9:30 PM, Michael Wall wrote:
> > The Apache Accumulo PMC decided to draft its quarterly board
> > reports on the dev list. Here is a draft of our report which is due
> > by Wednesday, Jan 9, 1 week before the board meeting on
> > Wednesday, Jan 16. Please let me know if you have any feedback.
> >
> > I will submit this Wed morning.  Thanks to Keith and Mike Walch for help
> > with a script to gather the counts of issues and PRs across all our
> repos.
> >
> > Mike
> >
> > 
> >
> > ## Description:
> >   - The Apache Accumulo sorted, distributed key/value store is a robust,
> > scalable, high performance data storage system that features
> cell-based
> > access control and customizable server-side processing.  It is based
> on
> > Google's BigTable design and is built on top of Apache Hadoop,
> Zookeeper,
> > and Thrift.
> >
> > ## Issues:
> >   - There are no issues requiring board attention at this time.
> >
> > ## Activity:
> >   - There was 1 new release, Accumulo-2.0.0-alpha-1 since the last
> > report [1] to coincide with the Accumulo Summit which was held on
> > Oct 15 [2].
> >   - The PMC decided to stop using IRC and started a new channel on Slack
> > for communication with the community [3].
> >
> > ## Health report:
> >   - The project remains healthy.  Activity levels on mailing lists,
> issues
> > and
> > pull requests remain constant.
> >
> > ## PMC changes:
> >   - Currently 34 PMC members.
> >   - No new PMC members added in the last 3 months
> >   - Last PMC addition was Nick Felts on Thu Mar 22 2018
> >
> > ## Committer base changes:
> >   - All committers are PMC members
> >
> > ## Releases:
> >   - accumulo-2.0.0-alpha-1 was released on Sat Oct 13 2018
> >
> > ## Mailing list activity:
> >   - Nothing significant in the figures
> >
> > ## Issue activity:
> >   - 68 issues created [4] and 48 closed [5] across all the Accumulo repos
> > since the last report.
> >   - 140 pull requests created [6] and 136 closed [7] across all the
> Accumulo
> > repos
> > since the last report.
> >
> > [1]: https://accumulo.apache.org/release/accumulo-2.0.0-alpha-1/
> > [2]: http://accumulosummit.com/
> > [3]: https://the-asf.slack.com/messages/CERNB8NDC
> > [4]:
> >
> https://github.com/search?q=is:issue+created:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> > [5]:
> >
> https://github.com/search?q=is:issue+closed:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> > [6]:
> >
> https://github.com/search?q=is:pr+created:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> > [7]:
> >
> https://github.com/search?q=is:pr+closed:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
> >
>

Builds

[Michael Wall]

Anyone look at this yet?
https://lists.apache.org/thread.html/e78b1b8ccaf11eb5cb557ec29d3208c3fec0450fd2b908b3f7922c56@%3Cbuilds.apache.org%3E

Not sure who even has karma to do anything here
https://builds.apache.org/view/A/view/Accumulo/

[DRAFT] [REPORT] Apache Accumulo - Jan 2019

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
by Wednesday, Jan 9, 1 week before the board meeting on
Wednesday, Jan 16. Please let me know if you have any feedback.

I will submit this Wed morning.  Thanks to Keith and Mike Walch for help
with a script to gather the counts of issues and PRs across all our repos.

Mike



## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new release, Accumulo-2.0.0-alpha-1 since the last
   report [1] to coincide with the Accumulo Summit which was held on
   Oct 15 [2].
 - The PMC decided to stop using IRC and started a new channel on Slack
   for communication with the community [3].

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
 - All committers are PMC members

## Releases:
 - accumulo-2.0.0-alpha-1 was released on Sat Oct 13 2018

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 68 issues created [4] and 48 closed [5] across all the Accumulo repos
   since the last report.
 - 140 pull requests created [6] and 136 closed [7] across all the Accumulo
repos
   since the last report.

[1]: https://accumulo.apache.org/release/accumulo-2.0.0-alpha-1/
[2]: http://accumulosummit.com/
[3]: https://the-asf.slack.com/messages/CERNB8NDC
[4]:
https://github.com/search?q=is:issue+created:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[5]:
https://github.com/search?q=is:issue+closed:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[6]:
https://github.com/search?q=is:pr+created:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp
[7]:
https://github.com/search?q=is:pr+closed:2018-10-17..2019-01-16+repo:apache/accumulo+repo:apache/accumulo-website+repo:apache/accumulo-examples+repo:apache/accumulo-docker+repo:apache/accumulo-testing+repo:apache/accumulo-wikisearch+repo:apache/accumulo-proxy+repo:apache/accumulo-maven-plugin+repo:apache/accumulo-pig+repo:apache/accumulo-instamo-archetype+repo:apache/accumulo-bsp

Re: Can I be added to this list.

[Michael Wall]

Hi Jeffrey,

The mailing lists are self subscribe/unsubscribe.  See details on
http://accumulo.apache.org/contact-us/, but basically email
dev-subscr...@accumulo.apache.org to get started.

Mike

On Thu, Dec 13, 2018 at 2:17 PM Jeffrey Zeiberg  wrote:

> Just joined the project.
>
> Thank you.
>

Re: Slack for Accumulo

[Michael Wall]

Yeah, there are some Apache projects that use slack.  Can you create an
Accumulo channel at https://the-asf.slack.com?  I don't recall what I did
to set up my account there, but I did have to use my apache.org email
account.  The only thing I see from other communities is a small delay for
users since they need to be given access to the channel.

+1 to shutting down IRC.

Mike

On Mon, Dec 10, 2018 at 4:11 PM Christopher  wrote:

> We did have a HipChat room, but we didn't advertise it well and nobody
> really used it. With all that happened with HipChat being bought by
> Atlassian and then sold off to Slack (or something like that), I'm not sure
> where ASF Infra currently stands on providing chat as an ASF resource.
>
> I have no objections to trying out Slack within the project. However, if
> Infra does move towards something in future (like an official ASF Slack
> group), we should try to follow whatever path they pave.
>
> Regardless of whether Slack pans out, we should probably shut down the IRC
> room... hardly anybody uses it, and the few that do are lurkers only or
> bots. It doesn't make sense to continue to advertise it as a way for
> users/devs to contact us.
>
> On Mon, Dec 10, 2018, 15:44 Mike Walch 
> > I would like to create a Slack chatroom for Accumulo and advertise it on
> on
> > our 'contact us' page [1] with an invite link to make it easy to join. Is
> > anyone opposed to this?  There will be no requirement that Accumulo users
> > or developers use Slack. We currently have an IRC chatroom but it's not
> > used much. I think Slack will be used more as it's simpler and saves the
> > latest history which helps if you join an ongoing discussion.  If it ends
> > up being rarely used over the next few months, I am OK with shutting it
> > down.
> >
> > [1]: https://accumulo.apache.org/contact-us/
> >
>

Re: [DRAFT][ANNOUNCE] Apache Accumulo 2.0.0-alpha-1

[Michael Wall]

Looks good to me Christopher, thanks for making a release in time for the
summit.  I agree with Mike about not sending to announce yet

On Mon, Oct 15, 2018, 13:39 Mike Drob  wrote:

> I would not send to a@a.o
>
> On Mon, Oct 15, 2018, 12:35 PM Keith Turner  wrote:
>
> > Sounds good.
> > On Mon, Oct 15, 2018 at 1:16 PM Christopher  wrote:
> > >
> > > The Apache Accumulo project is pleased to announce the release of
> > > Apache Accumulo 2.0.0-alpha-1! This *alpha* release is a preview for
> > > 2.0.0 and contains numerous feature enhancements and API changes.
> > >
> > > While this version is *not* recommended for production use, it is made
> > > available for feedback, testing, and evaluation. Please report any
> issues
> > > you find to our issue tracker[1] or discuss on our dev email list[2].
> > >
> > > ***
> > >
> > > Apache Accumulo® is a sorted, distributed key/value store that
> > > provides robust, scalable data storage and retrieval. With
> > > Apache Accumulo, users can store and manage large data sets
> > > across a cluster. Accumulo uses Apache Hadoop's HDFS to store
> > > its data and Apache ZooKeeper for consensus.
> > >
> > > This version is now available in Maven Central, and at:
> > > https://accumulo.apache.org/downloads/
> > >
> > > The release notes for this alpha can be viewed at:
> > > https://accumulo.apache.org/release/accumulo-2.0.0-alpha-1/
> > >
> > > [1]: https://github.com/apache/accumulo
> > > [2]: dev@accumulo.apache.org
> > >
> > > --
> > > The Apache Accumulo Team
> >
>

Re: [REPORT] Accumulo - October 2018

[Michael Wall]

Noted, thanks Mike.  I'll work that in next time.

Mike

On Wed, Oct 10, 2018 at 11:21 AM Mike Walch  wrote:

> Oops. I thought I was replying to the [Draft] report email.  No worries
> about the stats for this report.  It would be good to include in the other
> repos in future reports.
>
> On Wed, Oct 10, 2018 at 11:16 AM Mike Walch  wrote:
>
> > The accumulo-website, accumulo-testing, accumulo-examles, and
> > accumulo-docker repos should be included in 'Issue activity' statistics.
> > Below are updated stats and links with these repos included.
> >
> > ## Issue activity:
> >  - 56 issues created [3] and 31 closed [4] in the last 3 months
> >  - 106 pull requests created [5] and 105 closed [6] in the last 3 months
> >
> > [3]
> >
> https://github.com/search?q=is%3Apr+repo%3Aapache%2Faccumulo+repo%3Aapache%2Faccumulo-website+repo%3Aapache%2Faccumulo-testing+repo%3Aapache%2Faccumulo-examples+repo%3Aapache%2Faccumulo-docker+created%3A2018-07-18..2018-10-17
> > [4]
> >
> https://github.com/search?q=is%3Apr+repo%3Aapache%2Faccumulo+repo%3Aapache%2Faccumulo-website+repo%3Aapache%2Faccumulo-testing+repo%3Aapache%2Faccumulo-examples+repo%3Aapache%2Faccumulo-docker+closed%3A2018-07-18..2018-10-17
> > [5]
> >
> https://github.com/search?q=is%3Aissue+repo%3Aapache%2Faccumulo+repo%3Aapache%2Faccumulo-website+repo%3Aapache%2Faccumulo-testing+repo%3Aapache%2Faccumulo-examples+repo%3Aapache%2Faccumulo-docker+created%3A2018-07-18..2018-10-17
> > [6]
> >
> https://github.com/search?q=is%3Aissue+repo%3Aapache%2Faccumulo+repo%3Aapache%2Faccumulo-website+repo%3Aapache%2Faccumulo-testing+repo%3Aapache%2Faccumulo-examples+repo%3Aapache%2Faccumulo-docker+closed%3A2018-07-18..2018-10-17
> >
> >
> > On Wed, Oct 10, 2018 at 7:38 AM Michael Wall  wrote:
> >
> >> ## Description:
> >>  - The Apache Accumulo sorted, distributed key/value store is a robust,
> >>scalable, high performance data storage system that features
> cell-based
> >>access control and customizable server-side processing.  It is based
> on
> >>Google's BigTable design and is built on top of Apache Hadoop,
> >> Zookeeper,
> >>and Thrift.
> >>
> >> ## Issues:
> >>  - There are no issues requiring board attention at this time.
> >>
> >> ## Activity:
> >>  - There was 1 new release, Accumulo 1.9.2 since the last
> >>report [1].
> >>  - There were no new committers since the last report.  All committers
> are
> >>also PMC members.
> >>  - The fifth annual Accumulo Summit will be held on Oct 15 in Columbia,
> MD
> >> [2].
> >>
> >> ## Health report:
> >>  - The project remains healthy.  Activity levels on mailing lists,
> issues
> >> and
> >>pull requests remain constant.
> >>
> >> ## PMC changes:
> >>  - Currently 34 PMC members.
> >>  - No new PMC members added in the last 3 months
> >>  - Last PMC addition was Nick Felts on Thu Mar 22 2018
> >>
> >> ## Committer base changes:
> >>  - All committers are PMC members
> >>
> >> ## Releases:
> >>  - accumulo-1.9.2 was released on Wed Jul 18 2018
> >>
> >> ## Mailing list activity:
> >>  - Nothing significant in the figures
> >>
> >> ## Issue activity:
> >>  - 39 issues created [3] and 25 issued [4] closed in the last 3 months
> >>  - 81 pull requests created [5] and 81 closed [6] in the last 3 months
> >>
> >> [1]: https://accumulo.apache.org/release/accumulo-1.9.2/
> >> [2]: http://accumulosummit.com/
> >> [3]:
> >>
> >>
> https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+created%3A2018-07-18..2018-10-17+
> >> [4]:
> >>
> >>
> https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-07-18..2018-10-17+
> >> [5]:
> >>
> >>
> https://github.com/apache/accumulo/pulls?q=is%3Apr+created%3A2018-07-18..2018-10-17
> >> [6]:
> >>
> >>
> https://github.com/apache/accumulo/pulls?q=is%3Apr+closed%3A2018-07-18..2018-10-17
> >>
> >
>

[REPORT] Accumulo - October 2018

[Michael Wall]

## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new release, Accumulo 1.9.2 since the last
   report [1].
 - There were no new committers since the last report.  All committers are
   also PMC members.
 - The fifth annual Accumulo Summit will be held on Oct 15 in Columbia, MD
[2].

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
 - All committers are PMC members

## Releases:
 - accumulo-1.9.2 was released on Wed Jul 18 2018

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 39 issues created [3] and 25 issued [4] closed in the last 3 months
 - 81 pull requests created [5] and 81 closed [6] in the last 3 months

[1]: https://accumulo.apache.org/release/accumulo-1.9.2/
[2]: http://accumulosummit.com/
[3]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+created%3A2018-07-18..2018-10-17+
[4]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-07-18..2018-10-17+
[5]:
https://github.com/apache/accumulo/pulls?q=is%3Apr+created%3A2018-07-18..2018-10-17
[6]:
https://github.com/apache/accumulo/pulls?q=is%3Apr+closed%3A2018-07-18..2018-10-17

[DRAFT] [REPORT] Apache Accumulo - Oct 2018

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
by Wednesday, Oct 10, 1 week before the board meeting on
Wednesday, Oct 17. Please let me know if you have any suggestions.

I will submit this Wed morning.  Thanks

Mike

--

## Description:
 - The Apache Accumulo sorted, distributed key/value store is a robust,
   scalable, high performance data storage system that features cell-based
   access control and customizable server-side processing.  It is based on
   Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
   and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new releases, Accumulo 1.9.2 since the last
   report [1].
 - There were no new committers since the last report.  All committers are
   also PMC members.
 - The fifth annual Accumulo Summit will be held on Oct 15 in Columbia, MD
[2].

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, issues
and
   pull requests remain constant.

## PMC changes:
 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:
 - All committers are PMC members

## Releases:
 - accumulo-1.9.2 was released on Wed Jul 18 2018

## Mailing list activity:
 - Nothing significant in the figures

## Issue activity:
 - 39 issues created [3] and 25 issued [4] closed in the last 3 months
 - 81 pull requests created [5] and 81 closed [6] in the last 3 months

[1]: https://accumulo.apache.org/release/accumulo-1.9.2/
[2]: http://accumulosummit.com/
[3]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+created%3A2018-07-18..2018-10-17+
[4]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-07-18..2018-10-17+
[5]:
https://github.com/apache/accumulo/pulls?q=is%3Apr+created%3A2018-07-18..2018-10-17
[6]:
https://github.com/apache/accumulo/pulls?q=is%3Apr+closed%3A2018-07-18..2018-10-17

Re: Apache Roadshow in DC - December 4, 2018

[Michael Wall]

Sweet, good luck.  Let us know if you get accepted

On Sat, Sep 1, 2018, 13:15 Marc  wrote:

> I submitted so I will go if accepted or not.
>
> On Sat, Sep 1, 2018, 8:04 AM Michael Wall  wrote:
>
> > I am not planning to submit a paper but I am considering going.  Anyone
> > else?
> >
> > On Mon, Aug 27, 2018 at 3:08 PM Billie Rinaldi 
> wrote:
> >
> > > Hello Accumulo Folks,
> > >
> > > There is a call for papers open for the Apache Roadshow in DC on
> December
> > > 4, 2018:
> > > http://www.apachecon.com/usroadshow18/cfp.html
> > >
> > > Billie
> > >
> >
>

Re: Apache Roadshow in DC - December 4, 2018

[Michael Wall]

I am not planning to submit a paper but I am considering going.  Anyone
else?

On Mon, Aug 27, 2018 at 3:08 PM Billie Rinaldi  wrote:

> Hello Accumulo Folks,
>
> There is a call for papers open for the Apache Roadshow in DC on December
> 4, 2018:
> http://www.apachecon.com/usroadshow18/cfp.html
>
> Billie
>

Fwd: [ANNOUNCE] Apache Accumulo 1.9.2 (Critical Bug Fixes)

[Michael Wall]

Forwarding to dev as well.  Thanks Christopher to getting the release out
and thanks Keith for finishing up these last details.

-- Forwarded message -
From: Keith Turner 
Date: Wed, Jul 25, 2018 at 9:28 AM
Subject: [ANNOUNCE] Apache Accumulo 1.9.2 (Critical Bug Fixes)
To: , 


The Apache Accumulo project is pleased to announce the release
of Apache Accumulo 1.9.2! This release contains fixes for **critical**
bugs, which could result in unexpected problems during recovery from
a previous failure. (See the release notes linked below for details.)

Versions 1.8.0, 1.8.1, 1.9.0, and 1.9.1 are affected, and users of those
versions are encouraged to upgrade to this version immediately to
avoid serious problems. Users of earlier versions who are planning to
upgrade to one of the affected versions are encouraged to upgrade
directly to this version instead.

***

Apache Accumulo® is a sorted, distributed key/value store that
provides robust, scalable data storage and retrieval. With
Apache Accumulo, users can store and manage large data sets
across a cluster. Accumulo uses Apache Hadoop's HDFS to store
its data and Apache ZooKeeper for consensus.

This version is now available in Maven Central, and at:
https://accumulo.apache.org/downloads/

The full release notes can be viewed at:
https://accumulo.apache.org/release/accumulo-1.9.2/

--
The Apache Accumulo Team

Re: [DRAFT][ANNOUNCE] Apache Accumulo 1.9.2 (Critical Bug Fixes)

[Michael Wall]

+1  thanks Christopher for pushing this through and thanks everyone who
worked this

On Fri, Jul 20, 2018 at 8:10 AM Marc  wrote:

> +1
> On Fri, Jul 20, 2018 at 8:08 AM J. Mark Owens  wrote:
> >
> > +1
> >
> > On Thu, Jul 19, 2018 at 11:21 PM, Keith Turner  wrote:
> >
> > > +1
> > >
> > > On Thu, Jul 19, 2018 at 5:48 PM, Christopher 
> wrote:
> > > > The following is a DRAFT announcement for the 1.9.2 release. Please
> > > review
> > > > and provide feedback. My intent is to publish on Friday.
> > > > *
> > > >
> > > > The Apache Accumulo project is pleased to announce the release
> > > > of Apache Accumulo 1.9.2! This release contains fixes for
> **critical**
> > > > bugs, which could result in unexpected problems during recovery from
> > > > a previous failure. (See the release notes linked below for details.)
> > > >
> > > > Versions 1.8.0, 1.8.1, 1.9.0, and 1.9.1 are affected, and users of
> those
> > > > versions are encouraged to upgrade to this version immediately to
> > > > avoid serious problems. Users of earlier versions who are planning to
> > > > upgrade to one of the affected versions are encouraged to upgrade
> > > > directly to this version instead.
> > > >
> > > > ***
> > > >
> > > > Apache Accumulo® is a sorted, distributed key/value store that
> > > > provides robust, scalable data storage and retrieval. With
> > > > Apache Accumulo, users can store and manage large data sets
> > > > across a cluster. Accumulo uses Apache Hadoop's HDFS to store
> > > > its data and Apache ZooKeeper for consensus.
> > > >
> > > > This version is now available in Maven Central, and at:
> > > > https://accumulo.apache.org/downloads/
> > > >
> > > > The full release notes can be viewed at:
> > > > https://accumulo.apache.org/release/accumulo-1.9.2/
> > > >
> > > > --
> > > > The Apache Accumulo Team
> > >
>

Re: [DRAFT] [REPORT] Apache Accumulo - July 2018

[Michael Wall]

Report posted, thanks everyone

On Mon, Jul 9, 2018 at 5:36 PM Michael Wall  wrote:

> Mike D, good catch.  Our last report was due at the 18 Apr board meeting,
> so I made a date range from 18 Apr to 17 Jul, which is the day before the
> board meeting this month.  Those number may fluctuate between now and the
> board meeting time but should stay constant after the 17.  To Mike Walch's
> point, I summed the open and closed to get the total for created and closed
> during the time range for both issues and PRs.
>
> Josh, added a comment that we will review the contributors before the next
> meeting.  Always happy to skip middle steps.
>
> Thanks guys.
>
> Mike
>
> --
>
> [DRAFT] [REPORT] Apache Accumulo - July 2018
>
>
> The Apache Accumulo PMC decided to draft its quarterly board
> reports on the dev list. Here is a draft of our report which is due
> by Wednesday, Jul 11, 1 week before the board meeting on
> Wednesday, Jul 18. Please let me know if you have any suggestions.
>
> I am a little earlier with this one since I will be on vacation 5-15 Jul.
> My plan is to submit this report sometime on Mon, Jul 9.
>
> Mike
>
> --
>
> ## Description:
>
>  - The Apache Accumulo sorted, distributed key/value
>  store is a robust, scalable, high performance data storage system that
>  features cell-based access control and customizable server-side
>  processing.  It is based on Google's BigTable design and is built on
>  top of Apache Hadoop, Zookeeper, and Thrift.
>
> ## Issues:
>
>  - There are no issues requiring board attention at this time.
>
> ## Activity:
>
>  - There were 2 new releases, Accumulo 1.9.0 and Accumulo 1.9.1 since
>  the last report.  The 1.9.0 release [1] had a critical bug in the Write
>  Ahead Log (WAL) process that is fixed in 1.9.1 [2].
>  - The PMC approved the use of the Apache Accumulo trademark for the
>5th annual Accumulo Summit, to be held on October 15, 2018 in Columbia,
> MD.
>  - There were no new committers since the last report.  All committers
>  are also PMC members.  We will review contributors during the next 3
> months
>  to see if anyone should be invited to become a committer.
>  - The PMC decided to switch to using github issue for the project and all
>  subprojects [3], which is why the Jira activity dropped off.  Github
> issues
>  and pull request statistics are included below.
>  - Another bug has been found in the WAL process and a 1.9.2 is in the
> works.
>
> ## Health report:
>
>  - The project remains healthy.  Activity levels on mailing lists, issues
> and pull
>  requests remain constant.
>
> ## PMC changes:
>
>  - Currently 34 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Nick Felts on Thu Mar 22 2018
>
> ## Committer base changes:
>
>  - See PMC changes, all committers are PMC members currently.
>
> ## Releases:
>
>  - accumulo-1.9.0 was released on Tue Apr 17 2018
>  - accumulo-1.9.1 was released on Sun May 13 2018
>
> ## Mailing list activity:
>
>  - Nothing significant in the figures
>
> ## Issue activity:
>
>  - 49 issued created [4] and 28 closed [5] in the last 3 months
>  - 75 pull requests created [6] and 67 closed [7] in the last 3 months
>
> [1]: https://accumulo.apache.org/release/accumulo-1.9.0/
> [2]: https://accumulo.apache.org/release/accumulo-1.9.1/
> [3]:
> https://accumulo.apache.org/blog/2018/03/16/moving-to-github-issues.html
> [4]:
> https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+created%3A2018-04-18..2018-07-17+
> [5]:
> https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-04-18..2018-07-17+
> [6]:
> https://github.com/apache/accumulo/pulls?utf8=%E2%9C%93=is%3Apr+created%3A2018-04-18..2018-07-17+
> [7]:
> https://github.com/apache/accumulo/pulls?q=is%3Apr+closed%3A2018-04-18..2018-07-17+
>
> On Mon, Jul 9, 2018 at 5:14 PM Josh Elser  wrote:
>
>>
>>
>> On 7/9/18 4:54 PM, Michael Wall wrote:
>> > Josh, I am not clear on what you are suggesting for another action item.
>> > Are you suggesting a pass over contributors to add see if anyone should
>> be
>> > invited to become a committer or are you suggesting we revisit that
>> every
>> > committer becomes a PMC member?
>>
>> If we say that we have no added any new committers/PMC members in a long
>> period of time, the board will most assuredly say "Have you looked at
>> your contributors to see if you should invite some to be committers?"
>>
>> I was trying to suggest that we proactively tell them "we know we need
>> to see if there are contributors to invite to be committers" in order to
>> save that middle step. No need to do this -- just trying to be helpful
>> based on what I see over and over again from the board :)
>>
>

Re: [DISCUSS] 1.9.2 release

[Michael Wall]

Sean,

That link has the things I have been roughly tracking.  When we moved to
github, I failed to watch to watch the github project and had unsubscribed
from notifications@a.a.o so I was not tracking anything for a while.  Not
sure if anyone is doing RM, maybe Christopher.

Mike

On Mon, Jul 9, 2018 at 4:20 PM Sean Busbey  wrote:

> heya folks,
>
> Our DRAFT board report for this month ( https://s.apache.org/AYwm )
> mentions:
>
> > Another bug has been found in the WAL process and a 1.9.2 is in the
> works.
>
> I don't see anything on dev@accumulo around 1.9.2. Is someone already
> acting as RM?
>
> How do I figure out what, if any, issues remain as blockers for this
> release? I don't see any github projects or milestones; is it things open
> with the 1.9.2 label?
>
> i.e.
>
> https://github.com/apache/accumulo/labels/v1.9.2
>

Re: [DRAFT] [REPORT] Apache Accumulo - July 2018

[Michael Wall]

Mike D, good catch.  Our last report was due at the 18 Apr board meeting,
so I made a date range from 18 Apr to 17 Jul, which is the day before the
board meeting this month.  Those number may fluctuate between now and the
board meeting time but should stay constant after the 17.  To Mike Walch's
point, I summed the open and closed to get the total for created and closed
during the time range for both issues and PRs.

Josh, added a comment that we will review the contributors before the next
meeting.  Always happy to skip middle steps.

Thanks guys.

Mike

--

[DRAFT] [REPORT] Apache Accumulo - July 2018


The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
by Wednesday, Jul 11, 1 week before the board meeting on
Wednesday, Jul 18. Please let me know if you have any suggestions.

I am a little earlier with this one since I will be on vacation 5-15 Jul.
My plan is to submit this report sometime on Mon, Jul 9.

Mike

--

## Description:

 - The Apache Accumulo sorted, distributed key/value
 store is a robust, scalable, high performance data storage system that
 features cell-based access control and customizable server-side
 processing.  It is based on Google's BigTable design and is built on
 top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - There were 2 new releases, Accumulo 1.9.0 and Accumulo 1.9.1 since
 the last report.  The 1.9.0 release [1] had a critical bug in the Write
 Ahead Log (WAL) process that is fixed in 1.9.1 [2].
 - The PMC approved the use of the Apache Accumulo trademark for the
   5th annual Accumulo Summit, to be held on October 15, 2018 in Columbia,
MD.
 - There were no new committers since the last report.  All committers
 are also PMC members.  We will review contributors during the next 3 months
 to see if anyone should be invited to become a committer.
 - The PMC decided to switch to using github issue for the project and all
 subprojects [3], which is why the Jira activity dropped off.  Github issues
 and pull request statistics are included below.
 - Another bug has been found in the WAL process and a 1.9.2 is in the
works.

## Health report:

 - The project remains healthy.  Activity levels on mailing lists, issues
and pull
 requests remain constant.

## PMC changes:

 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:

 - See PMC changes, all committers are PMC members currently.

## Releases:

 - accumulo-1.9.0 was released on Tue Apr 17 2018
 - accumulo-1.9.1 was released on Sun May 13 2018

## Mailing list activity:

 - Nothing significant in the figures

## Issue activity:

 - 49 issued created [4] and 28 closed [5] in the last 3 months
 - 75 pull requests created [6] and 67 closed [7] in the last 3 months

[1]: https://accumulo.apache.org/release/accumulo-1.9.0/
[2]: https://accumulo.apache.org/release/accumulo-1.9.1/
[3]:
https://accumulo.apache.org/blog/2018/03/16/moving-to-github-issues.html
[4]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+created%3A2018-04-18..2018-07-17+
[5]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-04-18..2018-07-17+
[6]:
https://github.com/apache/accumulo/pulls?utf8=%E2%9C%93=is%3Apr+created%3A2018-04-18..2018-07-17+
[7]:
https://github.com/apache/accumulo/pulls?q=is%3Apr+closed%3A2018-04-18..2018-07-17+

On Mon, Jul 9, 2018 at 5:14 PM Josh Elser  wrote:

>
>
> On 7/9/18 4:54 PM, Michael Wall wrote:
> > Josh, I am not clear on what you are suggesting for another action item.
> > Are you suggesting a pass over contributors to add see if anyone should
> be
> > invited to become a committer or are you suggesting we revisit that every
> > committer becomes a PMC member?
>
> If we say that we have no added any new committers/PMC members in a long
> period of time, the board will most assuredly say "Have you looked at
> your contributors to see if you should invite some to be committers?"
>
> I was trying to suggest that we proactively tell them "we know we need
> to see if there are contributors to invite to be committers" in order to
> save that middle step. No need to do this -- just trying to be helpful
> based on what I see over and over again from the board :)
>

Re: [DRAFT] [REPORT] Apache Accumulo - July 2018

[Michael Wall]

Thanks for all the input

- Added the summit info
- Redid the counts (Mike Walch good catch, I think what you sent still
wasn't quite right.  I think two two queries get it though)
- Used https

Josh, I am not clear on what you are suggesting for another action item.
Are you suggesting a pass over contributors to add see if anyone should be
invited to become a committer or are you suggesting we revisit that every
committer becomes a PMC member?

Updated report is attached.  I'd like to submit it later tonight, so let me
know if there is anything else that should be added/changed.  Thanks
everyone.

---

## Description:

 - The Apache Accumulo sorted, distributed key/value
 store is a robust, scalable, high performance data storage system that
 features cell-based access control and customizable server-side
 processing.  It is based on Google's BigTable design and is built on
 top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - There were 2 new releases, Accumulo 1.9.0 and Accumulo 1.9.1 since
 the last report.  The 1.9.0 release [1] had a critical bug in the Write
 Ahead Log (WAL) process that is fixed in 1.9.1 [2].
 - The PMC approved the use of the Apache Accumulo trademark for the
   5th annual Accumulo Summit, to be held on October 15, 2018 in Columbia,
MD.
 - There were no new committers since the last report.  All committers
 are also PMC members.
 - The PMC decided to switch to using github issue for the project and all
 subprojects [3], which is why the Jira activity dropped off.  Github issues
 and pull request statistics are included below.
 - Another bug has been found in the WAL process and a 1.9.2 is in the
works.

## Health report:

 - The project remains healthy.  Activity levels on mailing lists, git
 and JIRA remain constant.

## PMC changes:

 - Currently 34 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Nick Felts on Thu Mar 22 2018

## Committer base changes:

 - See PMC changes, all committers are PMC members currently.

## Releases:

 - accumulo-1.9.0 was released on Tue Apr 17 2018
 - accumulo-1.9.1 was released on Sun May 13 2018

## Mailing list activity:

 - Nothing significant in the figures

## Issue activity:

 - 47 issued created [4] and 26 closed [5] in the last 3 months
 - 73 pull requests created [6] and 66 closed [7] in the last 3 months

[1]: https://accumulo.apache.org/release/accumulo-1.9.0/
[2]: https://accumulo.apache.org/release/accumulo-1.9.1/
[3]:
https://accumulo.apache.org/blog/2018/03/16/moving-to-github-issues.html
[4]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+created%3A%3E2018-04-18+
[5]:
https://github.com/apache/accumulo/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A%3E2018-04-18+
[6]:
https://github.com/apache/accumulo/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aopen+created%3A%3E2018-04-18+
[7]:
https://github.com/apache/accumulo/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aopen+closed%3A%3E2018-04-18+

On Thu, Jul 5, 2018 at 1:22 PM Josh Elser  wrote:

> +1 definitely. Especially since the organizers went through the proper
> TM approval steps.
>
> I'd suggest expanding that, in addition to no new committers/PMC
> members, to include an action item. e.g. Should we make a pass over
> contributors? Or, is participation "constant" (c=pmc makes this a bit
> easier to put into words ;))
>
> On 7/1/18 5:06 PM, Mike Drob wrote:
> > Worth mentioning upcoming summit?
> >
> > On Sun, Jul 1, 2018, 3:54 PM Michael Wall  wrote:
> >
> >> The Apache Accumulo PMC decided to draft its quarterly board
> >> reports on the dev list. Here is a draft of our report which is due
> >> by Wednesday, Jul 11, 1 week before the board meeting on
> >> Wednesday, Jul 18. Please let me know if you have any suggestions.
> >>
> >> I am a little earlier with this one since I will be on vacation 5-15
> Jul.
> >> My plan is to submit this report sometime on Mon, Jul 9.
> >>
> >> Mike
> >>
> >> --
> >>
> >> ## Description:
> >>
> >>   - The Apache Accumulo sorted, distributed key/value
> >>   store is a robust, scalable, high performance data storage system that
> >>   features cell-based access control and customizable server-side
> >>   processing.  It is based on Google's BigTable design and is built on
> >>   top of Apache Hadoop, Zookeeper, and Thrift.
> >>
> >> ## Issues:
> >>
> >>   - There are no issues requiring board attention at this time.
> >>
> >> ## Activity:
> >>
> >>   - There were 2 new releases, Accumulo 1.9.0 and Accumulo 1.9.1 since
> >>   the last report.  The 1.9.0 release [1] had a critical bug in the
> W

Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1

[Michael Wall]

Thanks for the summary Christopher, and thanks for pushing the release
through.

On Wed, Apr 18, 2018 at 4:02 PM Christopher <ctubb...@apache.org> wrote:

> On Wed, Apr 18, 2018 at 3:21 PM Michael Wall <mjw...@gmail.com> wrote:
>
> > Congrats.  Don't forget to update the release notes with the testing
> > information to include versions.  I didn't realize that 1.9 would work
> with
> > Hadoop 3 but I see it in the parent pom as a profile.  Also, did anything
> > change as result of Sean and Mike's comments?
> >
> >
> Regarding Hadoop 3 and testing,
>
> Accumulo 1.9.0 will, in theory, work with Hadoop 3, because of the work
> Josh did to check during development, and to modify the build... but using
> it with Hadoop 3 may require building from source with the Hadoop 3
> profile, or at least, require users to perform some packaging/integration
> steps to set up the class path for their deployments with Hadoop 3. I don't
> know if anybody has done any tests other than build tests with the profile
> active. Also, some Hadoop 3 features may or may not be available, due to
> lack of Accumulo ability to configure them (per-table HDFS erasure encoding
> settings, for example, as an alternative to replication factor). In short,
> user mileage may vary, but at least the option is there to try (because the
> code compiles and the basic build tests pass).
>
> Regarding Sean and Mike's comments:
>
> In response to Sean and Mike's comments, I copied the tarballs to the SVN
> dist/dev area, along with their SHA512 sums, but no votes were changed as a
> result. I saw no indication in the discussion that anybody other than
> myself examined those files to ensure they met expectations. I also
> proposed a change in the thread to the release process as a result of Sean
> and Mike's comments (specifically, to include the SHA512 for the tarballs,
> directly in future vote threads), but have not heard a response back on
> that proposal. I will likely proceed with a change to the build.sh script
> to incorporate that proposal in a future pull request, unless somebody has
> a better proposal before then.
>
>
>
> > On Wed, Apr 18, 2018 at 2:59 PM Christopher <ctubb...@apache.org> wrote:
> >
> > > This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
> > >
> > > +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
> > > -0: mdrob
> > > -1: busbey
> > >
> > > Thanks for the votes all, I'll start working on the post-vote steps
> next.
> > > It looks like folks are still making updates to the release notes.
> > >
> > > On Wed, Apr 18, 2018 at 2:47 PM Christopher <ctubb...@apache.org>
> wrote:
> > >
> > > > +1
> > > >
> > > > * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs
> > match
> > > > Nexus staging area (artifacts and GPG sigs) and SHA512s there are
> > > correct.
> > > > * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
> > > > * Ran all ITs successfully with Hadoop 2
> > > > * GPG signatures match release tarball artifacts (and other Maven
> > > > artifacts)
> > > > * Maven repo is consistent (all md5, sha1 sigs match their Maven
> > > artifacts)
> > > > * All jars have corresponding javadoc and source jars.
> > > > * Contents of binary tarball lib directory match Maven jars
> > > > * Source tarball matches git commit
> > > > * Jar manifest indicates build from correct git commit
> > > > * Jars are sealed
> > > > * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
> > > > * Also attempted to build Hive... which works, but some Accumulo
> tests
> > > > fail because of the use of "." in iterator names, which is broken,
> and
> > > > explicitly checked for as of ACCUMULO-3389
> > > > * Also attempted to build geowave, but that failed because geowave
> > > appears
> > > > to extensively make use of non-public API from Accumulo, so I gave
> up.
> > > >
> > > > I checked the LICENSE and NOTICE files also, and they look good,
> except
> > > > for the fact that they still say 2017, instead of 2018. I can't
> > believe I
> > > > forgot to check this a second time, after this same thing happened
> for
> > > > 1.7.4. In any case, I don't think it's worth holding up the release,
> > > given
> > > > that there do not seem to be any other serious issues with the
> > artifacts.
> > > >
> > > >
> > > > On Wed, Apr 

Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1

[Michael Wall]

Congrats.  Don't forget to update the release notes with the testing
information to include versions.  I didn't realize that 1.9 would work with
Hadoop 3 but I see it in the parent pom as a profile.  Also, did anything
change as result of Sean and Mike's comments?

On Wed, Apr 18, 2018 at 2:59 PM Christopher  wrote:

> This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
>
> +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
> -0: mdrob
> -1: busbey
>
> Thanks for the votes all, I'll start working on the post-vote steps next.
> It looks like folks are still making updates to the release notes.
>
> On Wed, Apr 18, 2018 at 2:47 PM Christopher  wrote:
>
> > +1
> >
> > * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs match
> > Nexus staging area (artifacts and GPG sigs) and SHA512s there are
> correct.
> > * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
> > * Ran all ITs successfully with Hadoop 2
> > * GPG signatures match release tarball artifacts (and other Maven
> > artifacts)
> > * Maven repo is consistent (all md5, sha1 sigs match their Maven
> artifacts)
> > * All jars have corresponding javadoc and source jars.
> > * Contents of binary tarball lib directory match Maven jars
> > * Source tarball matches git commit
> > * Jar manifest indicates build from correct git commit
> > * Jars are sealed
> > * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
> > * Also attempted to build Hive... which works, but some Accumulo tests
> > fail because of the use of "." in iterator names, which is broken, and
> > explicitly checked for as of ACCUMULO-3389
> > * Also attempted to build geowave, but that failed because geowave
> appears
> > to extensively make use of non-public API from Accumulo, so I gave up.
> >
> > I checked the LICENSE and NOTICE files also, and they look good, except
> > for the fact that they still say 2017, instead of 2018. I can't believe I
> > forgot to check this a second time, after this same thing happened for
> > 1.7.4. In any case, I don't think it's worth holding up the release,
> given
> > that there do not seem to be any other serious issues with the artifacts.
> >
> >
> > On Wed, Apr 18, 2018 at 11:07 AM Keith Turner  wrote:
> >
> >> +1
> >>
> >>  * Successfully built Fluo against RC
> >>  * Ran continuous ingest for 24hrs on 9 node cluster using RC.
> >> Verified successfully.  Table had 32.3 billion entries after test.
> >>
> >>
> >>
> >> On Thu, Apr 12, 2018 at 6:21 PM, Christopher 
> wrote:
> >> > Accumulo Developers,
> >> >
> >> > Please consider the following candidate for Apache Accumulo 1.9.0.
> >> >
> >> > Git Commit:
> >> > bca516000bdb54b1e5582f908e0a525634a120f7
> >> > Branch:
> >> > 1.9.0-rc1
> >> >
> >> > If this vote passes, a gpg-signed tag will be created using:
> >> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
> >> > bca516000bdb54b1e5582f908e0a525634a120f7
> >> >
> >> > Staging repo:
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
> >> > Source (official release artifact):
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
> >> > Binary:
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-bin.tar.gz
> >> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for
> a
> >> > given artifact.)
> >> >
> >> > All artifacts were built and staged with:
> >> > mvn release:prepare && mvn release:perform
> >> >
> >> > Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> >> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >> >
> >> > Release notes (in progress) can be found at:
> >> > https://accumulo.apache.org/release/accumulo-1.9.0/
> >> >
> >> > Please vote one of:
> >> > [ ] +1 - I have verified and accept...
> >> > [ ] +0 - I have reservations, but not strong enough to vote against...
> >> > [ ] -1 - Because..., I do not accept...
> >> > ... these artifacts as the 1.9.0 release of Apache Accumulo.
> >> >
> >> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC 2018
> >> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
> >> > Voting continues until the release manager sends an email closing the
> >> vote.
> >> >
> >> > Thanks!
> >> >
> >> > P.S. Hint: download the whole staging repo with
> >> > wget -erobots=off -r -l inf -np -nH \
> >> >
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/
> >> > # note the trailing slash is needed
> >>
> >
>

Fwd: REMINDER - TAC Applications closes in 2 weeks for ACNA Montréal

[Michael Wall]

FYI, if you going to ApacheCon in Montreal and would like to pursue travel
assistance

Mike

-- Forwarded message -
From: Gavin McDonald 
Date: Tue, Apr 17, 2018 at 8:41 PM
Subject: REMINDER - TAC Applications closes in 2 weeks for ACNA Montréal
To: 


Hello PMCs.

Please could you forward on the below email to your dev and user lists.

Thanks

Gav…

—
Reminder that travel assistance applications for ApacheCon NA 2018 are
still open but only for another 2 weeks!
Please get your applications in NOW.

We will be supporting ApacheCon NA Montréal, Canada on 24th - 29th
September 2018

 TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons.
For more info on this years applications and qualifying criteria, please
visit the TAC website at < http://www.apache.org/travel/ <
http://www.apache.org/travel/> >. Applications are now open and will close
1st May.

Important: Applications close on May 1st, 2018. Applicants have until the
closing date above to submit their applications (which should contain as
much supporting material as required to efficiently and accurately process
their request), this will enable TAC to announce successful awards shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.
We look forward to greeting many of you in Montreal

Kind Regards,
Gavin - (On behalf of the Travel Assistance Committee)

[REPORT] Apache Accumulo - April 2018

[Michael Wall]

## Description:

 - The Apache Accumulo sorted, distributed key/value
 store is a robust, scalable, high performance data storage system that
 features cell-based access control and customizable server-side
 processing.  It is based on Google's BigTable design and is built on
 top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:

 - There are no issues requiring board attention at this time.

## Activity:

 - There was 1 new release, Accumulo 1.7.4, since the last report. [1]
 - There were 4 new committers since the last report.  All committers
 are also PMC members.
 - The PMC decided to switch to using github issue for the project
 and all subprojects. [2]
 - The PMC decided to drop support for Hadoop 2 in the Accumulo 2.0.
 - A contributor requested permission to use the Accumulo logo on
 t-shirts and/or stickers to promote projects he uses.  VP Brand
 Management and the PMC had no objections.
 - PMC is working on a 1.9.0 release.

## Health report:

 - The project remains healthy.  Activity levels on mailing lists, git
 and JIRA remain constant.

## PMC changes:

 - Currently 34 PMC members.
 - New PMC members:
- Adam J. Shook was added to the PMC on Wed Jan 24 2018
- Mark Owens was added to the PMC on Tue Mar 20 2018
- Luis Tavarez was added to the PMC on Tue Mar 20 2018
- Nick Felts was added to the PMC on Thu Mar 22 2018

## Committer base changes:

 - See PMC changes, all committers are PMC members currently.

## Releases:

 - accumulo-1.7.4 was released on Thu Mar 22 2018

## Mailing list activity:

 - Nothing significant in the figures

## JIRA activity:

 - 65 JIRA tickets created in the last 3 months
 - 101 JIRA tickets closed/resolved in the last 3 months

[1]: http://accumulo.apache.org/release/accumulo-1.7.4/
[2]: http://accumulo.apache.org/blog/2018/03/16/moving-to-github-issues.html

Re: [DRAFT] [REPORT] Apache Accumulo - March 2018

[Michael Wall]

Planning to submit this tomorrow

---

## Description:
 - The Apache Accumulo sorted, distributed key/value
 store is a robust, scalable, high performance data storage system that
 features cell-based access control and customizable server-side
 processing.  It is based on Google's BigTable design and is built on
 top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new release, Accumulo 1.7.4, since the last report.
 - There were 4 new committers since the last report.  All committers
 are also PMC members.
 - The PMC decided to switch to using github issue for the project
 and all subprojects.
 - The PMC decided to drop support for Hadoop 2 in the Accumulo 2.0.
 - A contributor requested permission to use the
Accumulo logo on t-shirts and/or stickers to promote projects he uses.
VP Brand Management and the PMC had no objections.
 - PMC is working on a 1.9.0 release.

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, git
 and JIRA remain constant.

## PMC changes:

 - Currently 34 PMC members.
 - New PMC members:
- Adam J. Shook was added to the PMC on Wed Jan 24 2018
- Mark Owens was added to the PMC on Tue Mar 20 2018
- Luis Tavarez was added to the PMC on Tue Mar 20 2018
- Nick Felts was added to the PMC on Thu Mar 22 2018

## Committer base changes:

 - Currently 34 committers.
 - New commmitters:
- Adam J. Shook was added as a committer on Wed Jan 24 2018
- Mark Owens was added as a committer on Wed Mar 21 2018
- Luis Tavarez was added as a committer on Wed Mar 21 2018
- Nick Felts was added as a committer on Sat Mar 24 2018

## Releases:

 - accumulo-1.7.4 was released on Thu Mar 22 2018

## Mailing list activity:

 - Nothing significant in the figures

## JIRA activity:

 - 65 JIRA tickets created in the last 3 months
 - 101 JIRA tickets closed/resolved in the last 3 months

On Mon, Apr 9, 2018 at 6:59 PM Michael Wall <mjw...@gmail.com> wrote:

> Yep thanks Tony.  I see your contributions to
> https://lists.apache.org/list.html?dev@accumulo.apache.org
>
>
> On Mon, Apr 9, 2018 at 5:03 PM Tony Kurc <trk...@gmail.com> wrote:
>
>> For what it is worth, I'm much happier attributing my request to me being
>> an Accumulo contributor than as a PMC member of another project. I like to
>> think my occasional opining on mailing list would qualify me as such [1].
>>
>> 1. https://community.apache.org/contributors/
>>
>> On Mon, Apr 9, 2018 at 12:40 PM, Michael Wall <mjw...@gmail.com> wrote:
>>
>> > Thanks for reading this Josh.
>> >
>> > 1 - In my first draft I had no information about Tony but I felt like
>> that
>> > was going to prompt questions.  I agree contributor is more relevant
>> but he
>> > is not listed on the people page.  Do we think that matters?
>> > 2 - What were you thinking on the "what's next"?  Maybe it is time for
>> us
>> > to really define a roadmap, not sure there is time before this is due on
>> > Wed though.
>> >
>> > Mike
>> >
>> > On Mon, Apr 9, 2018 at 12:00 PM Josh Elser <els...@apache.org> wrote:
>> >
>> > > Two minor suggestions:
>> > >
>> > > * Strike the "A member of the Apache Nifi PMC" part. The fact that
>> Tony
>> > > was NiFi PMC member isn't really relevant to the request, is it? IMO,
>> if
>> > > anything, it's more relevant that Tony is a contributor to Accumulo.
>> > > * There isn't any discussion about what is coming next -- we have the
>> > > 1.7.4 release, but no details about what's in the pipeline.
>> > >
>> > > On 4/7/18 10:19 AM, Michael Wall wrote:
>> > > > The Apache Accumulo PMC decided to draft its quarterly board
>> > > > reports on the dev list. Here is a draft of our report which is due
>> > > > by Wednesday, Mar 11, 1 week before the board meeting on
>> > > > Wednesday, Mar 18. Please let me know if you have any suggestions.
>> > > > I plan to submit it late on the 10th.
>> > > >
>> > > > Mike
>> > > >
>> > > > --
>> > > >
>> > > > ## Description:
>> > > >   - The Apache Accumulo sorted, distributed key/value
>> > > >   store is a robust, scalable, high performance data storage system
>> > that
>> > > >   features cell-based access control and customizable server-side
>> > > >   processing.  It is based on Google's BigTable design and is built
>> on
>> > > >   top of Apache 

Re: [DRAFT] [REPORT] Apache Accumulo - March 2018

[Michael Wall]

Yep thanks Tony.  I see your contributions to
https://lists.apache.org/list.html?dev@accumulo.apache.org

On Mon, Apr 9, 2018 at 5:03 PM Tony Kurc <trk...@gmail.com> wrote:

> For what it is worth, I'm much happier attributing my request to me being
> an Accumulo contributor than as a PMC member of another project. I like to
> think my occasional opining on mailing list would qualify me as such [1].
>
> 1. https://community.apache.org/contributors/
>
> On Mon, Apr 9, 2018 at 12:40 PM, Michael Wall <mjw...@gmail.com> wrote:
>
> > Thanks for reading this Josh.
> >
> > 1 - In my first draft I had no information about Tony but I felt like
> that
> > was going to prompt questions.  I agree contributor is more relevant but
> he
> > is not listed on the people page.  Do we think that matters?
> > 2 - What were you thinking on the "what's next"?  Maybe it is time for us
> > to really define a roadmap, not sure there is time before this is due on
> > Wed though.
> >
> > Mike
> >
> > On Mon, Apr 9, 2018 at 12:00 PM Josh Elser <els...@apache.org> wrote:
> >
> > > Two minor suggestions:
> > >
> > > * Strike the "A member of the Apache Nifi PMC" part. The fact that Tony
> > > was NiFi PMC member isn't really relevant to the request, is it? IMO,
> if
> > > anything, it's more relevant that Tony is a contributor to Accumulo.
> > > * There isn't any discussion about what is coming next -- we have the
> > > 1.7.4 release, but no details about what's in the pipeline.
> > >
> > > On 4/7/18 10:19 AM, Michael Wall wrote:
> > > > The Apache Accumulo PMC decided to draft its quarterly board
> > > > reports on the dev list. Here is a draft of our report which is due
> > > > by Wednesday, Mar 11, 1 week before the board meeting on
> > > > Wednesday, Mar 18. Please let me know if you have any suggestions.
> > > > I plan to submit it late on the 10th.
> > > >
> > > > Mike
> > > >
> > > > --
> > > >
> > > > ## Description:
> > > >   - The Apache Accumulo sorted, distributed key/value
> > > >   store is a robust, scalable, high performance data storage system
> > that
> > > >   features cell-based access control and customizable server-side
> > > >   processing.  It is based on Google's BigTable design and is built
> on
> > > >   top of Apache Hadoop, Zookeeper, and Thrift.
> > > >
> > > > ## Issues:
> > > >   - There are no issues requiring board attention at this time.
> > > >
> > > > ## Activity:
> > > >   - There was 1 new release, Accumulo 1.7.4, since the last report.
> > > >   - There were 4 new committers since the last report.  All
> committers
> > > >   are also PMC members.
> > > >   - The PMC decided to switch to using github issue for the project
> > > >   and all subprojects.
> > > >   - The PMC decided to drop support for Hadoop 2 in the Accumulo 2.0.
> > > >   - A member of the Apache Nifi PMC requested permission to use the
> > > > Accumulo logo on t-shirts and/or stickers to promote projects he
> uses.
> > > > VP Brand Management and the PMC had no objections.
> > > >
> > > > ## Health report:
> > > >   - The project remains healthy.  Activity levels on mailing lists,
> git
> > > >   and JIRA remain constant.
> > > >
> > > > ## PMC changes:
> > > >
> > > >   - Currently 34 PMC members.
> > > >   - New PMC members:
> > > >  - Adam J. Shook was added to the PMC on Wed Jan 24 2018
> > > >  - Mark Owens was added to the PMC on Tue Mar 20 2018
> > > >  - Luis Tavarez was added to the PMC on Tue Mar 20 2018
> > > >  - Nick Felts was added to the PMC on Thu Mar 22 2018
> > > >
> > > > ## Committer base changes:
> > > >
> > > >   - Currently 34 committers.
> > > >   - New commmitters:
> > > >  - Adam J. Shook was added as a committer on Wed Jan 24 2018
> > > >  - Mark Owens was added as a committer on Wed Mar 21 2018
> > > >  - Luis Tavarez was added as a committer on Wed Mar 21 2018
> > > >  - Nick Felts was added as a committer on Sat Mar 24 2018
> > > >
> > > > ## Releases:
> > > >
> > > >   - accumulo-1.7.4 was released on Thu Mar 22 2018
> > > >
> > > > ## Mailing list activity:
> > > >
> > > >   - Nothing significant in the figures
> > > >
> > > > ## JIRA activity:
> > > >
> > > >   - 65 JIRA tickets created in the last 3 months
> > > >   - 101 JIRA tickets closed/resolved in the last 3 months
> > > >
> > >
> >
>

[DRAFT] [REPORT] Apache Accumulo - March 2018

[Michael Wall]

The Apache Accumulo PMC decided to draft its quarterly board
reports on the dev list. Here is a draft of our report which is due
by Wednesday, Mar 11, 1 week before the board meeting on
Wednesday, Mar 18. Please let me know if you have any suggestions.
I plan to submit it late on the 10th.

Mike

--

## Description:
 - The Apache Accumulo sorted, distributed key/value
 store is a robust, scalable, high performance data storage system that
 features cell-based access control and customizable server-side
 processing.  It is based on Google's BigTable design and is built on
 top of Apache Hadoop, Zookeeper, and Thrift.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - There was 1 new release, Accumulo 1.7.4, since the last report.
 - There were 4 new committers since the last report.  All committers
 are also PMC members.
 - The PMC decided to switch to using github issue for the project
 and all subprojects.
 - The PMC decided to drop support for Hadoop 2 in the Accumulo 2.0.
 - A member of the Apache Nifi PMC requested permission to use the
Accumulo logo on t-shirts and/or stickers to promote projects he uses.
VP Brand Management and the PMC had no objections.

## Health report:
 - The project remains healthy.  Activity levels on mailing lists, git
 and JIRA remain constant.

## PMC changes:

 - Currently 34 PMC members.
 - New PMC members:
- Adam J. Shook was added to the PMC on Wed Jan 24 2018
- Mark Owens was added to the PMC on Tue Mar 20 2018
- Luis Tavarez was added to the PMC on Tue Mar 20 2018
- Nick Felts was added to the PMC on Thu Mar 22 2018

## Committer base changes:

 - Currently 34 committers.
 - New commmitters:
- Adam J. Shook was added as a committer on Wed Jan 24 2018
- Mark Owens was added as a committer on Wed Mar 21 2018
- Luis Tavarez was added as a committer on Wed Mar 21 2018
- Nick Felts was added as a committer on Sat Mar 24 2018

## Releases:

 - accumulo-1.7.4 was released on Thu Mar 22 2018

## Mailing list activity:

 - Nothing significant in the figures

## JIRA activity:

 - 65 JIRA tickets created in the last 3 months
 - 101 JIRA tickets closed/resolved in the last 3 months

Re: [DRAFT][ANNOUNCE] Apache Accumulo 1.7.4

[Michael Wall]

Yea, I was thinking just a mention to see the release notes in the NOTICE
section.  Although you could just link to
https://accumulo.apache.org/docs/2.0/administration/upgrading which is
where the release notes point.  With the 1.8.1 release, we moved toward
putting upgrade instructions in the release notes (
http://accumulo.apache.org/release/accumulo-1.8.1/#upgrading), but it looks
like we are moving back to dedicated page.

On Mon, Mar 26, 2018 at 12:12 PM Christopher <ctubb...@apache.org> wrote:

> To keep the announcement as brief as possible, and to ensure that
> information persists in the docs (rather than only in the email archives),
> it might be best to add those links to the release notes, which is already
> linked.
>
> On Mon, Mar 26, 2018 at 12:01 PM Sean Busbey <bus...@apache.org> wrote:
>
> > A guide on upgrading to 1.8. Things that changed / broke that folks
> > upgrading need to look out for, etc.
> >
> > On 2018/03/26 15:46:39, Christopher <ctubb...@apache.org> wrote:
> > > What links?
> > >
> > > On Mon, Mar 26, 2018 at 8:26 AM Michael Wall <mjw...@apache.org>
> wrote:
> > >
> > > > In your notice to upgrade, it would be nice to provide some links.
> > > >
> > > > On Sat, Mar 24, 2018, 17:00 Mike Miller <mmil...@apache.org> wrote:
> > > >
> > > > > Keith and I still need to add info for the testing we did to RC-0
> to
> > the
> > > > > release notes.  I don't think this will have to hold up the release
> > or
> > > > > announcement but just a heads up the "Testing" section is blank
> right
> > > > now.
> > > > >
> > > > > On Sat, Mar 24, 2018 at 4:33 PM, Christopher <ctubb...@apache.org>
> > > > wrote:
> > > > >
> > > > > > *
> > > > > > The following is a draft announcement for the 1.7.4 release. If
> > all is
> > > > > > good, I will send to annou...@apache.org and
> > u...@accumulo.apache.org
> > > > on
> > > > > > Monday.
> > > > > > *
> > > > > >
> > > > > > The Apache Accumulo project is pleased to announce the release of
> > > > Apache
> > > > > > Accumulo 1.7.4! This release contains many bug fixes, performance
> > > > > > improvements, build quality improvements, and more. This is a
> > > > maintenance
> > > > > > (patch) release. Users of any previous 1.7.x release are strongly
> > > > > > encouraged to update as soon as possible to benefit from the
> > > > improvements
> > > > > > with very little concern in change of underlying functionality.
> > > > > >
> > > > > > NOTICE: As development shifts to maintaining the newer versions
> of
> > > > > Accumulo
> > > > > > (1.9 and beyond), this will likely be the last maintenance
> release
> > of
> > > > the
> > > > > > 1.7 series, so users should begin making plans to upgrade to 1.8
> or
> > > > > later,
> > > > > > if they haven't already.
> > > > > >
> > > > > > This version is now available in Maven Central, and at:
> > > > > > https://accumulo.apache.org/downloads/
> > > > > >
> > > > > > The full release notes can be viewed at:
> > > > > > https://accumulo.apache.org/release/accumulo-1.7.4/
> > > > > >
> > > > > > Apache Accumulo® is a sorted, distributed key/value store that
> > provides
> > > > > > robust, scalable data storage and retrieval. With Apache
> Accumulo,
> > > > users
> > > > > > can store and manage large data sets across a cluster. Accumulo
> > uses
> > > > > Apache
> > > > > > Hadoop's HDFS to store its data and Apache ZooKeeper for
> consensus.
> > > > > >
> > > > > > --
> > > > > > The Apache Accumulo Team
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DRAFT][ANNOUNCE] Apache Accumulo 1.7.4

[Michael Wall]

In your notice to upgrade, it would be nice to provide some links.

On Sat, Mar 24, 2018, 17:00 Mike Miller  wrote:

> Keith and I still need to add info for the testing we did to RC-0 to the
> release notes.  I don't think this will have to hold up the release or
> announcement but just a heads up the "Testing" section is blank right now.
>
> On Sat, Mar 24, 2018 at 4:33 PM, Christopher  wrote:
>
> > *
> > The following is a draft announcement for the 1.7.4 release. If all is
> > good, I will send to annou...@apache.org and u...@accumulo.apache.org on
> > Monday.
> > *
> >
> > The Apache Accumulo project is pleased to announce the release of Apache
> > Accumulo 1.7.4! This release contains many bug fixes, performance
> > improvements, build quality improvements, and more. This is a maintenance
> > (patch) release. Users of any previous 1.7.x release are strongly
> > encouraged to update as soon as possible to benefit from the improvements
> > with very little concern in change of underlying functionality.
> >
> > NOTICE: As development shifts to maintaining the newer versions of
> Accumulo
> > (1.9 and beyond), this will likely be the last maintenance release of the
> > 1.7 series, so users should begin making plans to upgrade to 1.8 or
> later,
> > if they haven't already.
> >
> > This version is now available in Maven Central, and at:
> > https://accumulo.apache.org/downloads/
> >
> > The full release notes can be viewed at:
> > https://accumulo.apache.org/release/accumulo-1.7.4/
> >
> > Apache Accumulo® is a sorted, distributed key/value store that provides
> > robust, scalable data storage and retrieval. With Apache Accumulo, users
> > can store and manage large data sets across a cluster. Accumulo uses
> Apache
> > Hadoop's HDFS to store its data and Apache ZooKeeper for consensus.
> >
> > --
> > The Apache Accumulo Team
> >
>

Re: Welcome Nick Felts, new committer/PMC

[Michael Wall]

Salutations Nick

On Fri, Mar 23, 2018 at 1:37 PM Christopher  wrote:

> Welcome, Nick!
>
> On Fri, Mar 23, 2018 at 12:32 PM Mike Miller  wrote:
>
> > Congrats Nick!
> >
> > On Fri, Mar 23, 2018 at 11:43 AM, Mike Walch  wrote:
> >
> > > Welcome Nick!
> > >
> > > On Fri, Mar 23, 2018 at 11:38 AM, Keith Turner 
> wrote:
> > >
> > > > Accumulo devs,
> > > >
> > > > Please join me in welcoming Nick Felts as a new Accumulo
> committer+PMC
> > > > member!
> > > >
> > > > Nick has made many improvements to RFile and encryption.  Surely no
> > > > one would ever do this, but if you get a nice clean error when trying
> > > > to put a 6GB key into a RFile, thank Nick.  You can find Nick on
> > > > GitHub at https://github.com/PircDef.
> > > >
> > > > Welcome, Nick!
> > > >
> > >
> >
>

Re: New committer: Luis Tavarez

[Michael Wall]

Way to go Luis

On Thu, Mar 22, 2018 at 3:28 PM Keith Turner  wrote:

> On Thu, Mar 22, 2018 at 11:40 AM, Mike Walch  wrote:
> > Join me in welcoming Luis Tavarez as a new Apache Accumulo committer and
> > PMC member!  Luis worked on a major refactor of the Accumulo monitor for
> > the upcoming 2.0 release. Thanks for your contributions so far, Luis!
>
> Congrats and welcome Luis
>

Re: [DISCUSS] Remove tracer service (not instrumentation)

[Michael Wall]

Yeah, I get it.  That should have said "without a working example
alternative".  Something to make it as easy as possible for someone
currently using tracing to not loose functionality.

Thanks

On Fri, Mar 16, 2018, 18:38 Christopher <ctubb...@apache.org> wrote:

> The alternative is to configure any of the other HTrace sinks which are
> available. The current code for Accumulo's tracer service could even be
> forked and supported as a separate sink to optionally use (but as I said in
> my original email, I think it'd be better to encourage contribution to
> other presentation projects to use Accumulo as a backing store).
>
> On Fri, Mar 16, 2018 at 6:34 PM Michael Wall <mjw...@apache.org> wrote:
>
> > I am in favor of removing the tracer ui from the monitor and the tracer
> > service that stores the spans in Accumulo.  I worry about doing so with a
> > working alternative though.
> >
> > On Fri, Mar 16, 2018 at 6:25 PM Mike Drob <md...@apache.org> wrote:
> >
> > > Do we have a migration story ready to go for folks that are used to
> > seeing
> > > traces on the monitor?
> > >
> > > On Fri, Mar 16, 2018 at 5:17 PM, Tony Kurc <trk...@gmail.com> wrote:
> > >
> > > > I like this idea.
> > > >
> > > > On Fri, Mar 16, 2018 at 5:09 PM, Christopher <ctubb...@apache.org>
> > > wrote:
> > > >
> > > > > Devs,
> > > > >
> > > > > (This discussion is somewhat of a spinoff of our previous recent
> > > > > conversation about HTrace, but I'd like to narrow the discussion to
> > one
> > > > > specific topic regarding our tracer service.)
> > > > >
> > > > > I'd like to remove Accumulo's tracer service and corresponding
> > > > > presentations in the monitor for 2.0.
> > > > >
> > > > > The tracer service currently acts as a sink for the traces from
> > > Accumulo.
> > > > >
> > > > > While there is interest in tracing Accumulo, and Accumulo may
> itself
> > be
> > > > > suitable (with the right schema) for storing traces, I do not think
> > > > acting
> > > > > as a "trace sink" is really the kind of thing we should be doing as
> > > part
> > > > of
> > > > > Accumulo's out-of-the-box core functionality.
> > > > >
> > > > > Also, the presentation and search capabilities of the traces found
> in
> > > the
> > > > > trace table (by convention, and assumed by the monitor) is far from
> > an
> > > > > ideal presentation of this data, and I don't think the Accumulo
> > project
> > > > > should continue maintaining that inside the core project's monitor,
> > > > either.
> > > > >
> > > > > I think we should encourage interested volunteers to contribute to
> > > other
> > > > > trace presentation software (wherever they may exist) any necessary
> > > > > "backing store" implementation based on Accumulo.
> > > > >
> > > > > None of this would remove tracing instrumentation from Accumulo...
> it
> > > > would
> > > > > just require users interested in trace data from Accumulo to
> > configure
> > > an
> > > > > appropriate sink to collect that data in some other integrated
> > > component
> > > > of
> > > > > their overall architecture.
> > > > >
> > > > > Decoupling the integrated trace sink from the instrumentation in
> > > Accumulo
> > > > > like this could even be a step towards providing support for
> multiple
> > > > > different tracing libraries. (I guess we could do this now, but it
> > > would
> > > > be
> > > > > easier if we were not also trying to provide a sink implementation
> > for
> > > > one
> > > > > specific version of one specific instrumentation library.)
> > > > >
> > > > > Thoughts?
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Remove tracer service (not instrumentation)

[Michael Wall]

I am in favor of removing the tracer ui from the monitor and the tracer
service that stores the spans in Accumulo.  I worry about doing so with a
working alternative though.

On Fri, Mar 16, 2018 at 6:25 PM Mike Drob  wrote:

> Do we have a migration story ready to go for folks that are used to seeing
> traces on the monitor?
>
> On Fri, Mar 16, 2018 at 5:17 PM, Tony Kurc  wrote:
>
> > I like this idea.
> >
> > On Fri, Mar 16, 2018 at 5:09 PM, Christopher 
> wrote:
> >
> > > Devs,
> > >
> > > (This discussion is somewhat of a spinoff of our previous recent
> > > conversation about HTrace, but I'd like to narrow the discussion to one
> > > specific topic regarding our tracer service.)
> > >
> > > I'd like to remove Accumulo's tracer service and corresponding
> > > presentations in the monitor for 2.0.
> > >
> > > The tracer service currently acts as a sink for the traces from
> Accumulo.
> > >
> > > While there is interest in tracing Accumulo, and Accumulo may itself be
> > > suitable (with the right schema) for storing traces, I do not think
> > acting
> > > as a "trace sink" is really the kind of thing we should be doing as
> part
> > of
> > > Accumulo's out-of-the-box core functionality.
> > >
> > > Also, the presentation and search capabilities of the traces found in
> the
> > > trace table (by convention, and assumed by the monitor) is far from an
> > > ideal presentation of this data, and I don't think the Accumulo project
> > > should continue maintaining that inside the core project's monitor,
> > either.
> > >
> > > I think we should encourage interested volunteers to contribute to
> other
> > > trace presentation software (wherever they may exist) any necessary
> > > "backing store" implementation based on Accumulo.
> > >
> > > None of this would remove tracing instrumentation from Accumulo... it
> > would
> > > just require users interested in trace data from Accumulo to configure
> an
> > > appropriate sink to collect that data in some other integrated
> component
> > of
> > > their overall architecture.
> > >
> > > Decoupling the integrated trace sink from the instrumentation in
> Accumulo
> > > like this could even be a step towards providing support for multiple
> > > different tracing libraries. (I guess we could do this now, but it
> would
> > be
> > > easier if we were not also trying to provide a sink implementation for
> > one
> > > specific version of one specific instrumentation library.)
> > >
> > > Thoughts?
> > >
> >
>

Re: [VOTE] Switch to GitHub issues

[Michael Wall]

+0

On Wed, Mar 14, 2018 at 2:48 AM Christopher  wrote:

> +1
>
> On Tue, Mar 13, 2018, 22:12 Ed Coleman  wrote:
>
> > +0 I defer to others.
> >
> > -Original Message-
> > From: Keith Turner [mailto:ke...@deenlo.com]
> > Sent: Tuesday, March 13, 2018 12:53 PM
> > To: Accumulo Dev List 
> > Subject: [VOTE] Switch to GitHub issues
> >
> > Accumulo PMC,
> >
> > Please vote on initiating the transition from JIRA to GitHub. The purpose
> > of this vote is to see if there is agreement on the following three items
> > the community discussed.
> >
> >   * Using this workflow initially :
> >  https://github.com/apache/accumulo-website/pull/59
> >   * The ability to modify the workflow via lazy consensus through
> > discussions on the dev list.
> >   * The goal of only using one issue tracker after a transition period in
> > which two are used.
> >
> > If the vote passes, I will ask Infra to enable Github Issues and then
> > merge the website PR.
> >
> > This vote will be open through at least Fri Mar 16 16:45:00 UTC 2018 (Fri
> > Mar 16 12:45:00 EDT 2018 / Fri Mar 16 09:45:00 PDT 2018)
> >
> >
>