druid/web-console
Vadim Ogievetsky 7addfc27da
Web console: fine grained capabilities / graceful degradation (#8805)
* fine grained capabilities

* fix tests

* configure all cards

* better detection

* update tests

* rename server to service

* node -> service

* remove console log

* better loader in data loader
2019-11-05 23:39:14 -08:00
..
assets Support HDFS firehose (#8752) 2019-10-28 08:22:20 -07:00
lib Web console: Fix segment re-ingest (#8454) 2019-09-03 12:13:57 -07:00
old-console
script Web console: Better data loader flow (#8763) 2019-10-28 08:08:46 -07:00
src Web console: fine grained capabilities / graceful degradation (#8805) 2019-11-05 23:39:14 -08:00
.gitignore Web console: Better build experience (#8389) 2019-08-24 11:35:30 -07:00
.stylelintrc.json
README.md
babel.config.js Web console: work in IE11 (#8804) 2019-10-31 21:03:05 -07:00
console-config.js Web console: Save query context also (#8395) 2019-08-25 16:56:27 -07:00
console.html
favicon.png
package-lock.json Web console: Update versions and dependencies (#8751) 2019-10-25 17:53:06 -07:00
package.json Web console: Update versions and dependencies (#8751) 2019-10-25 17:53:06 -07:00
pom.xml Use Codecov (#8388) 2019-08-28 08:49:30 -07:00
sasslint.json
tsconfig.json Web console: Better build experience (#8389) 2019-08-24 11:35:30 -07:00
tslint.json
unified-console.html Web console: Update versions and dependencies (#8751) 2019-10-25 17:53:06 -07:00
webpack.config.js Web console: work in IE11 (#8804) 2019-10-31 21:03:05 -07:00

README.md

Apache Druid web console

This is the unified Druid web console that servers as a data management layer for Druid.

How to watch and run for development

  1. You need to be withing the web-console directory
  2. Install the modules with npm install
  3. Run npm start will start in development mode and will proxy druid requests to localhost:8888

Note: you can provide an environment variable to proxy to a different Druid host like so: druid_host=1.2.3.4:8888 npm start Note: you can provide an environment variable use webpack-bundle-analyzer as a plugin in the build script or like so: BUNDLE_ANALYZER_PLUGIN='TRUE' npm start

Description of the directory structure

A lot of the directory structure was created to preserve the existing console structure as much as possible.

As part of this repo:

  • console.html - Entry file for the overlord console
  • lib/ - A place where some overrides to the react-table stylus files live, this is outside of the normal SCSS build system.
  • old-console/ - Files for the overlord console
  • public/ - The compiled destination of the file powering this console
  • assets/ - The images (and other assets) used within the console
  • script/ - Some helper bash scripts for running this console
  • src/ - This directory (together with lib) constitutes all the source code for this console

Generated/copied dynamically

  • index.html - Entry file for the coordinator console
  • pages/ - The files for the older coordinator console
  • coordinator-console/ - Files for the coordinator console

List of non SQL data reading APIs used

GET /status
GET /druid/indexer/v1/supervisor?full
POST /druid/indexer/v1/worker
GET /druid/indexer/v1/workers
GET /druid/coordinator/v1/loadqueue?simple
GET /druid/coordinator/v1/config
GET /druid/coordinator/v1/metadata/datasources?includeUnused
GET /druid/coordinator/v1/rules
GET /druid/coordinator/v1/config/compaction
GET /druid/coordinator/v1/tiers

Updating the list of license files

From the web-console directory run script/licenses