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

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion-ballista.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 34a9810d0 Publish built docs triggered by 
08502f67bc46e30059ef7f7d82060b8a20d19bd4
34a9810d0 is described below

commit 34a9810d0affb3b80645dc0442fafc28ec88634e
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Sat Jan 24 17:33:40 2026 +0000

    Publish built docs triggered by 08502f67bc46e30059ef7f7d82060b8a20d19bd4
---
 _sources/user-guide/cli.md.txt                       | 2 +-
 _sources/user-guide/deployment/docker-compose.md.txt | 4 ++--
 _sources/user-guide/deployment/docker.md.txt         | 4 ++--
 _sources/user-guide/deployment/kubernetes.md.txt     | 2 +-
 searchindex.js                                       | 2 +-
 user-guide/cli.html                                  | 2 +-
 user-guide/deployment/docker-compose.html            | 4 ++--
 user-guide/deployment/docker.html                    | 4 ++--
 user-guide/deployment/kubernetes.html                | 2 +-
 9 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/_sources/user-guide/cli.md.txt b/_sources/user-guide/cli.md.txt
index 597bc1953..0661199cd 100644
--- a/_sources/user-guide/cli.md.txt
+++ b/_sources/user-guide/cli.md.txt
@@ -71,7 +71,7 @@ It is also possible to run the CLI in standalone mode, where 
it will create a sc
 ```bash
 $ ballista-cli
 
-Ballista CLI v51.0.0
+Ballista CLI v52.0.0
 
 > CREATE EXTERNAL TABLE foo (a INT, b INT) STORED AS CSV LOCATION 'data.csv';
 0 rows in set. Query took 0.001 seconds.
diff --git a/_sources/user-guide/deployment/docker-compose.md.txt 
b/_sources/user-guide/deployment/docker-compose.md.txt
index 96f69d692..ff3c53361 100644
--- a/_sources/user-guide/deployment/docker-compose.md.txt
+++ b/_sources/user-guide/deployment/docker-compose.md.txt
@@ -42,8 +42,8 @@ Creating network "ballista-benchmarks_default" with the 
default driver
 Creating ballista-benchmarks_ballista-scheduler_1 ... done
 Creating ballista-benchmarks_ballista-executor_1  ... done
 Attaching to ballista-benchmarks_ballista-scheduler_1, 
ballista-benchmarks_ballista-executor_1
-ballista-scheduler_1  | INFO ballista_scheduler: Ballista v51.0.0 Scheduler 
listening on 0.0.0.0:50050
-ballista-executor_1   | INFO ballista_executor: Ballista v51.0.0 Rust Executor 
listening on 0.0.0.0:50051
+ballista-scheduler_1  | INFO ballista_scheduler: Ballista v52.0.0 Scheduler 
listening on 0.0.0.0:50050
+ballista-executor_1   | INFO ballista_executor: Ballista v52.0.0 Rust Executor 
listening on 0.0.0.0:50051
 ```
 
 The scheduler listens on port 50050 and this is the port that clients will 
need to connect to.
diff --git a/_sources/user-guide/deployment/docker.md.txt 
b/_sources/user-guide/deployment/docker.md.txt
index cf5488a67..ad3571c50 100644
--- a/_sources/user-guide/deployment/docker.md.txt
+++ b/_sources/user-guide/deployment/docker.md.txt
@@ -67,7 +67,7 @@ Run `docker logs CONTAINER_ID` to check the output from the 
process:
 
 ```
 $ docker logs a756055576f3
-INFO ballista_scheduler::scheduler_process: Ballista v51.0.0 Scheduler 
listening on 0.0.0.0:50050
+INFO ballista_scheduler::scheduler_process: Ballista v52.0.0 Scheduler 
listening on 0.0.0.0:50050
 INFO ballista_scheduler::scheduler_process: Starting Scheduler grpc server 
with task scheduling policy of PullStaged
 INFO ballista_scheduler::scheduler_server::query_stage_scheduler: Starting 
QueryStageScheduler
 INFO ballista_core::event_loop: Starting the event loop query_stage
@@ -99,7 +99,7 @@ $ docker logs fb8b530cee6d
 INFO ballista_executor::executor_process: Running with config:
 INFO ballista_executor::executor_process: work_dir: /tmp/.tmpAkP3pZ
 INFO ballista_executor::executor_process: concurrent_tasks: 48
-INFO ballista_executor::executor_process: Ballista v51.0.0 Rust Executor 
Flight Server listening on 0.0.0.0:50051
+INFO ballista_executor::executor_process: Ballista v52.0.0 Rust Executor 
Flight Server listening on 0.0.0.0:50051
 INFO ballista_executor::execution_loop: Starting poll work loop with scheduler
 ```
 
