Hi! Hbase is nearing 3.0, and this could be a good time to approach HBase about resolving any issues that hold Phoenix back, to see if they can be fixed in 3.0.
As many people are wearing both hats, the usual process is simply opening a HBase ticket (and ideally a PR) for what we need, which is great, but if there is some big ticket item, or you are just hesitant to approach HBase about something directly, a slightly more formal forum might be beneficial. These are the issues on my list (but these don't really need more discussion at this point) - Transitive Hadoop dependency CVE issues. Ongoing in HBASE-28846 <https://issues.apache.org/jira/browse/HBASE-28846> - Slimming down hbase mapredcp by factoring out Jetty-related functionality (recently discussed on the HBase list, this would need a POC) - Marking Private APIs used by Phoenix as LimitedPrivate (this would require an audit of Phoenix first, so that we know what to ask for) If you have any other changes / improvements in HBase in mind that you think would merit a formal project-to-project discussion, then let's discuss it. István
