153495068b
* Doc update for new input source and input format. - The input source and input format are promoted in all docs under docs/ingestion - All input sources including core extension ones are located in docs/ingestion/native-batch.md - All input formats and parsers including core extension ones are localted in docs/ingestion/data-formats.md - New behavior of the parallel task with different partitionsSpecs are documented in docs/ingestion/native-batch.md * parquet * add warning for range partitioning with sequential mode * hdfs + s3, gs * add fs impl for gs * address comments * address comments * gcs
3.5 KiB
| id | title | sidebar_label |
|---|---|---|
| javascript | JavaScript programming guide | JavaScript functionality |
This page discusses how to use JavaScript to extend Apache Druid.
Examples
JavaScript can be used to extend Druid in a variety of ways:
- Aggregators
- Extraction functions
- Filters
- Post-aggregators
- Input parsers
- Router strategy
- Worker select strategy
JavaScript can be injected dynamically at runtime, making it convenient to rapidly prototype new functionality without needing to write and deploy Druid extensions.
Druid uses the Mozilla Rhino engine at optimization level 9 to compile and execute JavaScript.
Security
Druid does not execute JavaScript functions in a sandbox, so they have full access to the machine. So JavaScript
functions allow users to execute arbitrary code inside druid process. So, by default, JavaScript is disabled.
However, on dev/staging environments or secured production environments you can enable those by setting
the configuration property
druid.javascript.enabled = true.
Global variables
Avoid using global variables. Druid may share the global scope between multiple threads, which can lead to unpredictable results if global variables are used.
Performance
Simple JavaScript functions typically have a slight performance penalty to native speed. More complex JavaScript functions can have steeper performance penalties. Druid compiles JavaScript functions once on each data process per query.
You may need to pay special attention to garbage collection when making heavy use of JavaScript functions, especially garbage collection of the compiled classes themselves. Be sure to use a garbage collector configuration that supports timely collection of unused classes (this is generally easier on JDK8 with the Metaspace than it is on JDK7).
JavaScript vs. Native Extensions
Generally we recommend using JavaScript when security is not an issue, and when speed of development is more important than performance or memory use. If security is an issue, or if performance and memory use are of the utmost importance, we recommend developing a native Druid extension.
In addition, native Druid extensions are more flexible than JavaScript functions. There are some kinds of extensions (like sketches) that must be written as native Druid extensions due to their need for custom data formats.