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 j
Simply cataloguing the CVE in Jira is a good start. The community can make
a decision as for how to handle each one, and that decision is recorded on
Jira, that ever the action may be.
On Wed, Apr 26, 2023 at 15:39 Wes Schuitema wrote:
> I'm having a bit of trouble creating actionable issues. So
I'm having a bit of trouble creating actionable issues. Some of the CVEs
are low impact and/or found in largely unused transitive dependencies.
Actually getting rid of the CVEs may not be worth the effort since the CVEs
are not applicable, or some mitigating measures are already in place. We
could
Wes Schuitema created HBASE-27817:
-
Summary: Migrate javax.el:3.0.1-b08 to jakarta.el-4.0.2
Key: HBASE-27817
URL: https://issues.apache.org/jira/browse/HBASE-27817
Project: HBase
Issue Type:
Nihal Jain created HBASE-27815:
--
Summary: Add support for process metrics servlet in REST InfoServer
Key: HBASE-27815
URL: https://issues.apache.org/jira/browse/HBASE-27815
Project: HBase
Issue
Nihal Jain created HBASE-27816:
--
Summary: Support option to auto bind to an available port for REST
Info Server
Key: HBASE-27816
URL: https://issues.apache.org/jira/browse/HBASE-27816
Project: HBase
Nihal Jain created HBASE-27814:
--
Summary: Add support for dump servlet in REST InfoServer
Key: HBASE-27814
URL: https://issues.apache.org/jira/browse/HBASE-27814
Project: HBase
Issue Type: Sub-t
Nihal Jain created HBASE-27813:
--
Summary: REST Info Server improvements
Key: HBASE-27813
URL: https://issues.apache.org/jira/browse/HBASE-27813
Project: HBase
Issue Type: Umbrella
Re