[DRILL-5116] Enable generated code debugging in each Drill operator

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.10.0
• Labels: ready-to-commit
• Assignee: Paul Rogers
• Reporter: Paul Rogers
• Reviewer: Boaz Ben-Zvi
• Created: 08/Dec/16 23:44
• Updated: 28/Mar/17 22:37
• Resolved: 11/Jan/17 02:32

Description

DRILL-5052 adds the ability to debug generated code. Some of the code generated by Drill's operators has minor problems when compiled directly using the new technique. These issues are ignore by the byte-code-merge technique uses in production. This ticket asks to try the DRILL-5052 feature in each operator, clean up any minor problems, and ensure each operator generates code suitable for debugging. Use the new CodeGenerator.plainOldJavaCapable() method to mark each generated class as ready for "plain-old Java" code gen.

The advantages of this feature are two:

1. Ability to step through the generated code to increase understanding of existing operators and to ease development of improvements to existing operators and of any new operators we choose to create.
2. Open the door to experimenting with how to improve performance of the generated code.

Issue Links

• links to: GitHub Pull Request #716