diff --git a/_sources/user-guide/deployment/kubernetes.md.txt 
b/_sources/user-guide/deployment/kubernetes.md.txt
index 3e25d1f9a..a979a6c8c 100644
--- a/_sources/user-guide/deployment/kubernetes.md.txt
+++ b/_sources/user-guide/deployment/kubernetes.md.txt
@@ -212,7 +212,7 @@ You can view the scheduler logs with `kubectl logs 
ballista-scheduler-<pod-id>`:
 
 ```
 $ kubectl logs ballista-scheduler-<pod-id>
-INFO ballista_scheduler::scheduler_process: Ballista v51.0.0 Scheduler 
listening on 0.0.0.0:50050
+INFO ballista_scheduler::scheduler_process: Ballista v52.0.0 Scheduler 
listening on 0.0.0.0:50050
 INFO ballista_scheduler::scheduler_server::grpc: Received register_executor 
request for ExecutorMetadata { id: "b5e81711-1c5c-46ec-8522-d8b359793188", 
host: "10.1.23.149", port: 50051 }
 INFO ballista_scheduler::scheduler_server::grpc: Received register_executor 
request for ExecutorMetadata { id: "816e4502-a876-4ed8-b33f-86d243dcf63f", 
host: "10.1.23.150", port: 50051 }
 ```
