You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/01/16 20:39:35 UTC
[jira] [Commented] (CALCITE-489) Teach CalciteAssert to respect
multiple settings
[ https://issues.apache.org/jira/browse/CALCITE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280716#comment-14280716 ]
Julian Hyde commented on CALCITE-489:
-------------------------------------
The test infrastructure isn't perfect, and never will be. People should enhance it as they add tests. As long as there is a way to concisely write a test case that tests the functionality you want to test, that is good enough.
> Teach CalciteAssert to respect multiple settings
> ------------------------------------------------
>
> Key: CALCITE-489
> URL: https://issues.apache.org/jira/browse/CALCITE-489
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Reporter: Vladimir Sitnikov
> Assignee: Julian Hyde
> Labels: newbie
> Fix For: 1.0.0-incubating
>
>
> Currently {{CalciteAssert}} allows to specify _either_ custom connection properties via {{with(Map)}} or custom schema via {{with(String, Object)}}.
> Often it is required to set both simultaneously:
> For instance, {{lex=JAVA}} is an easy way to write queries without quotes.
> For testing correlation runtime, it is required to set {{forceDecorrelate=true/false}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)