You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/14 21:18:00 UTC

[jira] [Resolved] (HBASE-6850) REST implementation internals conflict with clients that use Jersey

     [ https://issues.apache.org/jira/browse/HBASE-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-6850.
----------------------------------------
    Resolution: Not A Problem

> REST implementation internals conflict with clients that use Jersey
> -------------------------------------------------------------------
>
>                 Key: HBASE-6850
>                 URL: https://issues.apache.org/jira/browse/HBASE-6850
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, REST
>    Affects Versions: 0.94.1
>            Reporter: Jonathan Leech
>            Priority: Major
>
> - It is my understanding that there is one and only one hbase jar, which includes org.apache.hadoop.hbase.rest.provider.producer.PlainTextMessageBodyProducer, which is only used in the REST / jersey server-side implementation.
> - PlainTextMessageBodyProducer claims to provide a text/plain output for absolutely any input by calling .toString() on it.
> - If I am a client to HBase, and I do my own REST / jersey, including my own custom text/plain writing, by default the jersey stack finds PlainTextMessageBodyProducer and uses it instead of mine.
> I could be off base here; so please feel free to change this from a Bug to a Feature Request or close it, especially if my assumptions are wrong.
> Workaround: set init-param of com.sun.jersey.config.property.packages to limit it to my own packages.
> Recommended fix: 
> - provide a client jar and / or a maven pom for hbase-client which doesn't include server-side hbase code or dependencies.
> and / or 
> - don't return true from isWriteable() for every possible input, or create a different custom mime type that other users of the API might be also using, and if possible map text/plain to that type in the server.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)