I agree with Dave that it could be moved out of Other and into the
Project activity and Releases sections. But I don't know that it
matters much.
On Fri, Apr 5, 2024 at 4:21 PM Daniel Roberts wrote:
>
> Report looks good!
>
> On Fri, Apr 5, 2024 at 3:41 PM Dave Marion wrote:
>
> > I'm fine with
LGTM
On Tue, Apr 2, 2024 at 11:09 AM Ed Coleman wrote:
>
> Thanks - I incorporated the suggestions.
>
> On 2024/04/02 14:57:56 Mark Owens wrote:
> > LGTM
> >
> > I have two small grammatical suggestions you can consider if you'd like.
> >
> > > The difference between committers and PMC members
wrote:
> Christopher,
>
> Regarding your issues, notes, etc.:
>
> 1. IIRC versions 1 and 2 were not built correctly and I did not restart
> the numbering for the first good build.
> 2. The build script gave me the option of where to put the branches and I
> wasn't sure
ran the example and both benchmarks using the instructions in the readme
>
>
>
> On Fri, Feb 16, 2024 at 7:53 AM Dave Marion wrote:
>
> > Christopher,
> >
> > Regarding your issues, notes, etc.:
> >
> > 1. IIRC versions 1 and 2 were not built corre
+1, I verified:
* source-release artifact content matches contents of git checkout at the
commit that will be tagged
* signatures match and are signed by the key with the specified fingerprint
* nexus-generated md5 and sha1 hashes exist in the staging repo and match
the artifacts
* the jar, the
On Mon, Jan 15, 2024 at 2:18 AM Christofer Dutz
wrote:
>
> Hi Christopher,
>
> I do understand that some of the things Apache requires from its projects may
> seem obsolete and outdated.
I hope I didn't give the impression that that's what I think. I know
it's a common sentiment
ger relies on it.
Kind regards,
Christopher
On Sun, Jan 14, 2024, 10:14 Christofer Dutz wrote:
> Hi all,
>
> while reviewing the project's activity as part of me preparing for the
> upcoming board meeting, i noticed that in the last vote thread, there were
> only simple +1 votes and
LGTM as well
On Fri, Jan 5, 2024 at 10:45 AM Christopher wrote:
> Looks good to me.
>
> On Fri, Jan 5, 2024 at 10:43 AM Dave Marion wrote:
> >
> > Looks good Ed. Thanks!
> >
> > On Fri, Jan 5, 2024 at 10:20 AM dev1 wrote:
> >
> > >
>
Looks good to me.
On Fri, Jan 5, 2024 at 10:43 AM Dave Marion wrote:
>
> Looks good Ed. Thanks!
>
> On Fri, Jan 5, 2024 at 10:20 AM dev1 wrote:
>
> >
> >
> > The Accumulo community decided to draft the Apache community reports on
> > the Accumulo dev list – and this is a draft of the January
The following is the draft of the announcement for 1.10.4
***
The Apache Accumulo project is pleased to announce the release of
Apache Accumulo 1.10.4! Apache Accumulo 1.10.4 is the final bug fix
release of the 1.10 LTM release line. After this release, the 1.10
release line will be considered
This vote passes with 6 +1s and no other votes.
Thanks all.
The post-vote release steps are being tracked at:
https://github.com/apache/accumulo/issues/3947
On Thu, Nov 16, 2023 at 3:59 PM Christopher wrote:
>
> I offer my +1 as well.
> I checked the signatures and and checksums, and
1
>
> 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:
> > 47ac68d1
gt;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)
> >
>
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
On Sat, Oct 14, 2023 at 9:41 AM Vincent Russell
wrote:
>
> Christopher,
>
> I don't remember configuring anything with regards to commons-vfs. How do
> I disable this?
There's some VFS stuff enabled by default, for backwards
compatibility. There isn't an explicit way to disable
I think a performance hit is expected, due to the expected overhead of the
TLS handshake, and the number of connections Accumulo requires in order to
distribute work across a cluster. I think whether the overhead is tolerable
is a per user decision, and may also be dependent upon the details of
if the manager is actually running. If that
doesn't happen eventually, I'm not sure what could be happening
without further troubleshooting.
On Thu, Oct 12, 2023 at 12:36 PM Vincent Russell
wrote:
>
> Christopher,
>
> I have run through an upgrade with a bit more data than I di
t 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 "Mode
tHub activity are 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 i
I wouldn't describe the ongoing activity as "moderate". It seems
pretty busy, at least as busy as ever, anyway. Maybe that's what you
meant, but it feels like the word "moderate" carries the connotation
of "mediocre" to me. I think we've been pretty active addressing the
2.1 issues. Not everything
se another monitor was running, though. I would expect the
2.1 behavior you described over that 2.0 behavior.
On Mon, Sep 25, 2023 at 11:59 AM Vincent Russell
wrote:
>
> Thank you Christopher,
>
> I did neglect to update the log4j2 files.
>
> One thing that is weird is that
properties or environment variables
that control log4j.
On Tue, Sep 12, 2023 at 8:10 PM Vincent Russell
wrote:
>
> Thank you Christopher,
>
> Don't worry. I definitely planned on testing an upgrade on a test
> cluster. :)
>
> I just upgraded a test cluster and ever
I'm not 100% certain about the name, but a new repo is a really low risk
thing. I say go for it.
On Thu, Sep 7, 2023, 08:54 Marc P. wrote:
> Out of curiosity, what is the benefit of having a new repo over a release
> target of accumulo-visibility ?
>
> I've used VisibilityEvaluator on non
insight, having probably seen it before.
On Wed, Aug 30, 2023 at 4:50 PM Vincent Russell
wrote:
>
> Thank you Christopher.
>
> Does there exist some documentation for upgrading zookeeper from 3.4.14 to
> 3.8.1? Is there a preferred upgrade path?
>
> Also...Is there any
The correct link seems to be
https://accumulo.apache.org/docs/2.x/troubleshooting/zookeeper#zookeeper-acls
It looks like both `bin/accumulo dump-zoo` and `bin/accumulo-util
dump-zoo` will do the same thing. It was originally a disconnected
utility that existed for convenience, but was
See below for the draft consolidated release announcement for 2.1.2
and 3.0.0. I intend to send this out on Tuesday evening to the apache
announce list and our own user list, but am presenting it here for
review while I polish up the release notes.
***
The Apache Accumulo project is pleased to
This vote passes with 6 +1s and no other votes.
The post-vote release tasks are tracked at
https://github.com/apache/accumulo/issues/3713
On Mon, Aug 21, 2023 at 4:53 PM Christopher wrote:
>
> +1
>
> I checked:
>
> * signatures, hashes
> * full ITs
> * bin tarball's lib
This vote passes with 6 +1s and no other votes.
The post-vote release tasks are tracked at
https://github.com/apache/accumulo/issues/3714
On Mon, Aug 21, 2023 at 4:54 PM Christopher wrote:
>
> +1
>
> I checked:
>
> * signatures, hashes
> * full ITs
> * bin tarball's lib
built from tar with no errors
> * ran all tests and ITs (only failure was the known
> flaky MemoryStarvedScanIT)
>
> On Mon, Aug 14, 2023 at 4:18 AM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candida
gt; * verified psunny passes successfully
>
> On Mon, Aug 14, 2023 at 4:08 AM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 2.1.2.
> >
> > Git Commit:
> > ee7ae63a823477b557aa9415a
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: M
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
&
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 \
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 \
Congrats Dan!
On Thu, Aug 10, 2023 at 12:08 AM Christopher wrote:
> Welcome Dan, and congrats
>
> On Wed, Aug 9, 2023, 18:27 dev1 wrote:
>
> > The Project Management Committee (PMC) for Apache Accumulo has invited
> Dan
> > Roberts to become a committer / PM
Welcome Dan, and congrats
On Wed, Aug 9, 2023, 18:27 dev1 wrote:
> The Project Management Committee (PMC) for Apache Accumulo has invited Dan
> Roberts to become a committer / PMC member and we are pleased to announce
> that they have accepted.
>
> Being a committer enables easier contribution
Accumulo Developers,
***
NOTE: This is just a TEST release candidate to verify the release
process, and to establish a milestone as a baseline for testing. There
is no need to actually vote, because this is not a real vote.
***
Please consider the following candidate for Apache Accumulo 3.0.0.
Thanks all.
This vote passes with 8 "+1" and no other votes.
I will work on the post-vote tasks, which I'm tracking at
https://github.com/apache/accumulo/issues/3507
On Mon, Jun 19, 2023, 10:43 Christopher wrote:
> +1
>
> Verified:
> * Hashes/sigs
> * Full ITs (som
t 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
sha512) match expected
> > Sunny tests passed with no failures.
> >
> > Ed Coleman
> >
> > From: Christopher
> > Date: Wednesday, June 14, 2023 at 1:49 AM
> > To: accumulo-dev
> > Subject: [VOTE] Apache Accumulo 2.1.1-rc2
> > Accumulo Develope
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
Given the building consensus around #3491, and the fact that a patch
is already merged in, I will withdraw this vote, and cut an RC2 soon
with the updates.
On Tue, Jun 13, 2023 at 7:33 PM Adam Lerman wrote:
>
> -1 because of #3491
>
> On Mon, Jun 12, 2023 at 8:06 PM Christ
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.1.
Git Commit:
4937a2739f2a9f27e99bd6105cad644a9b868e8b
Branch:
2.1.1-rc1
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 \
:
>
> > 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 ann
t; wrote:
>
> > Ok.. Thank you for the update.
> >
> > On Fri, Dec 30, 2022 at 11:55 AM Christopher wrote:
> >
> >> For reference, here's the PR working on the fix for 2.1.1:
> >> https://github.com/apache/accumulo/pull/3134
> >>
> >> On Fri, Dec
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
hat do you think about
having the Docker build as an option for local staging? Would that be
enough for you to get on board with removing the mandatory staging
site step?
On Thu, Apr 20, 2023 at 12:01 AM Christopher wrote:
>
> I reviewed your PR. It includes changes that are likely to b
is what my original goal was in streamlining this. I'm
okay with having a Dockerfile... but the other changes are probably
going to cause more problems for us in the short term than they solve.
On Mon, Apr 17, 2023 at 6:11 PM Daniel Roberts wrote:
>
> Christopher,
>
> I added a conta
.
On Mon, Apr 17, 2023 at 1:33 PM Daniel Roberts wrote:
>
> Christopher,
>
> In your breakdown of my proposal, I think there's a miscommunication in
> regard to the number of build steps and branches needed to maintain.
>
> Looking back I should have used descriptors like Branc
This vote passes with:
5 +1s, and no other votes
I will track the release tasks on https://github.com/apache/accumulo/issues/3295
On Wed, Apr 12, 2023 at 1:44 PM Christopher wrote:
>
> +1 to this release
>
> I checked:
>
> * Hashes/signatures
> * Source and javado
the git tree. I wonder if this is a change in the
apache-source-release-assembly-descriptor that is executed in the
parent POM, or if it's a change in the default behavior of
maven-assembly-plugin. I'm not sure.
On Wed, Apr 12, 2023 at 12:58 PM Christopher wrote:
>
> https://github.com/
:
>
> Thanks Christopher for setting me straight. This information did enable the
> build to move beyond the CredentialProviderFactoryShimTest. I'm unable to
> get past MiniAccumuloClusterTest though. Two tests timeout for me every
> time even when increasing the timeout factor (th
, 2023 at 9:56 AM Dave Marion wrote:
>
> Christopher,
>
> IIRC the local build is likely sufficient. It may have been that I failed
> to use it in all cases. I do remember in the past merging some PR's then
> noticing on the staging site that the links or formatting were no
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.s
t
> > >>>
> >
> org.apache.accumulo.core.conf.CredentialProviderFactoryShimTest.extractFromHdfs(CredentialProviderFactoryShimTest.java:185)
> > >>> Caused by: java.lang.ClassNotFoundException:
> > >>> org.apache.commons.beanutils.BeanIntrospector
&
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:
> 733863638d85d0109d217da7ea5f36f
emember to be more careful. There is a way to deploy locally IIRC, I'll
> just have to use that.
>
> On Fri, Apr 7, 2023 at 6:34 PM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > +1 to make the change. I agree that when PRs are merged we g
f the QA build
> step? Or maybe a manual build step being triggered?
> I could see the latter being useful if multiple PRs were open at the same
> time to avoid artifact publishing collisions.
>
> On Fri, Apr 7, 2023 at 6:34 PM Christopher Shannon <
> christopher.l.shan...@gmail.c
:49 PM Christopher wrote:
> Hi Accumulo Devs,
>
> When I first set up the automation using .asf.yaml for Jekyll builds
> to go to the asf-staging branch, I expected us to get a bit more use
> out of the staging site at https://accumulo.staged.apache.org/
> However, tha
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 \
.
Any thoughts or opinions on this? I'm leaning slightly towards
streamlining this.
Regards,
Christopher
nd customizable server-side processing.
> >
> > ## Issues:
> > There are no issues requiring board attention.
> >
> > ## Membership Data:
> > Apache Accumulo was founded 2012-03-21 (11 years ago)
> > There are currently 41 committers and 39 PMC members in this proj
t
> 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!
> >
pl.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.l
thSpec(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:
> > >
> > >> Mi
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
> > w
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 sign
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:
sues requiring board attention.
>
> ## Membership Data:
> Apache Accumulo was founded 2012-03-21 (11 years ago)
> There are currently 41 committers and 39 PMC members in this project.
> The Committer-to-PMC ratio is roughly 6:5.
>
> Community changes, past quarter:
>
the risks, try it on a test environment first.
On Thu, Mar 30, 2023, 20:55 Christopher wrote:
> Accumulo doesn't use AVRO directly, so it shouldn't affect Accumulo if you
> upgrade it for Hadoop.
>
> On Thu, Mar 30, 2023, 14:56 Logan Jones wrote:
>
>> Hello:
>>
>&g
Accumulo doesn't use AVRO directly, so it shouldn't affect Accumulo if you
upgrade it for Hadoop.
On Thu, Mar 30, 2023, 14:56 Logan Jones wrote:
> Hello:
>
> Hadoop 3.3.4 has some critical vulnerabilities that it pulls in from avro
> 1.7.7 -> jackson-mapper-asl 1.9.13
>
> The only thing in my
when a TabletServer is low on memory it
> doesn't call the specified TabletUnloader, it just unloads a Tablet.
>
> [1]
> https://github.com/apache/accumulo/blob/elasticity/core/src/main/java/org/apache/accumulo/core/spi/ondemand/OnDemandTabletUnloader.java
> [2]
> https:
I think we should deprecate support for offline table scanning, since
it shouldn't be needed with the availability of ScanServers. Any
MapReduce that previously relied on scanning offline tables could be
made to use that instead.
I agree there is a need to have an immutable table state, for which
gt; with tables in the on demand state. The reason to not modify an offline
> table is the export case, where the table needs to be immutable until the
> files are copied.
>
> On Thu, Mar 23, 2023, 6:58 PM Christopher wrote:
>
>> What do you mean by "when not used in this manner"?
What do you mean by "when not used in this manner"? What other way is
there to use that feature? Do you mean simply never being brought
online?
Would it be possible to support (external) compactions for an offline table?
I feel like that's a pretty useful feature to revert, and would want
to
to the website. I still think that Confluence is a better option
> regarding comments and discussion, hopefully infra can figure that out.
>
> On Thu, Mar 16, 2023 at 7:51 AM Christopher wrote:
>
> > Isn't that basically the same as how the website repo works? How would
> > t
.
>
> Ref: https://nimblehq.co/blog/create-github-wiki-pull-request and
> https://stackoverflow.com/questions/10642928/how-can-i-make-a-pull-request-for-a-wiki-page-on-github
>
> On Wed, Mar 15, 2023 at 2:16 PM Christopher wrote:
>
> > It seems like there's a majority co
It seems like there's a majority consensus of those engaged. No need for a
vote, but I think the question about notifications should be addressed
first.
On Wed, Mar 15, 2023, 13:47 Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> I'm +1 to using some kind of wiki so if
fed into, or
> originated on the mailing lists.
>
> As a side question, if there is a lengthy discussion on a GH issue, is it
> standard practice to just recap that in a mailing list message?
> Or is there a more "formal" inclusion process to follow?
>
>
> On Wed, Mar 15, 2023 a
> On Wed, Mar 15, 2023 at 1:39 PM Christopher wrote:
>
> > I don't think the workflow I proposed about using PRs and discussion on
> > tickets, etc. and the accompanying arguments about keeping things
> > consolidated and accessible to potential contributors not participating
> o
; >> Right, I was just curious if there was any follow-up as I think Ed
> > >> said that it was going to be discussed by the INFRA team yesterday.
> > >> There is at least one other recent ticket (
> > >> https://issues.apache.org/jira/browse/INFRA-24216) where s
You can track that issue at https://issues.apache.org/jira/browse/INFRA-24291
On Fri, Mar 3, 2023 at 10:31 AM Dave Marion wrote:
>
> Ed,
>
> Any update from INFRA on being able to create confluence pages?
>
> On Thu, Mar 2, 2023 at 4:07 PM Christopher wrote:
>
>
ence accounts (see https://issues.apache.org/jira/browse/INFRA-7058),
> so if a non-committer wanted to participate they could.
>
> On Thu, Mar 2, 2023 at 2:53 PM Christopher wrote:
>
> > On Thu, Mar 2, 2023 at 1:34 PM Dave Marion wrote:
> > >
> > > I'm opp
external". The website, with its own issue
tracker, the ability to render markdown, do reviews, and
collaboratively edit, seems like the ideal place to me. We've used it
before for the same purpose, and I think we should continue to do so.
>
> On Thu, Mar 2, 2023 at 12:56 PM Christo
le at
> > > https://accumulo.staged.apache.org/, but human intervention is
> > > required to publish it at https://accumulo.apache.org/).
> > > >
> > > > I looked in the INFRA issues and other projects are using the GH
> > > > Wiki
> >
You would need to upgrade both.
On Sat, Feb 25, 2023, 07:08 Logan Jones wrote:
> Christopher,
>
> Understood. For an Accumulo upgrade, do I need to upgrade clients and
> servers simultaneously? Or are the 1.10 clients compatible with 2.1
> servers?
>
> -Logan
>
> On S
the GitHub project settings to lock the GitHub
> wiki down so that only committers can modify it. If GitHub Wiki is not
> acceptable, then I think Apache Confluence (https://cwiki.apache.org) might
> be an acceptable alternative.
>
> -Original Message-
> From: Christ
Thrift makes a lot of breaking changes between releases. It is not a simple
operation to bump it. We have already made the change to do it and included
updates in 2.0 and 2.1. 1.10 is the legacy version that is to remain stable
until it is EOL in November. If libthrift bugs are a concern to you, I
I don't recall a discussion about this change, but I think it goes against
previous efforts to make the website the one canonical location for our
documentation. I don't even think infra is backing up wiki repos, so there
wouldn't even be a record of the wiki contents in ASF spaces (vs. the main
rom the command-line, and not using the
GitHub UI.
Thanks,
Christopher
On Mon, Jan 23, 2023 at 1:48 PM dev1 wrote:
>
> The 2.1 branch on Accumulo GiHub repo was inadvertently deleted (Friday 1/20)
> and then was restored Sat (1/21). The activity occurred due to
> https://github.com/apa
;
> ## 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:
> - No new PMC members. Last addition was Chri
For reference, here's the PR working on the fix for 2.1.1:
https://github.com/apache/accumulo/pull/3134
On Fri, Dec 30, 2022 at 11:39 AM Christopher Shannon
wrote:
>
> Version 2.1.1 will be released with bug fixes and this fix (when finished
> and merged) is planned to be include
accumulo 2.1 patch to fix this issue?
>
> Thanks,
>
> On Sat, Dec 17, 2022 at 7:36 PM Vincent Russell >
> wrote:
>
> > No worries. I'm glad I was able to help in some small way.
> >
> > Thank you for fixing the issue.
> >
> > On Sat, Dec 17, 2
I created https://github.com/apache/accumulo/pull/3134 and that should fix
this issue.
Thanks Vincent for pointing out the issue in TServerUtils, your testing
made this easy to track down and fix.
On Sat, Dec 17, 2022 at 9:00 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote
I was able to reproduce the issue by setting the value size for a mutation
to size 16384001 to make sure it's greater than the default value for
Thrift and it fails immediately. I will work on a fix now that we know how
to reproduce it.
On Fri, Dec 16, 2022 at 2:31 PM Christopher wrote:
>
not sure if this
> is intentional or not.
>
> On Thu, Dec 15, 2022 at 3:26 PM Vincent Russell
> wrote:
>
> > Christopher,
> >
> > I am not sure if this issue is related to 3042 or not.
> >
> > On the client side it does look like TConfiguration ends up being c
These could be better documented. It's been awhile since I've thought
about these, but I think:
SystemPermission.SYSTEM - basically permits superuser access to
perform most operations. However, this does not allow automatic access
to tables. A user with this permission, however, can grant
which I have already upgraded to 2.0.
> >
> > I'll spend some time investigating how bad the usage of the internal
> > packages are and get back to you.
> >
> > Thanks again,
> >
> > On Tue, Dec 13, 2022 at 3:20 PM Christopher wrote:
> >
> &g
>
> >
> >
> > On Fri, Dec 9, 2022 at 9:02 AM Vincent Russell
> > wrote:
> >
> > > I mean Christopher.
> > >
> > > Thanks again.
> > >
> > > On Fri, Dec 9, 2022 at 9:01 AM Vincent Russell <
> > vincent.russ...@gmail.co
Hi Vincent,
Version 2.0.1 is end of life as of the 2.1.0 LTM release, and 2.0 is
not expected to receive any further updates. Version 2.1.0 may work
with ZooKeeper 3.4, but was developed and tested against 3.5 and later
versions. I believe the ZooKeeper community is currently considering
whether
1 - 100 of 1859 matches
Mail list logo
