diff --git a/benchmarks/src/main/java/io/druid/benchmark/ConciseComplementBenchmark.java b/benchmarks/src/main/java/io/druid/benchmark/ConciseComplementBenchmark.java new file mode 100644 index 000000000000..944c59f03c85 --- /dev/null +++ b/benchmarks/src/main/java/io/druid/benchmark/ConciseComplementBenchmark.java @@ -0,0 +1,52 @@ +/* + * Licensed to Metamarkets Group Inc. (Metamarkets) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. Metamarkets licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +package io.druid.benchmark; + + +import it.uniroma3.mat.extendedset.intset.ImmutableConciseSet; +import org.openjdk.jmh.annotations.Benchmark; +import org.openjdk.jmh.annotations.BenchmarkMode; +import org.openjdk.jmh.annotations.Mode; +import org.openjdk.jmh.annotations.OutputTimeUnit; +import org.openjdk.jmh.annotations.Param; +import org.openjdk.jmh.annotations.Scope; +import org.openjdk.jmh.annotations.State; +import org.openjdk.jmh.infra.Blackhole; + +import java.util.concurrent.TimeUnit; + +@State(Scope.Benchmark) +public class ConciseComplementBenchmark +{ + + // Number of rows to read, the test will read random rows + @Param({"1000", "10000", "100000", "1000000", "1000000"}) + int emptyRows; + + @Benchmark + @BenchmarkMode(Mode.AverageTime) + @OutputTimeUnit(TimeUnit.MICROSECONDS) + public void uncompressed(Blackhole blackhole) + { + final ImmutableConciseSet set = ImmutableConciseSet.complement(null, emptyRows); + blackhole.consume(set); + assert (emptyRows == set.size()); + } +} diff --git a/docs/content/Tutorial-A-First-Look-at-Druid.md b/docs/content/Tutorial:-A-First-Look-at-Druid.md similarity index 100% rename from docs/content/Tutorial-A-First-Look-at-Druid.md rename to docs/content/Tutorial:-A-First-Look-at-Druid.md diff --git a/docs/content/Tutorial-All-About-Queries.md b/docs/content/Tutorial:-All-About-Queries.md similarity index 100% rename from docs/content/Tutorial-All-About-Queries.md rename to docs/content/Tutorial:-All-About-Queries.md diff --git a/docs/content/Tutorial-Loading-Batch-Data.md b/docs/content/Tutorial:-Loading-Batch-Data.md similarity index 100% rename from docs/content/Tutorial-Loading-Batch-Data.md rename to docs/content/Tutorial:-Loading-Batch-Data.md diff --git a/docs/content/Tutorial-Loading-Streaming-Data.md b/docs/content/Tutorial:-Loading-Streaming-Data.md similarity index 100% rename from docs/content/Tutorial-Loading-Streaming-Data.md rename to docs/content/Tutorial:-Loading-Streaming-Data.md diff --git a/docs/content/Tutorial-The-Druid-Cluster.md b/docs/content/Tutorial:-The-Druid-Cluster.md similarity index 100% rename from docs/content/Tutorial-The-Druid-Cluster.md rename to docs/content/Tutorial:-The-Druid-Cluster.md diff --git a/docs/content/configuration/index.md b/docs/content/configuration/index.md index b1ef3ea55214..6a4045930bce 100644 --- a/docs/content/configuration/index.md +++ b/docs/content/configuration/index.md @@ -68,7 +68,7 @@ The indexing service also uses its own set of paths. These configs can be includ If `druid.zk.paths.base` and `druid.zk.paths.indexer.base` are both set, and none of the other `druid.zk.paths.*` or `druid.zk.paths.indexer.*` values are set, then the other properties will be evaluated relative to their respective `base`. For example, if `druid.zk.paths.base` is set to `/druid1` and `druid.zk.paths.indexer.base` is set to `/druid2` then `druid.zk.paths.announcementsPath` will default to `/druid1/announcements` while `druid.zk.paths.indexer.announcementsPath` will default to `/druid2/announcements`. -The following path is used service discovery and are **not** affected by `druid.zk.paths.base` and **must** be specified separately. +The following path is used for service discovery. It is **not** affected by `druid.zk.paths.base` and **must** be specified separately. |Property|Description|Default| |--------|-----------|-------| diff --git a/docs/content/configuration/indexing-service.md b/docs/content/configuration/indexing-service.md index 6a2e2e51b167..afe4b83c2b47 100644 --- a/docs/content/configuration/indexing-service.md +++ b/docs/content/configuration/indexing-service.md @@ -95,7 +95,7 @@ The overlord can dynamically change worker behavior. The JSON object can be submitted to the overlord via a POST request at: ``` -http://:/druid/indexer/v1/worker +http://:/druid/indexer/v1/worker ``` Optional Header Parameters for auditing the config change can also be specified. @@ -153,7 +153,7 @@ Issuing a GET request at the same URL will return the current worker config spec To view the audit history of worker config issue a GET request to the URL - ``` -http://:/druid/indexer/v1/worker/history?interval= +http://:/druid/indexer/v1/worker/history?interval= ``` default value of interval can be specified by setting `druid.audit.manager.auditHistoryMillis` (1 week if not configured) in overlord runtime.properties. diff --git a/docs/content/design/design.md b/docs/content/design/design.md index 109ea876b800..e9fa1fe426ee 100644 --- a/docs/content/design/design.md +++ b/docs/content/design/design.md @@ -39,7 +39,7 @@ This separation allows each node to only care about what it is best at. By separ The following diagram shows how queries and data flow through this architecture, and which nodes (and external dependencies, discussed below) are involved: - + All nodes can be run in some highly available fashion, either as symmetric peers in a share-nothing cluster or as hot-swap failover nodes. @@ -51,7 +51,7 @@ Aside from these nodes, there are 3 external dependencies to the system: The following diagram illustrates the cluster's management layer, showing how certain nodes and dependencies help manage the cluster by tracking and exchanging metadata: - + ### Segments and Data Storage diff --git a/docs/content/design/indexing-service.md b/docs/content/design/indexing-service.md index 910448df23ca..eac3083bfa06 100644 --- a/docs/content/design/indexing-service.md +++ b/docs/content/design/indexing-service.md @@ -13,7 +13,7 @@ Overlords and middle managers may run on the same node or across multiple nodes Indexing Service Overview ------------------------- -![Indexing Service](../img/indexing_service.png "Indexing Service") +![Indexing Service](../../img/indexing_service.png "Indexing Service")