Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 6 Jun 2014 14:40:02 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12680796.1385144285596.81864.1402065602212@arcas>
In-Reply-To: <JIRA.12680796.1385144285596@arcas>
References: <JIRA.12680796.1385144285596@arcas>
Subject: [jira] [Commented] (ACCUMULO-1919) Size of visibility cache in
 AccumuloFileOutputFormat should be configurable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser commented on ACCUMULO-1919:
--------------------------------------

Great! This LGTM. I'll run some tests with the patch applied, and then apply it if later today if no one else has any opinions/requests.

> Size of visibility cache in AccumuloFileOutputFormat should be configurable
> ---------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1919
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1919
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Mike Drob
>            Priority: Minor
>              Labels: newbie
>         Attachments: ACCUMULO-1919.patch, ACCUMULO-1919.patch
>
>
> AccumuloFileOutputFormat uses an LRUMap hard-coded to max size of 1000. It is possible that the client writing the data knows more about the visibility distribution and can specify a better value if this is made configurable.


--
This message was sent by Atlassian JIRA
(v6.2#6252)