accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Coleman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3840) Refactor OpTimer so that it does not use log4j logger.
Date Sun, 24 May 2015 02:32:17 GMT

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

Ed Coleman updated ACCUMULO-3840:
---------------------------------
    Attachment: ACCUMULO-3840-1.patch

This replaces ACCUMULO-3840.patch.

Uses class (EventTimer) that is based on 2.7 hadoop class org.apache.hadoop.util.StopWatch.
 When 2.7 is minimum version, EventTimer can be replaced with that class.

This replacement uses nanoTime instead of millisecond timer.

Moved away from using Accumulo StopWatch because it does not provide a reset method and time
measured is accumulated.  

Accumulo StopWatch could be refactored to use EventTimer, but that is out of scope of log4j
dependency removal.
 

> Refactor OpTimer so that it does not use log4j logger.
> ------------------------------------------------------
>
>                 Key: ACCUMULO-3840
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3840
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 1.6.2, 1.7.0
>            Reporter: Ed Coleman
>            Assignee: Ed Coleman
>            Priority: Minor
>             Fix For: 1.8.0
>
>         Attachments: ACCUMULO-3840-1.patch, ACCUMULO-3840.patch
>
>
> OpTimer currently uses log4j specific classes. OpTimer and the callers can be modified
so that log4j dependencies are not required.
> The evaluation of timer consolidation raised in ACCUMULO-3329 can still be performed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message