Run JUnit (SQL) Tests in Multiple Query Execution Modes #1223
Description
Summary
Currently, SQL tests with JUnit are only run with interpreted query execution (the default). Support should be added such that these tests are run in both interpreted and compiled query execution modes.
Solution
We will need to add support in the unit testing framework for specifying system parameters each time the DBMS is restarted to run a new test. It looks like this should be simple enough by modifying test_server.py(in script/testing/util/) to pass commandline arguments when the DBMS subprocess is spawned. This functionality should be generally useful as we move forward and need to ensure correct operation of the system under all of our supported parameter combinations.
As mentioned above, interpreted query execution is the default, and compiled query execution may be enabled by specifying the -compiled_query_execution=true flag when launching the DBMS.