Re: Accumulo Quarterly Report - Due Wed, July 10th.

[Mark Owens]

LGTM

On Mon, Jul 8, 2024 at 1:49 AM Ed Coleman  wrote:

> The Accumulo community decided to draft the Apache community reports on the
> Accumulo dev list – and this is a draft of the April report for review /
> comments. The report is due by Wednesday, July 10th. The text below is
> copied from the reporting tool and may not reflect the final formatting of
> the final report when submitted.
>
> Ed Coleman --- begin report text from report tool ---
> ## 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.
>
> ## Project Status:
> - Current project status: Ongoing with high activity.
> - Issues for the board: None.
>
> ## Membership Data:
> Apache Accumulo was founded 2012-03-20 (12 years ago) There are currently
> 42
> committers and 39 PMC members in this project. The Committer-to-PMC ratio
> is
> roughly 1:1. It is our practice to invite committers to be PMC members at
> the
> same time. The difference between committers and PMC members is because
> some
> PMC members have elected to go emeritus.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Daniel Roberts on 2023-08-08.
> - No new committers. Last addition was Daniel Roberts on 2023-08-10.
>
> ## Project Activity:
>
> Accumulo is currently working on some significant development efforts.
> - Improving the performance and stability of the 2.1.x line
> - Adding new features and performance improvements to 3.1 line
> - The evolution of the processing model to support dynamic scaling and
> provide
>   elasticity.
>
> ### Releases:
> - accumulo-1.10.4 was released on 2023-11-16.
> - accumulo-2.1.2 was released on 2023-08-21.
> - accumulo-3.0.0 was released on 2023-08-21.
> - accumulo-access-1.0.0-beta was released on 2024-02-17.
>
> The Accumulo 1-10.x line reached end-of-life and Accumulo-1.10.4 is the
> final
> release. The vote thread can be found at [1]
>
> Release activity for a 2.1.3 release has started. A pre-release RC-0 vote
> started on 2 July 2024.  (The pre-release vote is to validate the release
> process before formal releases are created.)
>
> Work on 3.1.0 and future elasticity branches remain very active.
>
> ### Other:
>
> During the past quarter, Accumulo had an opportunity to perform at-scale
> testing.  There were a number of minor issues that were resolved and
> incorporated into 2.1.3 and future release branches. Overall, the testing
> successfully validated scalability and performance improvements and
> demonstrated the stability of new Accumulo features at scale.
>
> ## Community Health:
> Overall community health is good and GitHub activity remains consistent.
> The
> email traffic reflects the community preference of using GitHub projects
> and
> issues for planning and PRs for code discussions. We also use our slack
> channel for day-to-day communications. We continue to use the mailing list
> for
> official Apache business and remains a channel for users to contact us.
>
> ## Links
> [1] https://lists.apache.org/thread/6jy0v0qk14163xx19ocz4l3xxc1rzr3z
> [2] https://lists.apache.org/thread/5tlykw1o5rcz5vps5gz4vo1o7kjnpsld
>

Re: Accumulo Quarterly Report - Due Wednesday, April 10th.

[Mark Owens]

LGTM

I have two small grammatical suggestions you can consider if you'd like.

> The difference between committers and PMC members is because some
> PMC members have elected to go emeritus.

The difference between committers and PMC members is due to some PMC
members electing to go emeritus.


> We continue to use the mailing list for official Apache business and
remains a channel
> for users to contact us.

Perhaps change the last sentence to one of the following:

We continue to use the mailing list for official Apache business and it
remains a channel
for users to contact us.

or

We continue to use the mailing list for official Apache business and as a
channel for users
to contact us.

On Tue, Apr 2, 2024 at 2:34 PM Ed Coleman  wrote:

> The Accumulo community decided to draft the Apache community reports on the
> Accumulo dev list – and this is a draft of the April report for review /
> comments. The report is due by Wednesday, April 10th. I'd like to submit
> the report on Friday, April 5th.
>
> The text below is copied from the reporting tool and may not reflect the
> final formatting of the final report when submitted.
>
> Ed Coleman
>
> --- begin report text from report tool ---
>
> ## 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.
>
> ## Project Status:
> - Current project status: Ongoing with high activity.
> - Issues for the board: None.
>
> Accumulo is currently working on some significant development efforts.
> Improving
> the performance and stability of the 2.1.x line, adding new features and
> performance improvements to 3.1 line, and the evolution of the processing
> model to support dynamic scaling and provide elasticity.
>
> ## Membership Data:
> Apache Accumulo was founded 2012-03-21 (12 years ago) There are currently
> 42
> committers and 39 PMC members in this project. The Committer-to-PMC ratio
> is
> roughly 1:1. It is our practice to invite committers to be PMC members at
> the
> same time. The difference between committers and PMC members is because
> some
> PMC members have elected to go emeritus.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Daniel Roberts on 2023-08-09.
> - No new committers. Last addition was Daniel Roberts on 2023-08-10.
>
> ## Project Activity:
>
> ### Releases:
> - accumulo-1.10.4 was released on 2023-11-16.
> - accumulo-2.1.2 was released on 2023-08-21.
> - accumulo-3.0.0 was released on 2023-08-21.
>
> The Accumulo 1-10.x line reached end-of-life and Accumulo-1.10.4 is the
> final release. The vote thread can be found at [1]
>
> Activity on the next release of 2.1.3, has been very active with bug-fixes
> and
> performance improvements that are being driven by community adoption of
> 2.1.x. Currently 174 PRs have been merged, and there are 21 open issues
> with 1
> labeled as a blocker for the release.
>
> Work is actively proceeding on 3.1.0 that will contain new features and
> performance improvements. Currently, 3.1.0 has 266 merged PRs.
>
> In parallel to 3.1, work continues on the evolution of the Accumulo
> processing
> model to support dynamic scaling and provide elasticity [2]. The goal for
> Accumulo is to move from a model where active table metadata and table data
> management is hosted in active processes to a model that can dynamically
> scale
> server components on-demand to provide configurable latency and higher
> scalability.
>
> ### Other:
> 2024-02-17 Released Accumulo Access Library.  The library provides a
> stand-alone java library with an AccessExpression syntax and an ANTLRv4
> grammar that enables reuse separate from Accumulo.  Within Accumulo, the
> AccessExpression is used in the ColumnVisibility and VisibilityEvaluator to
> provide column-level authorization for data access. The vote thread is
> available at [3]
>
>
> ## Community Health:
> Overall community health is good and GitHub activity remains consistent.
>
> The email traffic reflects the community preference of using GitHub
> projects
> and issues for planning and PRs for code discussions. We also use our slack
> channel for day-to-day communications. We continue to use the mailing list
> for
> official Apache business and remains a channel for users to contact us.
>
> ## Links
> [1] https://lists.apache.org/thread/6jy0v0qk14163xx19ocz4l3xxc1rzr3z
> [2] https://github.com/orgs/apache/projects/164/views/1
> [3] https://lists.apache.org/thread/q96v767png90mfm4t330kfbjvml0rc37
>
> --- end text ---
>

Re: [VOTE] Apache Accumulo 1.10.4-rc1

[Mark Owens]

+1

* Verified signatures and hashes
* Extracted and built from source tarball
* Successfully ran 'mvn test'
* Successfully ran Sunny tests
* Used fluo-uno to build and ran basic operations within the shell



On Wed, Nov 15, 2023 at 1:02 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:

> +1
>
> * Validated signatures and checksums
> * Verified license and notice files in archives
> * Verified source license headers with 'mvn apache-rat:check'
> * Built and ran all the sunny integration tests
> * Started up using Uno to make sure everything started correctly (also ran
> a couple scans, etc)
>
> On Wed, Nov 15, 2023 at 11:46 AM Dominic Garguilo 
> wrote:
>
> > +1
> >
> >
> >- Verified signatures
> >- built from source
> >- ran sunny day tests
> >- ran ingest and verify with the following stats:
> >org.apache.accumulo.test.continuous.ContinuousVerify$Counts
> >REFERENCED=146147488
> >UNREFERENCED=105
> >
> >
> > On Mon, Nov 13, 2023 at 9:42 AM Christopher  wrote:
> >
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Apache Accumulo 1.10.4 (a
> > > closeout final release for 1.10)
> > >
> > > Git Commit:
> > > 47ac68d1a220a90bc80618f9684252b243df6b27
> > > Branch:
> > > 1.10.4-rc1
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -s -m 'Apache Accumulo 1.10.4' rel/1.10.4 \
> > > 47ac68d1a220a90bc80618f9684252b243df6b27
> > >
> > > Staging repo:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1107
> > > Source (official release artifact):
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1107/org/apache/accumulo/accumulo/1.10.4/accumulo-1.10.4-src.tar.gz
> > > Binary:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1107/org/apache/accumulo/accumulo/1.10.4/accumulo-1.10.4-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.10.4-src.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-1.10.4-src.tar.gz) =
> > >
> > >
> >
> 78233784261031a3f6bf18f5c503ad1c9b52098b443291ffcd491785c49f3cc9f8ea2c0904719bf82b52d668ae35025c5b63d23729135120ade367e9c457
> > > accumulo-1.10.4-bin.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-1.10.4-bin.tar.gz) =
> > >
> > >
> >
> fbd7b7449c2ddd438ec966e6e13835cd85e11a349991ab7ca47bc4f7f84b8844ca5e5933f8068bd166c121f65fe4f35afaa8182787fd83589f458e96009bd2f6
> > >
> > > Release notes (in progress) can be found at:
> > > https://accumulo.apache.org/release/accumulo-1.10.4
> > >
> > > 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.10.4 release of Apache Accumulo.
> > >
> > > This vote will remain open until at least Thu Nov 16 03:00:00 PM UTC
> > 2023.
> > > (Thu Nov 16 10:00:00 AM EST 2023 / Thu Nov 16 07:00:00 AM PST 2023)
> > > 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-1107/
> > > # note the trailing slash is needed
> > >
> >
>

Re: Accumulo Board Report - due by Oct 11th

[Mark Owens]

Hi Ed, I have a few minor grammatical suggestions. Nothing major, so
they can be ignored if you wish.

> Accumulo is planning on a 1.10.4 release [2] this quarter as the last
release
> of the 1.10 line that reaches declared end-of-life 2023-11-01.

Accumulo is planning a 1.10.4 release [2] this quarter as the last release
of the 1.10 line reaches declared end-of-life on 2023-11-01.

> Accumulo 3.0.0 release was a removal of deprecated items as permitted by
> semver.

The Accumulo 3.0.0 release was a removal of deprecated items as permitted by
semver.

> In parallel to 3.1, work on the evolution of the Accumulo processing
model to
> support dynamic scaling and provide elasticity [3].

In parallel to 3.1, work continues on the evolution of the Accumulo
processing model to
support dynamic scaling and provide elasticity [3].

> The working being perfumed on elasticity will likely be a 4.0 release, but
> that has not been formally decided by the community.

The work being perfumed on elasticity will likely be a 4.0 release, but
that has not been formally decided by the community.


On Wed, Sep 27, 2023 at 10:12 PM Christopher  wrote:

