[
https://issues.apache.org/jira/browse/DRILL-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374179#comment-16374179
]
Robert Hou commented on DRILL-4692:
-----------------------------------
This has become issue when mapr customers want to read their audit logs. One
of the fields is "user". Here is an example:
{"timestamp":\{"$date":"2018-01-26T23:17:25.198Z"},"operation":"WRITE","user":"myuser","uid":5001,"ipAddress":"172.18.4.101","nfsServer":"172.18.4.100","srcPath":"/ingest_authtest/clarity_edg_hph/data/CLARITY_EDG/0c088c67-472c-432c-8561-abf1b43129e2.parquet","srcFid":"2753.64.131292","VolumeName":"clarity_edg_hph","volumeId":53904125,"status":0}
> Column named user unresolvable
> ------------------------------
>
> Key: DRILL-4692
> URL: https://issues.apache.org/jira/browse/DRILL-4692
> Project: Apache Drill
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.6.0
> Reporter: John Omernik
> Priority: Major
>
> With a set of Parquet files created outside of drill is attempted to be
> processed in Drill, and that set of files contains a column named "user" it
> is impossible to resolve that column, as Drill always replaces user with the
> currently logged in user.
> select user from table -> the logged in user
> select `user` from table -> the logged in user
> There is just no way to address that field. Backticks should allow us to
> access that field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
