drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Westin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-2625) org.apache.drill.common.StackTrace should follow standard stacktrace format
Date Mon, 30 Mar 2015 19:12:52 GMT

    [ https://issues.apache.org/jira/browse/DRILL-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387243#comment-14387243
] 

Chris Westin commented on DRILL-2625:
-------------------------------------

What's an example of a tool that parses stack traces?

> 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
>    Affects Versions: 0.8.0
>            Reporter: Daniel Barclay (Drill)
>            Assignee: Chris Westin
>
> 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-2624, 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