This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-training.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 4d98ec0  Site checkin for project Training: Website
4d98ec0 is described below

commit 4d98ec01d14948b6900cc7d1df535c7a291d1eab
Author: jenkins <[email protected]>
AuthorDate: Wed Dec 11 23:03:03 2024 +0000

    Site checkin for project Training: Website
---
 dependencies.html                                  |  10 +++---
 .../druid/WEB-INF/classes/images/druid-logo.png    | Bin 0 -> 28426 bytes
 presentations/druid/images/druid-logo.png          | Bin 0 -> 28426 bytes
 presentations/druid/index.html                     |  40 +++++++++++----------
 presentations/training/demo/index.html             |   2 +-
 5 files changed, 27 insertions(+), 25 deletions(-)

diff --git a/dependencies.html b/dependencies.html
index 8edf9e8..f4b84b5 100644
--- a/dependencies.html
+++ b/dependencies.html
@@ -771,7 +771,7 @@
    <tr class="b"> 
     <td align="left">training-content-apache-druid-1.0.0-SNAPSHOT.war</td> 
     <td align="right">2.9 MB</td> 
-    <td align="right">212</td> 
+    <td align="right">214</td> 
     <td align="right">0</td> 
     <td align="right">0</td> 
     <td align="center">-</td> 
@@ -923,8 +923,8 @@
    </tr> 
    <tr class="a"> 
     <td align="right">20</td> 
-    <td align="right">204.4 MB</td> 
-    <td align="right">4444</td> 
+    <td align="right">204.5 MB</td> 
+    <td align="right">4446</td> 
     <td align="right">7</td> 
     <td align="right">3</td> 
     <td align="center">1.8</td> 
@@ -932,8 +932,8 @@
    </tr> 
    <tr class="b"> 
     <td align="right">compile: 20</td> 
-    <td align="right">compile: 204.4 MB</td> 
-    <td align="right">compile: 4444</td> 
+    <td align="right">compile: 204.5 MB</td> 
+    <td align="right">compile: 4446</td> 
     <td align="right">compile: 7</td> 
     <td align="right">compile: 3</td> 
     <td align="center">1.8</td> 
diff --git a/presentations/druid/WEB-INF/classes/images/druid-logo.png 
b/presentations/druid/WEB-INF/classes/images/druid-logo.png
new file mode 100644
index 0000000..017e569
Binary files /dev/null and 
b/presentations/druid/WEB-INF/classes/images/druid-logo.png differ
diff --git a/presentations/druid/images/druid-logo.png 
b/presentations/druid/images/druid-logo.png
new file mode 100644
index 0000000..017e569
Binary files /dev/null and b/presentations/druid/images/druid-logo.png differ
diff --git a/presentations/druid/index.html b/presentations/druid/index.html
index bc5362c..5ae1ede 100644
--- a/presentations/druid/index.html
+++ b/presentations/druid/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="en"><head><meta charset="utf-8" /><meta 
name="viewport" content="width=device-width, initial-scale=1.0, 
maximum-scale=1.0, user-scalable=no, minimal-ui" /><title>What is Apache 
Druid?</title><link rel="stylesheet" href="reveal.js-5.1.0/dist/reset.css" 
/><link rel="stylesheet" href="reveal.js-5.1.0/dist/reveal.css" /><link 
href="css/c3.min.css" rel="stylesheet" /><script src="js/d3.min.js" 
charset="utf-8"></script><script src="js/c3.min.js"></script><link rel="s [...]
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8" /><meta 
name="viewport" content="width=device-width, initial-scale=1.0, 
maximum-scale=1.0, user-scalable=no, minimal-ui" /><title>Apache 
Druid</title><meta name="description" content="Introduction to Apache Druid" 
/><meta name="keywords" content="Apache, Druid" /><meta name="author" 
content="Your Name" /><link rel="stylesheet" 
href="reveal.js-5.1.0/dist/reset.css" /><link rel="stylesheet" 
href="reveal.js-5.1.0/dist/reveal.css" /> [...]
   float: right
 }
 
