Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2702 from pjain1/improve_docs 

how to query in the querying section, correct default for select strategy, formatting
This commit is contained in:
Gian Merlino 2016-03-22 16:40:35 -07:00
parent 826b371259 39ecb9929d
commit 451c0bc6d8
3 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/content/configuration/indexing-service.md
View File

@ -184,7 +184,7 @@ Workers are assigned tasks until capacity.
|Property|Description|Default| |Property|Description|Default|
|--------|-----------|-------| |--------|-----------|-------|
|`type`|`fillCapacity`.|fillCapacity| |`type`|`fillCapacity`.|required; must be `fillCapacity`|
##### Fill Capacity With Affinity ##### Fill Capacity With Affinity
@ -192,7 +192,7 @@ An affinity config can be provided.
|Property|Description|Default| |Property|Description|Default|
|--------|-----------|-------| |--------|-----------|-------|
|`type`|`fillCapacityWithAffinity`.|fillCapacityWithAffinity| |`type`|`fillCapacityWithAffinity`.|required; must be `fillCapacityWithAffinity`|
|`affinity`|JSON object mapping a datasource String name to a list of indexing service middle manager host:port String values. Druid doesn't perform DNS resolution, so the 'host' value must match what is configured on the middle manager and what the middle manager announces itself as (examine the Overlord logs to see what your middle manager announces itself as).|{}| |`affinity`|JSON object mapping a datasource String name to a list of indexing service middle manager host:port String values. Druid doesn't perform DNS resolution, so the 'host' value must match what is configured on the middle manager and what the middle manager announces itself as (examine the Overlord logs to see what your middle manager announces itself as).|{}|
Tasks will try to be assigned to preferred workers. Fill capacity strategy is used if no preference for a datasource specified. Tasks will try to be assigned to preferred workers. Fill capacity strategy is used if no preference for a datasource specified.
@ -203,7 +203,7 @@ The workers with the least amount of tasks is assigned the task.
|Property|Description|Default| |Property|Description|Default|
|--------|-----------|-------| |--------|-----------|-------|
|`type`|`equalDistribution`.|fillCapacity| |`type`|`equalDistribution`.|required; must be `equalDistribution`|
##### Javascript ##### Javascript
@ -216,7 +216,7 @@ its better to write a druid extension module with extending current worker selec
|Property|Description|Default| |Property|Description|Default|
|--------|-----------|-------| |--------|-----------|-------|
|`type`|`javascript`.|javascript| |`type`|`javascript`.|required; must be `javascript`|
|`function`|String representing javascript function|| |`function`|String representing javascript function||
Example: a function that sends batch_index_task to workers 10.0.0.1 and 10.0.0.2 and all other tasks to other available workers. Example: a function that sends batch_index_task to workers 10.0.0.1 and 10.0.0.2 and all other tasks to other available workers.

3
docs/content/querying/joins.md
View File

@ -4,8 +4,7 @@ layout: doc_page
# Joins # Joins
Druid has limited support for joins through [query-time lookups](../querying/lookups.html). The common use case of Druid has limited support for joins through [query-time lookups](../querying/lookups.html). The common use case of
query-time lookups is to replace one dimension value that (e.g. a String ID) with another value (e.g. a human-readable query-time lookups is to replace one dimension value (e.g. a String ID) with another value (e.g. a human-readable String value). This is similar to a star-schema join.
String value). This is similar a star-schema join.
Druid does not yet have full support for joins. Although Druid’s storage format would allow for the implementation Druid does not yet have full support for joins. Although Druid’s storage format would allow for the implementation
of joins (there is no loss of fidelity for columns included as dimensions), full support for joins have not yet been implemented yet of joins (there is no loss of fidelity for columns included as dimensions), full support for joins have not yet been implemented yet

7
docs/content/querying/querying.md
View File

@ -8,7 +8,12 @@ Querying
Queries are made using an HTTP REST style request to queryable nodes ([Broker](../design/broker.html), Queries are made using an HTTP REST style request to queryable nodes ([Broker](../design/broker.html),
[Historical](../design/historical.html), or [Realtime](../design/realtime.html)). The [Historical](../design/historical.html), or [Realtime](../design/realtime.html)). The
query is expressed in JSON and each of these node types expose the same query is expressed in JSON and each of these node types expose the same
REST query interface. For normal Druid operations, queries should be issued to the broker nodes. REST query interface. For normal Druid operations, queries should be issued to the broker nodes. Queries can be posted
to the queryable nodes like this -
```bash
curl -X POST '<queryable_host>:<port>/druid/v2/?pretty' -H 'Content-Type:application/json' -d @<query_json_file>
```
Druid's native query language is JSON over HTTP, although many members of the community have contributed different Druid's native query language is JSON over HTTP, although many members of the community have contributed different
[client libraries](../development/libraries.html) in other languages to query Druid. [client libraries](../development/libraries.html) in other languages to query Druid.