Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/1714
@HeartSaVioR with this change we are going to be heavily dependent on the
calcite's code generator to translate expressions correct?. Just thinking if we
should have an option to make the code generation pluggable with an option to
plug in our code generator as well. The calcite's code generator can be the
default.
Just thinking if in future we want to do some optimizations around the
generated code or have our own implementation for a built in function or want
to fix some bugs in the generated code without waiting for a calcite release
etc, it may not be possible with the current patch. Let me know what you think.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
