README.rst 5.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187
  1. Welcome to the repository for Hue
  2. =================================
  3. .. note::
  4. This is the development-oriented readme. If you want to write notes for
  5. end users, please put them in ``dist/README``.
  6. Hue is both a web UI for Hadoop and a framework to create interactive web
  7. applications. It features a FileBrowser for accessing HDFS, JobSub and
  8. JobBrowser applications for submitting and viewing MapReduce jobs, a Beeswax
  9. application for interacting with Hive. On top of that, the web frontend
  10. is mostly built from declarative widgets that require no JavaScript and are
  11. easy to learn.
  12. File Layout
  13. ===========
  14. The "core" stuff is in ``desktop/core/``, whereas installable apps live in
  15. ``apps/``. Please place third-party dependencies in the app's ext-py/
  16. directory.
  17. The typical directory structure for inside an application includes:
  18. src/
  19. for Python code
  20. conf/
  21. for configuration (``.ini``) files to be installed
  22. static/
  23. for static HTML and js resources
  24. templates/
  25. for data to be put through a template engine
  26. docs/
  27. for helpful notes
  28. The python code is structured simply as
  29. ``module/package.py``,
  30. where module may be "filebrowser" or "jobsub". Because it is unlikely that
  31. there are going to be huge conflicts, we're going without a deep nested
  32. hierarchy.
  33. URL Layout
  34. ==========
  35. ``core/src/desktop/urls.py`` contains the current layout for top-level URLs.
  36. For the URLs within your application, you should make your own ``urls.py``
  37. which will be automatically rooted at ``/yourappname/`` in the global
  38. namespace. See ``apps/hello/src/hello/urls.py`` for an example.
  39. Development Prerequisites
  40. ===========================
  41. You'll need these library development packages and tools installed on
  42. your system:
  43. Debian:
  44. * ant
  45. * asciidoc
  46. * gcc
  47. * g++
  48. * libkrb5-dev
  49. * libmysqlclient-dev
  50. * libsasl2-dev
  51. * libsqlite3-dev
  52. * libxml2-dev
  53. * libxslt-dev
  54. * mvn (from ``maven2`` package or tarball)
  55. * openldap-dev
  56. * python-dev
  57. * python-simplejson
  58. CentOS:
  59. * ant
  60. * asciidoc
  61. * cyrus-sasl-devel
  62. * gcc
  63. * gcc-c++
  64. * krb5-devel
  65. * libxml2-devel
  66. * libxslt-devel
  67. * mvn (from ``maven2`` package or tarball)
  68. * mysql
  69. * mysql-devel
  70. * openldap-devel
  71. * python-devel
  72. * python-simplejson
  73. * sqlite-devel
  74. MacOS (mac port):
  75. * liblxml
  76. * libxml2
  77. * libxslt
  78. * mysql5-devel
  79. * simplejson (easy_install)
  80. * sqlite3
  81. Getting Started
  82. ===============
  83. To build and get the core server running::
  84. $ export HADOOP_HOME=<path-to-hadoop-home>
  85. $ git clone http://github.com/cloudera/hue.git
  86. $ cd hue
  87. $ make apps
  88. $ build/env/bin/hue runserver_plus
  89. To start the helper daemons::
  90. $ build/env/bin/hue beeswax_server
  91. $ build/env/bin/hue jobsubd
  92. Now Hue should be running on http://localhost:8000.
  93. FAQ
  94. ===
  95. 1: What does "Exception: no app!" mean?
  96. Your template has an error in it. Check for messages from the server that
  97. look like::
  98. INFO:root:Processing exception: Unclosed tag 'if'. Looking for one of: else, endif
  99. 2: What do I do if I get "There was an error launching ..."?
  100. Turn on debugging by issuing ``dbug.cookie()`` in a Firebug console.
  101. Django Conventions
  102. ==================
  103. If you need to name your urls
  104. (http://docs.djangoproject.com/en/dev/topics/http/urls/#naming-url-patterns)
  105. because there's ambiguity in the view, be sure to prefix the name
  106. with the application name. The url name namespace is global. So
  107. ``jobsub.list`` is fine, but ``list`` is not.
  108. Hue is using Django 1.2, which supports the notion of URL namespaces:
  109. http://docs.djangoproject.com/en/dev/topics/http/urls/#url-namespaces.
  110. We have yet to move over our URLs to this construct. Brownie points for the
  111. developer who takes this on.
  112. Using and Installing Thrift
  113. ===========================
  114. Right now, we check in the generated thrift code.
  115. To generate the code, you'll need the thrift binary version 0.7.0.
  116. Please download from http://thrift.apache.org/.
  117. When preparing ``.thrift`` files, you can use she-bangs to generate
  118. the python bindings like so::
  119. #!/usr/bin/env thrift -r --gen py:new_style -o ../../../
  120. Profiling Hue Apps
  121. ==================
  122. Hue has a profiling system built in, which can be used to analyze server-side
  123. performance of applications. To enable profiling::
  124. $ build/env/bin/hue runprofileserver
  125. Then, access the page that you want to profile. This will create files like
  126. /tmp/useradmin.users.000072ms.2011-02-21T13:03:39.745851.prof. The format for
  127. the file names is /tmp/<app_module>.<page_url>.<time_taken>.<timestamp>.prof.
  128. Hue uses the hotshot profiling library for instrumentation. The documentation
  129. for this library is located at: http://docs.python.org/library/hotshot.html.
  130. To make use of the profiling data quickly, you can create a script that does
  131. the following::
  132. #!/usr/bin/python
  133. import hotshot.stats
  134. import sys
  135. stats = hotshot.stats.load(sys.argv[1])
  136. stats.sort_stats('cumulative', 'calls')
  137. stats.print_stats(100)
  138. This script takes in a .prof file, and orders function calls by the cumulative
  139. time spent in that function, followed by the number of times the function was
  140. called, and then prints out the top 100 time-wasters. For information on the
  141. other stats available, take a look at this website:
  142. http://docs.python.org/library/profile.html#pstats.Stats