You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by Thejas Nair <th...@hortonworks.com> on 2011/10/11 00:40:12 UTC
LogicalExpressionSimplifier rules
Sending this email for getting wider attention.
I propose disabling LogicalExpressionSimplifier optimizer rule, because
the complexity of that rule and number of bugs that seem to come from
there does not justify the expected performance gains -
https://issues.apache.org/jira/browse/PIG-2316?focusedCommentId=13124489&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13124489
In general, I think any new code that is significantly complex (ie hard
to maintain, and likely source of bugs) should be added to pig only if
there are enough gains to justify it.
-Thejas
RE: LogicalExpressionSimplifier rules
Posted by Olga Natkovich <ol...@yahoo-inc.com>.
+1
-----Original Message-----
From: Thejas Nair [mailto:thejas@hortonworks.com]
Sent: Monday, October 10, 2011 3:40 PM
To: dev@pig.apache.org
Subject: LogicalExpressionSimplifier rules
Sending this email for getting wider attention.
I propose disabling LogicalExpressionSimplifier optimizer rule, because
the complexity of that rule and number of bugs that seem to come from
there does not justify the expected performance gains -
https://issues.apache.org/jira/browse/PIG-2316?focusedCommentId=13124489&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13124489
In general, I think any new code that is significantly complex (ie hard
to maintain, and likely source of bugs) should be added to pig only if
there are enough gains to justify it.
-Thejas