Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 76C4A200BF8 for ; Fri, 9 Dec 2016 05:37:02 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7566B160B30; Fri, 9 Dec 2016 04:37:02 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 520D1160B38 for ; Fri, 9 Dec 2016 05:37:01 +0100 (CET) Received: (qmail 40039 invoked by uid 500); 9 Dec 2016 04:37:00 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 39979 invoked by uid 99); 9 Dec 2016 04:37:00 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2016 04:37:00 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 76BC82C0086 for ; Fri, 9 Dec 2016 04:37:00 +0000 (UTC) Date: Fri, 9 Dec 2016 04:37:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-5052) Option to debug generated Java code using an IDE MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 09 Dec 2016 04:37:02 -0000 [ https://issues.apache.org/jira/browse/DRILL-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734276#comment-15734276 ] ASF GitHub Bot commented on DRILL-5052: --------------------------------------- Github user paul-rogers commented on a diff in the pull request: https://github.com/apache/drill/pull/660#discussion_r91640094 --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/compile/JaninoClassCompiler.java --- @@ -58,5 +56,27 @@ public JaninoClassCompiler(ClassLoader parentClassLoader, boolean debug) { } @Override + public Map compile(final ClassNames className, final String sourceCode) + throws CompileException, IOException, ClassNotFoundException { + + ClassFile[] classFiles = doCompile( className, sourceCode ); + Map results = new HashMap<>( ); + for(int i = 0; i < classFiles.length; i++) { + ClassFile classFile = classFiles[i]; + results.put( classFile.getThisClassName(), classFile.toByteArray() ); + } + return results; + } + + public ClassFile[] doCompile(final ClassNames className, final String sourceCode) --- End diff -- Done. > Option to debug generated Java code using an IDE > ------------------------------------------------ > > Key: DRILL-5052 > URL: https://issues.apache.org/jira/browse/DRILL-5052 > Project: Apache Drill > Issue Type: Improvement > Components: Execution - Codegen > Affects Versions: 1.8.0 > Reporter: Paul Rogers > Assignee: Paul Rogers > Priority: Minor > > Drill makes extensive use of Java code generation to implement its operators. Drill uses sophisticated techniques to blend generated code with pre-compiled template code. An unfortunate side-effect of this behavior is that it is very difficult to visualize and debug the generated code. > As it turns out, Drill's code-merge facility is, in essence, a do-it-yourself version of subclassing. The Drill "template" is the parent class, the generated code is the subclass. But, rather than using plain-old subclassing, Drill combines the code from the two classes into a single "artificial" packet of byte codes for which no source exists. > Modify the code generation path to optionally allow "plain-old Java" compilation: the generated code is a subclass of the template. Compile the generated code as a plain-old Java class with no byte-code fix-up. Write the code to a known location that the IDE can search when looking for source files. > With this change, developers can turn on the above feature, set a breakpoint in a template, then step directly into the generated Java code called from the template. > This feature should be an option, enabled by developers when needed. The existing byte-code technique should be used for production code generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)