Hi Fabio, Hue is OSS and ASL-ed, and you can re-use the thrift bindings it uses to communicate with the various daemons via plugins, and then feed information into its UIs.
I do think you can easily separate out the desktop UI and the backend (thrift binding) parts, and plug in your own UI layers if you absolutely need to do that. If you are still interested in doing that, you are welcome to ask your questions at https://groups.google.com/a/cloudera.org/group/hue-dev lists. The hue community also welcomes any feedback you may have that can help improve Hue to address your issues. But to answer your specific question, you essentially would need to load a plugin at each daemon that you can communicate to, and your UI project should use the plugin to fetch what it needs. This is how HUE does it and the sources are all at http://github.com/cloudera/hue Note: Hue is undergoing a look and feel change (and ditching the desktop model, which may be the pain for you here?), which you may want to check further at https://groups.google.com/a/cloudera.org/group/hue-user/browse_thread/thread/cea3cf743d230d9d# -- This work is already available in the hue2 git branch for testing/consumption. On Fri, Feb 17, 2012 at 3:31 PM, <fabio.pitz...@gmail.com> wrote: > Hello everyone, > > in order to provide our clients a custom UI for their MapReduce jobs and HDFS > files, what is the best solution to create a web-based UI for Hadoop? > We are not going to use Cloudera HUE, we need something more user-friendly > and shaped for our clients needs. > > Thanks, > > Fabio Pitzolu -- Harsh J Customer Ops. Engineer Cloudera | http://tiny.cloudera.com/about
