You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@calcite.apache.org by GitBox <gi...@apache.org> on 2019/10/30 01:55:31 UTC

[GitHub] [calcite] danny0405 commented on issue #1543: [CALCITE-3455] Redundant rule firing for both logical and physical nodes

danny0405 commented on issue #1543: [CALCITE-3455] Redundant rule firing for both logical and physical nodes
URL: https://github.com/apache/calcite/pull/1543#issuecomment-547704840
 
 
   Quotes Julian's comment in the mailing list:
   
   > Is there a change we could make to the rule API that would make it easier to customize rules? I have been thinking for a while about adding an “operand builder” to replace the static methods (e.g. RelOptRule.operandJ) that we use to build the operands inside rules. Maybe as part of this change, we could allow rules to clone themselves with slightly different parameters.
   
   >I’m interested in hearing about a “big change” that would save us from a myriad of small changes in the coming years.
   
   I'm also expecting if we can make more effort to do a bigger refactoring to make the RelOptRule customization more easier.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services