[
https://issues.apache.org/jira/browse/IGNITE-29034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18110964#comment-18110964
]
Ignite TC Bot commented on IGNITE-29034:
----------------------------------------
{panel:title=Branch: [pull/13545/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13545/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 13{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9322332]]
* {color:#013220}IgniteCacheTestSuite13:
SystemViewCacheExpiryPolicyTest.testCacheViewExpiryPolicy[factory=javax.cache.configuration.FactoryBuilder$SingletonFactory@7a65c995,
actual=SingletonFactory [expiryPlc=EternalExpiryPolicy [create=ETERNAL]]] -
PASSED{color}
{color:#00008b}Calcite SQL 3{color} [[tests
3|https://ci2.ignite.apache.org/viewLog.html?buildId=9322435]]
* {color:#013220}IgniteCalciteTestSuite3:
OperatorsExtensionIntegrationTest.testUserDefinedDualView - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
OperatorsExtensionIntegrationTest.testDualTableInNewSchema - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite3:
OperatorsExtensionIntegrationTest.testDualTable - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9322468&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9322468
rerunBuildIds=9323281{color}
> SQL Calcite: Add support for FROM DUAL queries
> ----------------------------------------------
>
> Key: IGNITE-29034
> URL: https://issues.apache.org/jira/browse/IGNITE-29034
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add support for the {{DUAL}} pseudo-table.
> Calcite exposes this capability through
> {{{}SqlConformance.isSupportedDualTable(){}}}, but Ignite does not currently
> register {{DUAL}} in its schemas.
> When this conformance option is enabled, {{DUAL}} should be exposed as a
> virtual table with Oracle-compatible contents:
> * Exactly one row.
> * One column named {{{}DUMMY{}}}.
> * Column value {{{}'X'{}}}.
> The following queries should work:
> {noformat}
> SELECT 1 + 1 FROM DUAL;
> SELECT DUMMY FROM DUAL; SELECT LAG(rate, 1, rate) OVER (ORDER BY period) FROM
> (SELECT 1 AS rate, 1 AS period FROM DUAL);
> {noformat}
> Acceptance criteria:
> * {{DUAL}} is registered when the active SQL conformance supports it.
> * {{SELECT * FROM DUAL}} returns one row with {{{}DUMMY = 'X'{}}}.
> * {{DUAL}} works in nested queries and with window functions.
> * An existing user table or view named {{DUAL}} is not overwritten.
> * Integration tests cover expressions, the {{DUMMY}} column, and window
> functions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