> Hacktoberfest registration started yesterday. I signed up. However, they
> are not giving away T-shirts or stickers this year. Only planting trees and
> even then only for the first x participants. So there's not a huge
> incentive for people to participate like there has been in previous years,
> unless you're into digital badges as rewards, which I personally think are
> kind of meaningless.
>
> All of our repos are labeled appropriately though so people can find them
> and contribute if they want. We'll see if we get any new people from that
> this year.
>
> On Wed, Sep 27, 2023, 21:18 dev1  wrote:
>
> > They do suggest a few options, but it is all subjective.  I changed it to
> > high and am comfortable with that.  Pro for high (in my opinion)
> >
> >
> >   *   Very active with releases and bug fixes for 2.1.2 and well on the
> > way to releasing 2.1.3. and 1.10.4
> >   *   Major things in the works, no-chop, elasticity…
> >   *   Active discussions and responsive to user’s needs.
> >   *   Quickly addressing reported CVEs with dependencies.
> >
> > All which point to an active, healthy project.
> >
> > My initial choice of moderate was more from an ASF community perspective.
> > In the past we used to have a wider set of contributions from different
> > entities. While we do get the occasional inquiry, none of those recently
> > have chosen to engage enough to provide contributions.  I mention this as
> > something we need to be aware of as a community.
> >
> > If nothing else, it provides an opportunity to have these discussions on
> > the dev list.
> >
> > It also occurs to me that October and hence Hacktober may soon be upon
> > us.  We may want to make sure that we state that we are participating
> > (assuming that we are) and maybe make sure that we have some good
> > first-issues identified.
> >
> > Ed Coleman
> >
> >
> > From: Christopher 
> > Date: Wednesday, September 27, 2023 at 8:09 PM
> > To: dev@accumulo.apache.org 
> > Subject: Re: Accumulo Board Report - due by Oct 11th
> > Now that I think about it, I wonder if "Moderate" was a drop-down
> > selection from the reporter tool. I seem to remember having a similar
> > observation for the last report. If that's the case, then it probably
> > doesn't matter what you select. Sorry if my feedback on that point was
> > misplaced. I'll trust you to leave it whichever way you think is best,
> > even if you decide that it's better to change it back to Moderate.
> >
> > On Wed, Sep 27, 2023 at 5:29 PM dev1  wrote:
> > >
> > > I included Christopher’s and Dan’s suggestions.  The current report
> text
> > reads:
> > >
> > > --- text pasted from report tool ---
> > >
> > > ## 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.
> > >
> > > ## Project Status:
> > > - Current project status: Ongoing with high activity.
> > > - Issues for the board: None.
> > >
> > > Accumulo is currently working some significant development efforts.
> > Improving
> > > the performance and stability of the 2.1.x line, adding new features
> and
> > > performance improvements to 3.1 line, and the evolution of the
> processing
> > > model to support dynamic scaling and provide elasticity.
> > >
> > > The issue concerning accumulodata.com domain was raised at the last
> > board
> > > meeting. We have not been reporting on the issue because there has been
> > no
> > > progress and we stopped actively pursuing the issue (see past reports
> for
> > > details.) The domain was registered and is owned by an Accumulo PMC
> > member,
> > > but the domain was registered using an account that is not longer
> > accessible.
> > > Without access to that account, the 

Re: [VOTE] Apache Accumulo 3.0.0-rc1

[Mark Owens]

+1

- verified hashes
- verified sunny ITs
- verified unit tests
- built with Uno and verified basic functionality


On Tue, Aug 15, 2023 at 7:07 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:

> +1 (binding)
>
> Some of the things I did for verification/testing locally:
>
> * Validated signatures and checksums
> * Verified license and notice files in archives
> * Verified source license headers with 'mvn apache-rat:check'
> * Built and ran all the sunny integration tests
> * Started up using Uno to make sure everything started correctly
>
> On Tue, Aug 15, 2023 at 3:27 PM Dave Marion  wrote:
>
> > +1
> >
> > * verified signatures and hashes
> > * built from source tarball with no issues
> > * Sunny day tests passed
> > * Started instance locally. Ran ci until the disk was almost full. Ran
> > scan, walk, batchwalk with no issues.
> > * Looked at diff between 3.0 and 2.1 to look for changes that were not in
> > the release notes
> >
> > On Mon, Aug 14, 2023 at 7:38 PM dev1  wrote:
> >
> > > +1
> > >
> > >
> > >   *   Verified signatures
> > >   *   Built from tar with no errors (including errorprone)
> > >   *   Sunny tests passed
> > >   *   Started an uno instances and did some spot checks
> > >  *   Verified no unexpected exception in the log files
> > >
> > > Ed Coleman
> > >
> > > From: Christopher 
> > > Date: Monday, August 14, 2023 at 4:26 AM
> > > To: accumulo-dev 
> > > Subject: [VOTE] Apache Accumulo 3.0.0-rc1
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Apache Accumulo 3.0.0.
> > >
> > > Git Commit:
> > > fcf3192f27935ee3c66426fb89799ee0850944f2
> > > Branch:
> > > 3.0.0-rc1
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -s -m 'Apache Accumulo 3.0.0' rel/3.0.0 \
> > > fcf3192f27935ee3c66426fb89799ee0850944f2
> > >
> > > Staging repo:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1106
> > > Source (official release artifact):
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1106/org/apache/accumulo/accumulo/3.0.0/accumulo-3.0.0-src.tar.gz
> > > Binary:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1106/org/apache/accumulo/accumulo/3.0.0/accumulo-3.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-3.0.0-src.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-3.0.0-src.tar.gz) =
> > >
> > >
> >
> 02df744722e65ea65d86a8c89615b9a08435f32a66750e302b392ba9050708dc0fd246a240450f3226cbb64934fa490775264fc748bf941254ddd47c4b484a31
> > > accumulo-3.0.0-bin.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-3.0.0-bin.tar.gz) =
> > >
> > >
> >
> c992e7ce8073862057173bd1005af2c6b617e6ba2a1fb7f7f3e3aed0876dca6c87794257fe511863ffb9b7a641597bedad730673d4c504abc0ee88c78ecfed01
> > >
> > > Release notes (in progress) can be found at:
> > > https://accumulo.apache.org/release/accumulo-3.0.0
> > >
> > > 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 3.0.0 release of Apache Accumulo.
> > >
> > > This vote will remain open until at least Thu Aug 17 08:30:00 AM UTC
> > 2023.
> > > (Thu Aug 17 04:30:00 AM EDT 2023 / Thu Aug 17 01:30:00 AM PDT 2023)
> > > 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-1106/
> > > # note the trailing slash is needed
> > >
> >
>

Re: [VOTE] Apache Accumulo 2.1.2-rc1

[Mark Owens]

+1

- verified hashes
- verified sunny ITs
- verified unit tests
- built with Uno and verified basic functionality


On Mon, Aug 14, 2023 at 6:30 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:

> +1 (binding)
>
> Some of the things I did for verification/testing locally:
>
> * Validated signatures and checksums
> * Verified license and notice files in archives
> * Verified source license headers with 'mvn apache-rat:check'
> * Built and ran all the sunny integration tests
> * Started up using Uno to make sure everything started correctly
>
> On Mon, Aug 14, 2023 at 6:23 PM dev1  wrote:
>
> > +1
> >
> > Verified signatures and successfully ran sunny tests.  Errorprone does
> > fail with a minor error with assert usages that is fixed in PR 3691.
> >
> > Ed Coleman
> >
> > From: Christopher 
> > Date: Monday, August 14, 2023 at 4:16 AM
> > To: accumulo-dev 
> > Subject: [VOTE] Apache Accumulo 2.1.2-rc1
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 2.1.2.
> >
> > Git Commit:
> > ee7ae63a823477b557aa9415a92653e95aa64cb1
> > Branch:
> > 2.1.2-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -s -m 'Apache Accumulo 2.1.2' rel/2.1.2 \
> > ee7ae63a823477b557aa9415a92653e95aa64cb1
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1105
> > Source (official release artifact):
> >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1105/org/apache/accumulo/accumulo/2.1.2/accumulo-2.1.2-src.tar.gz
> > Binary:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1105/org/apache/accumulo/accumulo/2.1.2/accumulo-2.1.2-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.1.2-src.tar.gz.sha512 will contain:
> > SHA512 (accumulo-2.1.2-src.tar.gz) =
> >
> >
> ce27a7bc1892c93300a687ac335a5db5968d1718298acb38dccfb5eb53d2d9f5d912d70c0aa981351afdf7b3e5c5bc7f8bf80ecf0af1ab70634561b86be9f2ca
> > accumulo-2.1.2-bin.tar.gz.sha512 will contain:
> > SHA512 (accumulo-2.1.2-bin.tar.gz) =
> >
> >
> 27778c1c3f1d88ab128649fd0671d3be97ba052216ab43f1169395960e8c7d16375a51f940c2262437b836ea31f83f73f08f7a3d8cadda443e5e8bb31d9b23c5
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-2.1.2
> >
> > 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 2.1.2 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu Aug 17 08:30:00 AM UTC
> 2023.
> > (Thu Aug 17 04:30:00 AM EDT 2023 / Thu Aug 17 01:30:00 AM PDT 2023)
> > 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-1105/
> > # note the trailing slash is needed
> >
>

Re: Accumulo Quaterly Report - Due by 7/12

[Mark Owens]

There are two typo/grammar items that I see:

You should capitalize 'The' at the beginning of "the community has not
decided if the redesign will be a 3.1 or a 4.0 release."

Elasticity is misspelled in the final paragraph - "Currently there are 71
open issues against the elasity project, compared"

The next items are suggestions which you can feel free to ignore.

I'm not sure you need the two extra "issues" in the paragraph. This is how
it reads without them:

"Currently there are 71 open issues against the elasticity project, compared
  with 10 open and 2 in progress against the 2.1 branch and 2 open and
  5 in progress against the 3.0 branch."

A slight re-write of this sentence may be sufficient.

"The large number of issues opened (133) vs closed (77) reflects issues
being
  created as work on elasticity changes are identified."

On Tue, Jul 11, 2023 at 9:34 AM dev1  wrote:

> I updated the section that Mark pointed out.  It now reads (as pasted from
> the reported tool):
>
> Work continues on the evolution of the Accumulo processing model to support
> dynamic scaling and provide elasticity.  The goal for Accumulo is to move
> from
> a model where active table metatdata and table data management is hosted in
> active processes to a model that can dynamically scale server components
> on-demand to provide configurable latency and higher scalability. the
> community has not decided if the redesign will be a 3.1 or a 4.0 release.
>
> I also updated the community health section to read:
>
> ## Community Health:
> Overall community health is good and GitHub activity remains consistent.
>
> - Accumulo development centers on GitHub as reflected in the GitHub
> activity
>   (both pull requests and issues) compared to email list activity.
> Community
>discussions also occur on the the-asf accumulo slack channel.
> - The increase in GitHub activity is due to robust development on the 2.1.1
>   and 2,1.2 (planned) releases and the work on providing dynamic scaling
> and
>   elasticity.
> - The large number of issues opened (133) vs closed (77) reflects issues
> being
>   created as work is identified as work on elasticity changes are
> identified.
>   Currently there are 71 open issues against the elasity project, compared
>   with 10 open and 2 in progress issues against the 2.1 branch and 2 open
> and
>   5 in progress issues against the 3.0 branch.
>
> I’d like to submit this later today (it is due by tomorrow)
>
> Ed Coleman
>
> From: dev1 
> Date: Friday, July 7, 2023 at 9:56 AM
> To: dev@accumulo.apache.org 
> Subject: Re: Accumulo Quaterly Report - Due by 7/12
> Thanks – I’ll make that change.
>
> One section that I think could use more text is Community Health section.
> The ASF board is also interested in more than the technical details, but I
> struggled with providing anything meaningful.  For the recent quarter we
> have had a issues raised by a variety of users, but I did not know how to
> capture that. Any suggestions are greatly appreciated.
>
>
> From: Mark Owens 
> Date: Friday, July 7, 2023 at 7:12 AM
> To: dev@accumulo.apache.org 
> Subject: Re: Accumulo Quaterly Report - Due by 7/12
> Overall looks good to me,
>
> My only suggestion would be to modify the opening sentence in the paragraph
> prior to 'Community Health'. It seems incomplete to me, i.e.,  "Work on the
> evolution of the Accumulo processing model to support dynamic scaling and
> provide elasticity."
>
> A simple fix could be to add a verb into the sentence. Perhaps something
> like, i.e., "Work continues on the evolution of the Accumulo processing
> model to support dynamic scaling and provide elasticity." or "Work on the
> evolution of the Accumulo processing model to support dynamic scaling and
> provide elasticity is ongoing."
>
>
> On Thu, Jul 6, 2023 at 8:54 PM dev1  wrote:
>
> > The Accumulo community decided to draft the Apache community reports on
> > the Accumulo dev list – and this is a draft of the July report  for
> review
> > / comments.
> >
> > The text below is copied from the reporting tool and may not reflect the
> > final formatting of the final report when submitted.
> >
> > Ed Coleman
> >
> > --- report tool text ---
> >
> > ## 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.
> >
> > ## Project Status:
> > Current project status: Ongoing with moderate activity.
> > Issues for the board: none.
> >
&g

Re: Accumulo Quaterly Report - Due by 7/12

[Mark Owens]

Overall looks good to me,

My only suggestion would be to modify the opening sentence in the paragraph
prior to 'Community Health'. It seems incomplete to me, i.e.,  "Work on the
evolution of the Accumulo processing model to support dynamic scaling and
provide elasticity."

A simple fix could be to add a verb into the sentence. Perhaps something
like, i.e., "Work continues on the evolution of the Accumulo processing
model to support dynamic scaling and provide elasticity." or "Work on the
evolution of the Accumulo processing model to support dynamic scaling and
provide elasticity is ongoing."


On Thu, Jul 6, 2023 at 8:54 PM dev1  wrote:

