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

2019-01-07 Thread Kunal Khatua (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kunal Khatua updated DRILL-6941:

Labels: doc-impacting ready-to-commit  (was: )

> 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
>  Labels: doc-impacting, ready-to-commit
> 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)


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

2019-01-07 Thread Bridget Bevens (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bridget Bevens updated DRILL-6941:
--
Labels: doc-complete ready-to-commit  (was: doc-impacting ready-to-commit)

> 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
>  Labels: doc-complete, ready-to-commit
> 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)


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

2019-01-04 Thread Kunal Khatua (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kunal Khatua updated DRILL-6941:

Priority: Minor  (was: Major)
Reviewer: Bridget Bevens

> 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)