those commits added back in
accidentally.
On Thu, Dec 1, 2022 at 5:26 PM Christopher wrote:
>
> Hi Accumulo devs,
>
> I just wanted to give you a heads up about branch maintenance for the
> 2.1 branch. A few mistakes were made, and the main branch accidentally
> got merged back
mergetool` is your friend :)
I hope this explanation helps others understand what happened and how
to avoid similar issues with GitHub in future.
Regards,
Christopher Tubbs
Yes. You can do this with the balancer. The default balancer
("manager.tablet.balancer") is a per-table TableLoadBalancer, so each
table can have custom configuration for your specific table, with its
own custom balancer, or you may be able to use the existing
HostRegexTableLoadBalancer for your
rease in throughput (i.e. ingest rate in
> terms of operations per second seem to be roughly equivalent. The same is
> true for the ingest rate in MB/s.)
>
> On Fri, Nov 4, 2022 at 4:21 PM Christopher wrote:
>
> > I don't think it has any changes that would prevent rollback, but i
I don't think it has any changes that would prevent rollback, but it's not
a scenario that has been tested to my knowledge.
On Fri, Nov 4, 2022, 16:15 Dave Marion wrote:
> It's going to take some time to review the changes[1], but I don't see
> changes in the default JVM sizes. I was wondering
gt; > missing it? Thats a really nice user facing change that should be
> > > mentioned.
> > >
> > > On Wed, Nov 2, 2022 at 7:55 AM Christopher
> wrote:
> > > >
> > > > The following is a draft announcement for the 2.1 release. I've
> prepared
&g
The following is a draft announcement for the 2.1 release. I've prepared it
here for a little bit of feedback, before sending it out later today.
***
The Apache Accumulo project is pleased to announce the release
of Apache Accumulo 2.1.0! Apache Accumulo 2.1.0 contains numerous
features and
This vote passes with 6 +1s and no other votes.
Post-vote tasks are being tracked in
https://github.com/apache/accumulo/issues/3060 and I'll be working through
the list today.
On Tue, Nov 1, 2022 at 10:00 AM Christopher wrote:
> +1 (binding)
>
> Verified:
> * Checksums and signat
ntinuous ingest with agitation then stopped
> and flushed the table
> - Ran verify with eventual scans which completed successfully
>
>
>
>
> On Mon, Oct 31, 2022 at 3:14 PM Keith Turner wrote:
>
> > +1 after reading about the testing Dave did.
> >
> > On T
several tests using Uno for the new features in 2.1.0 such as per
table encryption, shell command changes, etc.
* Ran tests using accumulo-testing against Uno including ingest and verify
On Thu, Oct 27, 2022 at 2:02 AM Christopher wrote:
> Accumulo Developers,
>
> Please consider the
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.0.
The only change since 2.1.0-rc3 was
https://github.com/apache/accumulo/pull/3051
Git Commit:
706612f859d6e68891d487d624eda9ecf3fea7f9
Branch:
2.1.0-rc4
If this vote passes, a gpg-signed tag will be
t sure if its related to the other metadata issues, but
> looks odd - see https://github.com/apache/accumulo/issues/3050
>
> -Original Message-
> From: Christopher
> Sent: Wednesday, October 26, 2022 3:03 PM
> To: accumulo-dev
> Subject: [VOTE] Apache Accumulo 2.1.0-
That should have said the changes since rc2, not since rc1. They are
aggregate.
On Wed, Oct 26, 2022 at 3:02 PM Christopher wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Apache Accumulo 2.1.0.
> Notably, the changes since 2.1.0-rc1 were:
>
> *
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.0.
Notably, the changes since 2.1.0-rc1 were:
* https://github.com/apache/accumulo/pull/3047
* https://github.com/apache/accumulo/pull/3049
Git Commit:
d174737cb132027b9e74b5d30ddfbf949d3d9848
Branch:
gt; does not manifest until there are multiple tables, which is why the
> bulk ITs were happy.
>
> On Wed, Oct 26, 2022 at 4:21 AM Christopher wrote:
> >
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 2.1.0.
> >
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.0.
Notably, the changes since 2.1.0-rc1 were:
* https://github.com/apache/accumulo/pull/3043
* https://github.com/apache/accumulo/pull/3044
There are also 3 issues that were identified that could yet serve
maintenance branch. I
will do subsequent release candidates from that branch. Those changes can
be merged into the main branch after being applied to the 2.1 maintenance
branch first.
Thanks,
Christopher
On Tue, Oct 25, 2022 at 11:35 AM dev1 wrote:
> -1
>
> discovered an issue with the upg
to remove that is breaking API changes, and it'd be good to do that prior
to adding new 3.x features.
Christopher
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.0.
Git Commit:
92b07213f5e3e7f77be56f0866316b2f0eebe191
Branch:
2.1.0-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -s -m 'Apache Accumulo 2.1.0' rel/2.1.0 \
Accumulo Developers,
NOTE: this is only a test vote. You do *NOT* need to vote. This test
release candidate can serve as a baseline for testing for 2.1.0 releases,
and to test the release process automation. Again, this is not a real vote.
A subsequent release candidate will be made when an
I don't think we're doing anything special to publish to JMX. I think this
is something that is a feature of Hadoop Metrics2 that we're simply
enabling. So, this might be a question for the Hadoop general mailing list
if nobody knows the answer here.
On Wed, Oct 12, 2022 at 1:06 PM Logan Jones
age-
> From: Christopher
> Sent: Thursday, September 29, 2022 7:19 AM
> To: dev@accumulo.apache.org
> Subject: [EXTERNAL] Re: New committer / PMC member: Chris Shannon
>
> Congrats, and welcome
>
> On Thu, Sep 29, 2022 at 9:51 AM Jeffrey Manno
> wrote:
>
> > Congrats a
Congrats, and welcome
On Thu, Sep 29, 2022 at 9:51 AM Jeffrey Manno
wrote:
> Congrats and welcome!
>
> On Thu, Sep 29, 2022 at 9:43 AM Dave Marion wrote:
>
> > Congrats Chris!
> >
> > On Thu, Sep 29, 2022 at 9:26 AM Dominic Garguilo >
> > wrote:
> >
> > > Congrats and welcome, Chris!
> > >
>
ing used here. I saw a reference to
> 2.0.1 in an earlier email.
>
> On Fri, Jul 29, 2022 at 3:03 PM Christopher wrote:
>
> > That was a bug in the new AbstractServer class in 2.x. I don't think it
> > ever affected 1.x
> > I checked the 1.10 code and it wouldn't affect t
xed a bug in 2.1 where the
> -a argument was not correctly setting the hostname. It looks like 2.0.1 is
> affected by this too.
>
> On Fri, Jul 29, 2022 at 12:57 PM Christopher wrote:
>
> > The tracer should be advertising its own address in ZK. By default, the
> > serve
r
>
> [root@accumulo_gc /]# curl 0.0.0.0:12234
> curl: (7) Failed connect to 0.0.0.0:12234; Connection refused
>
> [root@accumulo_gc /]# curl accumulo_tracer:12234
> curl: (52) Empty reply from server
>
> Is there a way to set Trace hosts to accumulo_tracer:12234
>
>
register themselves in
ZooKeeper. I'm not a docker network expert, but whatever service address
the tracer service is advertising there should be routable from the tablet
servers.
On Thu, Jul 28, 2022 at 7:31 PM kma wrote:
> Thanks again Christopher,
>
> Our environment is a little
:
> Thank you Christopher,
>
> We can confirm that trace on and trace off are working fine in accumulo
> shell. We can see those trace messages in the trace table and tracer
> service is running.
>
> However, we are not seeing trace messages for MajC / MinC
>
> We do se
By default, the tracer service that collects traces and writes them to
the trace table does not run. Generally, it is also responsible for
creating the trace table. If you have an empty trace table, was it
created by the tracer service, or did you create it manually?
Assuming tracing is working
. If so, could you help me understand why?
>
> Thanks in advance,
>
> - Logan
>
>
>
> On Wed, Jul 6, 2022 at 6:31 PM Christopher wrote:
>
> > Yes, either here (especially if it's related to a bug or proposed code
> > change) or at user@ would work, if
Yes, either here (especially if it's related to a bug or proposed code
change) or at user@ would work, if it's more of a user question. Here is
fine if you're not sure.
On Wed, Jul 6, 2022, 16:35 Logan Jones wrote:
> Hello:
>
> I would like to discuss what happens when iterators cause
osing off open PRs before creating release candidates.
>
> Ed Coleman
>
> -Original Message-
> From: Christopher
> Sent: Monday, June 6, 2022 6:49 PM
> To: accumulo-dev
> Subject: Re: [VOTE] 2.1.0-beta-1 or 2.1.0-alpha-1 Release
>
> Unfortunately, I won't be creat
Unfortunately, I won't be creating one tonight, though. Maybe tomorrow?
On Mon, Jun 6, 2022 at 4:08 PM Christopher wrote:
>
> Yes, I can create one.
>
> On Mon, Jun 6, 2022 at 8:35 AM Mike Miller wrote:
> >
> > Christopher, are you going to create a RC? Let me know if
Yes, I can create one.
On Mon, Jun 6, 2022 at 8:35 AM Mike Miller wrote:
>
> Christopher, are you going to create a RC? Let me know if you can't and I
> can try to do something to get the release process moving.
>
> On Wed, Jun 1, 2022 at 3:41 PM Christopher wrote:
>
> >
Yes. I expect we'll do that when we prepare the RC for a beta.
On Tue, May 31, 2022 at 11:20 PM Keith Turner wrote:
>
> Should we also create a new 2.1 branch along with doing an alpha or
> beta release?
>
> On Tue, May 31, 2022 at 7:24 AM Christopher wrote:
> >
> >
I'm not sure it makes sense to vote on whether to do a vote. I'm okay
with creating a beta release later this week. When we're ready to do
that, we can just create that release candidate and vote on that,
though.
On Tue, May 31, 2022 at 7:12 AM Mike Miller wrote:
>
> I propose a vote to do a
Since Accumulo doesn't bundle Hadoop into the release, the only
difference this makes is whether or not it breaks our builds during
testing, which could indicate a bug in Hadoop, or an incompatibility
with that version of Hadoop. The version of Accumulo built with 3.3.0
should work perfectly fine
> > > do
> > > > so!
> > > >
> > > > On Wed, Apr 27, 2022 at 1:04 PM Dave Marion
> > wrote:
> > > >
> > > > > Welcome! And +1 for hearing more about how you are using Accumulo.
> I
> > > > > visited the Ghost's website earl
Hi Nikita!
Welcome to our community. I'm curious to hear more about how Ghost is
using Accumulo. Have you considered giving a presentation at the
upcoming ApacheCon this year? I think they are still accepting
submissions (https://apachecon.com/acna2022/cfp.html) and that sounds
like it would make
Isolation should only give you consistency within a row, to ensure you're
not scanning over partial changes from a mutation that is currently being
written to a row. It shouldn't have anything to do with compactions or
missing data that has already been written before the MapReduce scan has
is the best path forward. Additional feedback would be helpful
in deciding on one of the proposed options, or a different path
entirely.
https://github.com/apache/accumulo/pull/2622
Thanks,
Christopher
On Fri, Apr 8, 2022 at 4:12 PM dev1 wrote:
>
> There does not seem to be a path forward for us or Aaron C. - without the
> access to the account that created the domain, the owner cannot get anyone at
> Amazon to respond. Maybe they would respond to a legal request from Apache -
> but that's
Overall, it looks good to me.
Regarding the trademark issue with that domain, I think it is either a
problem we should pursue further (reach out to Amazon, the
registrar?), or it's not a problem worth our time, and we should drop
it. I'm not sure which is the case, I don't think it's worth
we may be able to get into
> 2.1 as well.
>
> [1] https://github.com/apache/accumulo/pull/2475
>
> On Mon, Apr 4, 2022 at 11:50 AM Keith Turner wrote:
>
> > On Mon, Apr 4, 2022 at 11:17 AM Christopher wrote:
> > >
> > > I haven't seen the metrics test fail v
On Mon, Apr 4, 2022 at 1:11 PM Dave Marion wrote:
>
> I understand the desire to see less coupling for the optional features, but
> getting to that point for ScanServers (and less so for ExternalCompactions)
> would be a ton of work I think.
The likelihood of it being a lot of work doesn't mean
On Mon, Apr 4, 2022 at 11:50 AM Keith Turner wrote:
>
> On Mon, Apr 4, 2022 at 11:17 AM Christopher wrote:
> >
> > However, I'm reluctant to include #2422, because I don't think it's near
> > ready enough, and by the time it is, it will be very last minute, and I
>
I haven't seen the metrics test fail very often lately. If it's stable, I
don't mind removing the blocker on that issue, but I'd be reluctant to
close it entirely just yet, until we can verify it doesn't happen anymore.
As for the original list of potential issues to include, I'm in favor of
It's not clear what you're asking. 1.10.2 is backwards compatible with
1.9.3 (source compatible, not necessarily binary compatible across
minor versions). And requires Java 8.
On Fri, Feb 25, 2022 at 12:14 PM Dushyant Tankariya
wrote:
>
> > Hi team,
> >
> > We are using Accumulo Database version
gt; >
> > On Mon, Feb 14, 2022 at 9:21 AM Christopher wrote:
> >
> > > This is also the tweet I have scheduled prepared:
> > >
> > > [image: ] Happy #ValentinesDay
> > > <https://twitter.com/search?q=%23ValentinesDay>! [image: ] B
(LTM)!
https://accumulo.apache.org/release/accumulo-1.10.2/ #opensource
<https://twitter.com/search?q=%23opensource> #BigData
<https://twitter.com/search?q=%23BigData>
On Mon, Feb 14, 2022 at 9:19 AM Mike Miller wrote:
> LGTM. The Release notes look good as well.
>
> On Sun, Feb 13, 2
The Apache Accumulo project is pleased to announce the release
of Apache Accumulo 1.10.2! Apache Accumulo 1.10.2 is a bug fix
release of the 1.10 LTM release line. Among other things, it
removes the dependency on log4j 1.2 (using reload4j instead).
See the release notes linked below for details.
This vote passes. I count:
* 11 binding +1s
* No other votes
I will continue the process to release this tomorrow and Monday (if not
done tomorrow). Release checklist being tracked at:
https://github.com/apache/accumulo/issues/2468
On Sat, Feb 12, 2022 at 5:07 PM Christopher wrote:
> +1 f
gt; https://github.com/apache/accumulo/compare/rel/1.10.1...1.10.2-rc1
> >
> > On Tue, Feb 8, 2022 at 10:08 AM Christopher wrote:
> > >
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Apache Accumulo 1.10.2.
>
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 \
this though.
On Fri, Feb 4, 2022 at 12:36 PM Michael Wall wrote:
> I have some GC fixes I am working on that I would like to get into the
> 1.10.2 release.
>
> https://github.com/apache/accumulo/issues/1377
> https://github.com/apache/accumulo/issues/2322
>
> On Thu, Feb 3, 2022 a
221.
> A
> little more testing needs to be done, do you have a schedule for the 1.10.2
> release?
>
> On Thu, Feb 3, 2022 at 1:55 PM Christopher wrote:
>
> > I'm interested in putting together a 1.10.2 release with the changes in
> > https://github.com/apache/accumul
,
Christopher
You can specify the bind address on the command line when starting Accumulo
services:
bin/accumulo tserver -a 127.0.0.1
bin/accumulo tserver --address 127.0.0.1
I believe this will also work if you specify a hostname, but the IP address
that it will bind to will be the IP address of whatever the
e also committers, we all have the same
roles/permissions.
In addition, the ASF-maintained bots have the Contributors role.
I removed all other individual entries that had been added manually,
as they aren't needed anymore.
Regards,
Christopher
I have not personally tested HDFS configured for SSL/TLS, but `new
Configuration()` will load the core-default.xml and core-site.xml
files it finds on the class path. So, it looks like it should work.
Have you tried it? Did you get an error?
On Tue, Dec 14, 2021 at 1:54 PM Vincent Russell
>> 2526 at
> >> io.opentelemetry.context.Context$$Lambda$209/0x000100357840.run(Unknown
> >> Source)
> >> 2527 at java.lang.Thread.run(java.base@11.0.11/Thread.java:829)
> >>
> >>
> >> 3151 "gc" #31 prio=5 os_prio=0
It looks like the tests are timing out. This happens frequently when
running on resource-constrained systems. You can give the test more
time by increasing the timeout factor: `mvn clean verify
-Dcheckstyle.skip -Dspotbugs.skip -Dit.test=ConcurrentDeleteTableIT
-Dtimeout.factor=3`
There's nothing
I'm not familiar with how to set up SSL/TLS for ZooKeeper, but if you
want to use ZooKeeper 3.5 with Accumulo 2.0.1, it should still be
possible. You may need to modify some scripts and config files to
ensure your classpath is set up correctly, since the ZK directory
names may have changed from
whereby everytime a
> > breaking change is made it gets documented at the time it is committed.
> >
> > On Wed, Oct 20, 2021 at 04:55:42PM -0400, Christopher wrote:
> > > If somebody were to volunteer to create such a document, they could do so
> > > fr
involved.
On Wed, Oct 20, 2021, 18:20 Jeremy Kepner wrote:
> Seeme like there should be document that is kept whereby everytime a
> breaking change is made it gets documented at the time it is committed.
>
> On Wed, Oct 20, 2021 at 04:55:42PM -0400, Christopher wrote:
> > If somebody
t; work through the errors one-by-one.
>
> On Tue, Oct 19, 2021 at 11:17:09AM -0400, Christopher wrote:
> > The best reference is the release notes:
> > https://accumulo.apache.org/release/accumulo-2.0.0/
> >
> > On Tue, Oct 19, 2021, 09:15 Jeremy Kepner wrote
We wouldn't *have* to remove additional deprecations if we did name it
3.0, but it might be a good opportunity to do some cleanup for some
stuff that deprecated prior to 2.0, but left in there to ease the
transition to 2.0. Then again, removing anything else might make the
transition from 1.10 LTM
For reference, our last conversation about the state of replication
was
https://lists.apache.org/thread.html/ra65ecbfcdb26af2672b7a064d313c0db0285b7d9f228c09559a14842%40%3Cdev.accumulo.apache.org%3E
; in that, I tried to make the community aware of the issues involving
the long-running and
The best reference is the release notes:
https://accumulo.apache.org/release/accumulo-2.0.0/
On Tue, Oct 19, 2021, 09:15 Jeremy Kepner wrote:
> Is there a list of things in 1.10 that will no longer work in 2.0.
>
> On Tue, Oct 19, 2021 at 08:59:58AM -0400, Christopher wrote:
>
Hi Vincent,
To supplement what Mike said, it's possible some stuff that was
deprecated in 1.10 was dropped in 2.0. I don't have a comprehensive
list of what that might include, but anything marked as deprecated in
1.10 is subject to removal in 2.0. If I recall, we did try to limit it
somewhat. It
LTM stands for "long-term maintenance". Its purpose is to communicate
what we are focusing our long-term maintenance efforts on, such as
backporting bug fixes and testing upgrade paths from older releases,
so we can balance the need to support previous releases against our
need to move forward and
Our repos should still be labeled for Hacktoberfest, so we should
still be ready for that. I didn't see any substantial rules changes
that would require additional steps from us.
On Tue, Sep 28, 2021 at 2:59 PM Michael Wall wrote:
>
> I think links 3 and 4 have a space that is breaking up the
+1 to everything Ed wrote. :)
On Wed, Sep 22, 2021 at 10:03 AM wrote:
>
> The information provided by micrometer instrumentation should be consistent
> with the values produced by Hadoop metrics. Things like gauges and counters
> are straight forward and should match 1:1. Things that collect
My impression is that the metrics names are a big pain point already,
and that they appear differently, depending on which Hadoop Metrics 2
sink the user has configured, and what happens to them after that
(InfluxDB naming conventions seems to be a problem sometimes while
using fluo-uno). Since
I could be wrong, but I don't think Accumulo has changed anything about the
way it is emitting metrics in 1.10 that would be substantially different
from 1.8. It's possible that the GraphiteSink has changed how it works in
your version of Hadoop. Or maybe newer versions of InfluxDB stores things
w spot. I'm about to go down the list to the next project. Are
> you still a possibility for this week, or is it further out than that?
>
> --Rich, for Feathercast.
>
> On 9/1/21 11:50 AM, Christopher wrote:
> > Hi Rich,
> >
> > I started a conversation on our private l
wants to step up. I have seen all the previous Feathercast
interviews on the YouTube channel, and think this definitely has
value, so hopefully somebody will be willing and able to do this with
you.
Thanks for reaching out,
Christopher
On Fri, Aug 27, 2021 at 12:54 PM Rich Bowen wrote:
>
&
d that I did not want to push. So I did
> another commit to revert those unintended changes.
>
> As for the sours merge, the test does not exist in 2.x. I did check
> that my two commits were the only unmerged commits before doing the
> sours merge.
>
> On Thu, Aug 5, 2021 at 7:3
Hey Keith,
Just curious because of all the activity around this change in 1.10
(the subsequent partial revert and the merge commits to main, which
seem to be -sours), what motivated the change to TabletIteratorTest in
the older branch?
On Thu, Aug 5, 2021 at 6:40 PM wrote:
>
> This is an
generally
without being tightly coupled to those implementations, I think that's
probably the best way forward for the ZooLease stuff.
>
> On 2021/07/28 17:41:10, Christopher wrote:
> > From what I saw from looking at the changes in Chris Milbert's fork,>
> > the f
The Project Management Committee (PMC) for Apache Accumulo has invited
Dominic Garguilo to become a committer and PMC member and we are
pleased to announce that they have accepted.
Dominic has been contributing various fixes and improvements to
Accumulo since Fall 2020.
Being a committer enables
>From what I saw from looking at the changes in Chris Milbert's fork,
the fork contains a couple S3 implementations of Hadoop's FileSystem
interface in a separate module (similar to s3a:// and abfss://
implementations). It seems to add accS3mo:// and accS3nf://
implementations, which, in spite of
ticket, can write one tonight.
>
> On Thu, Jul 1, 2021 at 11:10 AM Christine Buss
> wrote:
>
> >
> >
> > Thanks so much! Yes that was the problem. And thanks to everyone else that
> > took their time to help me.
> >
> >
> > Gese
The error message looks like it's saying you don't have the `make`
command installed on your machine. Based on the word "ubuntu" in your
OpenJDK build version, I think you're on an Ubuntu-based machine. I
found a StackOverflow answer (https://askubuntu.com/a/272020) that
said you can do:
sudo
Just a heads-up, if you use Eclipse to do Accumulo development, you'll
probably want to skip the June release, Eclipse 2021-06.
It doesn't work with Accumulo for some reason. I filed a bug at:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=574425
Hi Junwen,
It looks like the issues that your checker found were only problems in some
old alpha releases, and we're already fixed by the time we created a final
release.
On Tue, May 4, 2021, 02:15 junwen yang wrote:
> Deal all,
>
>
> Regarding the issue caused by the incompatibility of
Note: removed user@ list and added dev@ list. Preparing the board
report is a PMC responsibility, and we decided to prepare it publicly
on the dev mailing list, but it's probably not something most users
care about, and we should avoid spamming the user list with PMC
business, so that way users
An invitation was sent to your email address.
On Mon, Mar 1, 2021 at 2:52 PM wschultz wrote:
>
> Hi,
>
> I would like to join ASF slack.
>
> - Walter
ion
from when the commit messages were first authored and the final
result. When you merge, the commit message should reflect what the
change actually does in its final form, after all code reviews and
updates to the PR, not your first draft and the steps it took you to
get there.
Anyway, I hope these tips help somebody.
Thanks,
Christopher
ll-known performance limitations, and should generally be
> avoided" was added on Oct 13, 2020.
>
> Thanks.
>
> On Mon, Feb 8, 2021 at 5:06 PM Christopher wrote:
>
> > Guava's argument in the linked comment appears to be based on
> > pre-Java8, before the PermGen space
or problems happen in the
> > >> simulation, they may happen in the real environment.
> > >>
> > >>
> > >>
> > https://github.com/apache/hadoop/blob/ba631c436b806728f8ec2f54ab1e289526c90579/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapredu
While code reviewing, I saw that
core/src/main/java/org/apache/accumulo/core/clientImpl/TabletLocator.java
was using a WeakHashMap to deduplicate some strings.
This code can probably be removed in favor of one of the following two options:
1. Just explicitly use String.intern() - As of Java 7,
The Project Management Committee (PMC) for Apache Accumulo
has invited Karthick Narendran to become a committer and PMC
member and we are pleased to announce that they have accepted.
Karthick has contributed several bug fixes and quality improvements
to Accumulo, has written blog posts for our
The report looks good to me, but I don't think we should use the GitHub PR
mechanism to draft these. I provided some of my reasoning on the PR, but
basically:
1. I don't think it adds value to be archived to the website, since the
reports are already canonically archived elsewhere in ASF's
uld mention that users of
> 1.10 may want to wait until the 2.x LTM release line? Say that 2.1 is
> likely to be LTM?
>
> On Sun, Dec 27, 2020 at 11:48 PM Christopher wrote:
>
> > Karthick, tweeting is part of the checklist. Somebody typically does it
> > after these
Karthick, tweeting is part of the checklist. Somebody typically does it
after these announcements go out via email first.
On Sun, Dec 27, 2020, 17:19 karthick rn
wrote:
> Hi Billie,
> The draft looks good.
> Do we tweet for these releases?
>
> Thanks,
> Karthick
>
>
> On Sat, 26 Dec 2020 at
LGTM
On Sat, Dec 26, 2020, 13:49 Billie Rinaldi wrote:
> The following is a DRAFT announcement for the 2.0.1 release. Please review
> and provide feedback. I intend to publish this announcement on Dec 28.
> *
>
> The Apache Accumulo project is pleased to announce the release
> of Apache
LGTM
On Sat, Dec 26, 2020, 13:43 Billie Rinaldi wrote:
> The following is a DRAFT announcement for the 1.10.1 release. Please review
> and provide feedback. I intend to publish this announcement on Dec 28.
> *
>
> The Apache Accumulo project is pleased to announce the release
> of Apache
This vote passes with:
4 +1s (binding): Jeffrey, Billie, Christopher, Mike Miller, Ed
1 +1s (non-binding): Karthick
The post-vote release checklist is being tracked at
https://github.com/apache/accumulo/issues/1846
On Thu, Dec 24, 2020 at 5:12 PM wrote:
> +1
>
> * Verified comm
s pass
>
> I noticed we need to do a license and notice review of the main branch, but
> I am not inclined to delay this release due to that.
>
> On Mon, Dec 21, 2020 at 1:39 PM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candida
101 - 200 of 1859 matches
Mail list logo
