Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 20 Nov 2014 20:58:33 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12756815.1416517059000.548054.1416517113644@Atlassian.JIRA>
In-Reply-To: <JIRA.12756815.1416517059000@Atlassian.JIRA>
References: <JIRA.12756815.1416517059000@Atlassian.JIRA>
 <JIRA.12756815.1416517059777@arcas>
Subject: [jira] [Created] (ACCUMULO-3355) TraceDump.printStackTrace prints
 Long.MAX_VALUE as a date when trace is not found
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Josh Elser created ACCUMULO-3355:
------------------------------------

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


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)