> The Accumulo community decided to draft the Apache community reports on
> the Accumulo dev list – and this is a draft of the July report  for review
> / comments.
>
> The text below is copied from the reporting tool and may not reflect the
> final formatting of the final report when submitted.
>
> Ed Coleman
>
> --- report tool text ---
>
> ## 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.
>
> ## Project Status:
> Current project status: Ongoing with moderate activity.
> Issues for the board: none.
>
> Accumulo is currently working two significant development efforts.
> Improving
> the performance and stability of the 2.1.x line and the evolution of the
> processing model to support dynamic scaling and provide elasticity.
>
> ## Membership Data:
> Apache Accumulo was founded 2012-03-21 (11 years ago)
> There are currently 41 committers and 38 PMC members in this project.
> The Committer-to-PMC ratio is roughly 6:5.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Christopher L. Shannon on
> 2022-09-27.
> - No new committers. Last addition was Christopher L. Shannon on
> 2022-09-27.
>
> ## Project Activity:
>
> Releases:
> - accumulo-2.1.1 was released on 2023-06-19.
> - accumulo-1.10.3 was released on 2023-04-13.  1.x is planned to be end of
>   life on or around 2023-11-01, with an expected final release of any
>   ready-to-ship bug fixes.
>
> The 2.1.1 release closes CVE-2023-34340. Accumulo 2.1.0 contains a defect
> in
> the user authentication process that may succeed when invalid credentials
> are
> provided. The CVE was reported on 2023-06-01 and was closed with the
> release
> on 2023-06-19.
>
> Activity on 2.1 has been very active with bug-fixes and performance
> improvements that are being driven by increased community adoption of
> 2.1.x as
> 1.10.x approaches end of life. Accumulo is planning on a 2.1.2 release this
> quarter that includes items that were slated for 2.1.1, but were bumped
> because of the need for a quick release to resolve the CVE.
>
> A release of 3.0 is also expected this quarter. It is planned to be a
> removal
> of deprecated items as permitted by semver, but with minimal other changes.
> The 3.0 release will also complete the removal of potentially offensive
> terms.
>
> Work on the evolution of the Accumulo processing model to support dynamic
> scaling and provide elasticity.  The goal for Accumulo is to move from a
> model
> where active table metatdata and table data management is hosted in active
> processes to a model that can dynamically scale server components
> on-demand to
> provide configurable latency and higher scalability. the community has not
> decided if the redesign will be a 3.1 or a 4.0 release.
>
> ## Community Health:
> Overall community health is good and GitHub activity remains consistent.
>
> - The current decline in GitHub activity is due to quiet post-release
> activity
>   and work concentrating on a redesign efforts, including activity
>   occurring on Confluence
>
> - Accumulo has transitioned from Jira to GitHub issues. The remaining Jira
>   activity reflects closing obsolete issues.
>
> ## Links
> [1] https://www.cve.org/CVERecord?id=CVE-2023-34340
>

Re: [VOTE] Apache Accumulo 2.1.1-rc2

[Mark Owens]

+1

* Verified hashes
* Ran unit tests
* Ran Sunny ITs
* Opened shell and tested basic functionality
* Went through the JShell tour successfully
* Ran several random examples from the Accumulo-Examples repo successfully


On Sat, Jun 17, 2023 at 10:23 AM Jeffrey Manno 
wrote:

> +1
>
> Verified checksums. Initiated ingest testing with fluo-uno and
> accumulo-testing.
> Ran ITs.
>
> On Fri, Jun 16, 2023 at 7:04 PM Keith Turner  wrote:
>
> > +1
> >
> > Ran CI test w/ agitation on a 10 node cluster for a few hours.  Ingested
> > and verified ~8B entries.   Used the default accumuo-testing agitation
> > settings.
> > Ran 10x random walkers running the bulk test on a 10 node cluster using a
> > modification[1] to the test graph. Ran this for a few hours.  Saw 149
> > successful completions of the test across the 10 walkers.
> >
> > [1]:
> > https://github.com/apache/accumulo/issues/2667#issuecomment-1269905344
> >
> > On Wed, Jun 14, 2023 at 1:49 AM Christopher  wrote:
> >
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Apache Accumulo 2.1.1.
> > >
> > > Stuff that's changed since RC1:
> > > * Fix flaky gc tests: https://github.com/apache/accumulo/pull/3490
> > > * Fix hung compactions: https://github.com/apache/accumulo/pull/3492
> > > * Show lowercase table names better in monitor:
> > > https://github.com/apache/accumulo/pull/3493
> > >
> > > Git Commit:
> > > 9edc2b7cd764c190172076244689ae7c1129db70
> > > Branch:
> > > 2.1.1-rc2
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -s -m 'Apache Accumulo 2.1.1' rel/2.1.1 \
> > > 9edc2b7cd764c190172076244689ae7c1129db70
> > >
> > > Staging repo:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1102
> > > Source (official release artifact):
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1102/org/apache/accumulo/accumulo/2.1.1/accumulo-2.1.1-src.tar.gz
> > > Binary:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1102/org/apache/accumulo/accumulo/2.1.1/accumulo-2.1.1-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.1.1-src.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-2.1.1-src.tar.gz) =
> > >
> > >
> >
> 62634f8c36f28aa13bfc3f76a44bad67cf664594a716da5c0a0bb7948d4825c4bb8c296c9cb50a838722e2c74244debe2a88374bfaaf174b89bc41a761f07065
> > > accumulo-2.1.1-bin.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-2.1.1-bin.tar.gz) =
> > >
> > >
> >
> adb23e56362c2e3e813d07791389b8ca2d5976df8b00a29b607e6ae05ea465eff80ada6d1ec9a9c596df8b4066c51078cd5a4006dc78568ac38f638a1d3895be
> > >
> > > Release notes (in progress) can be found at:
> > > https://accumulo.apache.org/release/accumulo-2.1.1
> > >
> > > 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 2.1.1 release of Apache Accumulo.
> > >
> > > This vote will remain open until at least Sat Jun 17 06:00:00 AM UTC
> > 2023.
> > > (Sat Jun 17 02:00:00 AM EDT 2023 / Fri Jun 16 11:00:00 PM PDT 2023)
> > > 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-1102/
> > > # note the trailing slash is needed
> > >
> >
>

Re: [DRAFT][ANNOUNCE] Apache Accumulo 1.10.3

[Mark Owens]

LGTM

On Fri, Apr 28, 2023 at 6:49 AM Brian Loss  wrote:

> LGTM. Thanks Christopher.
>
> > On Apr 28, 2023, at 2:18 AM, Christopher  wrote:
> >
> > Accumulo Devs,
> >
> > See the below draft release announcement that will be sent to the
> > users list and the Apache announce list. I intend to submit this later
> > today, and am requesting a second pair of eyes to check for typos,
> > errors, omissions. Thanks!
> >
> > ***
> > The Apache Accumulo project is pleased to announce the release
> > of Apache Accumulo 1.10.3! Apache Accumulo 1.10.3 is a bug fix
> > release of the 1.10 LTM release line. This release includes several
> > minor bug fixes and performance improvements.
> > See the release notes linked below for details.
> >
> > Users of 1.10.2 or earlier are encouraged to upgrade to take
> > advantage of these included bug fixes and improvements prior to
> > upgrading to the newer 2.1 LTM release series, to ensure the best
> > upgrade experience.
> >
> > Please note that 1.10 will be end-of-life in November 2023, and we
> > encourage all users to migrate to 2.1 (or later) by then.
> >
> > ***
> >
> > 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.3/
>

Re: [VOTE] Apache Accumulo 1.10.3-rc1

[Mark Owens]

If I update the pom's with the commons-configuration changes suggested by
Dave in a previous post, I can successfully run the Sunny profile tests
with both Hadoop 2 and Hadoop 3.

On Tue, Apr 11, 2023 at 1:16 PM Daniel Roberts  wrote:

> Yes, I changed the memory settings last week and was able to pass the
> ExamplesIT.testScansWithInterference and
> ExamplesIT.testIsolatedScansWithInterference
> without issue. Given these environmental tweaks, do we have a documented
> minimum machine spec that we expect the release tests to pass on?
>
> On Tue, Apr 11, 2023 at 1:00 PM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > The test failure for ExamplesIT.testScansWithInterference is likely from
> > out of memory. See https://github.com/apache/accumulo/issues/3281
> >
> > On Tue, Apr 11, 2023 at 12:21 PM Dominic Garguilo <
> > dominic.gargu...@gmail.com> wrote:
> >
> > > After running
> > > mvn clean verify -Phadoop3,sunny
> > > I am consistently seeing the following:
> > >
> > > [ERROR]
> > > >
> > >
> >
> org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs
> > > >  Time elapsed: 3.605 s  <<< ERROR!
> > > > java.lang.NoClassDefFoundError:
> > > > org/apache/commons/beanutils/BeanIntrospector
> > > > at
> > > >
> > >
> >
> org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs(CredentialProviderFactoryShimTest.java:185)
> > > > Caused by: java.lang.ClassNotFoundException:
> > > > org.apache.commons.beanutils.BeanIntrospector
> > > > at
> > > >
> > >
> >
> org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs(CredentialProviderFactoryShimTest.java:185)
> > >
> > >
> > > This test passes consistently when run in my IDE but fails every time
> > when
> > > running the mentioned maven command.
> > >
> > > On Mon, Apr 10, 2023 at 6:04 PM Dave Marion 
> wrote:
> > >
> > > > *mvn clean verify -Phadoop3,sunny* failed in ExamplesIT with the
> > > > aforementioned changes. Specifically,
> > > ExamplesIT.testScansWithInterference
> > > > failed with a server error when closing the batch writer. No further
> > > > information in the logs.
> > > >
> > > > On Mon, Apr 10, 2023 at 5:06 PM Dave Marion 
> > wrote:
> > > >
> > > > > Updating commons-configuration from 1.6 to 1.10 did the trick I
> > think.
> > > > > Versions 1.7, 1.8, and 1.9 had compilation issues. I'm not veto-ing
> > > > because
> > > > > other people have built with the hadoop3 profile even though more
> > than
> > > > one
> > > > > of us have had an issue. Here are the changes I made to get me past
> > the
> > > > > CredentialProviderFactoryShimTest test failure in conf using the
> > > hadoop3
> > > > > profile.
> > > > >
> > > > >
> > > > > diff --git a/core/pom.xml b/core/pom.xml
> > > > > index 163a1c062f..2aad10486a 100644
> > > > > --- a/core/pom.xml
> > > > > +++ b/core/pom.xml
> > > > > @@ -201,6 +201,8 @@
> > > > >
> > > > >
> > > >
> > >
> >
> org[.]apache[.]hadoop[.]mapred[.](FileAlreadyExistsException|InvalidJobConfException)
> > > > >  
> > > > >
> > > > >
> > > >
> > >
> >
> org[.]apache[.]accumulo[.]core[.]iterators[.]ValueFormatException
> > > > > +
> > > > > +
> > > > >
> > org[.]apache[.]commons[.]configuration[.]Configuration
> > > > >
> > > > >  
> > > > >
> > > > > diff --git a/pom.xml b/pom.xml
> > > > > index 854443da2d..2193b46b54 100644
> > > > > --- a/pom.xml
> > > > > +++ b/pom.xml
> > > > > @@ -212,7 +212,7 @@
> > > > >
> > > > >  commons-configuration
> > > > >  commons-configuration
> > > > > -1.6
> > > > > +1.10
> > > > >
> > > > >
> > > > >  commons-io
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Apr 10, 2023 at 12:16 PM Dave Marion 
> > > > wrote:
> > > > >
> > > > >> From what I can tell:
> > > > >>
> > > > >> 1. commons-configuration:1.6 has a commons-beanutils:1.7.0
> > dependency
> > > > >> 2. hadoop-common:3.0.3 has a commons-beanutils:1.9.3 dependency,
> > > > >> hadoop-common:2.6.5 has no such dependency
> > > > >>
> > > > >> Hadoop 3.0.3 is failing because the commons-beanutils:1.9.3
> > dependency
> > > > >> must not be on the classpath for the test. I have no idea why this
> > is
> > > > >> failing on my machine and not for others. I'm also seeing general
> > > > slowness
> > > > >> building 1.10.3 on my machine, but not building other git
> branches.
> > > > >>
> > > > >> On Mon, Apr 10, 2023 at 8:24 AM Dave Marion 
> > > > wrote:
> > > > >>
> > > > >>> I built the source tarball using the hadoop3 profile again and
> > > > >>> encountered the issue below. The version of hadoop (3.0.3) has
> not
> > > > changed,
> > > > >>> so I assume that this is related to a change in our dependencies.
> > > > >>>
> > > > >>> [ERROR] Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time
> > > > elapsed:
> > > > >>> 3.856 s <<< FAILURE! - in
> > > > >>> 