@@ -413,40 +413,42 @@ ul.byline {
 ul.byline li + li {
   margin-top: 0.25em;
 }
-</style></head><body><div class="header"><div class="left"></div><div 
class="right"></div></div><div class="reveal"><div class="slides"><section 
id="_what_is_apache_druid"><h2>What is Apache Druid?</h2><div 
class="slide-content"><div class="paragraph"><p>Apache Druid is a fast and 
modern analytics database.
+</style><link rel="stylesheet" 
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/all.min.css";
 /><link rel="stylesheet" 
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/v4-shims.min.css";
 /></head><body><div class="header"><div class="left"></div><div 
class="right"></div></div><div class="reveal"><div class="slides"><section 
id="apache-druid"><h2>Apache Druid</h2><div class="slide-content"><div 
class="imageblock"><img src="images/druid-logo.png" alt=" [...]
+<aside class="notes"><div class="paragraph"><p>Introduce yourself, and your 
role in the Apache Druid community.</p></div></aside></div></section>
+<section id="what-is-apache-druid"><h2>What is Apache Druid?</h2><div 
class="slide-content"><div class="paragraph"><p>Apache Druid is a fast and 
modern analytics database.
 Druid is designed for workflows where fast ad-hoc analytics, instant data 
visibility, or supporting high concurrency is important.
 As such, Druid is often used to power UIs where an interactive, consistent 
user experience is desired.</p></div></div></section>
-<section id="_druid_high_level_architecture"><h2>Druid High Level 
Architecture</h2><div class="slide-content"><div class="paragraph"><p>Druid’s 
core design combines ideas from data warehouses, timeseries databases, and 
search systems to create a high performance real-time analytics database for a 
broad range of use cases. Druid merges key characteristics of each of the 3 
systems into its ingestion layer, storage format, querying layer, and core 
architecture.</p></div>
+<section id="druid-high-level-architecture"><h2>Druid High Level 
Architecture</h2><div class="slide-content"><div class="paragraph"><p>Druid’s 
core design combines ideas from data warehouses, timeseries databases, and 
search systems to create a high performance real-time analytics database for a 
broad range of use cases. Druid merges key characteristics of each of the 3 
systems into its ingestion layer, storage format, querying layer, and core 
architecture.</p></div>
 <div class="imageblock"><img src="http://druid.apache.org/img/diagram-2.png"; 
alt="diagram 2" width="40%"></div></div></section>
-<section id="_druid_features"><h2>Druid Features</h2><div 
class="slide-content"><div class="paragraph"><p>Apache Druid provides following 
features:</p></div>
+<section id="druid-features"><h2>Druid Features</h2><div 
class="slide-content"><div class="paragraph"><p>Apache Druid provides following 
features:</p></div>
 <div class="ulist"><ul><li><p>Column Oriented Storage</p></li><li><p>Streaming 
and batch ingest</p></li><li><p>Native search indexes</p></li><li><p>Flexible 
schemas</p></li><li><p>Time-optimized partitioning</p></li><li><p>SQL 
support</p></li><li><p>Horizontal 
scalability</p></li></ul></div></div></section>
-<section id="_druid_integration"><h2>Druid: Integration</h2><div 
class="slide-content"><div class="paragraph"><p>Druid is complementary to many 
open source data technologies in the Apache Software Foundation including 
Apache Kafka, Apache Hadoop, Apache Flink, and more.</p></div>
+<section id="druid-integration"><h2>Druid: Integration</h2><div 
class="slide-content"><div class="paragraph"><p>Druid is complementary to many 
open source data technologies in the Apache Software Foundation including 
Apache Kafka, Apache Hadoop, Apache Flink, and more.</p></div>
 <div class="paragraph"><p>Druid typically sits between a storage or processing 
layer and the end user, and acts as a query layer to serve analytic 
workloads.</p></div>
 <div class="imageblock"><img src="http://druid.apache.org/img/diagram-3.png"; 
alt="diagram 3" width="60%"></div></div></section>
-<section id="_druid_ingestion"><h2>Druid: Ingestion</h2><div 
class="slide-content"><div class="paragraph"><p>Druid supports both streaming 
and batch ingestion. Druid connects to a source of raw data, typically a 
message bus such as Apache Kafka (for streaming data loads), or a distributed 
filesystem such as HDFS (for batch data loads).</p></div>
+<section id="druid-ingestion"><h2>Druid: Ingestion</h2><div 
class="slide-content"><div class="paragraph"><p>Druid supports both streaming 
and batch ingestion. Druid connects to a source of raw data, typically a 
message bus such as Apache Kafka (for streaming data loads), or a distributed 
filesystem such as HDFS (for batch data loads).</p></div>
 <div class="paragraph"><p>Druid converts raw data stored in a source to a more 
read-optimized format (called a Druid “segment”) in a process calling 
“indexing”.</p></div>
 <div class="imageblock"><img src="http://druid.apache.org/img/diagram-4.png"; 
alt="diagram 4" width="60%"></div></div></section>
-<section id="_druid_storage"><h2>Druid: Storage</h2><div 
class="slide-content"><div class="paragraph"><p>Like many analytic data stores, 
Druid stores data in columns. Depending on the type of column (string, number, 
etc), different compression and encoding methods are applied. Druid also builds 
different types of indexes based on the column type.</p></div>
+<section id="druid-storage"><h2>Druid: Storage</h2><div 
class="slide-content"><div class="paragraph"><p>Like many analytic data stores, 
Druid stores data in columns. Depending on the type of column (string, number, 
etc), different compression and encoding methods are applied. Druid also builds 
different types of indexes based on the column type.</p></div>
 <div class="paragraph"><p>Similar to search systems, Druid builds inverted 
indexes for string columns for fast search and filter.</p></div></div></section>
-<section id="_druid_pre_aggregation"><h2>Druid: Pre-aggregation</h2><div 
class="slide-content"><div class="paragraph"><p>Unlike many traditional 
systems, Druid can optionally pre-aggregate data as it is ingested.
+<section id="druid-pre-aggregation"><h2>Druid: Pre-aggregation</h2><div 
class="slide-content"><div class="paragraph"><p>Unlike many traditional 
systems, Druid can optionally pre-aggregate data as it is ingested.
 This pre-aggregation step is known as rollup, and can lead to dramatic storage 
savings.</p></div>
 <div class="imageblock"><img src="http://druid.apache.org/img/diagram-5.png"; 
alt="diagram 5" width="60%"></div></div></section>
-<section id="_druid_querying"><h2>Druid: Querying</h2><div 
class="slide-content"><div class="paragraph"><p>Druid supports querying data 
through JSON-over-HTTP and SQL. In addition to standard SQL operators, Druid 
supports unique operators that leverage its suite of approximate algorithms to 
provide rapid counting, ranking, and quantiles.</p></div>
+<section id="druid-querying"><h2>Druid: Querying</h2><div 
class="slide-content"><div class="paragraph"><p>Druid supports querying data 
through JSON-over-HTTP and SQL. In addition to standard SQL operators, Druid 
supports unique operators that leverage its suite of approximate algorithms to 
provide rapid counting, ranking, and quantiles.</p></div>
 <div class="imageblock"><img src="http://druid.apache.org/img/diagram-6.png"; 
alt="diagram 6" width="60%"></div></div></section>
-<section id="_druid_high_level_architecture_diagram"><h2>Druid: High Level 
Architecture Diagram</h2><div class="slide-content"><div 
class="imageblock"><img src="http://druid.apache.org/img/diagram-7.png"; 
alt="diagram 7"></div></div></section>
-<section id="_druid_architecure"><h2>Druid: Architecure</h2><div 
class="slide-content"><div class="paragraph"><p>Druid has a microservice-based 
architecture can be thought of as a disassembled database. Each core service in 
Druid (ingestion, querying, and coordination) can be separately or jointly 
deployed on commodity hardware.</p></div>
+<section id="druid-high-level-architecture-diagram"><h2>Druid: High Level 
Architecture Diagram</h2><div class="slide-content"><div 
class="imageblock"><img src="http://druid.apache.org/img/diagram-7.png"; 
alt="diagram 7"></div></div></section>
+<section id="druid-architecure"><h2>Druid: Architecure</h2><div 
class="slide-content"><div class="paragraph"><p>Druid has a microservice-based 
architecture can be thought of as a disassembled database. Each core service in 
Druid (ingestion, querying, and coordination) can be separately or jointly 
deployed on commodity hardware.</p></div>
 <div class="paragraph"><p>Druid explicitly names every main service to allow 
the operator to fine tune each service based on the use case and 
workload.</p></div></div></section>
-<section id="_druid_operations"><h2>Druid: Operations</h2><div 
class="slide-content"><div class="paragraph"><p>Druid is designed to power 
applications that need to be up 24 hours a day, 7 days a week. Druid possesses 
several features to ensure uptime and no data loss.</p></div>
+<section id="druid-operations"><h2>Druid: Operations</h2><div 
class="slide-content"><div class="paragraph"><p>Druid is designed to power 
applications that need to be up 24 hours a day, 7 days a week. Druid possesses 
several features to ensure uptime and no data loss.</p></div>
 <div class="ulist"><ul><li><p><strong>Data 
replication</strong></p></li><li><p><strong>Independent 
services</strong></p></li><li><p><strong>Automatic data 
backup</strong></p></li><li><p><strong>Rolling 
updates</strong></p></li></ul></div></div></section>
-<section id="_druid_operations_data_replication"><h2>Druid Operations : Data 
replication</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Data replication</strong>
+<section id="druid-operations-data-replication"><h2>Druid Operations : Data 
replication</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Data replication</strong>
 All data in Druid is replicated a configurable number of times so single 
server failures have no impact on queries.</p></div></div></section>
-<section id="_druid_operations_independent_services"><h2>Druid Operations : 
Independent services</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Independent services</strong>
+<section id="druid-operations-independent-services"><h2>Druid Operations : 
Independent services</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Independent services</strong>
 Druid explicitly names all of its main services and each service can be fine 
tuned based on use case. Services can independently fail without impacting 
other services. For example, if the ingestion services fails, no new data is 
loaded in the system, but existing data remains 
queryable.</p></div></div></section>
-<section id="_druid_operations_automatic_data_backup"><h2>Druid Operations : 
Automatic data backup</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Automatic data backup</strong>
+<section id="druid-operations-automatic-data-backup"><h2>Druid Operations : 
Automatic data backup</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Automatic data backup</strong>
 Druid automatically backs up all indexed data to a filesystem such as HDFS. 
You can lose your entire Druid cluster and quickly restore it from this backed 
up data.</p></div></div></section>
-<section id="_druid_operations_rolling_updates"><h2>Druid Operations : Rolling 
updates</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Rolling updates</strong>
+<section id="druid-operations-rolling-updates"><h2>Druid Operations : Rolling 
updates</h2><div class="slide-content"><div 
class="paragraph"><p><strong>Rolling updates</strong>
 You can update a Druid cluster with no downtime and no impact to end users 
through rolling updates. All Druid releases are backwards compatible with the 
previous version.</p></div></div></section>
-<section id="_further_sources"><h2>Further Sources</h2><div 
class="slide-content"><div class="paragraph"><p>Refer official documents on 
Apache Druid here:</p></div>
+<section id="further-sources"><h2>Further Sources</h2><div 
class="slide-content"><div class="paragraph"><p>Refer official documents on 
Apache Druid here:</p></div>
 <div class="ulist"><ul><li><p><strong>Druid Documentation</strong>: <a 
href="http://druid.apache.org/"; 
class="bare">http://druid.apache.org/</a></p></li><li><p><strong>Druid 
Technology</strong>: <a href="http://druid.apache.org/technology"; 
class="bare">http://druid.apache.org/technology</a></p></li></ul></div></div></section></div></div><div
 class="footer"><div class="left"></div><div class="right"></div></div><script 
src="reveal.js-5.1.0/dist/reveal.js"></script><script>Array.prototype. [...]
   if (slide.getAttribute('data-background-color')) return;
   // user needs to explicitly say he wants CSS color to override otherwise we 
might break custom css or theme (#226)
@@ -482,7 +484,7 @@ Reveal.initialize({
   // page/copying the URL will return you to the same slide
   hash: false,
   // Push each slide change to the browser history. Implies `hash: true`
-  history: false,
+  history: true,
   // Enable keyboard shortcuts for navigation
   keyboard: true,
   // Enable the slide overview mode
@@ -490,7 +492,7 @@ Reveal.initialize({
   // Disables the default reveal.js slide layout so that you can use custom 
CSS layout
   disableLayout: false,
   // Vertical centering of slides
-  center: true,
+  center: false,
   // Enables touch navigation on devices with touch input
   touch: true,
   // Loop the presentation
diff --git a/presentations/training/demo/index.html 
b/presentations/training/demo/index.html
index 6d936a4..7537128 100644
--- a/presentations/training/demo/index.html
+++ b/presentations/training/demo/index.html
@@ -414,7 +414,7 @@ ul.byline li + li {
   margin-top: 0.25em;
 }
 </style><link rel="stylesheet" 
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/all.min.css";
 /><link rel="stylesheet" 
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/v4-shims.min.css";
 /></head><body><div class="header"><div class="left"></div><div 
class="right"></div></div><div class="reveal"><div class="slides"><section 
id="example-presentation"><h2>Example Presentation</h2><div 
class="slide-content"><div class="paragraph"><p>Doc Writer &lt;<a hr [...]
-2024-12-04
+2024-12-11
 :revnumber: 1.0.0-SNAPSHOT
 :example-caption!:</p></div></div></section>
 <section id="introduction"><h2>Introduction</h2><div 
class="slide-content"><div class="ulist"><ul><li class="fragment"><p>This is a 
presentation for an example project.</p></li><li class="fragment"><p>This 
project does something.</p></li><li class="fragment"><p>We just haven&#8217;t 
decided what that is yet.</p></li></ul></div></div></section>

Reply via email to