mirror of
https://github.com/apache/impala.git
synced 2026-01-06 15:01:43 -05:00
723509a571
If the leopard front end is run on a pristine system, the front end will raise exceptions, because the directories containing reports and schedules do not yet exist. Since it's the controller's responsibility to create and populate these filesystem artifacts, in the frontend, let's just protect against the exception and log warnings. Testing: Before the fix, the reload_reports thread would immediately raise an exception and the thread would die; loading the Web app in a browser would cause an internal server error. After the fix, the reload_reports thread logs a warning but continues to run, and loading the Web app in a browser presents an appropriately empty listing of run names and schedules. Change-Id: I186174db136694d3df04d9159362c6eeaa70b5b8 Reviewed-on: http://gerrit.cloudera.org:8080/2164 Reviewed-by: Michael Brown <mikeb@cloudera.com> Tested-by: Internal Jenkins
This package runs the query generator continuously. Compares Impala and Postgres results
for a randomly generated query and produces several reports per day. Reports are
displayed on a web page which allows the user to conveniently examine the discovered
issues. The user can also start a custom run against a private Impala branch using the
web interface.
Requirements:
Docker -- A docker image with Impala and Postgres installed and functional database
loaded into Postgres.
To get started, run ./controller.py and ./front_end.py. You should be able to view the
web page at http://localhost:5000. Results and logs are saved to /tmp/query_gen