[ https://issues.apache.org/jira/browse/PIG-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Dai updated PIG-3764: ---------------------------- Description: I started a prototype here: https://github.com/julienledem/pig/compare/trunk...compile_physical_plan The current physical plan is relatively inefficient at evaluating expressions. In the context of a better execution engine (Tez, Spark, ...), compiling expressions to bytecode would be a significant speedup. This is a candidate project for Google summer of code 2014. More information about the program can be found at https://cwiki.apache.org/confluence/display/PIG/GSoc2014 was: I started a prototype here: https://github.com/julienledem/pig/compare/trunk...compile_physical_plan The current physical plan is relatively inefficient at evaluating expressions. In the context of a better execution engine (Tez, Spark, ...), compiling expressions to bytecode would be a significant speedup. > Compile physical operators to bytecode > -------------------------------------- > > Key: PIG-3764 > URL: https://issues.apache.org/jira/browse/PIG-3764 > Project: Pig > Issue Type: Improvement > Components: impl > Reporter: Julien Le Dem > Labels: GSOC2014 > > I started a prototype here: > https://github.com/julienledem/pig/compare/trunk...compile_physical_plan > The current physical plan is relatively inefficient at evaluating expressions. > In the context of a better execution engine (Tez, Spark, ...), compiling > expressions to bytecode would be a significant speedup. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.1.5#6160)