I don't have a problem with having an examples module in the main repo, it
can be useful, and this way it is guaranteed to always work with the latest
version, and we don't have to maintain another repo.
Publishing the binary artifact to maven (as we do now) doesn't sound very
useful, but if
Should we remove hbase-examples from the main repository entirely? Should
it be its own download? Should we even ship it in binary form at all?
Anyway I’m fine with removing it from the assembly.
Thanks,
Nick
On Mon, 4 Mar 2024 at 13:27, Istvan Toth wrote:
> hbase assembly (and consequently
Pratyush Bhatt created HBASE-28419:
--
Summary: Allow Action and Policies of ServerKillingMonkey to be
configurable
Key: HBASE-28419
URL: https://issues.apache.org/jira/browse/HBASE-28419
Project:
Nihal Jain created HBASE-28418:
--
Summary: [JDK17] Jenkins build support for hbase-operator-tools
Key: HBASE-28418
URL: https://issues.apache.org/jira/browse/HBASE-28418
Project: HBase
Issue
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_392): ok
- mvn clean apache-rat:check -D skipTests=true
* Rat check (17.0.10): ok
- mvn clean apache-rat:check -D hadoop.profile=3.0 -D
skipTests=true
* Built from source
hbase assembly (and consequently the binary distributions) now depend on
hbase-examples.
I think this is problematic, as
* many of those examples are explicitly not production quality.
* It adds extra curator dependencies to the assembly and to the various
HBase classpaths. (whic the rest of
I’d say let’s do it. But if we want to do it for 2.6.0 then it’s be great
to put up a PR asap so it doesn’t block the release. I’m hoping to get the
RC0 out this week
On Mon, Mar 4, 2024 at 4:41 AM Nick Dimiduk wrote:
> On Fri, Mar 1, 2024 at 6:12 PM Andrew Purtell wrote:
>
> > I disagree. We
Duo Zhang created HBASE-28417:
-
Summary: TestBlockingIPC.testBadPreambleHeader sometimes fails
with broken pipe instead of bad auth
Key: HBASE-28417
URL: https://issues.apache.org/jira/browse/HBASE-28417
With 3 binding votes in the affirmative, 2 non-binding votes in the
affirmative, and no dissenting votes cast, this motion passes.
Thanks to everyone who took the time!
Thanks,
Nick
On Mon, Mar 4, 2024 at 11:54 AM Nick Dimiduk wrote:
> Here's my +1:
>
> * Signature: ok
> *
Here's my +1:
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_392): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_392): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_392): ok
- mvn clean package -P
On Fri, Mar 1, 2024 at 6:12 PM Andrew Purtell wrote:
> I disagree. We can keep the current defaults AND deprecate
> ZKConnectionRegistry as a warning to users that things will change in
> future releases. That is the entire reason for deprecation, yes?
>
Indeed. For me, there is value in
11 matches
Mail list logo
