You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/11/21 22:44:33 UTC
[jira] [Commented] (ACCUMULO-3355) TraceDump.printStackTrace prints
Long.MAX_VALUE as a date when trace is not found
[ https://issues.apache.org/jira/browse/ACCUMULO-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221467#comment-14221467 ]
Josh Elser commented on ACCUMULO-3355:
--------------------------------------
Turns out I broke ConditionalWriterIT#testTrace by doing this. Fixing it up here.
> TraceDump.printStackTrace prints Long.MAX_VALUE as a date when trace is not found
> ---------------------------------------------------------------------------------
>
> Key: ACCUMULO-3355
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3355
> Project: Accumulo
> Issue Type: Bug
> Components: trace
> Affects Versions: 1.6.1
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Trivial
> Fix For: 1.6.2, 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> If no trace is found in the trace table, we convert Long.MAX_VALUE to a date (yyyy/MM/dd) and print that out.
> That's rather silly -- an alternate message should be printed stating that there were no entries found in the trace table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)