Re: [VOTE] Apache Accumulo 1.10.3-rc1

[Mark Owens]

Running the hadoop3 profile, I also had an issue with the
CredentialProviderFactoryShimTest as did Dave. I was running on CentOS7.

[ERROR] Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
7.559 s <<< FAILURE! - in
org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest
[ERROR]
org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs
 Time elapsed: 2.527 s  <<< ERROR!
java.lang.NoClassDefFoundError:
org/apache/commons/beanutils/BeanIntrospector
at
org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs(CredentialProviderFactoryShimTest.java:185)
Caused by: java.lang.ClassNotFoundException:
org.apache.commons.beanutils.BeanIntrospector
at
org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs(CredentialProviderFactoryShimTest.java:185)


On Mon, Apr 10, 2023 at 12:16 PM Dave Marion  wrote:

> From what I can tell:
>
> 1. commons-configuration:1.6 has a commons-beanutils:1.7.0 dependency
> 2. hadoop-common:3.0.3 has a commons-beanutils:1.9.3 dependency,
> hadoop-common:2.6.5 has no such dependency
>
> Hadoop 3.0.3 is failing because the commons-beanutils:1.9.3 dependency must
> not be on the classpath for the test. I have no idea why this is failing on
> my machine and not for others. I'm also seeing general slowness building
> 1.10.3 on my machine, but not building other git branches.
>
> On Mon, Apr 10, 2023 at 8:24 AM Dave Marion  wrote:
>
> > I built the source tarball using the hadoop3 profile again and
> encountered
> > the issue below. The version of hadoop (3.0.3) has not changed, so I
> assume
> > that this is related to a change in our dependencies.
> >
> > [ERROR] Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> > 3.856 s <<< FAILURE! - in
> > org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest
> > [ERROR]
> >
> org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs
> >  Time elapsed: 1.186 s  <<< ERROR!
> > java.lang.NoClassDefFoundError:
> > org/apache/commons/beanutils/BeanIntrospector
> > at
> >
> org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs(CredentialProviderFactoryShimTest.java:185)
> > Caused by: java.lang.ClassNotFoundException:
> > org.apache.commons.beanutils.BeanIntrospector
> > at
> >
> org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs(CredentialProviderFactoryShimTest.java:185)
> >
> > On Sun, Apr 9, 2023 at 11:41 AM Jeffrey Manno 
> > wrote:
> >
> >> +1
> >>
> >> I did run into a few flaky tests but none seem to warrant a stoppage to
> >> this release candidate. Two common ones are SuspendTabletsIT and
> >> DeleteTableDuringSplitIT.
> >>
> >> Other checks I did:
> >>
> >>- Ran the entire test suite, along with sunny day tests.
> >>- Verified checksums.
> >>- Did some small ingest testing with agitation.
> >>
> >>
> >> On Sat, Apr 8, 2023 at 9:18 AM Christopher Shannon <
> >> christopher.l.shan...@gmail.com> wrote:
> >>
> >> > +1 (binding), LGTM
> >> >
> >> > Some of the things I did for verification/testing locally:
> >> >
> >> > * Validated signatures and checksums
> >> > * Verified license and notice files in archives
> >> > * Verified source license headers with 'mvn apache-rat:check'
> >> > * Built and ran all the sunny integration tests
> >> > * Started up using Uno to make sure everything started correctly (also
> >> ran
> >> > a couple scans, etc)
> >> >
> >> > On Fri, Apr 7, 2023 at 4:23 PM Christopher 
> wrote:
> >> >
> >> > > Accumulo Developers,
> >> > >
> >> > > Please consider the following candidate for Apache Accumulo 1.10.3.
> >> > >
> >> > > Git Commit:
> >> > > 733863638d85d0109d217da7ea5f36f5e483e207
> >> > > Branch:
> >> > > 1.10.3-rc1
> >> > >
> >> > > If this vote passes, a gpg-signed tag will be created using:
> >> > > git tag -f -s -m 'Apache Accumulo 1.10.3' rel/1.10.3 \
> >> > > 733863638d85d0109d217da7ea5f36f5e483e207
> >> > >
> >> > > Staging repo:
> >> > >
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1100
> >> > > Source (official release artifact):
> >> > >
> >> > >
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1100/org/apache/accumulo/accumulo/1.10.3/accumulo-1.10.3-src.tar.gz
> >> > > Binary:
> >> > >
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1100/org/apache/accumulo/accumulo/1.10.3/accumulo-1.10.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)
> >> > >
> 

Re: [TEST][VOTE] Apache Accumulo 1.10.3-rc0

[Mark Owens]

sure


On Thu, Apr 6, 2023 at 3:33 PM Christopher  wrote:

> Mark, I'm having trouble trying to parse the unformatted text dump in
> the email thread. Would you mind creating issues for the bugs you saw?
> That way, you can put output in markdown blocks with triple backticks.
>
> On Thu, Apr 6, 2023 at 3:27 PM Mark Owens  wrote:
> >
> > After downloading the artifacts, I ran the following:
> >
> > tar szf accumulo-1.10.3-src.tar.gz
> > cd accumulo-1.10.3/
> > mvn clean package
> >
> > The output in the surefire-reports directory doesn't provide too much
> info.
> >
> > Test set:
> > org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
> >
> ---
> > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.716 s
> <<<
> > FAILURE! - in
> > org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
> > org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
> >  Time elapsed: 1.698 s  <<< ERROR!
> > java.lang.ExceptionInInitializerError
> > Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3,
> > length 2
> >
> >
> > [main} INFO  org.apache.hadoop.hdfs.MiniDFSCluster  - starting cluster:
> > numNameNodes=1, numDataNodes=1
> > [main} INFO  org.apache.hadoop.hdfs.MiniDFSCluster  - Shutting down the
> > Mini HDFS Cluster
> >
> > No additional stacktrace info provided just from running the tests. I
> then
> > attempted to install Accumulo using fluo-uno. ZooKeeper throws the
> > following stacktrace (which I remember the out of bounds being related to
> > in the past):
> >
> > > uno setup accumulo
> > > uno status
> > This display accumulo and haoop running but no ZK. Attempts to start
> again
> > reveals the stacktrace info below.
> > > uno start accumulo
> >
> > ZooKeeper JMX enabled by default
> >
> >
> > Using config:
> > ${HOME}/dev/fluo-uno/install/zookeeper-3.4.14/bin/../conf/zoo.cfg
> >
> > Starting zookeeper ... STARTED
> >
> >
> > Exception in thread "main" java.lang.ExceptionInInitializerError
> >
> >
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.preProcessForWindows(GenericOptionsParser.java:438)
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.parseGeneralOptions(GenericOptionsParser.java:484)
> >
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.(GenericOptionsParser.java:170)
> >
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.(GenericOptionsParser.java:153)
> >
> > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:64)
> >
> >
> > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> >
> > at org.apache.hadoop.hdfs.tools.GetConf.main(GetConf.java:331)
> >
> >
> > Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3,
> > length 2
> >
> > at
> java.base/java.lang.String.checkBoundsBeginEnd(String.java:3319)
> >
> >
> > at java.base/java.lang.String.substring(String.java:1874)
> >
> >
> > at org.apache.hadoop.util.Shell.(Shell.java:50)
> >
> >
> > ... 7 more
> >
> >
> > Starting namenodes on []
> >
> >
> > localhost: starting namenode, logging to
> >
> /home/mark/dev/fluo-uno/install/logs/hadoop/hadoop-mark-namenode-devlap.out
> >
> > localhost: starting datanode, logging to
> >
> /home/mark/dev/fluo-uno/install/logs/hadoop/hadoop-mark-datanode-devlap.out
> >
> > Exception in thread "main" java.lang.ExceptionInInitializerError
> >
> >
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.preProcessForWindows(GenericOptionsParser.java:438)
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.parseGeneralOptions(GenericOptionsParser.java:484)
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.(GenericOptionsParser.java:170)
> > at
> >
> org.apache.hadoop.util.GenericOptionsParser.(GenericOptionsParser.java:153)
> > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:64)
> >
> > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> >
> > at org.apache.hadoop.hdfs.tools.GetConf.main(GetConf.java:331)
> >
> > Caused by: java.lang.StringIndexOutOfBoundsExce

Re: [TEST][VOTE] Apache Accumulo 1.10.3-rc0

[Mark Owens]

te' died.
java.lang.ExceptionInInitializerError

at org.apache.hadoop.util.StringUtils.(StringUtils.java:79)

at
org.apache.hadoop.security.Groups.parseStaticMapping(Groups.java:116)
at org.apache.hadoop.security.Groups.(Groups.java:93)
at org.apache.hadoop.security.Groups.(Groups.java:73)
at
org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:293)
at
org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:283)
at
org.apache.hadoop.security.UserGroupInformation.ensureInitialized(UserGroupInformation.java:260)
at
org.apache.hadoop.security.UserGroupInformation.loginUserFromSubject(UserGroupInformation.java:789)
at
org.apache.hadoop.security.UserGroupInformation.getLoginUser(UserGroupInformation.java:774)
at
org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:647)
at
org.apache.hadoop.fs.FileSystem$Cache$Key.(FileSystem.java:2755)
at
org.apache.hadoop.fs.FileSystem$Cache$Key.(FileSystem.java:2747)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2613)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:370)
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296)
at
org.apache.accumulo.core.volume.VolumeImpl.(VolumeImpl.java:45)
at
org.apache.accumulo.core.volume.VolumeConfiguration.create(VolumeConfiguration.java:161)
at
org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:357)
at
org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:339)
at
org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:333)
at
org.apache.accumulo.master.state.SetGoalState.main(SetGoalState.java:46)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.apache.accumulo.start.Main$2.run(Main.java:170)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3,
length 2
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3319)
at java.base/java.lang.String.substring(String.java:1874)
at org.apache.hadoop.util.Shell.(Shell.java:50)
... 27 more



On Thu, Apr 6, 2023 at 3:09 PM Christopher  wrote:

> I think we need more of that stack trace to be able to interpret it at all.
>
> On Thu, Apr 6, 2023, 13:57 Mark Owens  wrote:
>
> > I'm also running into an issue with the VfsClassLoaderTest.
> >
> > java.lang.ExceptionInInitializerError
> >
> >
> > Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3,
> > length 2
> >
> > I've seen this error message before but can't recall the details. May be
> > some misconfiguration on my machine perhaps, but I'm not sure.
> >
> > On Thu, Apr 6, 2023 at 1:48 PM Dave Marion  wrote:
> >
> > > `mvn -Dtimeout.factor=2 clean package -Psunny` works, but `mvn
> > > -Dtimeout.factor=2 clean package -Psunny,hadoop3` fails with:
> > >
> > > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> > > 1.153 s <<< FAILURE! - in
> > > org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
> > > [ERROR]
> > > org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
> > >  Time elapsed: 1.15 s  <<< ERROR!
> > > java.lang.NoSuchMethodError: 'boolean
> > >
> > >
> >
> org.eclipse.jetty.servlet.ServletMapping.containsPathSpec(java.lang.String)'
> > >
> > > On Thu, Apr 6, 2023 at 1:36 PM Dave Marion 
> wrote:
> > >
> > > > `mvn -Dtimeout.factor=2 clean package` worked. Thanks!
> > > >
> > > > On Thu, Apr 6, 2023 at 1:19 PM Christopher 
> > wrote:
> > > >
> > > >> Might just be a coincidence. If it's still failing with a higher
> > > timeout,
> > > >> I
> > > >> can look into it.
> > > >>
> > > >> On Thu, Apr 6, 2023, 12:51 Dave Marion  wrote:
> > > >>
> > > >> > I just thought it was odd that it was working in one place (git
> > > >> workspace),
> > > >> > but not from the source tarball.
> > > >> >
> > > >> > On Thu, Apr 6, 2023 at 12:48 PM Christopher 
> > > >> wrote:
> > > >> >
>

Re: [TEST][VOTE] Apache Accumulo 1.10.3-rc0

[Mark Owens]

I'm also running into an issue with the VfsClassLoaderTest.

java.lang.ExceptionInInitializerError


Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3,
length 2

I've seen this error message before but can't recall the details. May be
some misconfiguration on my machine perhaps, but I'm not sure.

On Thu, Apr 6, 2023 at 1:48 PM Dave Marion  wrote:

> `mvn -Dtimeout.factor=2 clean package -Psunny` works, but `mvn
> -Dtimeout.factor=2 clean package -Psunny,hadoop3` fails with:
>
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 1.153 s <<< FAILURE! - in
> org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
> [ERROR]
> org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
>  Time elapsed: 1.15 s  <<< ERROR!
> java.lang.NoSuchMethodError: 'boolean
>
> org.eclipse.jetty.servlet.ServletMapping.containsPathSpec(java.lang.String)'
>
> On Thu, Apr 6, 2023 at 1:36 PM Dave Marion  wrote:
>
> > `mvn -Dtimeout.factor=2 clean package` worked. Thanks!
> >
> > On Thu, Apr 6, 2023 at 1:19 PM Christopher  wrote:
> >
> >> Might just be a coincidence. If it's still failing with a higher
> timeout,
> >> I
> >> can look into it.
> >>
> >> On Thu, Apr 6, 2023, 12:51 Dave Marion  wrote:
> >>
> >> > I just thought it was odd that it was working in one place (git
> >> workspace),
> >> > but not from the source tarball.
> >> >
> >> > On Thu, Apr 6, 2023 at 12:48 PM Christopher 
> >> wrote:
> >> >
> >> > > Those are timeouts. The tests are passing in Jenkins. I suspect your
> >> > > machine is a little slower, but would finish with more time. You can
> >> set
> >> > > -Dtimeout.factor=2 to try to work around it for a local build on a
> >> > machine
> >> > > with more constrained resources. I wouldn't be surprised if 1.10
> tests
> >> > were
> >> > > a bit more flaky than newer branches, also, just because of test
> >> > > improvements over time, but timeouts can happen for any of our
> >> branches.
> >> > So
> >> > > overriding the arbitrary timeout by some factor can help.
> >> > >
> >> > > On Thu, Apr 6, 2023, 12:41 Dave Marion  wrote:
> >> > >
> >> > > > Verified sha1 & md5 signatures
> >> > > > Verified signing key
> >> > > >
> >> > > > Ran into an issue trying to build from the source tarball. I
> tried 3
> >> > > times
> >> > > > with the command `mvn clean package` and the build failed in the
> >> same
> >> > > spot
> >> > > > every time (see below). Note that on the same machine I ran `mvn
> >> clean
> >> > > > package` on my local git workspace copy of the 1.10 branch (at
> >> > > > commit fb09e7e2594c451317ce6294b9dd27bd0c5e6c05) with no issues.
> >> > > >
> >> > > > [ERROR] Tests run: 6, Failures: 0, Errors: 2, Skipped: 0, Time
> >> elapsed:
> >> > > > 96.173 s <<< FAILURE! - in
> >> > > > org.apache.accumulo.minicluster.MiniAccumuloClusterTest
> >> > > > [ERROR]
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> org.apache.accumulo.minicluster.MiniAccumuloClusterTest.testPerTableClasspath
> >> > > >  Time elapsed: 60.009 s  <<< ERROR!
> >> > > > org.junit.runners.model.TestTimedOutException: test timed out
> after
> >> > 6
> >> > > > milliseconds
> >> > > > at
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> app//org.apache.accumulo.minicluster.MiniAccumuloClusterTest.testPerTableClasspath(MiniAccumuloClusterTest.java:169)
> >> > > >
> >> > > > [ERROR]
> org.apache.accumulo.minicluster.MiniAccumuloClusterTest.test
> >> > > Time
> >> > > > elapsed: 30.001 s  <<< ERROR!
> >> > > > org.junit.runners.model.TestTimedOutException: test timed out
> after
> >> > 3
> >> > > > milliseconds
> >> > > > at
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> app//org.apache.accumulo.minicluster.MiniAccumuloClusterTest.test(MiniAccumuloClusterTest.java:157)
> >> > > >
> >> > > > On Wed, Apr 5, 2023 at 7:24 PM dev1  wrote:
> >> > > >
> >> > > > > I did some quick checks and all looks good.
> >> > > > >
> >> > > > > - verified sha512 signatures
> >> > > > > - verified signing key
> >> > > > > - sunny tests pass.
> >> > > > >
> >> > > > > Ed Coleman
> >> > > > >
> >> > > > > -Original Message-
> >> > > > > From: Christopher 
> >> > > > > Sent: Wednesday, April 5, 2023 4:25 PM
> >> > > > > To: accumulo-dev 
> >> > > > > Subject: [TEST][VOTE] Apache Accumulo 1.10.3-rc0
> >> > > > >
> >> > > > > Accumulo Developers,
> >> > > > >
> >> > > > > This is not an actual vote.
> >> > > > > I have prepared the following release candidate as a test build
> >> for
> >> > > > > 1.10.3. If there are no immediate objections or issues, I intend
> >> to
> >> > > > create
> >> > > > > an RC1 release candidate in the next day or so, to vote on.
> >> > > > >
> >> > > > > Git Commit:
> >> > > > > ed75b4521094faa6f6e1037a444747390a120068
> >> > > > > Branch:
> >> > > > > 1.10.3-rc0
> >> > > > >
> >> > > > > If this vote passes, a gpg-signed tag will be created using:
> >> > > > > git tag -f -s -m 'Apache Accumulo 1.10.3' rel/1.10.3 \
> >> > > > > 

Re: {DISCUSS} Accumulo quarterly report due Wednesday Oct 12

[Mark Owens]

Hi Ed,

Looks good! One other minor grammatical issue:

We expect to start the release process with an rc0 candidate soon, with the
remaining issues be actively worked.

I think "be actively" should be "being actively".



On Wed, Oct 12, 2022 at 6:25 AM Brian Loss  wrote:

> LGTM too, but another nit…
> “Community activity remains healthy and centers on GitHub, which is reflect
>  by robust GitHub activity and a corresponding decrease in email traffic.”
>
> Should that say “is reflected by” instead?
>
> > On Oct 11, 2022, at 8:50 PM, Arvind Shyamsundar 
> > 
> wrote:
> >
> > Hi Ed, thank you for drafting this. There's a minor typo - "no
> persuing" -> I guess that should be "is not pursuing"?
> >
> > Otherwise, it LGTM.
> >
> > Thank you again.
> >
> > - Arvind Shyamsundar (HE / HIM)
> >
> > -Original Message-
> > From: dev1 
> > Sent: Tuesday, October 11, 2022 5:46 PM
> > To: dev@accumulo.apache.org
> > Subject: [EXTERNAL] {DISCUSS} Accumulo quarterly report due Wednesday
> Oct 12
> >
> > The Apache Accumulo quarterly report is due Wednesday, Oct 12.  The
> community decided to publicly prepare the report on the dev mailing list.
> Below is the current draft. (note: This is a cut-n-paste from the report
> wizard, so there may be formatting differences that will not appear when
> the report is submitted via the apache reporting tool.)
> >
> >  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 and
> the community no persuing action at this time. The domain seems to continue
> to be automatically renewed even though the owner does not have access to
> the domain. Unless something changes, we will no longer continue to report
> on this issue.
> >
> > For historical background information, 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-20 (11 years ago) There are
> currently 41 committers and 41 PMC members in this project.
> > The Committer-to-PMC ratio is 1:1.
> >
> > Community changes, past quarter:
> > - Christopher L. Shannon was added to the PMC on 2022-09-26
> > - Christopher L. Shannon was added as committer on 2022-09-27
> >
> > ## Project Activity:
> > Project activity on the next release remains active with significant
> improvements to the current baseline. Currently, Accumulo is targeting an
> October / November release of version 2.1.  We expect to start the release
> process with an rc0 candidate soon, with the remaining issues be actively
> worked. The GitHub 2.1 project dashboard is available at [5] and an email
> discussion is available on thread [6]
> >
> > Current 2.1 progress includes:
> >
> >  - 26 pull requests that are currently in progress.
> >  - 28 issues that are open, but a lot of these will get bumped to the
> next
> >version.
> >  - 1359 issues that have been resolved.
> >
> > ## Community Health:
> > Overall community health is good and GitHub activity remains consistent.
> >
> > - Community activity remains healthy and centers on GitHub, which is
> reflect
> >  by robust GitHub activity and a corresponding decrease in email traffic.
> > - Accumulo has transitioned from Jira to GitHub issues. The remaining
> Jira
> >  activity reflects closing obsolete issues.issues.
> >
> > ## Links
> > (private) [1]:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fr8c8ef5575b14accb6fc00d670764a313b91d76033f761c6e5c7eb29d%2540%253Cprivate.accumulo.apache.org%253Edata=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=5DsIJXr8avv6potFhvdycQYLZstwj5FHJHbbjWiQjvY%3Dreserved=0
> > (private) [2]:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6%40%253Cprivate.accumulo.apache.org%253Edata=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=Pjx4zZxtKL0rPYn8dyZMXbcwIHaiV9FZmKoWp%2BHHTSk%3Dreserved=0
> > (private) [3]:
> 

Re: [VOTE] Apache Accumulo 1.10.2-rc1

[Mark Owens]

+1

Verified hashes
Successfully ran Sunny tests
Successfully created Accumulo instance using Fluo-Uno and performed some
basic operations.

On Wed, Feb 9, 2022 at 9:14 AM Dominic Garguilo 
wrote:

> +1
>
> Verified Psunny tests pass, both src and binary sha512 checksums match and
> commit hash matches.
> On Tue, Feb 8, 2022 at 4:28 PM Jeffrey Manno  wrote:
>
> > +1
> >
> > Verified Psunny tests pass. Confirmed sha512 matches.
> >
> >
> > On Tue, Feb 8, 2022 at 11:21 AM dev1  wrote:
> >
> > > +1
> > >
> > > Verified:
> > >
> > > Sunny day tests pass with no issues (mvn verify -Psunny
> > -DreuseForks-false)
> > > Commit hash matches
> > > sha512 checksums for src and binary tar files match expected
> > >
> > > Ed Coleman
> > >
> > > -Original Message-
> > > From: Christopher 
> > > Sent: Tuesday, February 8, 2022 10:08 AM
> > > To: accumulo-dev 
> > > Subject: [VOTE] Apache Accumulo 1.10.2-rc1
> > >
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Apache Accumulo 1.10.2.
> > >
> > > Git Commit:
> > > db2baf1706c0721e25438d5329ef1bba5159c24d
> > > Branch:
> > > 1.10.2-rc1
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -s -m 'Apache Accumulo 1.10.2' rel/1.10.2 \
> > > db2baf1706c0721e25438d5329ef1bba5159c24d
> > >
> > > Staging repo:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1092
> > > Source (official release artifact):
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1092/org/apache/accumulo/accumulo/1.10.2/accumulo-1.10.2-src.tar.gz
> > > Binary:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1092/org/apache/accumulo/accumulo/1.10.2/accumulo-1.10.2-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.10.2-src.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-1.10.2-src.tar.gz) =
> > >
> > >
> >
> d9963856a49f43e37d9b64fce440497c7b3621ba8cf2c6f56e4ce1e061edde11882905e99a21555c83f5c9c82d14e4323dd1246a344a8b9af55da863dfc55c1d
> > > accumulo-1.10.2-bin.tar.gz.sha512 will contain:
> > > SHA512 (accumulo-1.10.2-bin.tar.gz) =
> > >
> > >
> >
> 9b6e9286133120588f4c682e3fadee33704cf5983ef7e3c0be84c1678bd9bcf283a2c6efa6d4074c73f30032f5c0aa1073c15ec39f90d215505e028a1cf0a739
> > >
> > > Release notes (in progress) can be found at:
> > > https://accumulo.staged.apache.org/release/accumulo-1.10.2
> > >
> > > 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.10.2 release of Apache Accumulo.
> > >
> > > This vote will remain open until at least Fri Feb 11 03:30:00 PM UTC
> > 2022.
> > > (Fri Feb 11 10:30:00 AM EST 2022 / Fri Feb 11 07:30:00 AM PST 2022)
> > 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-1092/
> > > # note the trailing slash is needed
> > >
>

Re: [VOTE] Apache Accumulo 2.0.0-alpha-1-rc1

[J. Mark Owens]

+1

Verified all hashes
Ran unit tests successfully
Ran ITs successfully except for certain timeouts (common for my laptop)
Installed and tested basic capability using Fluo-uno


On Sun, Oct 14, 2018 at 3:27 PM Keith Turner  wrote:

