[
https://issues.apache.org/jira/browse/CALCITE-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708051#comment-17708051
]
TJ Banghart commented on CALCITE-5625:
--------------------------------------
Thanks for the notes Julian!
Given that context (and after some experimenting), I agree that expansion is
not the best approach. The serialized representation of some filter expressions
can become quite large and It would be best to have true JSON support for
{{SEARCH}} directly.
[~oliverlee] has already made good progress to that end in CALCITE-5614 by
delegating to {{com.fasterxml.jackson.datatype:jackson-datatype-guava}}. This
looks to be a [deprecated
project|https://github.com/FasterXML/jackson-datatype-guava] but assuming
[{{jackson-datatypes-collections}}|https://github.com/FasterXML/jackson-datatypes-collections]
has similar capabilities, would relying on Jackson be a viable option?
I don't believe we have looked at [RangeSets.Consumer or RangeSets.Handler
|https://calcite.apache.org/javadocAggregate/org/apache/calcite/util/RangeSets.html]
so it seems we may have a few possibilities. Either way, I think we are good
to close this issue and focus on CALCITE-5614. Thanks!
> Expand SEARCH RexNode when converting toJson
> ---------------------------------------------
>
> Key: CALCITE-5625
> URL: https://issues.apache.org/jira/browse/CALCITE-5625
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Oliver Lee
> Priority: Major
>
> Because the Sarg class is not able to be serialized/deserialized to/from
> JSON, we would like to expand the SEARCH RexNode as a workaround.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
