You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2015/05/05 15:38:19 UTC

[jira] [Updated] (DRILL-1913) Drill did not correctly preserve output field's case sensitivity

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

Jacques Nadeau updated DRILL-1913:
----------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.2.0

> Drill did not correctly preserve output field's case sensitivity
> ----------------------------------------------------------------
>
>                 Key: DRILL-1913
>                 URL: https://issues.apache.org/jira/browse/DRILL-1913
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: SQL Parser
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> For the following query,
> {code}
> select EMPLOYEE_ID from cp.`employee.json` limit 2;
> +-------------+
> | employee_id |
> +-------------+
> | 1           |
> | 2           |
> +-------------+
> {code}
> Even though upper-case EMPLOYEE_ID matches the field 'employee_id' in the input JSON file, Drill did not preset the upper-case in the output result, which seems to be not right.
> The plan coming out of optiq/calcite seems right, as it has a project which will do the renaming. But Drill's logical planning will remove such project, hence not being able to preserve the upper-case in the output.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)