[
https://issues.apache.org/jira/browse/DRILL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619709#comment-14619709
]
ASF GitHub Bot commented on DRILL-3476:
---------------------------------------
GitHub user StevenMPhillips opened a pull request:
https://github.com/apache/drill/pull/83
DRILL-3476: Merge paths in FieldSelection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StevenMPhillips/incubator-drill drill-3476
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/83.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #83
----
----
> Filter on nested element gives wrong results
> --------------------------------------------
>
> Key: DRILL-3476
> URL: https://issues.apache.org/jira/browse/DRILL-3476
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Steven Phillips
>
> Take this query for example:
> {code}
> 0: jdbc:drill:drillbit=localhost> select * from t;
> +----------------+
> | a |
> +----------------+
> | {"b":1,"c":1} |
> +----------------+
> {code}
> if I instead run:
> {code}
> 0: jdbc:drill:drillbit=localhost> select a from t where t.a.b = 1;
> +----------------+
> | a |
> +----------------+
> | {"b":1} |
> +----------------+
> {code}
> Only a.b was returned, but the select specified a. In this case, it should
> have returned all of the elements of a, not just the one specified in the
> filter.
> This is because the logic in FieldSelection does not correctly handle the
> case where a selected column is a child of another selected column. In such a
> case, the record reader should ignore the child column, and just return the
> full selected parent column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
