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

Lars Hofhansl updated HBASE-6476:
---------------------------------

    Description: 
There are still some areas where System.currentTimeMillis() is used in HBase. 
In order to make all parts of the code base testable and (potentially) to be 
able to configure HBase's notion of time, this should be generally be replaced 
with EnvironmentEdgeManager.currentTimeMillis().

How hard would it be to add a maven task that checks for that, so we do not 
introduce System.currentTimeMillis back in the future?

  was:
There are still some areas where System.currentTimeMillis() is used in HBase. 
In order to make all parts of the code base testable and (potentially) to be 
able to configure HBase's notion of time this should be generally replace 
EnvironmentEdgeManager.currentTimeMillis().

How hard would it be to add a maven task that check for that, so we do not 
introduce System.currentTimeMillis back in the future?

    
> Replace all occurrances of System.currentTimeMillis() with EnvironmentEdge 
> equivalent
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-6476
>                 URL: https://issues.apache.org/jira/browse/HBASE-6476
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Minor
>             Fix For: 0.94.2
>
>
> There are still some areas where System.currentTimeMillis() is used in HBase. 
> In order to make all parts of the code base testable and (potentially) to be 
> able to configure HBase's notion of time, this should be generally be 
> replaced with EnvironmentEdgeManager.currentTimeMillis().
> How hard would it be to add a maven task that checks for that, so we do not 
> introduce System.currentTimeMillis back in the future?

--
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

        

Reply via email to