You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2019/01/05 00:39:00 UTC

[jira] [Commented] (DRILL-6941) Incorrect EARLY_LIMIT0_OPT_KEY description

    [ https://issues.apache.org/jira/browse/DRILL-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734707#comment-16734707 ] 

Kunal Khatua commented on DRILL-6941:
-------------------------------------

Thanks for catching this, [~arina] !

[~bbevens] could you please review this?

> Incorrect EARLY_LIMIT0_OPT_KEY description
> ------------------------------------------
>
>                 Key: DRILL-6941
>                 URL: https://issues.apache.org/jira/browse/DRILL-6941
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.15.0
>            Reporter: Arina Ielchiieva
>            Assignee: Kunal Khatua
>            Priority: Minor
>             Fix For: 1.16.0
>
>
> Currently in ExecConstants:
> {noformat}
>   public static final String EARLY_LIMIT0_OPT_KEY = "planner.enable_limit0_optimization";
>   public static final BooleanValidator EARLY_LIMIT0_OPT = new BooleanValidator(EARLY_LIMIT0_OPT_KEY,
>       new OptionDescription("Sets the type of identifier quotes for the SQL parser. Default is backticks ('`'). The SQL parser accepts double quotes ('\"') and square brackets ('['). (Drill 1.11+)"));
> {noformat}
> Should be something like this: 
> planner.enable_limit0_optimization
> {noformat}
> Enables the query planner to determine data types returned by a query during the planning phase before scanning data. Default is true. (Drill 1.9 and later)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)