Hi Tim,
it looks like deprecating BaseTestQuery was a little bit pre-mature.
For example, from in this PR - https://github.com/apache/drill/pull/1331 -
Charles is trying to re-work BaseTestQuery usage to ClusterTest.
First, it did not contain getSigletonDouble method which Charles has
implemented. Now he has troubles with implementing getSigletonBoolean
method which might be due to reader limitations.
Also I am not quite clear how we can verify columns names and multiple
columns in the result.
For example:
testBuilder()
.sqlQuery("select (mi || lname) as CONCATOperator, mi, lname,
concat(mi, lname) as CONCAT from concatNull")
.ordered()
.baselineColumns("CONCATOperator", "mi", "lname", "CONCAT")
.baselineValues("A.Nowmer", "A.", "Nowmer", "A.Nowmer")
.baselineValues("I.Whelply", "I.", "Whelply", "I.Whelply")
.baselineValues(null, null, "Derry", "Derry")
.baselineValues("J.Spence", "J.", "Spence", "J.Spence")
.build().run();
Can you please suggest how this example can be re-written?
Kind regards,
Arina
On Mon, Jun 25, 2018 at 11:10 PM Timothy Farkas <tfar...@mapr.com> wrote:
> Hi All,
>
> BaseTestQuery was deprecated a while ago. Keeping it short and sweet :), if
> you want to use BaseTestQuery directly, don't. Use ClusterTest instead. If
> you are using PlanTestBase for planner tests, continue to do so. Eventually
> PlanTestBase will be changed to extend ClusterTest instead. There is a JIRA
> to track that issue https://issues.apache.org/jira/browse/DRILL-6536.
>
> Thanks,
> Tim
>
