accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-512) DEFAULT_MAX_LATENCY in AccumuloOutputFormat wrong units
Date Wed, 04 Apr 2012 13:55:22 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eric Newton resolved ACCUMULO-512.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.1
    
> DEFAULT_MAX_LATENCY in AccumuloOutputFormat wrong units
> -------------------------------------------------------
>
>                 Key: ACCUMULO-512
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-512
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: Dennis Patrone
>            Assignee: Billie Rinaldi
>            Priority: Minor
>             Fix For: 1.4.1
>
>
> In org.apache.accumulo.core.client.mapreduce.AccumuloOutputFormat, the DEFAULT_MAX_LATENCY
(line 88) is defined as:
> private static final int DEFAULT_MAX_LATENCY = 60; // 1 minute
> However, at line 233 that default value (assuming the key isn't set by the user) is provided
as an argument to createMultiTableBatchWriter().  The latency parameter there is documented
as milliseconds.  The DEFAULT_MAX_LATENCY should be set to 60000 if the desired default latency
value is 1 minute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message