[
https://issues.apache.org/jira/browse/DRILL-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002078#comment-16002078
]
Paul Rogers commented on DRILL-5492:
------------------------------------
Even more fun. Input file:
{code}
EXPR$0,EXPR$1,EXPR$2
a,b,c
d,e,f
{code}
Output:
{code}
2 row(s):
EXPR$0,EXPR$1,EXPR$2
a,b,c
d,e,f
{code}
Then, use this SQL:
{code}
SELECT `EXPR$1` as A, 1 + 2, 3 + 4 FROM `dfs.data`.`csv/test11.csv`
{code}
To get this output:
{code}
A,EXPR$1,EXPR$2
b,3,7
e,3,7
{code}
And this:
{code}
SELECT `EXPR$1`, 1 + 2, 3 + 4 FROM `dfs.data`.`csv/test11.csv`
{code}
Produces this:
{code}
2 row(s):
EXPR$1,EXPR$10,EXPR$11
b,3,7
e,3,7
{code}
At least Drill was smart enough to remap the first expression to EXPR$10 to
avoid the name conflict...
Still, would be better to disallow Drill internal names as column headers.
> CSV with spaces for header uses spaces as field name
> ----------------------------------------------------
>
> Key: DRILL-5492
> URL: https://issues.apache.org/jira/browse/DRILL-5492
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Paul Rogers
> Priority: Minor
>
> Consider the same test case as in DRILL-5491, but with a slightly different
> input file:
> {code}
> ___
> a,b,c
> d,e,f
> {code}
> The underscores represent three spaces: use spaces in the real test.
> In this case, the code discussed in DRILL-5491 finds some characters and
> happily returns the following array:
> {code}
> [" "]
> {code}
> The field name of three blanks is returned to the client to produce the
> following bizarre output:
> {code}
> 2 row(s):
>
> a
> d
> {code}
> The blank line is normally the header, but the header here was considered to
> be three blanks. (In fact, the blanks are actually printed.)
> Since the blanks were considered to be a field, the file is assumed to have
> only one field, so only the first column was returned.
> The expected behavior is that spaces are trimmed from field names, so the
> field name list would be empty and a User Error thrown. (That is, it is
> confusing to the user why a blank line produces NPE, some produce the
> {{ExecutionSetupException}} shown in DRILL-5491, and some produce blank
> headings. Behavior should be consistent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
