1. No. You should put one pair of username/password in hive-site.xml which will be used for all. 2. There is authentication/authorization in Hive yet. See HIVE-78 for more details on it will be done. For now, everything is readable and writeable except for the default database which can't be deleted. 3. The JDBC data store to use will greatly depend on what other RDBMS your organization uses. Most probably the biggest metastore is Facebook's and we use mysql for administrative purposes. I don't think performance is a big deal yet. You should use whatever you are comfortable with.
Prasad ________________________________ From: Tomer Shiran <[email protected]> Reply-To: <[email protected]> Date: Sun, 22 Nov 2009 17:55:43 -0800 To: <[email protected]> Subject: Re: Hive metastore on MySQL or files That definitely makes sense. I have a few follow-up questions: 1. If I'm using MySQL (i.e., Hive's Multi User Mode), does that mean that each user should have a valid MySQL username and password? 2. Is there any authentication built into the Thrift protocols when using Hive's Remote Server option. How are permissions handled in that case? 3. Does it make sense to use the Remote Server option with Derby? Thanks, Tomer On Sun, Nov 22, 2009 at 4:58 PM, Carl Steinbach <[email protected]> wrote: Hi Ed, Anyone have a great reason that MySQL is better then Derby? Given the negligible affect that metastore performance has on Hive's overall performance, I think manageability is the dominant concern for most people when selecting a metastore datastore. If your organization is already using MySQL/Postgres/etc and has a person maintaining and managing backups for these systems, it is probably better to piggyback on that effort than to further complicate matters with the addition of another critical infrastructure component. Carl -- Tomer Shiran Director of Product Management | MapR Technologies (www.mapr.com <http://www.mapr.com> ) | 650-804-8657
