After several rounds of discussions[1][2], we finally decided to set
the minimum supported java version for HBase 3.0.0+ to 17.
Notice that, we will keep HBase 2.x to work with both java 8, java 11
and java 17, so it is suggested to upgrade to use java 17 first on
HBase 2.x, and then upgrade to
After several rounds of discussions[1][2], we finally decided to set
the minimum supported java version for HBase 3.0.0+ to 17.
Notice that, we will keep HBase 2.x to work with both java 8, java 11
and java 17, so it is suggested to upgrade to use java 17 first on
HBase 2.x, and then upgrade to
Thanks Udo.
In the previous discussion thread, we also discussed this topic.
In general, we do not expect, and also do not suggest our users to
upgrade major hbase version and jdk version at the same time.
We will make branch-2.x to work with jdk8, jdk11 and jdk17, so users
could upgrade jdk
My opinion on this: If you choose jdk 11 as the minimum, it will be easier for
many to migrate from HBase 2.3+ to 3.0.
Best Regards
> Am 09.06.2024 um 16:08 schrieb Duo Zhang :
>
> HBase 3.0.0-beta-2 is about to come, it will be the last beta release
> and then we will release our first 3.x GA
HBase 3.0.0-beta-2 is about to come, it will be the last beta release
and then we will release our first 3.x GA HBase.
There is a discussion thread about dropping jdk8 support in HBase
3.x[1], we all agree to do this but there is no consensus on which jdk
version should be the minimum supported
It seems like some regions are assigned to at least 2 region servers,
so you will get different results if you connect to different region
servers while trying to fetch the same row.
Usually disabling all the tables and then enabling them can fix the problem.
And hbase-1.x has been EOL for about
Dear HBase Community,
We are experiencing an intermittent issue in our HBase cluster (version
1.4.14, HDFS 2.7.3, Zookeeper 3.4.10, 9 region servers, 2 masters).
Issue Details:
- Symptoms: Get operations intermittently return null for certain row
keys despite data presence.
- Duration:
Congratulations Andor!!
On Fri, May 31, 2024, 5:35 PM Andor Molnar wrote:
> Thank y'all!
>
>
> On Wed, 2024-05-29 at 17:13 -0400, Bryan Beaudreault wrote:
> > Congrats and welcome!
> >
> > On Wed, May 29, 2024 at 5:06 PM Viraj Jasani
> > wrote:
> >
> > > Congratulations and Welcome, Andor!
Thank y'all!
On Wed, 2024-05-29 at 17:13 -0400, Bryan Beaudreault wrote:
> Congrats and welcome!
>
> On Wed, May 29, 2024 at 5:06 PM Viraj Jasani
> wrote:
>
> > Congratulations and Welcome, Andor! Well deserved!!
> >
> >
> > On Wed, May 29, 2024 at 7:36 AM Duo Zhang
> > wrote:
> >
> > >
Thank y'all!
On Wed, 2024-05-29 at 17:13 -0400, Bryan Beaudreault wrote:
> Congrats and welcome!
>
> On Wed, May 29, 2024 at 5:06 PM Viraj Jasani
> wrote:
>
> > Congratulations and Welcome, Andor! Well deserved!!
> >
> >
> > On Wed, May 29, 2024 at 7:36 AM Duo Zhang
> > wrote:
> >
> > >
Congrats and welcome!
On Wed, May 29, 2024 at 5:06 PM Viraj Jasani wrote:
> Congratulations and Welcome, Andor! Well deserved!!
>
>
> On Wed, May 29, 2024 at 7:36 AM Duo Zhang wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Andor Molnár(andor) has accepted the
Congrats and welcome!
On Wed, May 29, 2024 at 5:06 PM Viraj Jasani wrote:
> Congratulations and Welcome, Andor! Well deserved!!
>
>
> On Wed, May 29, 2024 at 7:36 AM Duo Zhang wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Andor Molnár(andor) has accepted the
Congratulations and Welcome, Andor! Well deserved!!
On Wed, May 29, 2024 at 7:36 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Andor Molnár(andor) has accepted the PMC's invitation to become a
> committer on the project. We appreciate all of Andor
Congratulations and Welcome, Andor! Well deserved!!
On Wed, May 29, 2024 at 7:36 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Andor Molnár(andor) has accepted the PMC's invitation to become a
> committer on the project. We appreciate all of Andor
Well deserved and Congratulations, Andor!
-Stephen
On Wed, May 29, 2024 at 12:05 PM Ankit Singhal
wrote:
> Congratulations Andor !!
>
> On Wed, 29 May 2024 at 10:26, Shanmukha Haripriya Kota
> wrote:
>
> > Congratulations, Andor!
> >
> > Regards,
> > Shanmukha K
> >
> > On Wed, May 29, 2024
Well deserved and Congratulations, Andor!
-Stephen
On Wed, May 29, 2024 at 12:05 PM Ankit Singhal
wrote:
> Congratulations Andor !!
>
> On Wed, 29 May 2024 at 10:26, Shanmukha Haripriya Kota
> wrote:
>
> > Congratulations, Andor!
> >
> > Regards,
> > Shanmukha K
> >
> > On Wed, May 29, 2024
Congratulations Andor !!
On Wed, 29 May 2024 at 10:26, Shanmukha Haripriya Kota
wrote:
> Congratulations, Andor!
>
> Regards,
> Shanmukha K
>
> On Wed, May 29, 2024 at 10:22 AM Enrico Olivelli
> wrote:
>
> > Congrats !
> >
> > Enrico
> >
> > Il giorno mer 29 mag 2024 alle ore 16:38 Duo Zhang
Congratulations Andor !!
On Wed, 29 May 2024 at 10:26, Shanmukha Haripriya Kota
wrote:
> Congratulations, Andor!
>
> Regards,
> Shanmukha K
>
> On Wed, May 29, 2024 at 10:22 AM Enrico Olivelli
> wrote:
>
> > Congrats !
> >
> > Enrico
> >
> > Il giorno mer 29 mag 2024 alle ore 16:38 Duo Zhang
Congratulations, Andor!
Regards,
Shanmukha K
On Wed, May 29, 2024 at 10:22 AM Enrico Olivelli
wrote:
> Congrats !
>
> Enrico
>
> Il giorno mer 29 mag 2024 alle ore 16:38 Duo Zhang
> ha
> scritto:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Andor Molnár(andor)
Congrats !
Enrico
Il giorno mer 29 mag 2024 alle ore 16:38 Duo Zhang ha
scritto:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Andor Molnár(andor) has accepted the PMC's invitation to become a
> committer on the project. We appreciate all of Andor Molnár's
> generous
Congrats !
Enrico
Il giorno mer 29 mag 2024 alle ore 16:38 Duo Zhang ha
scritto:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Andor Molnár(andor) has accepted the PMC's invitation to become a
> committer on the project. We appreciate all of Andor Molnár's
> generous
On behalf of the Apache HBase PMC, I am pleased to announce that
Andor Molnár(andor) has accepted the PMC's invitation to become a
committer on the project. We appreciate all of Andor Molnár's
generous contributions thus far and look forward to his continued
involvement.
Congratulations and
On behalf of the Apache HBase PMC, I am pleased to announce that
Andor Molnár(andor) has accepted the PMC's invitation to become a
committer on the project. We appreciate all of Andor Molnár's
generous contributions thus far and look forward to his continued
involvement.
Congratulations and
The HBase team is happy to announce the immediate availability of HBase
2.4.18.
Apache HBase™ is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of rows
with millions of columns atop non-specialized hardware. To learn
The HBase team is happy to announce the immediate availability of HBase
2.4.18.
Apache HBase™ is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of rows
with millions of columns atop non-specialized hardware. To learn
Udo writes:
> https://hbase.apache.org/book.html#data.block.encoding.types contains
> a detailed description of compression in HBase. The final solution for
> us was to configure the snappy codec in hbase-site.xml:
>
>
> hbase.io.compress.snappy.codec
>
>
Haha yes, I noticed that…after sending. Hopefully the title and various
other mentions of 2.6.0 can suffice this time :)
On Mon, May 20, 2024 at 10:08 PM 张铎(Duo Zhang)
wrote:
> Congratulations!
>
> But it seems you missed the replacement for the first '_version_'
> placeholder...
>
> Bryan
Haha yes, I noticed that…after sending. Hopefully the title and various
other mentions of 2.6.0 can suffice this time :)
On Mon, May 20, 2024 at 10:08 PM 张铎(Duo Zhang)
wrote:
> Congratulations!
>
> But it seems you missed the replacement for the first '_version_'
> placeholder...
>
> Bryan
"Once these long compassions are finished, the queued ones are processed
very quickly."
I don't think that's the case as I described there was no additional
compaction completion log at that time. There was one item of compaction
completion log every several minutes, the same as when the queue was
Congratulations!
But it seems you missed the replacement for the first '_version_' placeholder...
Bryan Beaudreault 于2024年5月21日周二 00:44写道：
>
> The HBase team is happy to announce the immediate availability of HBase
> _version_.
>
> Apache HBase™ is an open-source, distributed, versioned,
Congratulations!
But it seems you missed the replacement for the first '_version_' placeholder...
Bryan Beaudreault 于2024年5月21日周二 00:44写道：
>
> The HBase team is happy to announce the immediate availability of HBase
> _version_.
>
> Apache HBase™ is an open-source, distributed, versioned,
The HBase team is happy to announce the immediate availability of HBase
_version_.
Apache HBase™ is an open-source, distributed, versioned, non-relational
database.
Apache HBase gives you low latency random access to billions of rows with
millions of columns atop non-specialized hardware. To
The HBase team is happy to announce the immediate availability of HBase
_version_.
Apache HBase™ is an open-source, distributed, versioned, non-relational
database.
Apache HBase gives you low latency random access to billions of rows with
millions of columns atop non-specialized hardware. To
By the description, it seems compaction of a specific subset of regions is
taking a long time to complete, filling all the compaction threads whilst
all other compaction requests are queued waiting for these long ones to
complete. Once these long compassions are finished, the queued ones are
Hi,
We are experiencing periodic slow response issue. We investigated the issue
and found it's related to hfile compaction. The slow down happens when
there are many compaction activities in log. So we tuned some compaction
parameters and also started to monitor the metric: compactionQueueLength.
Hi all,
HBase submits a report to the ASF board once a quarter, to inform the board
about project health. I'm sending the report to the user@ and dev@ mailing
lists because you are the project, and for transparency. If you have any
questions about the report or the running of the project, you can
Hi all,
HBase submits a report to the ASF board once a quarter, to inform the board
about project health. I'm sending the report to the user@ and dev@ mailing
lists because you are the project, and for transparency. If you have any
questions about the report or the running of the project, you can
OK, so finally the problem is that we are not load snappy compression
so all the regions with snappy compression enabled can not online?
It is good that you finally find the root cause.
For the bin with or without hadoop3, the difference is the version of
the hadoop jars bundled in the tarball.
Thanks a lot for your suggestion.
I tried a different approach based on your idea. I deleted my local
repository and used Maven Central as source instead of employer's maven
proxy. Build worked flawlessly without any issues. It seems that there are
issues with io-opentelemetry JARs hosted in my
I have four HBase clusters (A, B, C, D) with replication between them. I've
configured each cluster to replicate to all other clusters in an attempt to
have a hot-hot, eventually-consistent-across-all-clusters setup. One nice
property of this configuration is that any individual cluster can
Hi Adam,
https://hbase.apache.org/book.html#data.block.encoding.types contains a
detailed description of compression in HBase. The final solution for us was to
configure the snappy codec in hbase-site.xml:
hbase.io.compress.snappy.codec
Udo writes:
> Then I saw that the region servers had problems with Snappy
> compression. I'm not sure, but I believe the native Snappy libs were
> part of the previous Hadoop distribution, at least they are not
> included in the current one. After copying them over it seems to work
> now. But
The problem was actually with the Snappy codec or the native Snappy libraries.
After configuring the Snappy
Java implementation, the cluster started without any problems.
I have a final question regarding the Hbase distributions. Can you please tell
me the difference between the distributions:
Compare the local maven repo settings:
~/.m2/settings.xml
For me, I mostly use my employer's maven proxy, which occasionally causes
build issues if I am not behind the corporate VPN.
Maybe there's something different in your maven repo settings between the
two Macs.
You could also manually
Thanks for checking guys.I tried different maven/java versions but none of
them solved my issue. I also tried running maven in debug mode but it's not
throwing any error or warning/exceptions.
Do you have any recommendations on how I debug/solve this?
On Tue, Apr 30, 2024 at 6:06 PM Bryan
I also routinely build all branches of hbase on an apple M3, using hadoop3,
and Java 11+. I believe I’ve also built with java8 at some point, but don’t
quote me on that because we largely don’t use java8 at my company.
On Tue, Apr 30, 2024 at 4:48 PM Wei-Chiu Chuang wrote:
> I am on Apple M3,
I am on Apple M3, checked out HBase master branch,
my JDK is Zulu 1.8.0_392 and Maven 3.9.6.
I am able to build without modifying HBase code.
On Tue, Apr 30, 2024 at 1:39 PM Mihir Monani wrote:
> Also I tried the build with OpenJDK 8 aarchx64 JDK version and x64 JDK
> version, and it fails for
Also I tried the build with OpenJDK 8 aarchx64 JDK version and x64 JDK
version, and it fails for both of them.
If I explicitly add dependency for hbase-common/pom.xml, then it passes for
hbase-common.
*diff --git a/hbase-common/pom.xml b/hbase-common/pom.xml*
*index 0723298926..348c3a4bd4
If I add *io.opentelemetry:opentelemetry-context* as dependency in
hbase-common/pom.xml, it works fine.
I am more confused on why this works with Intel MacBook but doesn't work
with M1/M3 MacBook.
On Tue, Apr 30, 2024 at 11:28 AM Mihir Monani
wrote:
> Hi
>
> I am trying to build hbase (mvn
Hi
I am trying to build hbase (mvn clean install -DskipTests) and it fails
with the below error in hbase-common package. (Maven version : 3.8.8, Java
Version : JDK openjdk version "1.8.0_401")
[*ERROR*] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
Found it:
in hbase-site.xml:
hbase.io.compress.snappy.codec
org.apache.hadoop.hbase.io.compress.xerial.SnappyCodec
> Am 30.04.2024 um 16:32 schrieb Udo Offermann :
>
> I think we finally made it.
> There were a few more problems: First, I made sure that the class paths were
> clean -
I think we finally made it.
There were a few more problems: First, I made sure that the class paths were
clean - Classpath hygiene in Java is the be-all and end-all ;-)
Then I saw that the region servers had problems with Snappy compression. I'm
not sure, but I believe the native Snappy libs
Oh, there is a typo, I mean the ServerCrashProcedure should not block other
procedures if it is in claim replication queue stage.
张铎(Duo Zhang) 于2024年4月30日 周二10:41写道：
> Sorry to be a pain as the procedure store is a big problem before HBase
> 2.3 so we have done a big refactoring on HBase 2.3+
Sorry to be a pain as the procedure store is a big problem before HBase 2.3
so we have done a big refactoring on HBase 2.3+ so we have a migration
which makes the upgrading a bit complicated.
And on the upgrading, you do not need to mix up HBase and Hadoop, you can
upgrading them separately.
Hi Mike,
Disabling ipv6 should be a solution but...
Br,
Bugra
25.04.2024 13:59 tarihinde Mike Mills yazdı:
We have resolved this by:
- Getting the hbase code and editing ServerShutdownHandler.java to skip splitting for server
names starting with "0:0:0:0" and ignoring "Skip assigning
We have resolved this by:
- Getting the hbase code and editing ServerShutdownHandler.java to skip
splitting for server names starting with "0:0:0:0" and ignoring "Skip assigning
region in transition on other server" logic.
- We then swapped in the newly built hbase-server-096.1.12.jar and
Found this in the master log:
2024-04-24 10:29:49,421 DEBUG [MASTER_SERVER_OPERATIONS-master:6-4]
master.DeadServer: Finished processing 0:0:0:0:0:0:0:0,60020,1713708572030
2024-04-24 10:29:49,421 ERROR [MASTER_SERVER_OPERATIONS-master:6-4]
executor.EventHandler: Caught throwable while
Hello,
We have a production system down and can't get it back up. It's an older
version:0.96.1.1. We have 70 OFFLINE unassigned regions.
We were configuring for multiple nics and set both
hbase.regionserver.ipc.address and hbase.master.ipc.address to 0.0.0.0.
This caused hostname lookup
Hi Duo,
To be honest, we only use one master, so there is no way to swap them.
After the attempt throwing the NPE we ran the hbck tool again in which case no
NPE was thrown but also nothing else - the log looked just the one I’ve send
you just without the exception stack trace and nothing
Strange, I checked the code, it seems we get NPE on this line
https://github.com/apache/hbase/blob/4d7ce1aac724fbf09e526fc422b5a11e530c32f0/hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java#L2872
Could you please confirm that you connect to the correct active
Ah, NPE usually means a code bug, then there is no simple way to fix
it, need to take a deep look on the code :(
Sorry.
Udo Offermann 于2024年4月22日周一 15:32写道：
>
> Unfortunately not.
> I’ve found the node hosting the meta region and was able to run hack
> scheduleRecoveries using
Unfortunately not.
I’ve found the node hosting the meta region and was able to run hack
scheduleRecoveries using hbase-operator-tools-1.2.0.
The tool however stops with an NPE:
09:22:00.532 [main] WARN org.apache.hadoop.util.NativeCodeLoader - Unable to
load native-hadoop library for your
Before upgrading, disable the balancer, make sure there is no region
in transition, and there are no dead region servers currently being
processed, i.e, no ServerCrashProcedure.
This is to make sure that there is no procedure before shutting down,
so it is safe to just remove all the
Thank you, I can check on Monday.
This is the upgrade of the test system and serves as training for the upgrade
of the production system. What do we need to do to prevent this problem?
We had some problems starting zookeeper after the upgrade and I had to start it
with
OK, it was waitForMetaOnline.
Maybe the problem is that you do have some correct procedures before
upgrading, like ServerCrashProcedure, but then you delete all the
procedure wals so the ServerCrashProcedure is also gone, so meta can
never be online.
Please check the /hbase/meta-region-server
Master status for masterserver.gmd9.intern,16000,1713515965162 as of Fri
Apr 19 10:55:22 CEST 2024
Version Info:
===
HBase 2.5.7
Source code repository
git://buildbox.localdomain/home/apurtell/tmp/RM/hbase
Just post it somewhere so we can check it.
Udo Offermann 于2024年4月20日周六 20:25写道：
>
> I do have the dump File from the web ui. I can sende it all or you Tell me
> threads you are interessted in. Fortunately they all have meaningfull named.
>
> 张铎(Duo Zhang) schrieb am Sa., 20. Apr. 2024, 14:13:
>
I do have the dump File from the web ui. I can sende it all or you Tell me
threads you are interessted in. Fortunately they all have meaningfull named.
张铎(Duo Zhang) schrieb am Sa., 20. Apr. 2024, 14:13:
> What is the jstack result for HMaster while hanging? Wait on the
> namespace table online
What is the jstack result for HMaster while hanging? Wait on the
namespace table online or meta table online?
Udo Offermann 于2024年4月20日周六 19:43写道：
>
> Hello everyone,
>
> We are upgrading our Hadoop/HBase cluster from Hadoop 2.8.5 & HBase 2.2.5
> to Hadoop 3.3.6 & HBase 2.5.7
>
> The Hadoop
Hello everyone,
We are upgrading our Hadoop/HBase cluster from Hadoop 2.8.5 & HBase 2.2.5
to Hadoop 3.3.6 & HBase 2.5.7
The Hadoop upgrade worked well, but unfortunately we have problems with the
Hbase upgrade, because the master hangs on startup inside the „Starting
assignment manger“ task.
张铎(Duo Zhang) writes:
> OK, glad to hear that. Hope the rolling upgrading goes well
It did, kudos to the ZooKeeper and HBase teams for making it smooth
sailing, besides this little hiccup.
Best regards,
Adam
--
"Du frågor mig vad kärlek är Adam Sjøgren
should be able to run on JDK17
I think, at least, you need to provide your error logs, and related
environment variables.
On Wed, Apr 10, 2024 at 7:36 PM Bryan Beaudreault
wrote:
> I can’t answer that because I know nothing about your environment or the
> error you are receiving. For us it
I can’t answer that because I know nothing about your environment or the
error you are receiving. For us it just worked to start up. You may have to
change jvm flags in your hbase-env.sh if you are using old deprecated flags
that may be removed in jdk17.
On Wed, Apr 10, 2024 at 3:01 AM lisoda
Hi.
I am currently unable to start REGION using JDK17 directly. What adjustments do
I need to make to use JDK17/21?
Tks.
在 2024-04-09 18:52:34，"Bryan Beaudreault" 写道：
>We ran hbase under jdk17 for a few months. The only issue we saw was
+1 same here. gzip/lzo in the past, Snappy or zstd now.
On Tue, Apr 2, 2024 at 7:50 PM 张铎(Duo Zhang) wrote:
> For me I've never seen people actually use the xz compression.
>
> For size, usually people will choose gzip, and for speed, in the past
> people will choose lzo and now they choose
Let's remove in 2.6.0. I will submit a PR.
On Tue, Apr 2, 2024 at 7:50 PM 张铎(Duo Zhang) wrote:
> For me I've never seen people actually use the xz compression.
>
> For size, usually people will choose gzip, and for speed, in the past
> people will choose lzo and now they choose snappy or zstd.
We ran hbase under jdk17 for a few months. The only issue we saw was
https://issues.apache.org/jira/browse/HBASE-28206 which was fixed in 2.5.7.
More recently we’ve upgraded again to jdk21 to gain access to generational
zgc. That also has been working fine without any additional patches.
We’re
Hi.
I'm using HBase 2.5.8 and I'd like to upgrade the JDK version of the
RegionServer in my cluster to JDK17. Does anyone have any experience with this?
Tks.
Congratulations and welcome, Istvan!
On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's generous
Congratulations and welcome, Istvan!
On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's generous
Congratulations Istvan!!
Thanks,
Rajeshbabu.
On Tue, Apr 2, 2024, 8:53 PM Wei-Chiu Chuang wrote:
> congrats!
>
> On Tue, Apr 2, 2024 at 7:04 AM Pankaj Kumar
> wrote:
>
> > Congratulations Istvan, welcome !!
> >
> > Regards,
> > Pankaj
> >
> >
> > On Tue, Apr 2, 2024 at 4:53 PM Duo Zhang
Hi everyone,
As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.
We invite all projects and contributors to participate in the following
ways:
* Individuals - submit your first contribution:
For me I've never seen people actually use the xz compression.
For size, usually people will choose gzip, and for speed, in the past
people will choose lzo and now they choose snappy or zstd.
So for me I prefer we just deprecated the xz compression immediately
and remove it 2.6.0.
Thanks.
Congratulations Istvan, welcome !!
On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's generous
Congratulations Istvan!
Regards,
Shanmukha K
On Tue, Apr 2, 2024 at 10:39 AM Viraj Jasani wrote:
> Many Congratulations and Welcome, Istvan!!!
>
>
> On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Istvan Toth(stoty)
>
Congratulations Istvan, welcome !!
On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's generous
Congratulations Istvan !!
On Tue, 2 Apr 2024 at 08:53, Shanmukha Haripriya Kota
wrote:
> Congratulations Istvan!
>
> Regards,
> Shanmukha K
>
> On Tue, Apr 2, 2024 at 10:39 AM Viraj Jasani wrote:
>
> > Many Congratulations and Welcome, Istvan!!!
> >
> >
> > On Tue, Apr 2, 2024 at 4:23 AM Duo
Congratulations Istvan !!
On Tue, 2 Apr 2024 at 08:53, Shanmukha Haripriya Kota
wrote:
> Congratulations Istvan!
>
> Regards,
> Shanmukha K
>
> On Tue, Apr 2, 2024 at 10:39 AM Viraj Jasani wrote:
>
> > Many Congratulations and Welcome, Istvan!!!
> >
> >
> > On Tue, Apr 2, 2024 at 4:23 AM Duo
Congratulations Istvan!
Regards,
Shanmukha K
On Tue, Apr 2, 2024 at 10:39 AM Viraj Jasani wrote:
> Many Congratulations and Welcome, Istvan!!!
>
>
> On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Istvan Toth(stoty)
>
Many Congratulations and Welcome, Istvan!!!
On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's
Many Congratulations and Welcome, Istvan!!!
On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's
congrats!
On Tue, Apr 2, 2024 at 7:04 AM Pankaj Kumar
wrote:
> Congratulations Istvan, welcome !!
>
> Regards,
> Pankaj
>
>
> On Tue, Apr 2, 2024 at 4:53 PM Duo Zhang wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Istvan Toth(stoty)
> > has accepted the PMC's
Congratulations Istvan, welcome !!
Regards,
Pankaj
On Tue, Apr 2, 2024 at 4:53 PM Duo Zhang wrote:
> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan
Congratulations and welcome!
From: Duo Zhang
Date: Tuesday, April 2, 2024 at 13:23
To: HBase Dev List , hbase-user ,
user-zh
Subject: [ANNOUNCE] New HBase committer Istvan Toth
On behalf of the Apache HBase PMC, I am pleased to announce that
Istvan Toth(stoty)
has accepted the PMC's invitation
Congratulations and welcome!
From: Duo Zhang
Date: Tuesday, April 2, 2024 at 13:23
To: HBase Dev List , hbase-user ,
user-zh
Subject: [ANNOUNCE] New HBase committer Istvan Toth
On behalf of the Apache HBase PMC, I am pleased to announce that
Istvan Toth(stoty)
has accepted the PMC's invitation
On behalf of the Apache HBase PMC, I am pleased to announce that
Istvan Toth(stoty)
has accepted the PMC's invitation to become a committer on the
project. We appreciate all
of Istvan Toth's generous contributions thus far and look forward to
his continued involvement.
Congratulations and
On behalf of the Apache HBase PMC, I am pleased to announce that
Istvan Toth(stoty)
has accepted the PMC's invitation to become a committer on the
project. We appreciate all
of Istvan Toth's generous contributions thus far and look forward to
his continued involvement.
Congratulations and
Red Hat filed CVE-2024-3094 late last week on 2024-03-29. This implicates
recent releases of the native liblzma library as a vector for malicious
code.
This is not the pure Java version that we depend upon for HBase's support
for the LZMA algorithm (
Hello to all users, contributors and Committers!
[ You are receiving this email as a subscriber to one or more ASF project
dev or user
mailing lists and is not being sent to you directly. It is important that
we reach all of our
users and contributors/committers so that they may get a chance
That implementation is still incomplete, and PREFIX_TREE for index block
encoding is still unavailable.
Em ter., 26 de mar. de 2024 às 10:59, Bryan Beaudreault <
bbeaudrea...@apache.org> escreveu:
> INDEX_BLOCK_ENCODING is a new feature, but just the configuration exists.
> No actual encodings
1 - 100 of 41112 matches
Mail list logo
