You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/06/05 19:50:00 UTC

[jira] [Commented] (ACCUMULO-4463) Make caching implementation configurable

    [ https://issues.apache.org/jira/browse/ACCUMULO-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856994#comment-16856994 ] 

Christopher Tubbs commented on ACCUMULO-4463:
---------------------------------------------

I've uploaded the abandoned patches from 2017 as an attachment, [^IGNITE-patches.tar.gz], so we can clean out the git repository of unmaintained branches.

> Make caching implementation configurable
> ----------------------------------------
>
>                 Key: ACCUMULO-4463
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4463
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Assignee: Dave Marion
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: IGNITE-patches.tar.gz
>
>          Time Spent: 15h 10m
>  Remaining Estimate: 0h
>
> It would be nice to make the caching implementation configurable. ACCUMULO-4177 introduced a new cache type.  Instead of Accumulo having a list of built in cache implementations, it could have a configuration property for specifying a block cache factory class.  Accumulo could ship with multiple implementations of this as it does after 4177 and allow users to easily experiment with implementations that Accumulo did not ship with.
> It would be nice to have ACCUMULO-3384, so that these custom cache impls could use that for custom config.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)