[
https://issues.apache.org/jira/browse/CALCITE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713803#comment-17713803
]
Julian Hyde edited comment on CALCITE-5615 at 4/19/23 12:21 AM:
----------------------------------------------------------------
I have created
[hydromatic/sql-logic-test|https://github.com/hydromatic/sql-logic-test].
Please take a look.
Still to do:
* Move files from org.apache.calcite.slt package to
net.hydromatic.sqllogictest;
* Re-enable checkstyle;
* Add some more tests;
* Remove the dependency on Calcite; CalciteExecutor should move into Calcite,
and Calcite should instead depend on sql-logic-test;
* Squash commits and give [~mbudiu] author credit;
* Publish to maven central;
* Physically include the files from master.zip, rather than downloading each
time.
was (Author: julianhyde):
I have created
[hydromatic/sql-logic-test|https://github.com/hydromatic/sql-logic-test].
Please take a look.
> Run SQLLogicTests using Calcite
> -------------------------------
>
> Key: CALCITE-5615
> URL: https://issues.apache.org/jira/browse/CALCITE-5615
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.34.0
> Reporter: Mihai Budiu
> Assignee: Mihai Budiu
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Sqllogictest is a program designed to verify that an SQL database engine
> computes correct results by comparing the results to identical queries from
> other SQL database engines.
> https://www.sqlite.org/sqllogictest/doc/trunk/about.wiki
> The nice thing about SLT is that it contains more than 7 million tests. The
> tests only cover the core of SQL, ideally the portable part across all
> engines. They only test integers, doubles, and strings. So they could
> probably be part of the Calcite slow tests.
> The tests should be structured so that any query execution engine can be used.
> I plan to contribute such an implementation if people think it is useful, but
> I haven't yet worked out all the details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
