[
https://issues.apache.org/jira/browse/IGNITE-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ostanin closed IGNITE-4627.
--------------------------------
> Tester for SQL functionality
> ----------------------------
>
> Key: IGNITE-4627
> URL: https://issues.apache.org/jira/browse/IGNITE-4627
> Project: Ignite
> Issue Type: Task
> Reporter: Sergey Kozlov
> Assignee: Oleg Ostanin
> Priority: Major
>
> Due introduction of DML and extending SQL support we need more deep testing
> of ANSI-99 SQL in Ignite.
> One from more ways is to use a standard RDBMS and execute same SQL statement
> against Ignite and that DB. Then compare result sets and seek a difference
> (good point of start is the following article:
> https://www.voltdb.com/blog/testing-voltdb-sqlcoverage).
> It significantly reduces efforts for checking of correctness SQL results
> returned by Ignite SQL engine.
> Mandatory key points to implementation:
> - design as an optional module of Ignite (say 'sql-tester') activated by a
> maven profile
> - support JDBC connection to Ignite and H2
> - all parameters should be defined via command-line
> - multithread SQL execution mode support
> - able to compare unsorted result sets (if "ORDER BY" clause not used)
> - input file is the list of SQL statements parts used to combine full SQL
> statement
> - output file is the list of full SQL statements and result of comparison (OK
> or found different rows)
> - able to apply same SQL statement for different caches in Ignite
> Optional points to implementation:
> - support native connection to Ignite
> - support ODBC connections
> - support JDBC connection to MySQL and Postgress
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
