You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mikhail Bautin (Created) (JIRA)" <ji...@apache.org> on 2011/12/15 22:53:30 UTC
[jira] [Created] (HBASE-5048) Use
EnvironmentEdgeManager.currentTimeMillis() instead of
System.currentTimeMillis()
Use EnvironmentEdgeManager.currentTimeMillis() instead of System.currentTimeMillis()
------------------------------------------------------------------------------------
Key: HBASE-5048
URL: https://issues.apache.org/jira/browse/HBASE-5048
Project: HBase
Issue Type: Improvement
Reporter: Mikhail Bautin
Priority: Minor
We need to switch to using EnvironmentEdgeManager.currentTimeMillis() instead of System.currentTimeMillis() across the codebase to reduce confusion when writing tests that require custom timing of operations.
--
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
[jira] [Commented] (HBASE-5048) Use
EnvironmentEdgeManager.currentTimeMillis() instead of
System.currentTimeMillis()
Posted by "Chris Trezzo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449272#comment-13449272 ]
Chris Trezzo commented on HBASE-5048:
-------------------------------------
Do we want to add a check to HadoopQA to ensure that no new calls to System.currentTimeMillis() are added? If we think it is worth it, I can add a check.
Chris
> Use EnvironmentEdgeManager.currentTimeMillis() instead of System.currentTimeMillis()
> ------------------------------------------------------------------------------------
>
> Key: HBASE-5048
> URL: https://issues.apache.org/jira/browse/HBASE-5048
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Priority: Minor
>
> We need to switch to using EnvironmentEdgeManager.currentTimeMillis() instead of System.currentTimeMillis() across the codebase to reduce confusion when writing tests that require custom timing of operations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HBASE-5048) Use
EnvironmentEdgeManager.currentTimeMillis() instead of
System.currentTimeMillis()
Posted by "Chris Trezzo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Trezzo resolved HBASE-5048.
---------------------------------
Resolution: Duplicate
Dup'ing this. HBASE-6476 is more active.
> Use EnvironmentEdgeManager.currentTimeMillis() instead of System.currentTimeMillis()
> ------------------------------------------------------------------------------------
>
> Key: HBASE-5048
> URL: https://issues.apache.org/jira/browse/HBASE-5048
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Priority: Minor
>
> We need to switch to using EnvironmentEdgeManager.currentTimeMillis() instead of System.currentTimeMillis() across the codebase to reduce confusion when writing tests that require custom timing of operations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira