Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 23 May 2012 21:37:40 +0000 (UTC)
From: "Zhenxiao Luo (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <545844219.13398.1337809060781.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1120259066.4411.1298966497329.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HIVE-2015) Eliminate bogus Datanucleus.Plugin
 Bundle ERROR log messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281936#comment-13281936 ] 

Zhenxiao Luo commented on HIVE-2015:
------------------------------------

Setting datanucleus.plugin.pluginRegistryBundleCheck has no effect of this bug.

According to: 
http://www.datanucleus.org/products/datanucleus/persistence_properties.html

datanucleus.plugin.pluginRegistryBundleCheck
Description	 Defines what happens when plugin bundles are found and are duplicated
Range of Values	 EXCEPTION | LOG | NONE

Seems this is set to whether LOG, EXCEPTION, or NONE if the plugin bundles are found and are duplicated. If it is not found/unresolved, ERROR still shows up in the first CLI command.

Also tested setting it to be EXCEPTION. No exception at all, the same error message.
                
> Eliminate bogus Datanucleus.Plugin Bundle ERROR log messages
> ------------------------------------------------------------
>
>                 Key: HIVE-2015
>                 URL: https://issues.apache.org/jira/browse/HIVE-2015
>             Project: Hive
>          Issue Type: Bug
>          Components: Diagnosability, Metastore
>            Reporter: Carl Steinbach
>            Assignee: Zhenxiao Luo
>
> Every time I start up the Hive CLI with logging enabled I'm treated to the following ERROR log messages courtesy of DataNucleus:
> {code}
> DEBUG metastore.ObjectStore: datanucleus.plugin.pluginRegistryBundleCheck = LOG 
> ERROR DataNucleus.Plugin: Bundle "org.eclipse.jdt.core" requires "org.eclipse.core.resources" but it cannot be resolved. 
> ERROR DataNucleus.Plugin: Bundle "org.eclipse.jdt.core" requires "org.eclipse.core.runtime" but it cannot be resolved. 
> ERROR DataNucleus.Plugin: Bundle "org.eclipse.jdt.core" requires "org.eclipse.text" but it cannot be resolved.
> {code}
> Here's where this comes from:
> * The bin/hive scripts cause Hive to inherit Hadoop's classpath.
> * Hadoop's classpath includes $HADOOP_HOME/lib/core-3.1.1.jar, an Eclipse library.
> * core-3.1.1.jar includes a plugin.xml file defining an OSGI plugin
> * At startup, Datanucleus scans the classpath looking for OSGI plugins, and will attempt to initialize any that it finds, including the Eclipse OSGI plugins located in core-3.1.1.jar
> * Initialization of the OSGI plugin in core-3.1.1.jar fails because of unresolved dependencies.
> * We see an ERROR message telling us that Datanucleus failed to initialize a plugin that we don't care about in the first place.
> I can think of two options for solving this problem:
> # Rewrite the scripts in $HIVE_HOME/bin so that they don't inherit ALL of Hadoop's CLASSPATH.
> # Replace DataNucleus's NOnManagedPluginRegistry with our own implementation that does nothing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira