drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-1913) Drill did not correctly preserve output field's case sensitivity
Date Sun, 04 Jan 2015 23:57:58 GMT

     [ 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: 0.9.0
         Assignee: Jinfeng Ni

> 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
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
>            Priority: Minor
>             Fix For: 0.9.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)

Mime
View raw message