I'm +0 on hbase-examples, but +100 on any improvements we can make to
ltt/pe/chaos/minicluster/etc. It's extremely frustrating how much reliance
we have on test jars both generally but also specifically around these core
test executables. Unfortunately I haven't had time to dedicate to these
Thank you for bringing this up.
+1 for this change.
In fact, some time back, we had faced similar problem. Security scans found
that we were bundling some vulnerable hadoop test jar. To deal with that we
had to make a change in our internal HBase fork to exclude all HBase and
Hadoop test jars
David Manning created HBASE-28422:
-
Summary: SplitWalProcedure will attempt SplitWalRemoteProcedure on
the same target RegionServer indefinitely
Key: HBASE-28422
URL:
Pratyush Bhatt created HBASE-28421:
--
Summary: Add ofs (Ozone Filesystem) support for
acquireDelegationToken
Key: HBASE-28421
URL: https://issues.apache.org/jira/browse/HBASE-28421
Project: HBase
This sounds great to me.
The current PR does this, so I think we are all in agreement.
On Tue, Mar 5, 2024 at 10:49 AM 张铎(Duo Zhang) wrote:
> I prefer we still have the hbase-examples in the main repo and publish
> it to maven central, but we do not need to ship it in the binary
> releases. The
This would be great cleanup, big +1 from me for all three of these
adjustments, including the promotion of pe, ltt, and friends out of the
test scope.
I believe that we included hbase test jars because we used to freely mix
classes needed for minicluster between runtime and test jars, which in
I prefer we still have the hbase-examples in the main repo and publish
it to maven central, but we do not need to ship it in the binary
releases. The most important thing for hbase-examples is its source
code, so including it in binary releases does not help.
Istvan Toth 于2024年3月5日周二 03:28写道：
>
I agree, we don't want to omit those from the binary distro.
We should identify what those tools are. (Should be easy based on the
presence of main() or the Tool interface)
Such tools could either be moved into a new module, like hbase-tools, or
simply moved to the runtime JARs.
Istvan
On Tue,
[
https://issues.apache.org/jira/browse/HBASE-28379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-28379.
--
Resolution: Fixed
This is merged. FYI [~bbeaudreault].
> Upgrade thirdparty dep to 4.1.6
>
There are some tools in the tests jar, such as PerformanceEvaluation.
But anyway, maybe they should be moved to main...
Istvan Toth 于2024年3月5日周二 16:14写道：
>
> DISCLAIMER: I don't have a patch ready, or even an elegant way mapped out
> to achieve this, this is about discussing whether we even
Umesh Kumar Kumawat created HBASE-28420:
---
Summary: Aborting Active HMaster is not rejecting remote Procedure
Reports
Key: HBASE-28420
URL: https://issues.apache.org/jira/browse/HBASE-28420
DISCLAIMER: I don't have a patch ready, or even an elegant way mapped out
to achieve this, this is about discussing whether we even want to make
these changes.
These are also substantial changes, but they could be targeted for HBase
3.0.
One issue I have noticed is that we ship test jars and test
12 matches
Mail list logo
