-1 for removing. spymemcached is only used in the test. Removing it requires the only unit test for this module to be removed. Why? What is the justification? Is there a CVE?
I have tested the hbase-external-blockcache module, after fixing it in HBASE-27796 <https://issues.apache.org/jira/browse/HBASE-27796> it does plausibly work. It provides an option to externalize the block cache. We were looking at it once at my work and still might consider it in the future. Combined with, ok, other significant changes, you can imagine for each table or namespace a separate external blockcache. This allows an operator to allocate cache resources for a customer's table or namespace and then the cache is dedicated to that customer and the costs of operating it are easily accounted to the customer for charge-back or show-back. On Mon, Dec 9, 2024 at 4:02 AM Istvan Toth <st...@apache.org> wrote: > Hi! > > The HBase assembly currently includes spymemcached. > > Memcached is used as the reference implementation of an external block > cache in hbase-external-blockcache. > > However, the memcached dependency is marked as optional, which suggests > that it was not meant to be included out of the box in the binary > distribution. > > Also, the last release of the spymemcached java library was back in 2017. > > I propose removing the spymemcached JAR from the assembly. > Those who still wish to use memcached external block cache support can > provide the jar separately. > > What do you think ? > Do you know anyone who uses HBase with memcached ? > > Istvan > -- Best regards, Andrew Unrest, ignorance distilled, nihilistic imbeciles - It's what we’ve earned Welcome, apocalypse, what’s taken you so long? Bring us the fitting end that we’ve been counting on - A23, Welcome, Apocalypse
