Xiaolin Ha created HBASE-26434:
--
Summary: Do compact when all L0 files are expired
Key: HBASE-26434
URL: https://issues.apache.org/jira/browse/HBASE-26434
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-26412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-26412.
---
Fix Version/s: HBASE-26233
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to branch HBA
[
https://issues.apache.org/jira/browse/HBASE-26410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-26410.
---
Fix Version/s: 2.5.0
3.0.0-alpha-2
2.4.9
Hadoop Flags: Rev
[
https://issues.apache.org/jira/browse/HBASE-26271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-26271.
---
Fix Version/s: HBASE-26067
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to branch HBA
Rushabh Shah created HBASE-26435:
Summary: [branch-1] The log rolling request maybe canceled
immediately in LogRoller due to a race
Key: HBASE-26435
URL: https://issues.apache.org/jira/browse/HBASE-26435
[
https://issues.apache.org/jira/browse/HBASE-26433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HBASE-26433.
--
Hadoop Flags: Reviewed
Resolution: Fixed
Thanks for the reviews [~apurtell] [~gjacoby] [
Heya,
I've been kicking the tires on the OpenTelemetry tracing work and I have an
ugly question to present. One of the things suggested by the otel community
is that library implementers (like us, with hbase-client) expose the
Span/Scope objects to callers so that they can add context annotations.
Nick Dimiduk created HBASE-26436:
Summary: check-aggregate-license error related to javadns after
HADOOP-17317
Key: HBASE-26436
URL: https://issues.apache.org/jira/browse/HBASE-26436
Project: HBase
If it was akin to slf4j, that integration has been relatively smooth
for downstream.
log4j effectively being in our public api through configuration
formats has been a maintenance nightmare.
These would effectively be in our java binary API though, right? Would
we gain any meaningful isolation fr
Josh Elser created HBASE-26437:
--
Summary: [hboss] Rename does not clean up znodes for src location
Key: HBASE-26437
URL: https://issues.apache.org/jira/browse/HBASE-26437
Project: HBase
Issue Ty
What does ‘expose’ actually mean here?
I think a typical usage is that, users create a span and a scope, and in
the scope they call our client API, and our client API will make use of the
Span in the current scope?
So at least we need to let users know they have to use otel if they want to
trace
Let me find some clarification on what/how might be exposed.
On Tue, Nov 9, 2021 at 3:34 PM 张铎(Duo Zhang) wrote:
> What does ‘expose’ actually mean here?
>
> I think a typical usage is that, users create a span and a scope, and in
> the scope they call our client API, and our client API will mak
[
https://issues.apache.org/jira/browse/HBASE-26426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-26426.
---
Hadoop Flags: Reviewed
Release Note: HBase now uses github PR for submitting and reviewing
patch
chenglei created HBASE-26438:
Summary: Fix flaky test
TestHStore.testCompactingMemStoreCellExceedInmemoryFlushSize
Key: HBASE-26438
URL: https://issues.apache.org/jira/browse/HBASE-26438
Project: HBase
14 matches
Mail list logo
