[
https://issues.apache.org/jira/browse/HIVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756068#action_12756068
]
Edward Capriolo commented on HIVE-78:
-------------------------------------
Min,
First, let me say you have probably come along much farther then me on this
issue.
Your approach is too strong. Hive is an open-community process. Through it is
not very detailed we have loosely agreed on a spec (above), in that spec we
have decided not to store username/password information in hive. Rather
upstream is still going to be responsible for this information. We also agreed
on syntax.
You should not throw up a new spec, and some code, and say something along the
lines of "We are going to take over and do it this way". Imagine if each jira
issue you working on you were 20% to 50% done. And then someone jumped in and
said "I already finished it a different way", that would be rather annoying. It
would be a "first patch wins" system.
First, before you are going to write a line of code you should let someone know
your intention to work on it. Otherwise what is the point of having two people
work on something where one version gets thrown away? It is a waste, and this
would be the second issue this has happened to me.
Second even if you want to starting coding it up it has to be what people
agreed on. We agreed not to store user/pass (hadoop will be doing this upstream
soon), and we agreed on syntax, if you want to reopen that issue you should
discuss it before coding it. It has to be good for the community, not just your
deployment.
So where do we go from here? Do we go back to the design phase and describe all
the syntax we want to support?
> Authentication infrastructure for Hive
> --------------------------------------
>
> Key: HIVE-78
> URL: https://issues.apache.org/jira/browse/HIVE-78
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Server Infrastructure
> Reporter: Ashish Thusoo
> Assignee: Edward Capriolo
> Attachments: hive-78-metadata-v1.patch, hive-78-syntax-v1.patch,
> hive-78.diff
>
>
> Allow hive to integrate with existing user repositories for authentication
> and authorization infromation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.