hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10232) More options to HttpServer Builder
Date Wed, 15 Jan 2014 19:36:20 GMT

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

stack commented on HADOOP-10232:
--------------------------------

bq. +1 for the decoupling. The class is an internal class, it is never intended to be used
outside of HDFS and YARN...

>From HttpServer class branch-2 (and trunk has the same):

{code}
@InterfaceAudience.LimitedPrivate({"HDFS", "MapReduce", "HBase"})
@InterfaceStability.Evolving
public class HttpServer implements FilterContainer {
{code}

HBase has been ordained limited private (YARN is only in the list via proxy).

If the choice is between this small patch here and an all day maven hell transitive include
weeding project down the road -- that may or may not succeed -- I'd vote add this patch now
and meantime we'll work on decoupling (we'll circle back and remove our selves from the LimitedPrivate
list should we prevail).  Thanks.

> More options to HttpServer Builder
> ----------------------------------
>
>                 Key: HADOOP-10232
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10232
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Eric Charles
>         Attachments: HADOOP-10232-3.patch, HDFS-5760-1.patch, HDFS-5760-2.patch
>
>
> o.a.h.h.HttpServer can can be instanciated and configured:
> 1. Via classical constructor
> 2. Via static build method
> Those 2 methods don't populate the same way the (deprecated) hostname and port, nor the
jetty Connector.
> This gives issue when using hbase on hadoop3 (HBASE-6581)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message