[
https://issues.apache.org/jira/browse/TEZ-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342362#comment-14342362
]
Sreenath Somarajapuram commented on TEZ-2091:
---------------------------------------------
[~hitesh] Sorry for the confusion. Cloning was just my presumption based on #1
- #4 in readme that assumes the web server directory to exist before war untar,
and only place it would be available is the repo.
[~lichangleo]
Considering all factors, looks like patch is in the right direction. But have
few suggestion.
1. Add package.json with the respective dependencies, so that all the
dependencies can be added by just running 'npm install'.
2. webapp is what runs in a web browser. So its better to move out the server
code, maybe to src/main/scripts/server.
3. +1 for Hitesh's comment "Did you consider the case where a user specifies
the port but not the UI_dir in the config?"
Comments:
1. Express is a web framework and might be an overkill for our task. But
considering that its easy to add auth providers with express+passportjs,
express looks like the best option.
2. As its Node.js, configs as JSON looks apt.
Maven build & distribution:
The war is build specifically for hosting on tomcat/similar web servers, so
don’t think the server code should be in the war. And right now its not added
by the build.
Maybe a maven assembly plugin can be added that would package the server script
into a jar, and can look like tez-ui-server-0.7.0-SNAPSHOT.jar or something.
> Add support for hosting TEZ_UI with nodejs
> ------------------------------------------
>
> Key: TEZ-2091
> URL: https://issues.apache.org/jira/browse/TEZ-2091
> Project: Apache Tez
> Issue Type: Improvement
> Components: UI
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: TEZ_2091_V1.patch, TEZ_2091_V2.patch
>
>
> There are certain category of people who would like to host TEZ UI on nodejs,
> it will be a good feature to be added in
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