diff --git a/searchindex.js b/searchindex.js
index cfa910a16..0e130a3d2 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles": {"Apache DataFusion Ballista": [[4, null]], 
"Arrow-native": [[1, "arrow-native"]], "Autoscaling Executors": [[11, 
"autoscaling-executors"]], "Ballista Architecture": [[1, null]], "Ballista Code 
Organization": [[2, null]], "Ballista Command-line Interface": [[5, null]], 
"Ballista Configuration Settings": [[6, "ballista-configuration-settings"]], 
"Ballista Development": [[3, null]], "Ballista Python Bindings": [[18, null]], 
"Ballista Quickstart": [[12, null]], [...]
\ No newline at end of file
+Search.setIndex({"alltitles": {"Apache DataFusion Ballista": [[4, null]], 
"Arrow-native": [[1, "arrow-native"]], "Autoscaling Executors": [[11, 
"autoscaling-executors"]], "Ballista Architecture": [[1, null]], "Ballista Code 
Organization": [[2, null]], "Ballista Command-line Interface": [[5, null]], 
"Ballista Configuration Settings": [[6, "ballista-configuration-settings"]], 
"Ballista Development": [[3, null]], "Ballista Python Bindings": [[18, null]], 
"Ballista Quickstart": [[12, null]], [...]
\ No newline at end of file
diff --git a/user-guide/cli.html b/user-guide/cli.html
index ec4d34bd0..3eee5c77c 100644
--- a/user-guide/cli.html
+++ b/user-guide/cli.html
@@ -378,7 +378,7 @@ process.</p>
 <p>It is also possible to run the CLI in standalone mode, where it will create 
a scheduler and executor in-process.</p>
 <div class="highlight-bash notranslate"><div 
class="highlight"><pre><span></span>$<span class="w"> </span>ballista-cli
 
-Ballista<span class="w"> </span>CLI<span class="w"> </span>v51.0.0
+Ballista<span class="w"> </span>CLI<span class="w"> </span>v52.0.0
 
 &gt;<span class="w"> </span>CREATE<span class="w"> </span>EXTERNAL<span 
class="w"> </span>TABLE<span class="w"> </span>foo<span class="w"> </span><span 
class="o">(</span>a<span class="w"> </span>INT,<span class="w"> </span>b<span 
class="w"> </span>INT<span class="o">)</span><span class="w"> 
</span>STORED<span class="w"> </span>AS<span class="w"> </span>CSV<span 
class="w"> </span>LOCATION<span class="w"> </span><span 
class="s1">&#39;data.csv&#39;</span><span class="p">;</span>
 <span class="m">0</span><span class="w"> </span>rows<span class="w"> 
</span><span class="k">in</span><span class="w"> </span>set.<span class="w"> 
</span>Query<span class="w"> </span>took<span class="w"> </span><span 
class="m">0</span>.001<span class="w"> </span>seconds.
diff --git a/user-guide/deployment/docker-compose.html 
b/user-guide/deployment/docker-compose.html
index 7ae44a87d..baede43b3 100644
--- a/user-guide/deployment/docker-compose.html
+++ b/user-guide/deployment/docker-compose.html
@@ -341,8 +341,8 @@ Creating<span class="w"> </span>network<span class="w"> 
</span><span class="s2">
 Creating<span class="w"> </span>ballista-benchmarks_ballista-scheduler_1<span 
class="w"> </span>...<span class="w"> </span><span class="k">done</span>
 Creating<span class="w"> </span>ballista-benchmarks_ballista-executor_1<span 
class="w">  </span>...<span class="w"> </span><span class="k">done</span>
 Attaching<span class="w"> </span>to<span class="w"> 
</span>ballista-benchmarks_ballista-scheduler_1,<span class="w"> 
</span>ballista-benchmarks_ballista-executor_1
-ballista-scheduler_1<span class="w">  </span><span class="p">|</span><span 
class="w"> </span>INFO<span class="w"> </span>ballista_scheduler:<span 
class="w"> </span>Ballista<span class="w"> </span>v51.0.0<span class="w"> 
</span>Scheduler<span class="w"> </span>listening<span class="w"> 
</span>on<span class="w"> </span><span class="m">0</span>.0.0.0:50050
-ballista-executor_1<span class="w">   </span><span class="p">|</span><span 
class="w"> </span>INFO<span class="w"> </span>ballista_executor:<span 
class="w"> </span>Ballista<span class="w"> </span>v51.0.0<span class="w"> 
</span>Rust<span class="w"> </span>Executor<span class="w"> 
</span>listening<span class="w"> </span>on<span class="w"> </span><span 
class="m">0</span>.0.0.0:50051
+ballista-scheduler_1<span class="w">  </span><span class="p">|</span><span 
class="w"> </span>INFO<span class="w"> </span>ballista_scheduler:<span 
class="w"> </span>Ballista<span class="w"> </span>v52.0.0<span class="w"> 
</span>Scheduler<span class="w"> </span>listening<span class="w"> 
</span>on<span class="w"> </span><span class="m">0</span>.0.0.0:50050
+ballista-executor_1<span class="w">   </span><span class="p">|</span><span 
class="w"> </span>INFO<span class="w"> </span>ballista_executor:<span 
class="w"> </span>Ballista<span class="w"> </span>v52.0.0<span class="w"> 
</span>Rust<span class="w"> </span>Executor<span class="w"> 
</span>listening<span class="w"> </span>on<span class="w"> </span><span 
class="m">0</span>.0.0.0:50051
 </pre></div>
 </div>
 <p>The scheduler listens on port 50050 and this is the port that clients will 
need to connect to.</p>
diff --git a/user-guide/deployment/docker.html 
b/user-guide/deployment/docker.html
index b221735f2..e2fa190fc 100644
--- a/user-guide/deployment/docker.html
+++ b/user-guide/deployment/docker.html
@@ -374,7 +374,7 @@ a756055576f3   apache/datafusion-ballista-scheduler:latest  
 &quot;/root/schedul
 </div>
 <p>Run <code class="docutils literal notranslate"><span 
class="pre">docker</span> <span class="pre">logs</span> <span 
class="pre">CONTAINER_ID</span></code> to check the output from the process:</p>
 <div class="highlight-default notranslate"><div 
class="highlight"><pre><span></span>$ docker logs a756055576f3
-INFO ballista_scheduler::scheduler_process: Ballista v51.0.0 Scheduler 
listening on 0.0.0.0:50050
+INFO ballista_scheduler::scheduler_process: Ballista v52.0.0 Scheduler 
listening on 0.0.0.0:50050
 INFO ballista_scheduler::scheduler_process: Starting Scheduler grpc server 
with task scheduling policy of PullStaged
 INFO ballista_scheduler::scheduler_server::query_stage_scheduler: Starting 
QueryStageScheduler
 INFO ballista_core::event_loop: Starting the event loop query_stage
@@ -401,7 +401,7 @@ a756055576f3   apache/datafusion-ballista-scheduler:latest  
 &quot;/root/schedul
 INFO ballista_executor::executor_process: Running with config:
 INFO ballista_executor::executor_process: work_dir: /tmp/.tmpAkP3pZ
 INFO ballista_executor::executor_process: concurrent_tasks: 48
-INFO ballista_executor::executor_process: Ballista v51.0.0 Rust Executor 
Flight Server listening on 0.0.0.0:50051
+INFO ballista_executor::executor_process: Ballista v52.0.0 Rust Executor 
Flight Server listening on 0.0.0.0:50051
 INFO ballista_executor::execution_loop: Starting poll work loop with scheduler
 </pre></div>
 </div>
diff --git a/user-guide/deployment/kubernetes.html 
b/user-guide/deployment/kubernetes.html
index 833ae2d7d..4550f0aff 100644
--- a/user-guide/deployment/kubernetes.html
+++ b/user-guide/deployment/kubernetes.html
@@ -524,7 +524,7 @@ ballista-scheduler-879f874c5-rnbd6<span class="w">   
</span><span class="m">0</s
 </div>
 <p>You can view the scheduler logs with <code class="docutils literal 
notranslate"><span class="pre">kubectl</span> <span class="pre">logs</span> 
<span class="pre">ballista-scheduler-&lt;pod-id&gt;</span></code>:</p>
 <div class="highlight-default notranslate"><div 
class="highlight"><pre><span></span>$ kubectl logs 
ballista-scheduler-&lt;pod-id&gt;
-INFO ballista_scheduler::scheduler_process: Ballista v51.0.0 Scheduler 
listening on 0.0.0.0:50050
+INFO ballista_scheduler::scheduler_process: Ballista v52.0.0 Scheduler 
listening on 0.0.0.0:50050
 INFO ballista_scheduler::scheduler_server::grpc: Received register_executor 
request for ExecutorMetadata { id: 
&quot;b5e81711-1c5c-46ec-8522-d8b359793188&quot;, host: 
&quot;10.1.23.149&quot;, port: 50051 }
 INFO ballista_scheduler::scheduler_server::grpc: Received register_executor 
request for ExecutorMetadata { id: 
&quot;816e4502-a876-4ed8-b33f-86d243dcf63f&quot;, host: 
&quot;10.1.23.150&quot;, port: 50051 }
 </pre></div>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to