[
https://issues.apache.org/jira/browse/IGNITE-27084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov reassigned IGNITE-27084:
-----------------------------------------
Assignee: Andrey Mashenkov
> Sql. Improve printout of searchBounds in EXPLAIN
> ------------------------------------------------
>
> Key: IGNITE-27084
> URL: https://issues.apache.org/jira/browse/IGNITE-27084
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Reporter: Konstantin Orlov
> Assignee: Andrey Mashenkov
> Priority: Minor
> Labels: ignite-3
>
> Currently, {{toString}} is used to print out search bounds in explain writer.
> One of the drawback of this approach is that any change in related classes
> lead to changes in explain output. Another problem is that format of
> {{toString}} is out of the common style of rest of the expressions. Here is
> an example:
> {code}
> IndexScan
> table: PUBLIC.TEST_TABLE
> index: TEST_TABLE_IDX
> type: SORTED
> predicate: AND(SEARCH(C1, Sarg[1, 2, 3]),
> >(CAST(CURRENT_TIMESTAMP):TIMESTAMP(0) NOT NULL, 1970-01-01 00:00:00))
> searchBounds: [MultiBounds [bounds=ArrayList [ExactBounds [bound=1],
> ExactBounds [bound=2], ExactBounds [bound=3]]]]
> fieldNames: [C1]
> collation: [C1 ASC]
> est: (rows=1)
> {code}
> Search bounds above represents multiple lookup with 3 index keys: 1, 2, and 3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
