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

Sergey Soldatov commented on PHOENIX-3020:
------------------------------------------

With shaded jersey MR jobs fails with 
{noformat}
016-06-22 01:32:49,669 WARN [main] org.mortbay.log: failed guice: 
com.sun.jersey.spi.service.ServiceConfigurationError: 
com.sun.jersey.spi.HeaderDelegateProvider: The class 
org.apache.phoenix.shaded.com.sun.jersey.core.impl.provider.header.LocaleProvider
 implementing provider interface com.sun.jersey.spi.HeaderDelegateProvider 
could not be instantiated: Cannot cast 
org.apache.phoenix.shaded.com.sun.jersey.core.impl.provider.header.LocaleProvider
 to com.sun.jersey.spi.HeaderDelegateProvider
2016-06-22 01:32:49,669 WARN [main] org.mortbay.log: failed 
org.mortbay.jetty.webapp.WebAppContext@351f2244{/,jar:file:/Users/ssoldatov/bin/hadoop/share/hadoop/yarn/hadoop-yarn-common-2.7.2.jar!/webapps/mapreduce}:
 com.sun.jersey.spi.service.ServiceConfigurationError: 
com.sun.jersey.spi.HeaderDelegateProvider: The class 
org.apache.phoenix.shaded.com.sun.jersey.core.impl.provider.header.LocaleProvider
 implementing provider interface com.sun.jersey.spi.HeaderDelegateProvider 
could not be instantiated: Cannot cast 
org.apache.phoenix.shaded.com.sun.jersey.core.impl.provider.header.LocaleProvider
 to com.sun.jersey.spi.HeaderDelegateProvider
{noformat}
Once we shade jersey, shading plugin also shading all related records in 
META-INF/services and it becomes used by MR's jetty.  I will remove it 
(actually thought to keep it to remember that we are not shading it and 
possible we will need to address it in the future. Like removing services file 
if we do not use it)
our LICENSE/NOTICE files are copying to the root of the jar. Actually some 
clean up is required for this mess of licenses from dependencies, but at the 
moment there are no changes between how we handling them now and how we did it 
before shading stuff, so it can/should be done in a separate jira later.
As for the runJar - it happens during unpacking, so it's not related to our 
code.

> Bulk load tool is not working with new jars
> -------------------------------------------
>
>                 Key: PHOENIX-3020
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3020
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Ankit Singhal
>            Assignee: Sergey Soldatov
>            Priority: Blocker
>         Attachments: PHOENIX-3020.patch
>
>
> [~rajeshbabu] and [~sergey.soldatov] has identified an issue related to bulk 
> load tool with latest jars



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to