[
https://issues.apache.org/jira/browse/BOOKKEEPER-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503379#comment-13503379
]
Ivan Kelly commented on BOOKKEEPER-478:
---------------------------------------
Yup, I've come across this. The simple solution is to just not shade bookkeeper
in the bkjm jar. Another solution would be to account for the shading in the
configuration, but I think this is unnecessary. Really, what we need to shade
is anything that there may be an incompatability with in another hadoop module.
I doubt another hadoop module will import bookkeeper, so it's fine to not shade
it.
> Changes from BOOKKEEPER-203 broken capability of including bookkeeper-server
> jar in hidden package of BKJM
> ----------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-478
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-478
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Vinay
> Fix For: 4.2.0
>
>
> BOOKKEEPER-203 introduced changes to LedgerLayout to include
> ManagerFactoryClass instead of ManagerFactoryName.
> So because of this, BKJM cannot shade the bookkeeper-server jar inside BKJM
> jar
> LAYOUT znode created by BookieServer is not readable by the BKJM as it have
> classes in hidden packages. (same problem vice versa)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
