[
https://issues.apache.org/jira/browse/HIVE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006505#comment-14006505
]
Owen O'Malley commented on HIVE-6936:
-------------------------------------
My concern with removing the "table." prefix is that it becomes possible to
clobber security settings. For example, creating a table with the
"hive.security.authorization.manager" table property shouldn't allow the query
to override the setting.
For a compromise, how about removing the table prefix, but we check to see if
that key has a value in the configuration and won't override such a value. Does
that make sense?
> Provide table properties to InputFormats
> ----------------------------------------
>
> Key: HIVE-6936
> URL: https://issues.apache.org/jira/browse/HIVE-6936
> Project: Hive
> Issue Type: Bug
> Components: File Formats
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.14.0
>
> Attachments: HIVE-6936.patch, HIVE-6936.patch, HIVE-6936.patch,
> HIVE-6936.patch
>
>
> Some advanced file formats need the table properties made available to them.
> Additionally, it would be convenient to provide a unique id for fetch
> operators and the complete list of directories.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
