mapr / drill-test-framework Goto Github PK

When going through the code, I noticed a warning in getTestDefinitionList in Utils.java.

Dereference of 'root.listFiles()' may produce 'java.lang.NullPointerException'

I tried to reproduce the issue, to see if this warning can be ignored. Turns out this is easily reproducible. Consider the possibility that DRILL_TEST_DATA_DIR is configured wrongly in drillTestConfig.properties -

DRILL_TEST_DATA_DIR=framework/framework/resources

Results in the following error -

Exiting due to uncaught exception
java.lang.NullPointerException
	at org.apache.drill.test.framework.Utils.getTestDefinitionList(Utils.java:346)
	at org.apache.drill.test.framework.Utils.getTestDefSources(Utils.java:197)
	at org.apache.drill.test.framework.Utils.getDrillTestCases(Utils.java:227)
	at org.apache.drill.test.framework.TestDriver.runTests(TestDriver.java:174)
	at org.apache.drill.test.framework.TestDriver.main(TestDriver.java:93)

• Adding custom text makes it harder to parse the response from the Utils.execCmd.

Hi all, hi @Agirish ,

regarding the Mondrian tests under
https://github.com/mapr/drill-test-framework/tree/master/framework/resources/Advanced/mondrian

I have a few questions:

• How have the test queries been generated?
  • Is there any relationship to the Mondrian tests in https://github.com/pentaho/mondrian/tree/master/testsrc ?
• How is the status of the tests?
• Is it reasonable to execute the queries against Drill that is configured to access a PostgreSQL (equipped with the foodmart database) via the JDBC Storage Plugin ?

And a few general questions:

• Can you recommend using Mondrian with Drill?

Many thanks in advance

Adding a field such as consoleErr can help separate errors from standard outputs.