[
https://issues.apache.org/jira/browse/DRILL-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers updated DRILL-5059:
-------------------------------
Description:
The JDBC tests in {{org.apache.drill.jdbc.test.TestJdbcDistQuery}},
{{TestBugFixes}} (and perhaps others) "test" queries by running them and
dumping the results to stdout. In a normal Maven build, the output clutters up
the test output and is ignored.
To be an actual test, the output should be captured, then compared against a
"golden" file to verify that the query produced the expected results. Else, the
test can capture only catastrophic failure, but not other problems.
was:
The JDBC tests in {{org.apache.drill.jdbc.test.TestJdbcDistQuery}} "test"
queries by running them and dumping the results to stdout. In a normal Maven
build, the output clutters up the test output and is ignored.
To be an actual test, the output should be captured, then compared against a
"golden" file to verify that the query produced the expected results. Else, the
test can capture only catastrophic failure, but not other problems.
> JDBC tests queries by dumping query to stdout
> ---------------------------------------------
>
> Key: DRILL-5059
> URL: https://issues.apache.org/jira/browse/DRILL-5059
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Affects Versions: 1.8.0
> Reporter: Paul Rogers
> Priority: Minor
>
> The JDBC tests in {{org.apache.drill.jdbc.test.TestJdbcDistQuery}},
> {{TestBugFixes}} (and perhaps others) "test" queries by running them and
> dumping the results to stdout. In a normal Maven build, the output clutters
> up the test output and is ignored.
> To be an actual test, the output should be captured, then compared against a
> "golden" file to verify that the query produced the expected results. Else,
> the test can capture only catastrophic failure, but not other problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
