JingsongLi commented on pull request #17186:
URL: https://github.com/apache/flink/pull/17186#issuecomment-920783089
> I don't know how that would possibly work, though? We'd somehow have to
"tag" the RexLiteral so we can know that it originated from a call to
JSON_OBJECT, but also make sure this RexLiteral doesn't get re-used in a
different context. I don't think this is a temporary workaround, but rather a
hard limitation.
I think there is a solution that can be repaired. It may cost a lot now, but
it's good to record a JIRA.
For example:
```
public interface RexExecutor {
void reduce(RexBuilder rexBuilder, List<RexNode> originalExps,
List<RexNode> constExps, List<RexNode> reducedValues);
}
```
We can add a arguement `List<RexNode> originalExps` to `RexExecutor`, in
this way, we can know the originalExp is a `RexCall` or not.
--
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.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