> +1
>
> I made some update to the 2.0.0 WIP release notes to cover more of the
> features added.
>
> https://accumulo.apache.org/release/accumulo-2.0.0/
>
> My changes :
>
>
> https://github.com/apache/accumulo-website/commit/65a48e69a7644e5b6ab54ed732785a98f22907dd
>
> For this updates I added two liquid tags for linking to issues, making
> linking to Jira and Github issues much easier.
> On Thu, Oct 11, 2018 at 7:22 PM Christopher  wrote:
> >
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo
> 2.0.0-alpha-1.
> >
> > Note that an alpha release should satisfy all the usual ASF
> > requirements for copyright notices/license information. However, for
> > semantic versioning purposes, alpha denotes a preview release of what
> > is expected to come in 2.0.0, but without the API
> > stability/compatibility guarantees that come with other semver
> > releases. (https://semver.org/#spec-item-9).
> >
> > The intent of this alpha is to provide a preview of what is to come in
> > 2.0.0, and to solicit feedback from testing and evaluation which will
> > help us on our way to finalizing a 2.0.0 release in the near future.
> >
> > If this vote passes, it should *NOT* be recommended for production
> > environments, and should only be used for testing and evaluation
> > purposes.
> >
> > Git Commit:
> > 9244e2c13266a50f3645913ee0a881a58784f029
> > Branch:
> > 2.0.0-alpha-1-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 2.0.0-alpha-1' -s rel/2.0.0-alpha-1 \
> > 9244e2c13266a50f3645913ee0a881a58784f029
> >
> > Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1074
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1074/org/apache/accumulo/accumulo/2.0.0-alpha-1/accumulo-2.0.0-alpha-1-src.tar.gz
> > Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1074/org/apache/accumulo/accumulo/2.0.0-alpha-1/accumulo-2.0.0-alpha-1-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-2.0.0-alpha-1-src.tar.gz.sha512 will contain:
> > SHA512 (accumulo-2.0.0-alpha-1-src.tar.gz) =
> >
> 477e69c693372f9103b1271b96a27049798056ed53c2721a4c462d4fb782a230965c0fcadddfa464988a74dee56718a9815b225cce1050613ac17f67e6f7df01
> > accumulo-2.0.0-alpha-1-bin.tar.gz.sha512 will contain:
> > SHA512 (accumulo-2.0.0-alpha-1-bin.tar.gz) =
> >
> fbb5a09c9b9033409281a5a7211b7666ad7ddf1b87c9fff15cb961a84ba8f755a383c213f5907a8016dee2cc0490c2e02fcbef3ba7a84c2d64e9d8ed4479d2d3
> >
> > 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-2.0.0-alpha-1/
> >
> > Release testing instructions:
> > https://accumulo.apache.org/contributor/verifying-release (Note: in my
> > opinion, errors or bugs in testing an alpha release which might
> > normally block a regular release should not be considered blockers for
> > an alpha release, since it is a preview release, so long as basic
> > functionality is sufficient to allow testing and evaluation; however,
> > voters should vote according to their own criteria.)
> >
> > 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 2.0.0-alpha-1 release of Apache Accumulo.
> >
> > This vote will remain open until at least Sun Oct 14 23:30:00 UTC 2018.
> > (Sun Oct 14 19:30:00 EDT 2018 / Sun Oct 14 16:30:00 PDT 2018)
> > 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-1074/
> > # note the trailing slash is needed
>

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

[J. Mark Owens]

+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: [VOTE] Apache Accumulo 1.9.2-rc2

[J. Mark Owens]

+1

Verified signatures
Ran ITs and unit tests
Built from source tarball.
Using built instance, installed using Uno, exercising various commands and
tasks via the shell.


On Wed, Jul 18, 2018 at 5:32 PM, Christopher  wrote:

> Just published draft release notes for both 1.9.2 and 1.9.3 (to get ahead
> of the curve). Please edit as needed. I plan to close this vote tonight or
> tomorrow morning if nothing changes.
>
> On Wed, Jul 18, 2018 at 5:01 PM Mike Miller 
> wrote:
>
> > +1
> > Verified both source and binary signatures and hashes (asc, md5 and sha1)
> > Successfully built from source tar ball
> >
> > On Wed, Jul 18, 2018 at 3:41 PM Christopher  wrote:
> >
> > > +1
> > >
> > > * All ITs passing on both Hadoop 2 (2.6.4) and Hadoop 3 (3.0.0)
> profiles
> > > * Checksums and sigs match
> > > * javadoc and source jar exists for each jar
> > > * source tarball matches git commit and branch
> > > * binary tarball contains expected jars
> > > * LICENSE and NOTICE files look fine
> > > * Built Fluo with this version and all ITs passed
> > > * Manually ran Accumulo using Uno with ZK 3.4.12 and Hadoop 2.8.4
> > > * Manually confirmed no public API files were changed since 1.9.1
> > >
> > >
> > > On Wed, Jul 18, 2018 at 1:24 PM Keith Turner  wrote:
> > >
> > > > +1
> > > >
> > > > Ran continuous ingest for 24 Hr and verified w/o agitation.  Ran on
> 10
> > > > node cluster.
> > > >
> > > > org.apache.accumulo.test.continuous.ContinuousVerify$Counts
> > > > REFERENCED=3872850
> > > > UNREFERENCED=8001285
> > > >
> > > > Hashes and sigs look good.
> > > > Built Fluo against staging repo w/o issue.
> > > >
> > > > On Sun, Jul 15, 2018 at 11:30 PM, Christopher 
> > > wrote:
> > > > > Accumulo Developers,
> > > > >
> > > > > Please consider the following candidate for Apache Accumulo 1.9.2.
> > > > >
> > > > > Git Commit:
> > > > > 3520d31ba60f5b50a9558bac087b8221d0df7900
> > > > > Branch:
> > > > > 1.9.2-rc2
> > > > >
> > > > > If this vote passes, a gpg-signed tag will be created using:
> > > > > git tag -f -m 'Apache Accumulo 1.9.2' -s rel/1.9.2 \
> > > > > 3520d31ba60f5b50a9558bac087b8221d0df7900
> > > > >
> > > > > Staging repo:
> > > > >
> > > >
> > >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1073
> > > > > Source (official release artifact):
> > > > >
> > > >
> > >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1073/org/apache/accumulo/accumulo/1.9.
> 2/accumulo-1.9.2-src.tar.gz
> > > > > Binary:
> > > > >
> > > >
> > >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1073/org/apache/accumulo/accumulo/1.9.
> 2/accumulo-1.9.2-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.2-src.tar.gz.sha512 will contain:
> > > > > SHA512 (accumulo-1.9.2-src.tar.gz) =
> > > > >
> > > >
> > >
> > 38928ffa9e25796d1edf52075d2770e6bcfcf31a28b7a2bbc4dd90ffe2b3
> 4713bedabd8473ba6c3fd4387113f66856e9007240ece10955e5640c7682740b6b2b
> > > > > accumulo-1.9.2-bin.tar.gz.sha512 will contain:
> > > > > SHA512 (accumulo-1.9.2-bin.tar.gz) =
> > > > >
> > > >
> > >
> > 3018d55284940ca22946389c546db3c0dcaca682d49aee8fc031e25321ba
> db8e1e518d5c086906e03e8c53926db5bb79a97daecaee5d1aa5417d46ee2b8a2419
> > > > >
> > > > > 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.2/
> > > > >
> > > > > 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.2 release of Apache Accumulo.
> > > > >
> > > > > This vote will remain open until at least Thu Jul 19 03:30:00 UTC
> > 2018.
> > > > > (Wed Jul 18 23:30:00 EDT 2018 / Wed Jul 18 20:30:00 PDT 2018)
> > > > > 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-1073/
> > > > > # note the trailing slash is needed
> > > >
> > >
> >
>

Re: [DISCUSS] Draft release timeline for 2.0.0

[J. Mark Owens]

I'd like to get ACCUMULO-4808 into 2.0. I think I should be able to make
the proposed deadline.

On Mon, Jun 11, 2018 at 6:36 PM, Josh Elser  wrote:

> Based on that, https://issues.apache.org/jira/browse/ACCUMULO-4733 is the
> only thing outstanding (and just one question at that).
>
> Mid/late August seems like a long time until feature-complete for
> essentially a no-op of work :)
>
>
> On 6/11/18 5:07 PM, Christopher wrote:
>
>> I believe those are being maintained in the draft release notes at
>> https://accumulo.apache.org/release/accumulo-2.0.0/
>>
>> On Mon, Jun 11, 2018 at 5:02 PM Josh Elser  wrote:
>>
>> What are the current 2.0.0 features? (Outstanding and completed)
>>>
>>> On 6/11/18 4:35 PM, Christopher wrote:
>>>
 Hi Accumulo Devs,

 I've been thinking about the 2.0.0 release timeline. I was thinking
 something like this milestone timeline:

 Feature Complete : mid-late August
 Dedicated Testing, Documentation, and release voting : all of September
 Final release : October 1st

 This schedule would make 2.0.0 available for the Accumulo Summit coming

>>> up
>>>
 in October, with a few weeks to spare.


>>>
>>

Re: [VOTE] Apache Accumulo 1.9.0-rc1

[J. Mark Owens]

+1

* verified hashes and signature
* build passed mvn clean verify -Psunny
* build passed all unit testing
* ran an accumulo instance using Uno
* verified basic functionality via the accumulo shell command

On Sun, Apr 15, 2018 at 1:24 PM, Mike Drob  wrote:

> I am strongly against generating and publishing checksum information after
> a vote because that ostensibly means it hasn't been verified and voted on.
>
> On Sun, Apr 15, 2018 at 12:35 AM, Christopher  wrote:
>
> > Mike,
> >
> > We use stronger checksums (SHA512) in the SVN[1] area and downloads
> page[2]
> > after a vote passes. In fact, we're one of the only "perfect projects" in
> > regards to compliance with this policy[3].
> >
> > The Maven staging area doesn't follow all the "SHOULD" statements, but
> > that's only because these checksums are automatically generated by
> > maven-deploy-plugin, and not under our direct control. However, it still
> > follows all the "MUST" statements, so it is still in compliance with the
> > cited policy. Unless we're willing to circumvent standard Maven tooling
> and
> > risk breaking things which depend on the conventions established by this
> > tooling (which, to be clear, I think would be a really terribly bad
> idea),
> > we simply cannot follow all the "SHOULD" statements for the Maven staging
> > area.
> >
> > [1]: https://www.apache.org/dist/accumulo/
> > [2]: https://accumulo.apache.org/downloads/
> > [3]: https://checker.apache.org/dist/unsummed.html
> >
> > On Sat, Apr 14, 2018 at 11:13 PM Mike Drob  wrote:
> >
> > > -0
> > >
> > > please do not publish md5 sums
> > > please add missing sha256 sums
> > >
> > > apache release policy:
> > > http://www.apache.org/dev/release-distribution#sigs-and-sums
> > >
> > > On Sat, Apr 14, 2018 at 11:37 AM, Mike Walch 
> wrote:
> > >
> > > > +1
> > > >
> > > > * Verified sha1 & md5 hashes matched
> > > > * Verified signatures
> > > > * Ran binary tarball locally using Uno
> > > > * Ran 'mvn verify' successfully for wikisearch using RC jars
> > > >
> > > > 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/orgapache
> > > > >
> > > >
> > > accumulo-1070/org/apache/accumulo/accumulo/1.9.0/
> > accumulo-1.9.0-src.tar.gz
> > > > > Binary:
> > > > > https://repository.apache.org/content/repositories/orgapache
> > > > >
> > > >
> > > accumulo-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
> > > > >
> > > >
> > >
> >
>

Re[2]: Welcome Mark Owens (new committer)

[J. Mark Owens]

Thanks everyone! Looking forward to continued contributions to the 
project!



-- Original Message --
From: "Mike Miller" <mmil...@apache.org>
To: dev@accumulo.apache.org
Sent: 3/23/2018 10:56:50 AM
Subject: Re: Welcome Mark Owens (new committer)


Congrats and welcome!

On Thu, Mar 22, 2018 at 10:08 PM, Michael Wall <mjw...@apache.org> 
wrote:



Welcome Mark

On Thu, Mar 22, 2018 at 8:44 PM Michael Hogue 
<michael.p.hogu...@gmail.com

>
wrote:

> Mark,
>
> Congrats and thanks for your contributions!
>
> Mike
> On Thu, Mar 22, 2018 at 17:59 Mike Walch <mwa...@apache.org> wrote:
>
> > Welcome Mark!
> >
> > On Thu, Mar 22, 2018 at 5:52 PM, Christopher <ctubb...@apache.org>
> wrote:
> >
> > > Accumulo devs,
> > >
> > > Please join me in welcoming Mark Owens, one of our newest Apache
> Accumulo
> > > committers (and PMC member)!
> > >
> > > Mark has been contributing many various fixes to bugs throughout
> > Accumulo's
> > > codebase for the past several months. You may recognize him from 
his

