drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Barclay (Drill) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-2625) org.apache.drill.common.StackTrace should follow standard stacktrace format
Date Mon, 30 Mar 2015 18:03:53 GMT
Daniel Barclay (Drill) created DRILL-2625:
---------------------------------------------

             Summary: org.apache.drill.common.StackTrace should follow standard stacktrace
format
                 Key: DRILL-2625
                 URL: https://issues.apache.org/jira/browse/DRILL-2625
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Daniel Barclay (Drill)


org.apache.drill.common.StackTrace uses a different textual format than JDK's standard format
for stack traces.

It should probably use the standard format so that its stack trace output can be used by tools
that already can parse the standard format to provide functionality such as displaying the
corresponding source.

(After correcting for DRILL-xxxx, StackTrace formats stack traces like this:

org.apache.drill.common.StackTrace.<init>:1
org.apache.drill.exec.server.Drillbit.run:20
org.apache.drill.jdbc.DrillConnectionImpl.<init>:232

The normal form is like this:
	at org.apache.drill.exec.memory.TopLevelAllocator.close(TopLevelAllocator.java:162)
	at org.apache.drill.exec.server.BootStrapContext.close(BootStrapContext.java:75)
	at com.google.common.io.Closeables.close(Closeables.java:77)
)





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

Mime
View raw message