+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_382): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_382): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_382): failed
- mvn clean package
en a PR for branch-2.x too, so we can catch the
>> differences between the 2 PRs, and whether to align them.
>>
>> WDYT?
>>
>> Thanks.
>>
>> Andrew Purtell 于2024年5月7日周二 20:20写道：
>>>
>>> I don’t expect 2.x to wind down for up to several
anch-2.x too, before mering the master PR, we should make sure the
> contributor open a PR for branch-2.x too, so we can catch the
> differences between the 2 PRs, and whether to align them.
>
> WDYT?
>
> Thanks.
>
> Andrew Purtell 于2024年5月7日周二 20:20写道：
>>
>> I
This sounds very reasonable to me, especially with the promise of a quick
follow on release of 2.6.1.
—
I apologize for not voting on the 2.6 candidates. I will set up a VM
somewhere where I can drive release candidate tests by phone for the next
time but did not think of this in advance.
On
that the
> > > initial
> > > > release of java11 was released 6 years ago and java17 released 3
> years.
> > > > Java21 is already released as well. So I could see java17 being
> widely
> > > > available enough that we could jump "in the middle" r
I also agree that mitigation of security problems in dependencies will be
increasingly difficult, as we cannot expect our dependencies to continue to
support Java 8. They might, but as time goes on it is less likely.
A minimum of Java 11 makes a lot of sense. This is where the center of
+1 (binding)
* CHANGES.md and RELEASENOTES.md: ok
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_382): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_382): ok
- mvn clean install -DskipTests
* Unit tests pass
appy or zstd.
>
> So for me I prefer we just deprecated the xz compression immediately
> and remove it 2.6.0.
>
> Thanks.
>
> Andrew Purtell 于2024年4月2日周二 08:02写道：
> >
> > Red Hat filed CVE-2024-3094 late last week on 2024-03-29. This implicates
> > recent
That makes sense.
Their support for protobuf-java 3.x ends in one year from now, and that is only
for 3.25.x.
> On Apr 5, 2024, at 5:47 AM, 张铎 wrote:
>
> When bumping dependency versions for hbase-thirdparty, I found that
> the next version for 3.25.x is 4.26.x...
>
> After investigating,
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
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 (
gt; > > We already commit the changes to master I believe. Let me see if we
> > > can cherry-pick them and commit to branch-2.6 as well.
> > >
> > > Thanks.
> > >
> > > Bryan Beaudreault 于2024年3月22日周五 07:35写道：
> > > >
> > >
The hadoop3 bin tarball for 2.5.8 is 352.8MB. Perhaps we have just barely
and recently crossed a threshold. File an INFRA JIRA and ask about it.
Perhaps some limit can be increased, or maybe they will ask us to live
within it.
Related, looking at the 2.5.8 hadoop3 bin tarball, the majority of the
The HBase team is happy to announce the immediate availability of HBase
2.5.8.
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
With 4 binding +1 votes, including my own, and one non-binding +1 vote, and
no 0 or -1 votes, this vote passes.
Thanks to everyone who evaluated the release candidate!
On Fri, Mar 1, 2024 at 1:40 PM Andrew Purtell wrote:
> Please vote on this Apache HBase release candidate, 2.5.8
of
> HBase", released in 3.0.0-alpha-1
> * HBASE-26067 -- "Change the way on how we track store file list", released
> in 2.6.0
> * HBASE-26233 -- "The region replication framework should not be built upon
> the general replication framework", released
PMC,
We need one more binding +1 in order to complete this VOTE.
Currently we have two binding +1s, one from myself and one from Nick, and
one nonbinding +1 from Rajeshbabu.
On Fri, Mar 1, 2024 at 1:40 PM Andrew Purtell wrote:
> Please vote on this Apache HBase release candidate, 2.5.8
Please vote on this Apache HBase release candidate, 2.5.8RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase 2.5.8
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.5.8RC0:
https://github.com/apache/hbase/tree/2.5.8RC0
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_382): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_382): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_382): ok
- mvn clean package -P
> > >
> > > > And in fact, I now realize that something like it will continue to
> > exist
> > > > even after the class is removed from our public API because I suspect
> > > that
> > > > the HMaster will need to use it in order to bootst
ate it in 2.6 and remove it in 4.0.
> This is how the HBase 2.x API changes were handled, where the removal of
> the old HBase 1.x APIs were targeted to 3.0.
> The ZK registry code is small, and doesn't cost much to keep in the
> codebase.
>
> Istvan
>
> On Fri, Mar 1, 20
+1 for deprecating ZKConnectionRegistry beginning with/in 2.6.0.
On Thu, Feb 29, 2024 at 2:30 AM Nick Dimiduk wrote:
> Heya,
>
> We have long had the ambition to get away from ZooKeeper as the means by
> which a client interfaces with an HBase cluster. The ConnectionRegistry was
> introduced
We have had this discussion before about other list* methods and we have
sometimes decided to restrict them to ADMIN. The reason for that was the
information returned by the method might leak sensitive information. For
example, listing table descriptors will include all arbitrary and
potentially
It's been about two months since 2.5.7 and 2.5.8 has 42 completed issues (
https://issues.apache.org/jira/projects/HBASE/versions/12354047). Looks
like we are due another 2.5 release.
I plan to spin a release candidate toward the end of this week and submit
it for voting next week on the Monday.
> Would like to gather opinion on which branches should we prioritize/enable
> JDK 17 pipelines
master
branch-3
When the JDK 17 pipelines have stabilized for those, then consider branch-2
and the release branches. Probably by then most issues would have a prior
developed solution that can be
Sounds right to me.
On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk wrote:
> Heya team,
>
> I noticed that we still have thirdparty-3.5.2 as an unreleased version in
> Jira. Looking at the release archives [0], I don't see that release in our
> history -- it appears that the world has moved on.
f we
> think this is a useful new feature, we could open an issue and also
> design doc.
>
> Thanks.
>
> Andrew Purtell 于2024年2月9日周五 11:09写道：
> >
> > Agreed, the key is going to be changing the design of references to
> support this new.
> >
> > Spli
me when
> splitting, and also the fail recovery will be more complicated.
>
> Thanks.
>
> Bryan Beaudreault 于2024年2月9日周五 09:27写道：
>>
>> Yep, I forgot about that nuance. I agree we can add a splitRegion overload
>> which takes a byte[][] for multiple spl
Rushabh already covered this but splitting is not complete until the region
can be split again. This is a very important nuance. The daughter regions
are online very quickly, as designed, but then background housekeeping
(compaction) must copy the data before the daughters become splittable.
I have not thought out the idea in detail but it seems to me this is less
about splitting and more about normalization. That is, the table exists on
both sides, and what we want is to apply a series of transformations to the
region boundaries to bring them closer in alignment such that then a
ssible, I could potentially fix these.
>>>> Thanks for the guidance.
>>>> On Tue, Jan 16, 2024 at 12:54 PM Bryan Beaudreault <
>>>> bbeaudrea...@apache.org>
>>>> wrote:
>>>>> Thank you both for the input. That's a good idea And
I was the original developer of this feature. It existed in pretty much the
same form in Hive and was a straightforward port. The style of using enums to
encode and restrict supported parameters came from the origin. I thought it a
good idea, though, because this shells out to an external
For 2.5.0 I based the change log on the change log of what was then the
last/most recent 2.4 release. Anything committed into 2.4 with a fix version of
2.5, I dropped the 2.5 fix version. The 2.5 fix version was kept for anything
novel in 2.5. The result was an orderly cumulative change log. I
e.
>
> Otherwise, I agree with everything else. I have the PR ready for updating
> netty in hbase-thirdparty. I can also vote and do the bump of
> hbase-thirdparty.version in hbase once the release is made.
>
> On Thu, Jan 4, 2024 at 3:15 PM Andrew Purtell wrote:
>
> > We sh
://issues.apache.org/jira/browse/HBASE-28291 to update
> pom.xml in hbase-thirdparty. I will handle that. We will need to do an
> hbase-thirdparty release, which I'm not sure I'll have time for given I'm
> already behind on the 2.6.0 release
>
> On Thu, Jan 4, 2024 at 11:58 AM And
We should do that bump to hbase-thirdparty and spin another release to keep our
house in order. It isn’t urgent but would be good to address this in the normal
release cadence. That has been about once per fiscal quarter recently. It’s
weird to have netty dependency versions diverging.
I
The HBase team is happy to announce the immediate availability of HBase
2.5.7.
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
With four binding +1s, including my own, and no 0 or -1 votes, this vote
passes.
Thanks to everyone who voted on this release candidate!
On Mon, Dec 18, 2023 at 4:37 PM Andrew Purtell wrote:
> Please vote on this Apache HBase release candidate, 2.5.7RC0
>
> The VOTE will re
so for replication, we may find that there is already a new
>> file in the queue but when reading the previous file, we can not read
>> the trailer yet, thus we consider the WAL file as not closed cleanly.
>>
>> Let me check how do we deal with this on master and branch-3.
Please file or promote an existing JIRA for this test issue (I seem to
recall some have been opened and closed over the previous months) so we can
track them. If you set a fix version of 2.5.8 it will be an effective
reminder.
On Wed, Dec 20, 2023 at 9:59 AM Andrew Purtell wrote:
> This t
tent
> off-by-one failure
>
>
>
> On Mon, Dec 18, 2023 at 10:38 PM Andrew Purtell
> wrote:
>
> > Please vote on this Apache HBase release candidate, 2.5.7RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this
amFSHLog
> fails nearly 100% of times.
>
> I think we need to find out whether this is just a test issue, if not
> we need to find out the root cause and fix it.
>
> Thanks.
>
> Andrew Purtell 于2023年12月19日周二 05:38写道：
> >
> > Please vote on this Apache HBase release can
Please vote on this Apache HBase release candidate, 2.5.7RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase 2.5.7
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.5.7RC0:
https://github.com/apache/hbase/tree/2.5.7RC0
In the upcoming 2.5.7RC0 you will notice in the compatibility report an
impact due to a recent upgrade of our ZooKeeper dependencies to deal with a
CVE issue in ZooKeeper. As 2.5 RM, I ask you to ALLOW these changes, for
these reasons:
- The ZooKeeper dependency must be upgraded because ZooKeeper
HBASE-28248 is resolved, proceeding.
On Thu, Dec 7, 2023 at 8:07 AM Andrew Purtell
wrote:
> If I could edit the thread subject I would.
>
> > HBASE-28248
>
> Noted.
>
> > On Dec 6, 2023, at 10:44 PM, 张铎 wrote:
> >
> > You must mean 2.5.7 :)
> &
If I could edit the thread subject I would.
> HBASE-28248
Noted.
> On Dec 6, 2023, at 10:44 PM, 张铎 wrote:
>
> You must mean 2.5.7 :)
>
> I think we should include HBASE-28248 , as HBASE-28210 and HBASE-28212
> has already been committed to branch-2.5.
>
> Andre
Some important fixes in branch-2.5. Let's do one more 2.5 release this
year, 2.5.6.
If you have any pending work, please try to commit it before Thursday of
this week. I will start the work of cutting RC0 then. If you are aware of
any potentially blocking issues feel free to raise them on this
change. At the very
> least, updating the doc would be good. I'll try to remember to do that when
> I have time.
>
> On Thu, Nov 30, 2023 at 12:24 PM Andrew Purtell
> wrote:
>
> > Maven automates the change so the human does not edit the POM files by
> > hand. A PR
ten enough time to do it since it is
> not easy for me as I'm not a jenkins expert...
>
> Andrew Purtell 于2023年11月30日周四 10:45写道：
>>
>> It seems silly to do a review just for a change that modifies the project
>> version. I mean, it's trivial to "mvn versi
related operations
> in a release tool, I do not think we need the signoff, just running
> the automatic tool is fine, but now it still requires manual
> operations, so I think having a double check is better.
>
> Thanks.
>
> Andrew Purtell 于2023年11月30日周四 02:45写道：
> >
> &g
> > Just send a notice to the dev mailing list, and then use the
> normal
> > >> > > git way to create a new branch called branch-2.6 from branch-2,
> push
> > >> > > it to github, done :)
> > >> > >
> > >> > > Bryan Beaudreault 于20
The HBase team is happy to announce the immediate availability of HBase
2.5.6.
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
With 4 binding +1s, including my own, and 3 non-binding +1 votes, and no 0
or -1 votes, this vote passes.
Thanks to all who voted on the release!
On Mon, Oct 16, 2023 at 11:23 AM Andrew Purtell wrote:
> Please vote on this Apache HBase release candidate, 2.5.6RC0.
>
> The VOTE will re
> > Hi Bryan, do we still have any blocker issues for cutting branch-2.6
> > > and starting to release 2.6.0?
> > >
> > > Thanks.
> > >
> > > Andrew Purtell 于2023年9月26日周二 01:02写道：
> > > >
> > > > Thanks Duo
Please vote on this Apache HBase release candidate, 2.5.6RC0.
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase 2.5.6
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.5.6RC0:
https://github.com/apache/hbase/tree/2.5.6RC0
Thank you Viraj.
> On Sep 25, 2023, at 6:14 PM, Viraj Jasani wrote:
>
> Apologies, I am bit occupied this week. Let me take a look tomorrow.
>
>> On Mon, Sep 25, 2023 at 10:04 AM Andrew Purtell wrote:
>>
>> The blocker is HBASE-28081. The regression is from
The blocker is HBASE-28081. The regression is from HBASE-28042
On Mon, Sep 25, 2023 at 9:57 AM Andrew Purtell wrote:
> HBASE-28042 is blocking. Let's see about resolving it soon.
>
HBASE-28042 is blocking. Let's see about resolving it soon.
On Thu, Sep 21, 2023 at 11:24 AM Andrew Purtell wrote:
> We are holding 2.6.0 for the resolution of some thirdparty related changes
> but can proceed with the next 2.5.
>
> If you have something pending for 2.5.6, please t
081, but anyway we have already
> found the root cause is HBASE-28042, so I think it will be fixed soon.
>
> All other issues have been resolved.
>
> Thanks.
>
> Andrew Purtell 于2023年9月22日周五 02:21写道：
> >
> > Both sound good, thanks.
> >
> >
> > O
We are holding 2.6.0 for the resolution of some thirdparty related changes
but can proceed with the next 2.5.
If you have something pending for 2.5.6, please try to commit it before
this coming Monday. (9/25)
Best regards,
Andrew
he RC yet, please also include HBASE-28061 in
> > > > > 2.5.6, as it could solve the problem for running pre compiled 2.5.x
> > > > > tarball and also our published artifacts in maven repo against
> hadoop
> > > > > 3.3.x.
> > > > &g
ed artifacts in maven repo against hadoop
> > 3.3.x.
> >
> > The hive community needs this as they want to upgrade hbase and hadoop
> > dependencies.
> >
> > Thanks.
> >
> > Andrew Purtell 于2023年8月30日周三 06:48写道：
> > >
> > > I am back from vacatio
lem, HBASE-27941, which is found
> when running ITBLL against branch-3.
>
> Viraj reported that it also affects branch-2.x.
>
> Buy anyway, since it also affects branch-2.5, should not be a blocker
> for branch-2.6.
>
> Andrew Purtell 于2023年8月31日周四 00:50写道：
> >
ult <
> bbeaudrea...@apache.org>
> > wrote:
> >
> > > I made
> > > https://issues.apache.org/jira/browse/HBASE-28010 a blocker so we
> don’t
> > > release a broken new feature. We will have it fixed early this week.
> > >
> > > On Fri, Aug
I am back from vacation. Slowly clearing my inbox. 1,545 unread, it's been
a while.
It seems we are ready to cut branch-2.6 for stabilizing for 2.6.0. Any
volunteers to RM 2.6.0? Otherwise I'm happy to do it, starting next week,
probably 9/5 or 9/6.
Some good changes have landed in branch-2.5.
Yes I think it is about time too.
I’m back from vacation next week and can do a release then unless you want to
do it Duo.
> On Aug 23, 2023, at 9:49 AM, 张铎 wrote:
>
> Bump.
>
> If the release managers are not available, I could help make the next
> 2.5.x release.
>
> Thanks.
>
> 张铎(Duo
ough we were
>>>>> comparing against our legacy haproxy setup and can't really compare
>>> against
>>>>> kerberos.
>>>>>
>>>>> One outstanding issue is
>>> https://issues.apache.org/jira/browse/HBASE-27782,
>>>>> which w
The HBase team is happy to announce the immediate availability of HBase
2.5.5.
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
With five binding +1, including my own, and one non-binding +1, and no 0 or
-1 votes, this vote passes.
Thanks to all who voted on the release candidate!
On Fri, Jun 2, 2023 at 9:20 AM Andrew Purtell wrote:
> Please vote on this Apache hbase release candidate, hbase-2.5.5RC0
>
>
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (11.0.19): ok
- mvn clean apache-rat:check
* Built from source (11.0.19): ok
- mvn clean install -DskipTests
* Unit tests pass (11.0.19): failed
- mvn clean package -P
Please vote on this Apache hbase release candidate, hbase-2.5.5RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase 2.5.5
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.5.5RC0:
, 2023 at 10:21 AM Andrew Purtell wrote:
> Please vote on this Apache hbase release candidate,
> hbase-2.5.5RC0
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase 2.5.5
> [ ] -1 Do not release this package because ...
&g
ons.
>
> Thanks.
>
> Andrew Purtell 于2023年5月27日周六 08:39写道：
>
> > I tried to make a release but ran into HBASE-27894.
> >
> > Next week.
> >
> > On Thu, May 25, 2023 at 5:24 PM Andrew Purtell
> > wrote:
> >
> > > All open issues res
Please vote on this Apache hbase release candidate,
hbase-2.5.5RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase 2.5.5
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.5.5RC0:
I tried to make a release but ran into HBASE-27894.
Next week.
On Thu, May 25, 2023 at 5:24 PM Andrew Purtell wrote:
> All open issues resolved or moved. Cutting RC0 tomorrow.
>
> On Mon, May 8, 2023 at 11:17 AM Andrew Purtell
> wrote:
>
>> https://issues.apache.or
All open issues resolved or moved. Cutting RC0 tomorrow.
On Mon, May 8, 2023 at 11:17 AM Andrew Purtell wrote:
> https://issues.apache.org/jira/projects/HBASE/versions/12353053
>
> There are 24 resolved issues marked with the fix version of 2.5.5, a few
> in progress, and ~30 pe
https://issues.apache.org/jira/projects/HBASE/versions/12353053
There are 24 resolved issues marked with the fix version of 2.5.5, a few in
progress, and ~30 pending issues to evaluate. I'm going to go through them
this week and hopefully cut a RC for 2.5.5 by the end of this week.
If you have
+1
> On May 5, 2023, at 12:13 AM, 张铎 wrote:
>
> As discussed in the online meeting, and also other places, before EOL
> 2.4.x, we should first move our stable pointer to 2.5.x.
>
> And there are also som2.5.x usages around the community on large clusters
> which proves that the release can
Congratulations and welcome, Nihal!
On Wed, May 3, 2023 at 5:12 AM Nick Dimiduk wrote:
> Hello!
>
> On behalf of the Apache HBase PMC, I am pleased to announce that Nihal Jain
> has accepted the PMC's invitation to become a committer on the project. We
> appreciate all of Nihal's generous
Gmail manages it pretty well for me, as a data point. Iteresting mails are
promoted to the inbox. Other mail clients have similar features.
I haven't been around much over the past month or so, so my hbase folder
has > 1000 messages in it. It is true that discussions in dev@ are buried
among the
The HBase team is happy to announce the immediate availability of HBase
2.5.4.
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
With 5 +1 votes, and no 0 or -1 votes, this vote passes.
Thanks to all who voted on the release candidate.
On Thu, Apr 6, 2023 at 10:03 PM Andrew Purtell wrote:
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache HBase 2.5.4
> [ ] -1 Do
Thank you, everyone. I will close the vote tomorrow (Friday), Pacific day
time.
On Wed, Apr 12, 2023 at 8:50 PM 张铎(Duo Zhang) wrote:
> Will take a look today.
>
> Andrew Purtell 于2023年4月13日周四 05:31写道：
>
> > Between Stephen and myself we have 2 +1 votes, but need a
Between Stephen and myself we have 2 +1 votes, but need at least one more.
--
Best regards,
Andrew
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase 2.5.4
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.5.4RC0:
https://github.com/apache/hbase/tree/2.5.4RC0
This tag currently points to git reference
n
> > the roadmap.
> >
> > It seems like cloudera may be closer to integrating TLS in production.
> > Balazs recently filed and fixed HBASE-27673 related to mTLS. Maybe he can
> > chime in on his status, or let me know if I am totally off base :)
> >
> > On Sun,
s.
>
> Mallikarjun 于2022年10月17日周一 02:09写道：
>
>> On hbase-backup, we are using in production for more then 1 year. I can
>> vouch for it to be stable enough to be in a release version so that more
>> people can use it and polished it further.
>>
>>
+1, I can also help if we need a RM, although you did great last time,
Stephen.
On Fri, Mar 24, 2023 at 8:58 AM Tak Lon (Stephen) Wu
wrote:
> +1, I can help and see if anyone shows interests
>
> -Stephen
>
> On Fri, Mar 24, 2023 at 12:17 AM Nick Dimiduk wrote:
> >
> > On Fri, Mar 24, 2023 at
I hope that such an effort could lead to a
> review and abstraction of how authentication and authorization are handled
> in Hadoop generally.
>
>> On Fri, Mar 17, 2023 at 6:51 PM Andrew Purtell wrote:
>>
>> We have also completed a migration to kubernetes (more specifical
We have also completed a migration to kubernetes (more specifically, EKS)
at $dayjob. Our basic deployment stack is helm, terraform, and spinnaker,
so we took a different approach in implementation. I think we would be
happy to review and offer advice/opinion/suggestion on points of
commonality,
posal when we change the base interface/abstract
>> class
>>> in FileSystem (if it's non-backward compatible). The discussion here
>> helps
>>> to confirm the direction, and let's see how we can make it generic and
>>> could help to avoid confusion in both
.
> On Mar 15, 2023, at 1:53 PM, Sean Busbey wrote:
>
> the check that Stephen is referring to is for logic around lease recovery
> and not stream flush/sync. the lease recovery is specific to DFS IIRC and
> doesn't have a FileSystem marker.
>
>> On Wed, Mar 15, 2023 a
sks. That way it is future proofing.
Also a good idea.
>
>> On Wed, Mar 15, 2023 at 12:50 PM Andrew Purtell wrote:
>>
>> Does Hadoop have a marker interface that lets an application know its
>> FileSystem instances can support hsync/hflush? Ideally all we should need
>>
the FS Data OutputStream probe fails for
> Hflush/Hsync:
>
> StreamLacksCapabilityException(StreamCapabilities.HFLUSH)
> and
> StreamLacksCapabilityException(StreamCapabilities.HSYNC)
>
>
> On Wed, Mar 15, 2023 at 12:51 PM Andrew Purtell
> wrote:
>
> > Doe
Does Hadoop have a marker interface that lets an application know its
FileSystem instances can support hsync/hflush? Ideally all we should need
to do is test with instanceof for that marker and use reflection (in the
worst case) to get a handle to the hsync or hflush method, and then call
it. This
gt; and
>>> APIs that make an implementation possible than in any specific
>>> implementation. I’d also like to see consideration for a cluster-wide
>>> compaction scheduler, something to prioritize allocation of precious IO
>>> resources.
>>>
>>&g
Approved the PR.
I see the self service portal is already mailing us about requests. I
approved one a few minutes ago.
On Mon, Mar 6, 2023 at 2:02 AM 张铎(Duo Zhang) wrote:
> https://selfserve.apache.org/jira-account.html
>
> The INFRA team has delivered a self serving tool for requesting a jira
Hi Rajesbabu,
You have proposed a solution without describing the problem. Please do that
first.
That said, compaction is fundamental to HBase operation and should have no
external dependency on a particular compute framework. Especially
MapReduce, which is out of favor and deprecated in many
As you point out these configuration settings were introduced when we migrated
from SequenceFile based WALs to the protobuf format. We needed to give users a
way to manually migrate, although, arguably, an auto migration would have been
better.
In theory these settings allow users to
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_332): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_332): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_332): failed, see below
- mvn
1 - 100 of 4922 matches
Mail list logo