> > GitHub
> > > pull requests (https://github.com/jmark99).
> > >
> > > Welcome, Mark!
> > >
> >
>

Re[2]: [VOTE] Accumulo 1.7.4-rc1

[J. Mark Owens]

I know that Christopher has been looking into the KerberosRenewalIT 
failures. Has anyone been having any additional issues with the Kerberos 
IT tests? I have been unsuccessful in getting through any of the four 
Kerberos related ITs.


I've attempted to run each of the four Kerberos-related tests 
individually.


KerberosIT tests fails with all 11 tests timing out after the allotted 5 
minutes per test.

KerberosReplicationIT times out after 180 seconds.
KerberosRenewalIT fails after 540 seconds.
KerberosProxyIT is failing as well.

I've been using the following command for the tests with the appropriate 
Kerberos IT proved for to the -Dit.test= argument.


mvn clean verify -Dtest=NoSuchTestExists -Dit.test=KerberosIT 
-DfailIfNoTests=false


Should I chalk it up to my testing setup not being robust enough to 
handle the tests or has anyone else experienced related failures?




-- Original Message --
From: "Mike Miller" 
To: dev@accumulo.apache.org
Cc: "Josh Elser" 
Sent: 3/20/2018 4:02:32 PM
Subject: Re: [VOTE] Accumulo 1.7.4-rc1


Well, just in case:
Verified sha1, md5 and asc signatures for binary and source tarballs:
gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
gpg:using RSA key 
8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D

gpg: Good signature from "Christopher L Tubbs II (Christopher) <
ctubb...@gmail.com>" [unknown]
gpg: aka "Christopher L Tubbs II (Developer) <
ctubb...@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B  835D 6F0C DAE7 00B6 
899D



On Tue, Mar 20, 2018 at 2:32 PM, Christopher  
wrote:


I'm currently looking at the KerberosRenewalIT failures that seem to 
be

persisting across branches. From the logs, it looks like the accumulo
services are trying to do ticket-cache based login renewals, instead 
of
keytab-based renewals. This has been a problematic test for me before, 
and
as such, I've gotten into the habit of ignoring it, but since I've not 
been
able to get it to work on reruns, and it fails nearly 100% of the time 
(if

not 100%) for me now, I decided to take a closer look. If it is doing
ticket-cache based renewals, that could indicate a bug in the Kerberos
authentication, and that would probably warrant a -1 from me... but I 
will

continue to investigate first.

Josh, you know more about the Kerberos stuff than anyone here, so if 
you
have time/interest, I wouldn't mind getting your feedback on why this 
test

might be failing for me.

On Mon, Mar 19, 2018 at 3:44 PM Christopher  
wrote:


> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.4.
>
> Git Commit:
> b2a59189108d736729432e81b3d5717000c6b891
> Branch:
> 1.7.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> b2a59189108d736729432e81b3d5717000c6b891
>
> Staging repo:
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1068
> Source (official release artifact):
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
4/accumulo-1.7.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
4/accumulo-1.7.4-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.7.4/
>
> 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.7.4 release of Apache Accumulo.
>
> This vote will remain open until at least Thu Mar 22 20:00:00 UTC 
2018

> (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00: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-1068/
> # note the trailing slash is needed
>
>

Re[2]: [VOTE] Switch to GitHub issues

[J. Mark Owens]

+1 (non-binding)

Re[2]: [TEST][VOTE] Accumulo 1.7.4-rc0

[J. Mark Owens]

Mike,
I had that failure as well when running mvn verify. But when I ran the 
IT test by itself it completed successfully. I had several IT tests fail 
 (different ones each run) during the 'mvn verify' runs, but when run in 
isolation they succeeded.


The exception to that was the 
KerberosRenewalIT.testReadAndWriteThroughTicketLifetime test. On my 
local system I could only get that one to succeed if I adjusted the 
TIME_DURATION value slightly. I think from 9 minutes to 11 in my 
particular case. Did you have any issues with that particular test?


mark

-- Original Message --
From: "Mike Miller" 
To: dev@accumulo.apache.org
Sent: 2/26/2018 4:56:24 PM
Subject: Re: [TEST][VOTE] Accumulo 1.7.4-rc0


Results from "mvn clean verify" on my MAC work machine:

[ERROR] Failures:
[ERROR]   TabletStateChangeIteratorIT.test:100 No tables should need
attention expected:<0> but was:<1>
[ERROR] Errors:
[ERROR]   NamespacesIT>AccumuloClusterIT.teardownCluster:223 » 
TestTimedOut

test timed o...
[ERROR]   ChaoticBalancerIT.test:80->Object.wait:502->Object.wait:-2 »
TestTimedOut test...
[ERROR]   KerberosRenewalIT.testReadAndWriteThroughTicketLifetime »
TestTimedOut test ti...

I believe the ones that timed out are known to be finicky but I haven't
seen that failure before.

On Mon, Feb 26, 2018 at 1:56 PM, Keith Turner  wrote:


I found the following while running continuous ingest test.  I can fix
this, unless someone else wants to try.

https://issues.apache.org/jira/browse/ACCUMULO-4832

On Wed, Feb 21, 2018 at 6:10 PM, Christopher  
wrote:

> Accumulo Developers,
>
> The following is a **TEST** release candidate (no need to vote) for
> Accumulo 1.7.4.
> As recently discussed, it's time for a 1.7.4 release. This candidate
> represents my test of the build system as it currently exists. 
Please use

> these artifacts to do any relevant testing.
>
> If there's no activity in the next few days, I'll create an rc1 to 
vote

on.
> I'm also willing to pass off to another release manager if somebody 
feels
> strongly about taking on that task, but I've got my dev environment 
set

up
> for it, so I don't mind.
>
> Git Commit:
> dbeca4335c850750ef90c2086c19527c7d73e729
> Branch:
> 1.7.4-rc0
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4
> dbeca4335c850750ef90c2086c19527c7d73e729
>
> Staging repo:
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1066
> Source (official release artifact):
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1066/org/apache/accumulo/accumulo/1.7.
4/accumulo-1.7.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/
orgapacheaccumulo-1066/org/apache/accumulo/accumulo/1.7.
4/accumulo-1.7.4-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://github.com/apache/accumulo-website/pull/58
>
> 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.7.4 release of Apache Accumulo.
>
> This vote will remain open until at least Sat Feb 24 23:30:00 UTC 
2018

> (Sat Feb 24 18:30:00 EST 2018 / Sat Feb 24 15:30:00 PST 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-1066/
> # note the trailing slash is needed

Re: [DISCUSS] Proposed formatter change: 100 char lines

[J. Mark Owens]

I would be in favor of this change. As my eyes continue to get weaker, I 
have to use larger fonts resulting in a lot of the code being off the 
screen. The constant need to scroll horizontally can get irritating.



-- Original Message --
From: "Christopher" 
To: "accumulo-dev" 
Sent: 2/15/2018 11:24:31 PM
Subject: [DISCUSS] Proposed formatter change: 100 char lines

Primarily for accessibility reasons (screen space with a comfortable 
font),
but also to support readability for devs working on sensibly-sized 
screens,
I want to change our formatter to format with 100 char line length 
instead

of its current 160.

Many of our files need to be reformatted anyway, because the current
formatter is configured incorrectly for Java 8 lambda syntax and needs 
to

be fixed, so this might be a good opportunity to make the switch.

Also, at this point I think it is sensible to require Java 8 to build
Accumulo... even when building older branches. (Accumulo 1.x will still
support running on Java 7, of course, but Java 8 would be required to 
build

it). The reason for this requirement is that in order to reduce merge
conflicts and merge bugs between branches, I'd like to update the
formatting across all branches, but the formatter which supports this
syntax requires Java 8 to run. The alternative to requiring Java 8 
would be
to only run the formatter when building with Java 8... and skip 
formatting

if building with Java 7, which might result in some unformatted
contributions, depending on the JRE version used to build.

Broken test

[J. Mark Owens]

I cloned the latest version of Accumulo a couple of hours ago and 
attempted to build it along with running the standard test suite, i.e., 
mvn clean package -Passemble.  The build failed due to an error in the 
TableLoadBalancerTest class:


Failed tests:
  TableLoadBalancerTest.test:188 expected:<15> but was:<0>

I performed a git checkout of commit 
3c55eed2198afc90d6c1230783fcdd64e4c7e47d and ran the tests successfully. 
But the next commit, 4879f52f0334ca1c52b613d297cd3c7fd4c19afa, failed.  
Anyone willing to verify this is not just some glitch with my setup?


thanks
mark

Re[2]: review board

[J. Mark Owens]

Thanks for the info.
mark

-- Original Message --
From: "Josh Elser" <josh.el...@gmail.com>
To: dev@accumulo.apache.org
Sent: 11/1/2017 12:38:16 PM
Subject: Re: review board


Hey Mark,

Yup, we're still a CTR project. That should be captured on the website 
on our governance page and would require a VOTE by the PMC to change.


We don't have any enforced means of mechanism to perform reviews. We 
used to use Reviewboard a bit, but, as of late, more happens on Github 
with the better integration that Infra has provided. For example, 
you'll find that some projects expressly state certain systems as the 
ones that must be used for code-review. It's not been an issue in 
Accumulo.


Re: CTR in practice, we do still have a bit of review happening before 
commit -- it's up to the discretion of the committer. If it's not a 
trivial change, you'll likely see the committer waiting for someone 
else to take a look before pushing it. Low-volume and decent test 
coverage helps make this a tenable process.


On 11/1/17 12:28 PM, J. Mark Owens wrote:

Hi,

I'm going through a lot of the Accumulo documentation as I look at 
ACCUMULO-4714 and had a question about some of the information.


Is the review board documentation page still up to date and accurate? 
I clicked the instance link  (https://reviews.apache.org/ ) and 
noticed that the last entry for Accumulo is over a year old. Is this 
something that is still actively utilized or should the information be 
revised in some manner? Is Accumulo still using a Commit-Then-Review 
policy, etc?


Thanks,
Mark

review board

[J. Mark Owens]

Hi,

I'm going through a lot of the Accumulo documentation as I look at 
ACCUMULO-4714 and had a question about some of the information.


Is the review board documentation page still up to date and accurate? I 
clicked the instance link  (https://reviews.apache.org/ ) and noticed 
that the last entry for Accumulo is over a year old. Is this something 
that is still actively utilized or should the information be revised in 
some manner? Is Accumulo still using a Commit-Then-Review policy, etc?


Thanks,
Mark

Jekyll issues

[J. Mark Owens]

Hi,
I recently updated the documentation for the user manual in the 
accumulo-website repo. I was attempting to verify the changes using the 
instructions at https://accumulo.apache.org/contributor/source.  But I'm 
having some issue getting things to work correctly. When running the 
command:


$ jekyll serve --safe

I'm getting the following error:

Configuration file: /home/mark/dev/accumulo-website/_config.yml
jekyll 3.1.6 | Error:  undefined method `config=' for 
#

Did you mean?  config

I'm not sure  exactly sure what it is referring to since I can't find a 
reference to config withing the supplied configuration file _config.yml.


Any suggestions?

Thanks,
Mark

ACCUMULO-4561

[J. Mark Owens]

Hi,

I added a comment on the behavior documented in ACCUMULO-4561.  I was 
hoping someone could take a look and offer comments and/or suggestions 
on how work on this ticket should proceed.


Thanks,
Mark

Re[2]: apache/accumulo-testing compile errors

[J. Mark Owens]

Thanks Mike,

That worked for now.  Is there a ticket to add the changes from 
ACCUMULO-3239 into the testing repo?




-- Original Message --
From: "Mike Miller" <mmil...@apache.org>
To: "dev@accumulo.apache.org" <dev@accumulo.apache.org>
Sent: 10/5/2017 10:58:15 AM
Subject: Re: apache/accumulo-testing compile errors


For now you can change the  in the pom to 1.8.1 and
everything should work OK.  Since we split testing out into its own 
repo,

there has only been one version, master, and I didn't apply the same
changes from ACCUMULO-3238
<https://issues.apache.org/jira/browse/ACCUMULO-3238> to the testing 
repo.

Unfortunately, it is easy to miss changes like this now that we have a
bunch of separate repos (testing, examples).  We could create multiple
branches in accumulo-testing that compile against different versions 
but

that seems like a lot of extra work.

On Thu, Oct 5, 2017 at 10:23 AM, Mike Miller <michaelpmil...@gmail.com>
wrote:

Hey Mark - I added the Table.ID stuff in master so you shouldn't be 
seeing
any in 1.8.  Check what version it is compiling against in the pom.  I 
will
take a look at the testing repo to make sure there wasn't anything I 
missed.


On Thu, Oct 5, 2017 at 9:28 AM, J. Mark Owens <jmark...@gmail.com> 
wrote:



Hi,

I cloned the apache/accumulo-testing repo this morning. When 
attempting to

run some of the tests I ran into compilation errors. Are there known
issues
with compiling the accumulo-tests straight from the repo? I'm using
version
1.8 of Java.

A sample of the output is included below:

[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/continuous/UndefinedAnaly
zer.java:[304,70]
incompatible types: org.apache.accumulo.core.client.impl.Table.ID can
not be converted to
java.lang.String
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[76,120]
incompatible types: java.lang.String cannot be converted to
org.apache.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[147,122]
incompatible types: java.lang.String cannot be converted to org.apach
e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[209,58]
cannot find symbol
[ERROR]   symbol:   method
getDefaultConfiguration()
[ERROR]   location: class
org.apache.accumulo.core.conf.AccumuloConfiguration
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[223,116]
incompatible types: java.lang.String cannot be converted to
org.apache.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[237,113]
incompatible types: java.lang.String cannot be converted to org.apach
e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[242,112]
incompatible types: java.lang.String cannot be converted to org.apach
e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/ingest/TestIngest.java:[222,56]
cannot find symbol
[ERROR]   symbol:   method
getDefaultConfiguration()

[ERROR]   location: class
org.apache.accumulo.core.conf.AccumuloConfiguration
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
AlterTablePerm.java:[80,53]
incompatible types: java.lang.String cannot be converted to org.
apache.accumulo.core.client.impl.Table.ID

[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
WalkingSecurity.java:[59,8]
org.apache.accumulo.testing.core.randomwalk.security.WalkingSecu
rity is not abstract and does not override abstract method
cleanNamespacePermissions(org.apache.accumulo.core.client.im
pl.Namespace.ID)
in org.apache.accumulo.server.security.handler.PermissionHandler
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
WalkingSecurity.java:[86,11]
no suitable constructor found for AccumuloServerContext(org.apa
che.accumulo.server.conf.ServerConfigurationFactory)
[ERROR] constructor
org.apache.accumulo.server.AccumuloServerContext.AccumuloSer
verContext(org.apache.accumulo.core.client.Instance,
org.apache.accumulo.server.conf.ServerConfigurationFactory)
is not applicab
le
[ERROR]   (actual and formal argument lists differ in length)
[ERROR] constructor
org.apache.accumulo.s

Re[3]: apache/accumulo-testing compile errors

[J. Mark Owens]

Correction - Is there a ticket to add the changes from ACCUMULO-3238 
(not 3239) into the testing repo?


-- Original Message --
From: "J. Mark Owens" <jmark...@gmail.com>
To: dev@accumulo.apache.org
Sent: 10/5/2017 11:06:47 AM
Subject: Re[2]: apache/accumulo-testing compile errors


Thanks Mike,

That worked for now.  Is there a ticket to add the changes from 
ACCUMULO-3239 into the testing repo?




-- Original Message --
From: "Mike Miller" <mmil...@apache.org>
To: "dev@accumulo.apache.org" <dev@accumulo.apache.org>
Sent: 10/5/2017 10:58:15 AM
Subject: Re: apache/accumulo-testing compile errors


For now you can change the  in the pom to 1.8.1 and
everything should work OK.  Since we split testing out into its own 
repo,

there has only been one version, master, and I didn't apply the same
changes from ACCUMULO-3238
<https://issues.apache.org/jira/browse/ACCUMULO-3238> to the testing 
repo.

Unfortunately, it is easy to miss changes like this now that we have a
bunch of separate repos (testing, examples).  We could create multiple
branches in accumulo-testing that compile against different versions 
but

that seems like a lot of extra work.

On Thu, Oct 5, 2017 at 10:23 AM, Mike Miller 
<michaelpmil...@gmail.com>

wrote:

Hey Mark - I added the Table.ID stuff in master so you shouldn't be 
seeing
any in 1.8.  Check what version it is compiling against in the pom.  
I will
take a look at the testing repo to make sure there wasn't anything I 
missed.


On Thu, Oct 5, 2017 at 9:28 AM, J. Mark Owens <jmark...@gmail.com> 
wrote:



Hi,

I cloned the apache/accumulo-testing repo this morning. When 
attempting to

run some of the tests I ran into compilation errors. Are there known
issues
with compiling the accumulo-tests straight from the repo? I'm using
version
1.8 of Java.

A sample of the output is included below:

[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/continuous/UndefinedAnaly
zer.java:[304,70]
incompatible types: org.apache.accumulo.core.client.impl.Table.ID 
can

not be converted to
java.lang.String
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[76,120]
incompatible types: java.lang.String cannot be converted to
org.apache.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[147,122]
incompatible types: java.lang.String cannot be converted to 
org.apach

e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[209,58]
cannot find symbol
[ERROR]   symbol:   method
getDefaultConfiguration()
[ERROR]   location: class
org.apache.accumulo.core.conf.AccumuloConfiguration
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[223,116]
incompatible types: java.lang.String cannot be converted to
org.apache.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[237,113]
incompatible types: java.lang.String cannot be converted to 
org.apach

e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
TableOp.java:[242,112]
incompatible types: java.lang.String cannot be converted to 
org.apach

e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/ingest/TestIngest.java:[222,56]
cannot find symbol
[ERROR]   symbol:   method
getDefaultConfiguration()

[ERROR]   location: class
org.apache.accumulo.core.conf.AccumuloConfiguration
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
AlterTablePerm.java:[80,53]
incompatible types: java.lang.String cannot be converted to org.
apache.accumulo.core.client.impl.Table.ID

[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
WalkingSecurity.java:[59,8]
org.apache.accumulo.testing.core.randomwalk.security.WalkingSecu
rity is not abstract and does not override abstract method
cleanNamespacePermissions(org.apache.accumulo.core.client.im
pl.Namespace.ID)
in org.apache.accumulo.server.security.handler.PermissionHandler
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/
org/apache/accumulo/testing/core/randomwalk/security/
WalkingSecurity.java:[86,11]
no suitable constructor found for AccumuloServerContext(org.apa
che.accumulo.server.conf.ServerConfigurationFactory)
[ERROR] constructor
org.a

apache/accumulo-testing compile errors

[J. Mark Owens]

Hi,

I cloned the apache/accumulo-testing repo this morning. When attempting to
run some of the tests I ran into compilation errors. Are there known issues
with compiling the accumulo-tests straight from the repo? I'm using version
1.8 of Java.

A sample of the output is included below:

[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/continuous/UndefinedAnalyzer.java:[304,70]
incompatible types: org.apache.accumulo.core.client.impl.Table.ID can
not be converted to
java.lang.String
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/TableOp.java:[76,120]
incompatible types: java.lang.String cannot be converted to
org.apache.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/TableOp.java:[147,122]
incompatible types: java.lang.String cannot be converted to org.apach
e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/TableOp.java:[209,58]
cannot find symbol
[ERROR]   symbol:   method
getDefaultConfiguration()
[ERROR]   location: class
org.apache.accumulo.core.conf.AccumuloConfiguration
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/TableOp.java:[223,116]
incompatible types: java.lang.String cannot be converted to
org.apache.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/TableOp.java:[237,113]
incompatible types: java.lang.String cannot be converted to org.apach
e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/TableOp.java:[242,112]
incompatible types: java.lang.String cannot be converted to org.apach
e.accumulo.core.client.impl.Table.ID
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/ingest/TestIngest.java:[222,56]
cannot find symbol
[ERROR]   symbol:   method
getDefaultConfiguration()

[ERROR]   location: class
org.apache.accumulo.core.conf.AccumuloConfiguration
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/AlterTablePerm.java:[80,53]
incompatible types: java.lang.String cannot be converted to org.
apache.accumulo.core.client.impl.Table.ID

[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/WalkingSecurity.java:[59,8]
org.apache.accumulo.testing.core.randomwalk.security.WalkingSecu
rity is not abstract and does not override abstract method
cleanNamespacePermissions(org.apache.accumulo.core.client.impl.Namespace.ID)
in org.apache.accumulo.server.security.handler.PermissionHandler
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/WalkingSecurity.java:[86,11]
no suitable constructor found for AccumuloServerContext(org.apa
che.accumulo.server.conf.ServerConfigurationFactory)
[ERROR] constructor
org.apache.accumulo.server.AccumuloServerContext.AccumuloServerContext(org.apache.accumulo.core.client.Instance,org.apache.accumulo.server.conf.ServerConfigurationFactory)
is not applicab
le
[ERROR]   (actual and formal argument lists differ in length)
[ERROR] constructor
org.apache.accumulo.server.AccumuloServerContext.AccumuloServerContext(org.apache.accumulo.core.client.Instance,org.apache.accumulo.server.conf.ServerConfigurationFactory,org.apache.accum
ulo.server.security.delegation.AuthenticationTokenSecretManager) is not
applicable
[ERROR]   (actual and formal argument lists differ in length)
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/WalkingSecurity.java:[219,3]
method does not override or implement a method from a supertype
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/WalkingSecurity.java:[225,3]
method does not override or implement a method from a supertype
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/WalkingSecurity.java:[265,3]
method does not override or implement a method from a supertype
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/WalkingSecurity.java:[280,3]
method does not override or implement a method from a supertype
[ERROR]
/home/mark/dev/apache-accumulo-testing/core/src/main/java/org/apache/accumulo/testing/core/randomwalk/security/WalkingSecurity.java:[296,3]
method does not override or implement a method from a supertype
[ERROR]

Re[2]: Assign myself to work ACCUMULO-2907

[J. Mark Owens]

jmark99


-- Original Message --
From: "Mike Drob" <md...@apache.org>
To: "Accumulo Dev List" <dev@accumulo.apache.org>
Sent: 9/18/2017 4:33:10 PM
Subject: Re: Assign myself to work ACCUMULO-2907


What is your apache jira id?

On Mon, Sep 18, 2017 at 3:29 PM, J. Mark Owens <jmark...@gmail.com> 
wrote:



Hi Mike,

I have an Apache Jira account.  But the Accumulo issues page is not
displaying the 'Assign to me" option underneath the 'Unassigned'  area 
on
the right.  Whereas on the Apache NiFi project page that option 
appeared

after someone granted me access to the project.
thanks,
mark


On Mon, Sep 18, 2017 at 4:23 PM, Mike Walch <mwa...@apache.org> wrote:

> Have created a Apache Jira account yet?  Below is the url where you 
can

> setup an account.
>
> https://issues.apache.org/jira/login.jsp
>
> The Accumulo Jira is a project under Apache Jira.  Anyone can create 
an
> account on Apache Jira.  After you create an account, you should be 
able

to
> assign yourself to an Accumulo issue.  If not, email the list again
someone
> can enable access.
>
> On Mon, Sep 18, 2017 at 4:14 PM J. Mark Owens <jmark...@gmail.com>
wrote:
>
> > Hi,
> >
> > I'd like to assign myself to work on ACCUMULO-2907
> > <https://issues.apache.org/jira/browse/ACCUMULO-2907>.
> >
> > Could I be granted access to Accumulo Jira in order to assign the
ticket
> > to myself?
> >
> > Thanks,
> > Mark Owens
>

Re: Assign myself to work ACCUMULO-2907

[J. Mark Owens]

Hi Mike,

I have an Apache Jira account.  But the Accumulo issues page is not
displaying the 'Assign to me" option underneath the 'Unassigned'  area on
the right.  Whereas on the Apache NiFi project page that option appeared
after someone granted me access to the project.
thanks,
mark


On Mon, Sep 18, 2017 at 4:23 PM, Mike Walch <mwa...@apache.org> wrote:

> Have created a Apache Jira account yet?  Below is the url where you can
> setup an account.
>
> https://issues.apache.org/jira/login.jsp
>
> The Accumulo Jira is a project under Apache Jira.  Anyone can create an
> account on Apache Jira.  After you create an account, you should be able to
> assign yourself to an Accumulo issue.  If not, email the list again someone
> can enable access.
>
> On Mon, Sep 18, 2017 at 4:14 PM J. Mark Owens <jmark...@gmail.com> wrote:
>
> > Hi,
> >
> > I'd like to assign myself to work on ACCUMULO-2907
> > <https://issues.apache.org/jira/browse/ACCUMULO-2907>.
> >
> > Could I be granted access to Accumulo Jira in order to assign the ticket
> > to myself?
> >
> > Thanks,
> > Mark Owens
>

Assign myself to work ACCUMULO-2907

[J. Mark Owens]

Hi,

I'd like to assign myself to work on ACCUMULO-2907 
<https://issues.apache.org/jira/browse/ACCUMULO-2907>.


Could I be granted access to Accumulo Jira in order to assign the ticket 
to myself?


Thanks,
Mark Owens