hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Srinivas <sur...@hortonworks.com>
Subject Re: [DISCUSS] Resolving the divergences for web-related code between branch-2 and trunk
Date Wed, 01 Oct 2014 23:05:28 GMT
Webui equivalent data has been exposed as jmx http APIs for a long time (I think from 0.20
release, almost 4 years ago). We have made many jsp changes that we have made that should
have broken these applications many times. I believe this is a frivolous objection for a functionality
that as a community we have never committed to keeping stable or backward compatible. 

Again I think given there is a clear and easier path for such uses to move to, I am +1 on
this change. 

Sent from phone

> On Oct 1, 2014, at 3:44 PM, Allen Wittenauer <aw@altiscale.com> wrote:
> 
> 
>    OK, then consider this an official objection.  Yes, people do have workflows based
upon scraping the Web UIs, especially workflows that simulate what interfaces users actually
use.
> 
>> On Oct 1, 2014, at 3:34 PM, Haohui Mai <hmai@hortonworks.com> wrote:
>> 
>> Hi,
>> 
>> Thanks for the discussions. If there is no objection, I plan to merge the
>> related jiras from trunk to branch-2 in the coming days.
>> 
>> ~Haohui
>> 
>> On Wed, Oct 1, 2014 at 2:35 PM, Suresh Srinivas <suresh@hortonworks.com>
>> wrote:
>> 
>>> Sorry for responding very late. I am +1 on removing the JSP UI in branch-2
>>> for the following reasons:
>>> 1. The new web UI added has all the functionality of JSP UI.
>>> 2. For folks who might have used web UI to scrape the HDFS status, we have
>>> build a http JMX interface a long time ago.
>>> 
>>> Given we do not guarantee the web UI as a stable and backward compatible
>>> interface, removing this should be okay.
>>> 
>>> 
>>> 
>>>> On Thu, Sep 11, 2014 at 3:29 PM, Haohui Mai <hmai@hortonworks.com>
wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> In HDFS, the code that relates to webhdfs and UIs has diverged quite a
>>> bit
>>>> between branch-2 and trunk. This complicates the processes of maintaining
>>>> webhdfs in several jiras (e.g., HDFS-5946)
>>>> 
>>>> Most of the divergences come from removing the JSP UI and the related
>>> clean
>>>> ups that are committed to trunk.
>>>> 
>>>> Though I myself have to take the blame of creating these divergences -- I
>>>> wonder, is it acceptable to resolve these divergences, by committing
>>> these
>>>> patches that remove JSP UI to branch-2? This would save us the pains of
>>>> providing two patches when fixing issues in webhdfs.
>>>> 
>>>> Note that the new HTML5-based UI is fairly mature, as it has been around
>>>> since 2.2, and it has been the default UI since 2.3. Compatibility,
>>>> however, might be a concern -- according to the compatibility guide,
>>> Hadoop
>>>> claims no compatibility for web UIs, thus we might be able to get away
>>> with
>>>> that.
>>>> 
>>>> Thoughts?
>>>> 
>>>> Regards,
>>>> Haohui
>>>> 
>>>> --
>>>> CONFIDENTIALITY NOTICE
>>>> NOTICE: This message is intended for the use of the individual or entity
>>> to
>>>> which it is addressed and may contain information that is confidential,
>>>> privileged and exempt from disclosure under applicable law. If the reader
>>>> of this message is not the intended recipient, you are hereby notified
>>> that
>>>> any printing, copying, dissemination, distribution, disclosure or
>>>> forwarding of this communication is strictly prohibited. If you have
>>>> received this communication in error, please contact the sender
>>> immediately
>>>> and delete it from your system. Thank You.
>>> 
>>> 
>>> 
>>> --
>>> http://hortonworks.com/download/
>>> 
>>> --
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender immediately
>>> and delete it from your system. Thank You.
>> 
>> -- 
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to 
>> which it is addressed and may contain information that is confidential, 
>> privileged and exempt from disclosure under applicable law. If the reader 
>> of this message is not the intended recipient, you are hereby notified that 
>> any printing, copying, dissemination, distribution, disclosure or 
>> forwarding of this communication is strictly prohibited. If you have 
>> received this communication in error, please contact the sender immediately 
>> and delete it from your system. Thank You.
> 

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
View raw message