You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Abhishek Girish (Jira)" <ji...@apache.org> on 2020/09/06 16:27:01 UTC

[jira] [Updated] (DRILL-7621) Refactor ExecConstants and PlannerSettings constant classes

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

Abhishek Girish updated DRILL-7621:
-----------------------------------
    Target Version/s: 1.19.0

> Refactor ExecConstants and PlannerSettings constant classes
> -----------------------------------------------------------
>
>                 Key: DRILL-7621
>                 URL: https://issues.apache.org/jira/browse/DRILL-7621
>             Project: Apache Drill
>          Issue Type: Task
>            Reporter: Igor Guzenko
>            Assignee: Igor Guzenko
>            Priority: Major
>             Fix For: 1.18.0
>
>
> According to [the discussion|http://mail-archives.apache.org/mod_mbox/drill-dev/202003.mbox/%3CBCB4CFC2-8BC5-43C6-8BD4-956F66F6D0D3%40gmail.com%3E], it makes sense to split the classes into multiple constant interfaces and get rid of validator constants. Then the validator instances won't be used for getting option values and the general approach will be getting type specific option value by string key from config instance. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)