You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@gluten.apache.org by gi...@apache.org on 2024/08/07 15:35:51 UTC

(incubator-gluten-site) branch asf-site updated: Automatic Site Publish by Buildbot

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-gluten-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new a614cf3  Automatic Site Publish by Buildbot
a614cf3 is described below

commit a614cf39dffa88ff15db2dd495f112ecf97f43c5
Author: buildbot <us...@infra.apache.org>
AuthorDate: Wed Aug 7 15:35:47 2024 +0000

    Automatic Site Publish by Buildbot
---
 output/404.html                                    |    2 +-
 output/about/index.html                            |    2 +-
 output/archives/index.html                         |    1 +
 .../v1.1.1/developers/UsingGperftoolsInCH.html     |    6 +
 .../v1.1.1/developers/UsingGperftoolsInCH.md       |   26 +
 .../v1.1.1/developers/UsingJemallocWithCH.html     |   12 +
 .../v1.1.1/developers/UsingJemallocWithCH.md       |   40 +
 .../v1.1.1/developers/cpp_code_style/index.html    |    1 +
 .../v1.1.1/developers/docker_centos7/index.html    |   38 +
 .../v1.1.1/developers/docker_centos8.html}         |   36 +-
 .../v1.1.1/developers/docker_ubuntu/index.html     |   44 +
 output/archives/v1.1.1/developers/howto/index.html |   22 +
 .../v1.1.1/developers/howtorelease/index.html      |  118 ++
 output/archives/v1.1.1/developers/index.html       |    1 +
 .../v1.1.1/developers/microbenchmark/index.html}   |    2 +-
 .../v1.1.1/developers/newto/index.html}            |    2 +-
 .../v1.1.1/developers/substrait/index.html         |    1 +
 .../velox_function_development/index.html          |   11 +
 .../docs/clickhouse/getting-started/index.html}    |    2 +-
 output/archives/v1.1.1/docs/clickhouse/index.html  |    1 +
 output/archives/v1.1.1/docs/index.html             |    1 +
 .../v1.1.1/docs/velox/build_parameters/index.html  |    1 +
 output/archives/v1.1.1/docs/velox/gcs/index.html   |    4 +
 .../v1.1.1/docs/velox/getting-started/index.html}  |    4 +-
 output/archives/v1.1.1/docs/velox/index.html       |    1 +
 output/archives/v1.1.1/docs/velox/s3/index.html    |   18 +
 output/archives/v1.1.1/images/apache-incubator.svg |    1 +
 output/archives/v1.1.1/images/gluten-logo-blue.png |  Bin 0 -> 14469 bytes
 output/archives/v1.1.1/index.html                  |    1 +
 output/asf/index.html                              |    2 +-
 output/assets/js/search-data.json                  | 1268 +++++++++++++++++---
 output/clickhouse/index.html                       |    2 +-
 output/contact-us.html                             |    2 +-
 output/contributing.html                           |    2 +-
 output/developers/CppCodingStyle.html              |    2 +-
 output/developers/HowTo.html                       |    2 +-
 output/developers/HowToRelease.html                |    2 +-
 output/developers/MicroBenchmarks.html             |    2 +-
 output/developers/NewToGluten.html                 |    2 +-
 output/developers/SubstraitModifications.html      |    2 +-
 output/developers/UsingGperftoolsInCH.html         |    2 +-
 output/developers/UsingJemallocWithCH.html         |    2 +-
 output/developers/docker_centos7.html              |    2 +-
 output/developers/docker_centos8.html              |    2 +-
 output/developers/docker_ubuntu22.04.html          |    2 +-
 output/developers/index.html                       |    2 +-
 .../velox-function-development-guide.html          |    2 +-
 output/docs/clickhouse/getting-started.html        |    2 +-
 output/docs/index.html                             |    2 +-
 output/docs/velox/build_parameters.html            |    2 +-
 output/docs/velox/gcs.html                         |    2 +-
 output/docs/velox/getting-started.html             |    2 +-
 output/docs/velox/index.html                       |    2 +-
 output/docs/velox/s3.html                          |    2 +-
 output/feed.xml                                    |    2 +-
 output/index.html                                  |    2 +-
 .../update/2024/02/08/welcome-to-jekyll.html       |    2 +-
 output/release.html                                |    2 +-
 58 files changed, 1536 insertions(+), 187 deletions(-)

diff --git a/output/404.html b/output/404.html
index 23b705a..128cf19 100644
--- a/output/404.html
+++ b/output/404.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
diff --git a/output/about/index.html b/output/about/index.html
index 36568b4..e6c814e 100644
--- a/output/about/index.html
+++ b/output/about/index.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(8)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(9)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/archives/index.html b/output/archives/index.html
new file mode 100644
index 0000000..677084e
--- /dev/null
+++ b/output/archives/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(4)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/archives/v1.1.1/developers/UsingGperftoolsInCH.html b/output/archives/v1.1.1/developers/UsingGperftoolsInCH.html
new file mode 100644
index 0000000..191f21f
--- /dev/null
+++ b/output/archives/v1.1.1/developers/UsingGperftoolsInCH.html
@@ -0,0 +1,6 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+export LD_PRELOAD=$tcmalloc_path,libch.so # load the library in the driver
+--files $tcmalloc_path # upload the library to the cluster
+--conf spark.executorEnv.LD_PRELOAD=./libtcmalloc_and_profiler.so,libch.so # load the library in the executor
+--conf spark.executorEnv.HEAPPROFILE=/tmp/gluten_heap_perf # set the heap profile path, you can change to CPUPROFILE for CPU profiling
+</code></pre></div></div> <p>For thrift server on local machine, note using <code class="language-plaintext highlighter-rouge">export LD_PRELOAD="$tcmalloc_path libch.so" # load the library in the driver</code> to preload dynamic libraries.</p> <h2 id="analyze-the-result"> <a href="#analyze-the-result" class="anchor-heading" aria-labelledby="analyze-the-result"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Analyze the result </h2> <p>We can get  [...]
diff --git a/output/archives/v1.1.1/developers/UsingGperftoolsInCH.md b/output/archives/v1.1.1/developers/UsingGperftoolsInCH.md
new file mode 100644
index 0000000..f0d5c72
--- /dev/null
+++ b/output/archives/v1.1.1/developers/UsingGperftoolsInCH.md
@@ -0,0 +1,26 @@
+We need using gpertools to find the memory or CPU issue. That's what this document is about.
+
+## Install gperftools
+Install gperftools as described in https://github.com/gperftools/gperftools.
+We get the library and the command line tools.
+
+## Compiler libch.so
+Disable jemalloc `-DENABLE_JEMALLOC=OFF` in cpp-ch/CMakeLists.txt, and recompile libch.so.
+
+## Run Gluten with gperftools
+For Spark on Yarn, we can change the submit script to run Gluten with gperftools.
+Add the following to the submit script:
+```
+export tcmalloc_path=/data2/zzb/gperftools-2.10/.libs/libtcmalloc_and_profiler.so # the path to the tcmalloc library
+export LD_PRELOAD=$tcmalloc_path,libch.so # load the library in the driver
+--files $tcmalloc_path # upload the library to the cluster
+--conf spark.executorEnv.LD_PRELOAD=./libtcmalloc_and_profiler.so,libch.so # load the library in the executor
+--conf spark.executorEnv.HEAPPROFILE=/tmp/gluten_heap_perf # set the heap profile path, you can change to CPUPROFILE for CPU profiling
+```
+
+For thrift server on local machine, note using `export LD_PRELOAD="$tcmalloc_path libch.so" # load the library in the driver` to preload dynamic libraries.
+
+## Analyze the result
+We can get the result in the path we set in the previous step. For example, we can get the result in `/tmp/gluten_heap_perf`. We can use the following website to analyze the result:
+https://gperftools.github.io/gperftools/heapprofile.html
+https://gperftools.github.io/gperftools/cpuprofile.html
diff --git a/output/archives/v1.1.1/developers/UsingJemallocWithCH.html b/output/archives/v1.1.1/developers/UsingJemallocWithCH.html
new file mode 100644
index 0000000..b0a1c54
--- /dev/null
+++ b/output/archives/v1.1.1/developers/UsingJemallocWithCH.html
@@ -0,0 +1,12 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+ # At the time ClickHouse uses LLVM libunwind which follows libgcc's way of backtracking.
+ #
+ # ClickHouse has to provide `unw_backtrace` method by the means of [commit 8e2b31e](https://github.com/ClickHouse/libunwind/commit/8e2b31e766dd502f6df74909e04a7dbdf5182eb1).
+-target_compile_definitions (_jemalloc PRIVATE -DJEMALLOC_PROF_LIBGCC=1)
++#target_compile_definitions (_jemalloc PRIVATE -DJEMALLOC_PROF_LIBGCC=1)
++target_compile_definitions (_jemalloc PRIVATE -DJEMALLOC_PROF_LIBUNWIND=1)
+ target_link_libraries (_jemalloc PRIVATE unwind)
+</code></pre></div></div> <p>For more infomation, check https://github.com/jemalloc/jemalloc/issues/2282.</p> <h2 id="get-jeprof"> <a href="#get-jeprof" class="anchor-heading" aria-labelledby="get-jeprof"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Get jeprof </h2> <p>Change to the directory where you want to install jemalloc, and run the following commands:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre clas [...]
+</code></pre></div></div> <p>Then we get jeprof in the directory <code class="language-plaintext highlighter-rouge">$Clickhouse_SOURCE_PATH/contrib/jemalloc/bin/jeprof</code>.</p> <h2 id="compiler-libchso"> <a href="#compiler-libchso" class="anchor-heading" aria-labelledby="compiler-libchso"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Compiler libch.so </h2> <p>Ensure to enable jemalloc <code class="language-plaintext highlighter-rouge">-DENAB [...]
+</code></pre></div></div> <p>You can find more options in https://github.com/jemalloc/jemalloc/wiki/Use-Case%3A-Heap-Profiling.</p> <h2 id="analyze-the-result"> <a href="#analyze-the-result" class="anchor-heading" aria-labelledby="analyze-the-result"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Analyze the result </h2> <p>After you get the heap file, you can use the following command to analyze the result: Check memory diff, so you can find whi [...]
+</code></pre></div></div> <p>You can find more usage about jeprof with <code class="language-plaintext highlighter-rouge">jeprof --help</code>.</p> </main> <hr> <footer> <p><a href="#top" id="back-to-top">Back to top</a></p> <a href="https://incubator.apache.org/">Apache Incubator</a> <p class="text-small text-grey-dk-100 mb-0">Copyright © 2024 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache Gluten, Gluten, Apache, the Apache feather logo, and the A [...]
diff --git a/output/archives/v1.1.1/developers/UsingJemallocWithCH.md b/output/archives/v1.1.1/developers/UsingJemallocWithCH.md
new file mode 100644
index 0000000..626f752
--- /dev/null
+++ b/output/archives/v1.1.1/developers/UsingJemallocWithCH.md
@@ -0,0 +1,40 @@
+We need using jemalloc to find the memory issue. That's what this document is about.
+
+## Change code of jemalloc
+Use libunwind instead of libgcc to get the backtrace which may cause process hangs.
+```
+@@ -177,7 +177,8 @@ target_compile_definitions(_jemalloc PRIVATE -DJEMALLOC_PROF=1)
+ # At the time ClickHouse uses LLVM libunwind which follows libgcc's way of backtracking.
+ #
+ # ClickHouse has to provide `unw_backtrace` method by the means of [commit 8e2b31e](https://github.com/ClickHouse/libunwind/commit/8e2b31e766dd502f6df74909e04a7dbdf5182eb1).
+-target_compile_definitions (_jemalloc PRIVATE -DJEMALLOC_PROF_LIBGCC=1)
++#target_compile_definitions (_jemalloc PRIVATE -DJEMALLOC_PROF_LIBGCC=1)
++target_compile_definitions (_jemalloc PRIVATE -DJEMALLOC_PROF_LIBUNWIND=1)
+ target_link_libraries (_jemalloc PRIVATE unwind)
+ ```
+For more infomation, check https://github.com/jemalloc/jemalloc/issues/2282.
+
+## Get jeprof
+Change to the directory where you want to install jemalloc, and run the following commands:
+```
+cd $Clickhouse_SOURCE_PATH/contrib/jemalloc && ./autogen.sh && ./configure.sh && make -j8
+```
+Then we get jeprof in the directory `$Clickhouse_SOURCE_PATH/contrib/jemalloc/bin/jeprof`.
+
+## Compiler libch.so
+Ensure to enable jemalloc `-DENABLE_JEMALLOC=ON` in cpp-ch/CMakeLists.txt, and compile libch.so.
+
+## Run Gluten with jemalloc heap tools
+For Yarn or thrift server, you need add the following to the submit script:
+```
+export MALLOC_CONF="prof:true,lg_prof_interval:30" # enable jemalloc heap profiling
+```
+You can find more options in https://github.com/jemalloc/jemalloc/wiki/Use-Case%3A-Heap-Profiling.
+
+## Analyze the result
+After you get the heap file, you can use the following command to analyze the result:
+Check memory diff, so you can find which part of the code consume the memory.
+```
+jeprof --svg /usr/lib/jvm/java-8-openjdk-amd64/bin/java --base=jeprof.3717358.1.i1.heap jeprof.3717358.30.i30.heap > diff.svg
+```
+You can find more usage about jeprof with `jeprof --help`.
\ No newline at end of file
diff --git a/output/archives/v1.1.1/developers/cpp_code_style/index.html b/output/archives/v1.1.1/developers/cpp_code_style/index.html
new file mode 100644
index 0000000..0f5a077
--- /dev/null
+++ b/output/archives/v1.1.1/developers/cpp_code_style/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
diff --git a/output/archives/v1.1.1/developers/docker_centos7/index.html b/output/archives/v1.1.1/developers/docker_centos7/index.html
new file mode 100644
index 0000000..68c7fbc
--- /dev/null
+++ b/output/archives/v1.1.1/developers/docker_centos7/index.html
@@ -0,0 +1,38 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+docker run -itd --name gluten centos:7 /bin/bash
+docker attach gluten
+</code></pre></div></div> <p>Run in docker:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>yum -y install epel-release centos-release-scl
+yum -y install \
+    git \
+    dnf \
+    cmake3 \
+    devtoolset-9 \
+    java-1.8.0-openjdk \
+    java-1.8.0-openjdk-devel \
+    ninja-build \
+    wget \
+    sudo
+
+# gluten need maven version &gt;=3.6.3
+wget https://downloads.apache.org/maven/maven-3/3.8.8/binaries/apache-maven-3.8.8-bin.tar.gz
+tar -xvf apache-maven-3.8.8-bin.tar.gz
+mv apache-maven-3.8.8 /usr/lib/maven
+export MAVEN_HOME=/usr/lib/maven
+export PATH=${PATH}:${MAVEN_HOME}/bin
+
+# cmake 3.x is required
+ln -s /usr/bin/cmake3 /usr/local/bin/cmake
+
+# enable gcc 9
+. /opt/rh/devtoolset-9/enable || exit 1
+
+export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk
+export PATH=$JAVA_HOME/bin:$PATH
+
+git clone https://github.com/oap-project/gluten.git
+cd gluten
+
+# To access HDFS or S3, you need to add the parameters `--enable_hdfs=ON` and `--enable_s3=ON`
+# If you have the same error with issue-3283, you need to add the parameter `--compile_arrow_java=ON`
+./dev/buildbundle-veloxbe.sh
+</code></pre></div></div> </main> <hr> <footer> <p><a href="#top" id="back-to-top">Back to top</a></p> <a href="https://incubator.apache.org/">Apache Incubator</a> <p class="text-small text-grey-dk-100 mb-0">Copyright © 2024 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache Gluten, Gluten, Apache, the Apache feather logo, and the Apache Gluten project logo are either registered trademarks or trademarks of the Apache Software Foundation in the United S [...]
diff --git a/output/developers/index.html b/output/archives/v1.1.1/developers/docker_centos8.html
similarity index 60%
copy from output/developers/index.html
copy to output/archives/v1.1.1/developers/docker_centos8.html
index f8adb51..a5c1ed8 100644
--- a/output/developers/index.html
+++ b/output/archives/v1.1.1/developers/docker_centos8.html
@@ -1 +1,35 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(3)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+docker run -itd --name gluten centos:8 /bin/bash
+docker attach gluten
+</code></pre></div></div> <p>Run in docker:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>#update mirror
+sed -i -e "s|mirrorlist=|#mirrorlist=|g" /etc/yum.repos.d/CentOS-*
+sed -i -e "s|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g" /etc/yum.repos.d/CentOS-*
+
+dnf install -y epel-release sudo
+yum install -y dnf-plugins-core
+yum config-manager --set-enabled powertools
+dnf --enablerepo=powertools install -y ninja-build
+dnf --enablerepo=powertools install -y libdwarf-devel
+dnf install -y --setopt=install_weak_deps=False ccache gcc-toolset-9 git wget which libevent-devel \
+  openssl-devel re2-devel libzstd-devel lz4-devel double-conversion-devel \
+  curl-devel cmake libicu-devel
+
+source /opt/rh/gcc-toolset-9/enable || exit 1
+
+yum install -y java-1.8.0-openjdk-devel patch
+export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk
+export PATH=$JAVA_HOME/bin:$PATH
+
+#gluten need maven version &gt;=3.6.3
+wget https://downloads.apache.org/maven/maven-3/3.8.8/binaries/apache-maven-3.8.8-bin.tar.gz
+tar -xvf apache-maven-3.8.8-bin.tar.gz
+mv apache-maven-3.8.8 /usr/lib/maven
+export MAVEN_HOME=/usr/lib/maven
+export PATH=${PATH}:${MAVEN_HOME}/bin
+
+git clone https://github.com/oap-project/gluten.git
+cd gluten
+
+# To access HDFS or S3, you need to add the parameters `--enable_hdfs=ON` and `--enable_s3=ON`
+./dev/buildbundle-veloxbe.sh
+</code></pre></div></div> </main> <hr> <footer> <p><a href="#top" id="back-to-top">Back to top</a></p> <a href="https://incubator.apache.org/">Apache Incubator</a> <p class="text-small text-grey-dk-100 mb-0">Copyright © 2024 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache Gluten, Gluten, Apache, the Apache feather logo, and the Apache Gluten project logo are either registered trademarks or trademarks of the Apache Software Foundation in the United S [...]
diff --git a/output/archives/v1.1.1/developers/docker_ubuntu/index.html b/output/archives/v1.1.1/developers/docker_ubuntu/index.html
new file mode 100644
index 0000000..5dda355
--- /dev/null
+++ b/output/archives/v1.1.1/developers/docker_ubuntu/index.html
@@ -0,0 +1,44 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+docker run -itd --network host --name gluten ubuntu:22.04 /bin/bash
+docker attach gluten
+</code></pre></div></div> <p>Run in docker:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>apt-get update
+
+#install gcc and libraries to build arrow
+apt install software-properties-common
+apt install maven build-essential cmake libssl-dev libre2-dev libcurl4-openssl-dev clang lldb lld libz-dev git ninja-build uuid-dev autoconf-archive curl zip unzip tar pkg-config bison libtool flex vim
+
+#velox script needs sudo to install dependency libraries
+apt install sudo
+
+# make sure jemalloc is uninstalled, jemalloc will be build in vcpkg, which conflicts with the default jemalloc in system
+apt purge libjemalloc-dev libjemalloc2 librust-jemalloc-sys-dev
+
+#make sure jdk8 is used. New version of jdk is not supported
+apt install -y openjdk-8-jdk
+apt install -y default-jdk
+export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
+export PATH=$JAVA_HOME/bin:$PATH
+
+#manually install tzdata to avoid the interactive timezone config
+ln -fs /usr/share/zoneinfo/America/New_York /etc/localtime
+DEBIAN_FRONTEND=noninteractive apt-get install -y tzdata
+dpkg --configure -a
+
+#setup proxy on necessary
+#export http_proxy=xxxx
+#export https_proxy=xxxx
+
+#clone gluten
+git clone https://github.com/oap-project/gluten.git
+cd gluten/
+
+#config maven proxy
+#mkdir ~/.m2/
+#vim ~/.m2/settings.xml
+
+# the script download velox &amp; arrow and compile all dependency library automatically
+# To access HDFS or S3, you need to add the parameters `--enable_hdfs=ON` and `--enable_s3=ON`
+# It's suggested to build using static link, enabled by `--enable_vcpkg=ON`
+# For developer, it's suggested to enable Debug info, by --build_type=RelWithDebInfo. Note RelWithDebInfo uses -o2, release uses -o3
+./dev/buildbundle-veloxbe.sh --enable_vcpkg=ON --build_type=RelWithDebInfo
+</code></pre></div></div> </main> <hr> <footer> <p><a href="#top" id="back-to-top">Back to top</a></p> <a href="https://incubator.apache.org/">Apache Incubator</a> <p class="text-small text-grey-dk-100 mb-0">Copyright © 2024 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache Gluten, Gluten, Apache, the Apache feather logo, and the Apache Gluten project logo are either registered trademarks or trademarks of the Apache Software Foundation in the United S [...]
diff --git a/output/archives/v1.1.1/developers/howto/index.html b/output/archives/v1.1.1/developers/howto/index.html
new file mode 100644
index 0000000..ecd1381
--- /dev/null
+++ b/output/archives/v1.1.1/developers/howto/index.html
@@ -0,0 +1,22 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+</code></pre></div> </div> <ul> <li>Compiling with <code class="language-plaintext highlighter-rouge">--build_type=Debug</code> is good for debugging.</li> <li>The executable file <code class="language-plaintext highlighter-rouge">generic_benchmark</code> will be generated under the directory of <code class="language-plaintext highlighter-rouge">gluten_home/cpp/build/velox/benchmarks/</code>.</li> </ul> </li> <li>build Gluten and generate the example files <div class="language-plaintext  [...]
+mvn clean package -Pspark-3.2 -Pbackends-velox -Prss
+mvn test -Pspark-3.2 -Pbackends-velox -Prss -pl backends-velox -am -DtagsToInclude="io.glutenproject.tags.GenerateExample" -Dtest=none -DfailIfNoTests=false -Darrow.version=11.0.0-gluten -Dexec.skip
+</code></pre></div> </div> <ul> <li>After the above operations, the examples files are generated under <code class="language-plaintext highlighter-rouge">gluten_home/backends-velox</code></li> <li>You can check it by the command <code class="language-plaintext highlighter-rouge">tree gluten_home/backends-velox/generated-native-benchmark/</code></li> <li>You may replace <code class="language-plaintext highlighter-rouge">-Pspark-3.2</code> with <code class="language-plaintext highlighter-r [...]
+gluten_home/backends-velox/generated-native-benchmark/
+├── example.json
+├── example_lineitem
+│   ├── part-00000-3ec19189-d20e-4240-85ae-88631d46b612-c000.snappy.parquet
+│   └── _SUCCESS
+└── example_orders
+ ├── part-00000-1e66fb98-4dd6-47a6-8679-8625dbc437ee-c000.snappy.parquet
+ └── _SUCCESS
+</code></pre></div> </div> </li> </ul> </li> <li>now, run benchmarks with GDB <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>cd gluten_home/cpp/build/velox/benchmarks/
+gdb generic_benchmark
+</code></pre></div> </div> <ul> <li>When GDB load <code class="language-plaintext highlighter-rouge">generic_benchmark</code> successfully, you can set <code class="language-plaintext highlighter-rouge">breakpoint</code> on the <code class="language-plaintext highlighter-rouge">main</code> function with command <code class="language-plaintext highlighter-rouge">b main</code>, and then run with command <code class="language-plaintext highlighter-rouge">r</code>, then the process <code cla [...]
+gdb gluten_home/cpp/build/releases/libgluten.so 'core-Executor task l-2000883-1671542526'
+
+</code></pre></div></div> <ul> <li>the <code class="language-plaintext highlighter-rouge">core-Executor task l-2000883-1671542526</code> represents the core file name.</li> </ul> <h1 id="how-to-run-tpc-h-on-velox-backend"> <a href="#how-to-run-tpc-h-on-velox-backend" class="anchor-heading" aria-labelledby="how-to-run-tpc-h-on-velox-backend"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> How to run TPC-H on Velox backend </h1> <p>Now, both Parquet [...]
+</code></pre></div> </div> </li> <li>set <code class="language-plaintext highlighter-rouge">var gluten_root</code> to correct directory. If <code class="language-plaintext highlighter-rouge">gluten_home</code> is the directory of <code class="language-plaintext highlighter-rouge">/home/gluten</code>, then modify it as below <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code> var gluten_root = "/home/gluten"
+</code></pre></div> </div> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>  - Modify `gluten_home/backends-velox/workload/tpch/run_tpch/tpch_parquet.sh`.
+</code></pre></div> </div> </li> <li>Set <code class="language-plaintext highlighter-rouge">GLUTEN_JAR</code> correctly. Please refer to the section of <a href="../get-started/Velox.md/#2-build-gluten-with-velox-backend">Build Gluten with Velox Backend</a></li> <li>Set <code class="language-plaintext highlighter-rouge">SPARK_HOME</code> correctly.</li> <li>Set the memory configurations appropriately. - Execute <code class="language-plaintext highlighter-rouge">tpch_parquet.sh</code> usin [...]
diff --git a/output/archives/v1.1.1/developers/howtorelease/index.html b/output/archives/v1.1.1/developers/howtorelease/index.html
new file mode 100644
index 0000000..838bef7
--- /dev/null
+++ b/output/archives/v1.1.1/developers/howtorelease/index.html
@@ -0,0 +1,118 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+$ gpg --full-generate-key
+
+# list the GPG keys
+$ gpg  --keyid-format SHORT --list-keys
+
+# upload the GPG key to the key server, xxx is the GPG key id
+# eg: pub rsa4096/4C21E346 2024-05-06 [SC], 4C21E346 is the GPG key id;
+$ gpg --keyserver keyserver.ubuntu.com --send-key xxx
+
+# append the GPG key to the KEYS file the svn repository
+# [IMPORTANT] Don't replace the KEYS file, just append the GPG key to the KEYS file. 
+$ svn co https://dist.apache.org/repos/dist/release/incubator/answer/
+$ (gpg --list-sigs xxx@apache.org &amp;&amp; gpg --export --armor xxx@apache.org) &gt;&gt; KEYS 
+$ svn ci -m "add gpg key" 
+
+# sign the release artifacts, xxxx is xxx@apache.org
+$ for i in *.tar.gz; do echo $i; gpg --local-user xxxx --armor --output $i.asc --detach-sig $i ; done
+</code></pre></div></div> <h4 id="how-to-generate-checksums-for-the-release-artifacts"> <a href="#how-to-generate-checksums-for-the-release-artifacts" class="anchor-heading" aria-labelledby="how-to-generate-checksums-for-the-release-artifacts"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> How to Generate checksums for the release artifacts. </h4> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><cod [...]
+$ for i in *.tar.gz; do echo $i; sha512sum  $i &gt; $i.sha512 ; done
+</code></pre></div></div> <h3 id="upload-the-release-artifacts-to-the-svn-repository"> <a href="#upload-the-release-artifacts-to-the-svn-repository" class="anchor-heading" aria-labelledby="upload-the-release-artifacts-to-the-svn-repository"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Upload the release artifacts to the SVN repository. </h3> <ol> <li> <p>Create a project directory in the SVN repository (1st time only). <code class="language-pla [...]
+$ cp /path/to/release/artifacts/* ./{release-version}/
+$ svn add ./{release-version}/*
+$ svn commit -m "add Apache Answer release artifacts for {release-version}"
+</code></pre></div> </div> </li> <li>After the upload, please visit the link <code class="language-plaintext highlighter-rouge">https://dist.apache.org/repos/dist/dev/incubator/gluten/{release-version}</code> to verify if the file upload is successful or not. The upload release artifacts should be include <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>* apache-gluten-#.#.#-incubating-src.tar.gz
+* apache-gluten-#.#.#-incubating-src.tar.gz.asc
+* apache-gluten-#.#.#-incubating-src.tar.gz.sha512
+</code></pre></div> </div> </li> </ol> <h3 id="verify-the-release-artifacts"> <a href="#verify-the-release-artifacts" class="anchor-heading" aria-labelledby="verify-the-release-artifacts"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Verify the release artifacts. </h3> <p>Please follow below steps to verify the release artifacts.</p> <ol> <li> <p>Check if the Download links are valid.</p> </li> <li> <p>Check if the checksums and GPG signatures a [...]
+$ curl https://dist.apache.org/repos/dist/release/incubator/gluten/KEYS &gt; KEYS
+
+# import KEYS and trust the key, please replace the email address with the one you want to trust.
+$ gpg --import KEYS
+$ gpg --edit-key xxx@apache.org
+gpg&gt; trust
+gpg&gt; 5
+gpg&gt; y
+gpg&gt; quit
+
+# enter the directory where the release artifacts are located
+$ cd /path/to/release/artifacts
+
+# verify the signature
+$ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
+
+# if you see 'Good signature' in the output, it means the signature is valid.
+</code></pre></div></div> <h4 id="how-to-verify-the-checksums"> <a href="#how-to-verify-the-checksums" class="anchor-heading" aria-labelledby="how-to-verify-the-checksums"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> How to Verify the checksums </h4> <p>Please follow below steps to verify the checksums</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># verify the checksums
+$ for i in *.tar.gz; do echo $i; sha512sum --check  $i.sha512; done
+</code></pre></div></div> <h3 id="initiate-a-release-vote"> <a href="#initiate-a-release-vote" class="anchor-heading" aria-labelledby="initiate-a-release-vote"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Initiate a release vote. </h3> <ol> <li> <p>Email a vote request to dev@gluten.apache.org, requiring at least 3 PPMC +1s.</p> </li> <li> <p>Allow 72 hours or until enough votes are collected.</p> </li> <li> <p>Share the vote outcome on the dev [...]
+
+Hello,
+
+    This is a call for vote to release Apache Gluten (Incubating) version {release-version}.
+
+    The vote thread:
+        https://lists.apache.org/thread/{id}
+
+    Vote Result:
+        https://lists.apache.org/thread/{id}
+
+    The release candidates:
+        https://dist.apache.org/repos/dist/dev/incubator/gluten/{release-version}/
+    
+    Release notes:
+        https://github.com/apache/incubator-gluten/releases/tag/{release-version}
+
+    Git tag for the release:
+        https://github.com/apache/incubator-gluten/releases/tag/{release-version}
+    
+    Git commit id for the release:
+        https://github.com/apache/incubator-gluten/commit/{id}
+
+    Keys to verify the Release Candidate:
+        https://downloads.apache.org/incubator/gluten/KEYS
+        
+    The vote will be open for at least 72 hours or until the necessary number of votes are reached.
+
+    Please vote accordingly:
+
+    [ ] +1 approve
+    [ ] +0 no opinion
+    [ ] -1 disapprove with the reason
+
+    Checklist for reference:
+
+    [ ] Download links are valid.
+    [ ] Checksums and PGP signatures are valid.
+    [ ] Source code distributions have correct names matching the current release.
+    [ ] LICENSE and NOTICE files are correct for each Apache Answer repo.
+    [ ] All files have license headers if necessary.
+    [ ] No unlicensed compiled archives bundled in source archive.
+
+    To compile from the source, please refer to:
+    
+    https://github.com/apache/incubator-gluten#building-from-source
+
+Thanks,
+&lt;YOUR NAME&gt;
+</code></pre></div></div> <h3 id="announce-the-results-and-the-release"> <a href="#announce-the-results-and-the-release" class="anchor-heading" aria-labelledby="announce-the-results-and-the-release"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Announce the results and the release. </h3> <p>Announce Email Template</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Hello everyone,
+
+The Apache Gluten (Incubating) {release-version} has been released!
+
+Apache Gluten is a Q&amp;A platform software for teams at any scale.
+Whether it's a community forum, help center, or knowledge management platform, you can always count on Apache Answer.
+
+Download Links: https://downloads.apache.org/incubator/gluten/
+
+Release Notes: https://github.com/apache/incubator-gluten/releases/tag/{release-version}
+
+Website: https://gluten.apache.org/
+
+Resources:
+- Issue: https://github.com/apache/incubator-gluten/issues
+- Mailing list: dev@gluten.apache.org
+
+Thanks,
+&lt;YOUR NAME&gt;
+
+</code></pre></div></div> </main> <hr> <footer> <p><a href="#top" id="back-to-top">Back to top</a></p> <a href="https://incubator.apache.org/">Apache Incubator</a> <p class="text-small text-grey-dk-100 mb-0">Copyright © 2024 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache Gluten, Gluten, Apache, the Apache feather logo, and the Apache Gluten project logo are either registered trademarks or trademarks of the Apache Software Foundation in the United S [...]
diff --git a/output/archives/v1.1.1/developers/index.html b/output/archives/v1.1.1/developers/index.html
new file mode 100644
index 0000000..dc8931f
--- /dev/null
+++ b/output/archives/v1.1.1/developers/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
diff --git a/output/developers/MicroBenchmarks.html b/output/archives/v1.1.1/developers/microbenchmark/index.html
similarity index 64%
copy from output/developers/MicroBenchmarks.html
copy to output/archives/v1.1.1/developers/microbenchmark/index.html
index c7fa75e..6100cec 100644
--- a/output/developers/MicroBenchmarks.html
+++ b/output/archives/v1.1.1/developers/microbenchmark/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(3)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
 ./dev/buildbundle-veloxbe.sh <span class="nt">--build_tests</span><span class="o">=</span>ON <span class="nt">--build_benchmarks</span><span class="o">=</span>ON
 
 <span class="c"># Run test to generate input data files. If you are using spark 3.3, replace -Pspark-3.2 with -Pspark-3.3</span>
diff --git a/output/developers/NewToGluten.html b/output/archives/v1.1.1/developers/newto/index.html
similarity index 71%
copy from output/developers/NewToGluten.html
copy to output/archives/v1.1.1/developers/newto/index.html
index a49b2aa..f695315 100644
--- a/output/developers/NewToGluten.html
+++ b/output/archives/v1.1.1/developers/newto/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
 update-alternatives <span class="nt">--config</span> java
 java <span class="nt">-version</span>
 </code></pre></div></div> <p><code class="language-plaintext highlighter-rouge">--config java</code> to config java executable path, <code class="language-plaintext highlighter-rouge">javac</code> and other commands can also use this command to config. For some other uses, we suggest to set <code class="language-plaintext highlighter-rouge">JAVA_HOME</code>.</p> <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">export </span [...]
diff --git a/output/archives/v1.1.1/developers/substrait/index.html b/output/archives/v1.1.1/developers/substrait/index.html
new file mode 100644
index 0000000..a34209e
--- /dev/null
+++ b/output/archives/v1.1.1/developers/substrait/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
diff --git a/output/archives/v1.1.1/developers/velox_function_development/index.html b/output/archives/v1.1.1/developers/velox_function_development/index.html
new file mode 100644
index 0000000..3becefa
--- /dev/null
+++ b/output/archives/v1.1.1/developers/velox_function_development/index.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+struct BitwiseAndFunction {
+  template &lt;typename TInput&gt;
+  // For void return type, it indicates null result will never be obtained for non-null input.
+  // For bool return type, it indicates null result can be obtained for non-null input (false for null).
+  FOLLY_ALWAYS_INLINE void call(TInput&amp; result, TInput a, TInput b) {
+    result = a &amp; b;
+  }
+};
+</code></pre></div></div> <p>It is templated, as well as the <code class="language-plaintext highlighter-rouge">call</code> function, to allow multiple types. In the above impl., the result will be null for null input. Please use <code class="language-plaintext highlighter-rouge">callNullable</code> if you need different behavior for null input, e.g., get a non-null result for null input. Also see <code class="language-plaintext highlighter-rouge">callNullFree</code> in velox document. I [...]
+</code></pre></div></div> <p>Functions for complex types have similar implementations. See <code class="language-plaintext highlighter-rouge">ArrayAverageFunction</code> in <a href="https://github.com/facebookincubator/velox/blob/main/velox/functions/prestosql/ArrayFunctions.h">velox/functions/prestosql/ArrayFunctions.h</a>.</p> <h3 id="reference"> <a href="#reference" class="anchor-heading" aria-labelledby="reference"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-lin [...]
diff --git a/output/docs/clickhouse/getting-started.html b/output/archives/v1.1.1/docs/clickhouse/getting-started/index.html
similarity index 75%
copy from output/docs/clickhouse/getting-started.html
copy to output/archives/v1.1.1/docs/clickhouse/getting-started/index.html
index 5057d06..5ca9d2c 100644
--- a/output/docs/clickhouse/getting-started.html
+++ b/output/archives/v1.1.1/docs/clickhouse/getting-started/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
 </code></pre></div></div> <h4 id="setup-clickhouse-backend-development-environment"> <a href="#setup-clickhouse-backend-development-environment" class="anchor-heading" aria-labelledby="setup-clickhouse-backend-development-environment"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Setup ClickHouse backend development environment </h4> <p>If you don’t care about development environment, you can skip this part.</p> <p>Otherwise, do:</p> <ol> <li>cl [...]
  git clone --recursive --shallow-submodules -b clickhouse_backend https://github.com/Kyligence/ClickHouse.git
 </code></pre></div> </div> </li> <li> <p>Configure cpp-ch ${GLUTEN_SOURCE}/cpp-ch can be treated as an add-on of Kyligence/Clickhouse</p> <p>First, initialize some configuration for this add-on:</p> <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="nb">export </span><span class="nv">GLUTEN_SOURCE</span><span class="o">=</span>/path/to/gluten
diff --git a/output/archives/v1.1.1/docs/clickhouse/index.html b/output/archives/v1.1.1/docs/clickhouse/index.html
new file mode 100644
index 0000000..67bdef0
--- /dev/null
+++ b/output/archives/v1.1.1/docs/clickhouse/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
diff --git a/output/archives/v1.1.1/docs/index.html b/output/archives/v1.1.1/docs/index.html
new file mode 100644
index 0000000..6ac10ab
--- /dev/null
+++ b/output/archives/v1.1.1/docs/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
diff --git a/output/archives/v1.1.1/docs/velox/build_parameters/index.html b/output/archives/v1.1.1/docs/velox/build_parameters/index.html
new file mode 100644
index 0000000..23a8600
--- /dev/null
+++ b/output/archives/v1.1.1/docs/velox/build_parameters/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
diff --git a/output/archives/v1.1.1/docs/velox/gcs/index.html b/output/archives/v1.1.1/docs/velox/gcs/index.html
new file mode 100644
index 0000000..130b73e
--- /dev/null
+++ b/output/archives/v1.1.1/docs/velox/gcs/index.html
@@ -0,0 +1,4 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+spark.hadoop.fs.gs.auth.service.account.json.keyfile // path to the json file with the credentials.
+</code></pre></div></div> <h2 id="configuring-gcs-endpoints"> <a href="#configuring-gcs-endpoints" class="anchor-heading" aria-labelledby="configuring-gcs-endpoints"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Configuring GCS endpoints </h2> <p>For cases when a GCS mock is used, an optional endpoint can be provided:</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>spark.hadoop.fs.gs.storage.roo [...]
+</code></pre></div></div> </main> <hr> <footer> <p><a href="#top" id="back-to-top">Back to top</a></p> <a href="https://incubator.apache.org/">Apache Incubator</a> <p class="text-small text-grey-dk-100 mb-0">Copyright © 2024 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache Gluten, Gluten, Apache, the Apache feather logo, and the Apache Gluten project logo are either registered trademarks or trademarks of the Apache Software Foundation in the United S [...]
diff --git a/output/docs/velox/getting-started.html b/output/archives/v1.1.1/docs/velox/getting-started/index.html
similarity index 82%
copy from output/docs/velox/getting-started.html
copy to output/archives/v1.1.1/docs/velox/getting-started/index.html
index 4454749..f50d44a 100644
--- a/output/docs/velox/getting-started.html
+++ b/output/archives/v1.1.1/docs/velox/getting-started/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
 <span class="nb">export </span><span class="nv">JAVA_HOME</span><span class="o">=</span>/usr/lib/jvm/java-8-openjdk-amd64
 <span class="nb">export </span><span class="nv">PATH</span><span class="o">=</span><span class="nv">$JAVA_HOME</span>/bin:<span class="nv">$PATH</span>
 </code></pre></div></div> <p><strong>For aarch64</strong></p> <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">## make sure jdk8 is used</span>
@@ -68,7 +68,7 @@ sudo chown &lt;sparkuser&gt;:&lt;sparkuser&gt; /var/lib/hadoop-hdfs/
 </code></pre></div></div> <ul> <li>Specify the environment variable <a href="https://github.com/apache/hawq/blob/e9d43144f7e947e071bba48871af9da354d177d0/depends/libhdfs3/src/client/FileSystem.cpp#L56">KRB5CCNAME</a> and upload the kerberos ticket cache file</li> </ul> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>--conf spark.executorEnv.KRB5CCNAME=krb5cc_0000  --files /tmp/krb5cc_0000
 </code></pre></div></div> <p>The ticket cache file can be found by <code class="language-plaintext highlighter-rouge">klist</code>.</p> <h2 id="aws-s3-support"> <a href="#aws-s3-support" class="anchor-heading" aria-labelledby="aws-s3-support"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> AWS S3 support </h2> <p>Velox supports S3 with the open source <a href="https://github.com/aws/aws-sdk-cpp">AWS C++ SDK</a> and Gluten uses Velox S3 connector t [...]
 ./dev/buildbundle-veloxbe.sh --enable_s3=ON
-</code></pre></div></div> <p>Currently there are several ways to asscess S3 in Spark. Please refer <a href="/docs/velox/s3">Velox S3</a> part for more detailed configurations</p> <h2 id="celeborn-support"> <a href="#celeborn-support" class="anchor-heading" aria-labelledby="celeborn-support"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Celeborn support </h2> <p>Gluten with velox backend supports <a href="https://github.com/apache/incubator-celeb [...]
+</code></pre></div></div> <p>Currently there are several ways to asscess S3 in Spark. Please refer <a href="/archives/v1.1.1/docs/velox/s3/">Velox S3</a> part for more detailed configurations</p> <h2 id="celeborn-support"> <a href="#celeborn-support" class="anchor-heading" aria-labelledby="celeborn-support"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Celeborn support </h2> <p>Gluten with velox backend supports <a href="https://github.com/apach [...]
 </code></pre></div></div> <p>Then add the Gluten and Spark Celeborn Client packages to your Spark application’s classpath(usually add them into <code class="language-plaintext highlighter-rouge">$SPARK_HOME/jars</code>).</p> <ul> <li>Celeborn: celeborn-client-spark-3-shaded_2.12-0.3.0-incubating.jar</li> <li>Gluten: gluten-velox-bundle-spark3.x_2.12-xx_xx_xx-SNAPSHOT.jar, gluten-thirdparty-lib-xx-xx.jar</li> </ul> <p>Currently to use Gluten following configurations are required in <code  [...]
 
 # celeborn master
diff --git a/output/archives/v1.1.1/docs/velox/index.html b/output/archives/v1.1.1/docs/velox/index.html
new file mode 100644
index 0000000..bb82351
--- /dev/null
+++ b/output/archives/v1.1.1/docs/velox/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
diff --git a/output/archives/v1.1.1/docs/velox/s3/index.html b/output/archives/v1.1.1/docs/velox/s3/index.html
new file mode 100644
index 0000000..743eb6e
--- /dev/null
+++ b/output/archives/v1.1.1/docs/velox/s3/index.html
@@ -0,0 +1,18 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+spark.hadoop.fs.s3a.aws.credentials.provider    org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider
+spark.hadoop.fs.s3a.access.key                  XXXXXXXXX
+spark.hadoop.fs.s3a.secret.key                  XXXXXXXXX
+spark.hadoop.fs.s3a.endpoint                    https://s3.us-west-1.amazonaws.com
+spark.hadoop.fs.s3a.connection.ssl.enabled      <span class="nb">true
+</span>spark.hadoop.fs.s3a.path.style.access           <span class="nb">false</span>
+</code></pre></div></div> <h2 id="configuring-s3-instance-credentials"> <a href="#configuring-s3-instance-credentials" class="anchor-heading" aria-labelledby="configuring-s3-instance-credentials"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Configuring S3 instance credentials </h2> <p>S3 also provides other methods for accessing, you can also use instance credentials by setting the following config</p> <div class="language-plaintext highlighter [...]
+</code></pre></div></div> <p>Note that in this case, “spark.hadoop.fs.s3a.endpoint” won’t take affect as Gluten will use the endpoint set during instance creation.</p> <h2 id="configuring-s3-iam-roles"> <a href="#configuring-s3-iam-roles" class="anchor-heading" aria-labelledby="configuring-s3-iam-roles"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Configuring S3 IAM roles </h2> <p>You can also use iam role credentials by setting the following c [...]
+spark.hadoop.fs.s3a.iam.role.session.name xxxx
+</code></pre></div></div> <p>Note that <code class="language-plaintext highlighter-rouge">spark.hadoop.fs.s3a.iam.role.session.name</code> is optional.</p> <h2 id="other-authentatication-methods-are-not-supported-yet"> <a href="#other-authentatication-methods-are-not-supported-yet" class="anchor-heading" aria-labelledby="other-authentatication-methods-are-not-supported-yet"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Other authentatication met [...]
+spark.gluten.sql.columnar.backend.velox.memCacheSize      // the total size of in-mem cache, default is 128MB.
+spark.gluten.sql.columnar.backend.velox.ssdCachePath      // the folder to store the cache files, default is "/tmp".
+spark.gluten.sql.columnar.backend.velox.ssdCacheSize      // the total size of the SSD cache, default is 128MB. Velox will do in-mem cache only if this value is 0.
+spark.gluten.sql.columnar.backend.velox.ssdCacheShards    // the shards of the SSD cache, default is 1.
+spark.gluten.sql.columnar.backend.velox.ssdCacheIOThreads // the IO threads for cache promoting, default is 1. Velox will try to do "read-ahead" if this value is bigger than 1 
+spark.gluten.sql.columnar.backend.velox.ssdODirect        // enable or disable O_DIRECT on cache write, default false.
+</code></pre></div></div> <p>It’s recommended to mount SSDs to the cache path to get the best performance of local caching. On the start up of Spark context, the cache files will be allocated under “spark.gluten.sql.columnar.backend.velox.cachePath”, with UUID based suffix, e.g. “/tmp/cache.13e8ab65-3af4-46ac-8d28-ff99b2a9ec9b0”. Gluten is not able to reuse older caches for now, and the old cache files are left there after Spark context shutdown.</p> </main> <hr> <footer> <p><a href="#to [...]
diff --git a/output/archives/v1.1.1/images/apache-incubator.svg b/output/archives/v1.1.1/images/apache-incubator.svg
new file mode 100644
index 0000000..dc152b4
--- /dev/null
+++ b/output/archives/v1.1.1/images/apache-incubator.svg
@@ -0,0 +1 @@
+{"payload":{"allShortcutsEnabled":false,"fileTree":{"static/img":{"items":[{"name":"benchmarks","path":"static/img/benchmarks","contentType":"directory"},{"name":"apache-incubator.svg","path":"static/img/apache-incubator.svg","contentType":"file"},{"name":"case1.png","path":"static/img/case1.png","contentType":"file"},{"name":"case2.png","path":"static/img/case2.png","contentType":"file"},{"name":"favicon.ico","path":"static/img/favicon.ico","contentType":"file"},{"name":"fury_banner.png [...]
\ No newline at end of file
diff --git a/output/archives/v1.1.1/images/gluten-logo-blue.png b/output/archives/v1.1.1/images/gluten-logo-blue.png
new file mode 100644
index 0000000..801fd9b
Binary files /dev/null and b/output/archives/v1.1.1/images/gluten-logo-blue.png differ
diff --git a/output/archives/v1.1.1/index.html b/output/archives/v1.1.1/index.html
new file mode 100644
index 0000000..6c48d20
--- /dev/null
+++ b/output/archives/v1.1.1/index.html
@@ -0,0 +1 @@
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/asf/index.html b/output/asf/index.html
index 3b1694f..0c97eab 100644
--- a/output/asf/index.html
+++ b/output/asf/index.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(7)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(7)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/assets/js/search-data.json b/output/assets/js/search-data.json
index 6f3e8e4..9af1ed9 100644
--- a/output/assets/js/search-data.json
+++ b/output/assets/js/search-data.json
@@ -1,1066 +1,2032 @@
 {"0": {
+    "doc": "v1.1.1/ClickHouse Backend",
+    "title": "Gluten Documents by version",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/clickhouse/#gluten-documents-by-version",
+    
+    "relUrl": "/archives/v1.1.1/docs/clickhouse/#gluten-documents-by-version"
+  },"1": {
+    "doc": "v1.1.1/ClickHouse Backend",
+    "title": "v1.1.1/ClickHouse Backend",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/clickhouse/",
+    
+    "relUrl": "/archives/v1.1.1/docs/clickhouse/"
+  },"2": {
     "doc": "ClickHouse Backend",
     "title": "Gluten Documents by version",
     "content": " ",
     "url": "/clickhouse/#gluten-documents-by-version",
     
     "relUrl": "/clickhouse/#gluten-documents-by-version"
-  },"1": {
+  },"3": {
     "doc": "ClickHouse Backend",
     "title": "ClickHouse Backend",
     "content": " ",
     "url": "/clickhouse/",
     
     "relUrl": "/clickhouse/"
-  },"2": {
+  },"4": {
     "doc": "CPP Code Style",
     "title": "Gluten CPP Core Guidelines",
     "content": "This is a set of CPP core guidelines for Gluten. The aim is to make the codebase simpler, more efficient, more maintainable by promoting consistency and according to best practices. ",
     "url": "/developers/CppCodingStyle.html#gluten-cpp-core-guidelines",
     
     "relUrl": "/developers/CppCodingStyle.html#gluten-cpp-core-guidelines"
-  },"3": {
+  },"5": {
     "doc": "CPP Code Style",
     "title": "Philosophy",
     "content": "Philosophical rules are generally not measurable. However, they are valuable. For Gluten CPP coding, there are a few Philosophical rules as the following. | Write in ISO Standard C++. | Standard API first, the CPP programming APIs are priority to system calls. | Write code consistently. It’s good for understanding and maintaining. | Keep simple, making code clear and easy to read. | Optimize code for reader, not for writer. Thus, more time will be spent reading code than  [...]
     "url": "/developers/CppCodingStyle.html#philosophy",
     
     "relUrl": "/developers/CppCodingStyle.html#philosophy"
-  },"4": {
+  },"6": {
     "doc": "CPP Code Style",
     "title": "Code Formatting",
     "content": "Many aspects of C++ coding style will be covered by clang-format, such as spacing, line width, indentation and ordering (for includes, using directives and etc).  . | Always ensure your code is compatible with clang-format-12 for Velox backend. | dev/formatcppcode.sh is provided for formatting Velox CPP code. | . ",
     "url": "/developers/CppCodingStyle.html#code-formatting",
     
     "relUrl": "/developers/CppCodingStyle.html#code-formatting"
-  },"5": {
+  },"7": {
     "doc": "CPP Code Style",
     "title": "Naming Conventions",
     "content": ". | Use PascalCase for types (class, struct, enum, type alias, type template parameter) and file name. | Use camelCase for function, member and local variable, and non-type template parameter. | Use camelCase_ for private and protected member variable. | Use snake_case for namespace name and build target. | Use UPPER_SNAKE_CASE for macro. | Use kPascalCase for static constant and enumerator. | . ",
     "url": "/developers/CppCodingStyle.html#naming-conventions",
     
     "relUrl": "/developers/CppCodingStyle.html#naming-conventions"
-  },"6": {
+  },"8": {
     "doc": "CPP Code Style",
     "title": "Designs",
     "content": ". | No over design. | No negation of negation, isValid is better than isNotInvalid. | Avoid corner case, and common case first. | Express ideas directly, don’t let me think. | Make a check for the arguments in the interface between modules, and don’t make a check in the inner implementation, use assert in the private implementation instead of too much safe check. | . ",
     "url": "/developers/CppCodingStyle.html#designs",
     
     "relUrl": "/developers/CppCodingStyle.html#designs"
-  },"7": {
+  },"9": {
     "doc": "CPP Code Style",
     "title": "Source File &amp; Header File",
     "content": ". | All header files must have a single-inclusion guard using #pragma once | Always use .h as header file suffix, not .hpp. | Always use .cc as source file suffix, neither .cpp nor .cxx. | One file should contain one main class, and the file name should be consistent with the main class name. | Obvious exception: files used for defining various misc functions. | . | If a header file has a corresponding source file, they should have the same file name with different suffix [...]
     "url": "/developers/CppCodingStyle.html#source-file--header-file",
     
     "relUrl": "/developers/CppCodingStyle.html#source-file--header-file"
-  },"8": {
+  },"10": {
     "doc": "CPP Code Style",
     "title": "Class",
     "content": ". | Base class name doesn’t end with Base, use Backend instead of BackendBase. | Ensure one class does one thing, and follows the single responsibility principle. | No big class, No huge class, No too much interfaces. | Distinguish interface from implementation, make implementations private. | When designing a class hierarchy, distinguish between interface inheritance and implementation inheritance. | Ensure that public inheritance represent the relation of is-a. | Ensure [...]
     "url": "/developers/CppCodingStyle.html#class",
     
     "relUrl": "/developers/CppCodingStyle.html#class"
-  },"9": {
+  },"11": {
     "doc": "CPP Code Style",
     "title": "Function",
     "content": ". | Make functions short and simple. | Calling a meaningful function is more readable than writing too many statements in place, but the performance-sensitive code path is an exception. | Give the function a good name, how to check whether the function name is good or not. | When you read it loudly, you feel smooth. | The information can be represented by arguments should not be encoded into the function name. such as. use get(size_t index) instead of getByIndex. | . | A  [...]
     "url": "/developers/CppCodingStyle.html#function",
     
     "relUrl": "/developers/CppCodingStyle.html#function"
-  },"10": {
+  },"12": {
     "doc": "CPP Code Style",
     "title": "Variable",
     "content": ". | Make variable names simple and meaningful. | Don’t group all your variables at the top of the scope, it’s an outdated habit. | Declare variables as close to the usage point as possible. | . ",
     "url": "/developers/CppCodingStyle.html#variable",
     
     "relUrl": "/developers/CppCodingStyle.html#variable"
-  },"11": {
+  },"13": {
     "doc": "CPP Code Style",
     "title": "Constant",
     "content": ". | Prefer const variables to using preprocessor (#define) to define constant values. | . ",
     "url": "/developers/CppCodingStyle.html#constant",
     
     "relUrl": "/developers/CppCodingStyle.html#constant"
-  },"12": {
+  },"14": {
     "doc": "CPP Code Style",
     "title": "Macro",
     "content": ". | Macros downgrade readability, break mind, and affect debug. | Macros have side effects. | Use macros cautiously and carefully. | Consider using const variables or inline functions to replace macros. | Consider defining macros with the wrap of do {...} while (0) | Avoid using 3rd party library macros directly. | . ",
     "url": "/developers/CppCodingStyle.html#macro",
     
     "relUrl": "/developers/CppCodingStyle.html#macro"
-  },"13": {
+  },"15": {
     "doc": "CPP Code Style",
     "title": "Namespace",
     "content": ". | Don’t using namespace xxx in header files. Instead, you can do this in source files. But it’s still not encouraged. | Place all Gluten CPP codes under namespace gluten because one level namespace is enough. No nested namespace. Nested namespaces bring mess. | The anonymous namespace is recommended for defining file level classes, functions and variables. It’s used to place file scoped static functions and variables. | . ",
     "url": "/developers/CppCodingStyle.html#namespace",
     
     "relUrl": "/developers/CppCodingStyle.html#namespace"
-  },"14": {
+  },"16": {
     "doc": "CPP Code Style",
     "title": "Resource Management",
     "content": ". | Use handles and RAII to manage resources automatically. | Immediately give the result of an explicit resource allocation to a manager object. | Prefer scoped objects and stack objects. | Use raw pointers to denote individual objects. | Use pointer + size_t to denote array objects if you don’t want to use containers. | A raw pointer (a T*) is non-owning. | A raw reference (a T&amp;) is non-owning. | Understand the difference of unique_ptr, shared_ptr, weak_ptr. | uniqu [...]
     "url": "/developers/CppCodingStyle.html#resource-management",
     
     "relUrl": "/developers/CppCodingStyle.html#resource-management"
-  },"15": {
+  },"17": {
     "doc": "CPP Code Style",
     "title": "Exception",
     "content": ". | The exception specifications are changing always. The difference between various CPP standards is big, so we should use exception cautiously in Gluten. | Prefer return code to throwing exceptions. | Prefer compile-time checking to run-time checking. | Encapsulate messy constructors, rather than spreading through the code. | . ",
     "url": "/developers/CppCodingStyle.html#exception",
     
     "relUrl": "/developers/CppCodingStyle.html#exception"
-  },"16": {
+  },"18": {
     "doc": "CPP Code Style",
     "title": "Code Comment",
     "content": ". | Add necessary comments. The comment is not the more the better, also not the less the better. | Good comment makes obscure code easily understood. It’s unnecessary to add comments for quite obvious code. | . ",
     "url": "/developers/CppCodingStyle.html#code-comment",
     
     "relUrl": "/developers/CppCodingStyle.html#code-comment"
-  },"17": {
+  },"19": {
     "doc": "CPP Code Style",
     "title": "References",
     "content": ". | CppCoreGuidelines | Velox CODING_STYLE | Thanks Gluten developers for their wise suggestions and helps. | . ",
     "url": "/developers/CppCodingStyle.html#references",
     
     "relUrl": "/developers/CppCodingStyle.html#references"
-  },"18": {
+  },"20": {
     "doc": "CPP Code Style",
     "title": "CPP Code Style",
     "content": " ",
     "url": "/developers/CppCodingStyle.html",
     
     "relUrl": "/developers/CppCodingStyle.html"
-  },"19": {
+  },"21": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Gluten CPP Core Guidelines",
+    "content": "This is a set of CPP core guidelines for Gluten. The aim is to make the codebase simpler, more efficient, more maintainable by promoting consistency and according to best practices. ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#gluten-cpp-core-guidelines",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#gluten-cpp-core-guidelines"
+  },"22": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Philosophy",
+    "content": "Philosophical rules are generally not measurable. However, they are valuable. For Gluten CPP coding, there are a few Philosophical rules as the following. | Write in ISO Standard C++. | Standard API first, the CPP programming APIs are priority to system calls. | Write code consistently. It’s good for understanding and maintaining. | Keep simple, making code clear and easy to read. | Optimize code for reader, not for writer. Thus, more time will be spent reading code than  [...]
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#philosophy",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#philosophy"
+  },"23": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Code Formatting",
+    "content": "Many aspects of C++ coding style will be covered by clang-format, such as spacing, line width, indentation and ordering (for includes, using directives and etc).  . | Always ensure your code is compatible with clang-format-12 for Velox backend. | dev/formatcppcode.sh is provided for formatting Velox CPP code. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#code-formatting",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#code-formatting"
+  },"24": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Naming Conventions",
+    "content": ". | Use PascalCase for types (class, struct, enum, type alias, type template parameter) and file name. | Use camelCase for function, member and local variable, and non-type template parameter. | Use camelCase_ for private and protected member variable. | Use snake_case for namespace name and build target. | Use UPPER_SNAKE_CASE for macro. | Use kPascalCase for static constant and enumerator. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#naming-conventions",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#naming-conventions"
+  },"25": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Designs",
+    "content": ". | No over design. | No negation of negation, isValid is better than isNotInvalid. | Avoid corner case, and common case first. | Express ideas directly, don’t let me think. | Make a check for the arguments in the interface between modules, and don’t make a check in the inner implementation, use assert in the private implementation instead of too much safe check. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#designs",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#designs"
+  },"26": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Source File &amp; Header File",
+    "content": ". | All header files must have a single-inclusion guard using #pragma once | Always use .h as header file suffix, not .hpp. | Always use .cc as source file suffix, neither .cpp nor .cxx. | One file should contain one main class, and the file name should be consistent with the main class name. | Obvious exception: files used for defining various misc functions. | . | If a header file has a corresponding source file, they should have the same file name with different suffix [...]
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#source-file--header-file",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#source-file--header-file"
+  },"27": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Class",
+    "content": ". | Base class name doesn’t end with Base, use Backend instead of BackendBase. | Ensure one class does one thing, and follows the single responsibility principle. | No big class, No huge class, No too much interfaces. | Distinguish interface from implementation, make implementations private. | When designing a class hierarchy, distinguish between interface inheritance and implementation inheritance. | Ensure that public inheritance represent the relation of is-a. | Ensure [...]
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#class",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#class"
+  },"28": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Function",
+    "content": ". | Make functions short and simple. | Calling a meaningful function is more readable than writing too many statements in place, but the performance-sensitive code path is an exception. | Give the function a good name, how to check whether the function name is good or not. | When you read it loudly, you feel smooth. | The information can be represented by arguments should not be encoded into the function name. such as. use get(size_t index) instead of getByIndex. | . | A  [...]
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#function",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#function"
+  },"29": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Variable",
+    "content": ". | Make variable names simple and meaningful. | Don’t group all your variables at the top of the scope, it’s an outdated habit. | Declare variables as close to the usage point as possible. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#variable",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#variable"
+  },"30": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Constant",
+    "content": ". | Prefer const variables to using preprocessor (#define) to define constant values. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#constant",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#constant"
+  },"31": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Macro",
+    "content": ". | Macros downgrade readability, break mind, and affect debug. | Macros have side effects. | Use macros cautiously and carefully. | Consider using const variables or inline functions to replace macros. | Consider defining macros with the wrap of do {...} while (0) | Avoid using 3rd party library macros directly. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#macro",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#macro"
+  },"32": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Namespace",
+    "content": ". | Don’t using namespace xxx in header files. Instead, you can do this in source files. But it’s still not encouraged. | Place all Gluten CPP codes under namespace gluten because one level namespace is enough. No nested namespace. Nested namespaces bring mess. | The anonymous namespace is recommended for defining file level classes, functions and variables. It’s used to place file scoped static functions and variables. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#namespace",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#namespace"
+  },"33": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Resource Management",
+    "content": ". | Use handles and RAII to manage resources automatically. | Immediately give the result of an explicit resource allocation to a manager object. | Prefer scoped objects and stack objects. | Use raw pointers to denote individual objects. | Use pointer + size_t to denote array objects if you don’t want to use containers. | A raw pointer (a T*) is non-owning. | A raw reference (a T&amp;) is non-owning. | Understand the difference of unique_ptr, shared_ptr, weak_ptr. | uniqu [...]
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#resource-management",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#resource-management"
+  },"34": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Exception",
+    "content": ". | The exception specifications are changing always. The difference between various CPP standards is big, so we should use exception cautiously in Gluten. | Prefer return code to throwing exceptions. | Prefer compile-time checking to run-time checking. | Encapsulate messy constructors, rather than spreading through the code. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#exception",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#exception"
+  },"35": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "Code Comment",
+    "content": ". | Add necessary comments. The comment is not the more the better, also not the less the better. | Good comment makes obscure code easily understood. It’s unnecessary to add comments for quite obvious code. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#code-comment",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#code-comment"
+  },"36": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "References",
+    "content": ". | CppCoreGuidelines | Velox CODING_STYLE | Thanks Gluten developers for their wise suggestions and helps. | . ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/#references",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/#references"
+  },"37": {
+    "doc": "v1.1.1/CPP Code Style",
+    "title": "v1.1.1/CPP Code Style",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/cpp_code_style/",
+    
+    "relUrl": "/archives/v1.1.1/developers/cpp_code_style/"
+  },"38": {
+    "doc": "v1.1.1/Getting Started with ClickHouse Backend",
+    "title": "ClickHouse Backend",
+    "content": "ClickHouse is a column-oriented database management system (DBMS) for online analytical processing of queries (OLAP), which supports best in the industry query performance, while significantly reducing storage requirements through its innovative use of columnar storage and compression. We port ClickHouse ( based on version 23.1 ) as a library, called ‘libch.so’, and Gluten loads this library through JNI as the native engine. In this way, we don’t need to deploy a standalo [...]
+    "url": "/archives/v1.1.1/docs/clickhouse/getting-started/#clickhouse-backend",
+    
+    "relUrl": "/archives/v1.1.1/docs/clickhouse/getting-started/#clickhouse-backend"
+  },"39": {
+    "doc": "v1.1.1/Getting Started with ClickHouse Backend",
+    "title": "v1.1.1/Getting Started with ClickHouse Backend",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/clickhouse/getting-started/",
+    
+    "relUrl": "/archives/v1.1.1/docs/clickhouse/getting-started/"
+  },"40": {
     "doc": "Getting Started with ClickHouse Backend",
     "title": "ClickHouse Backend",
     "content": "ClickHouse is a column-oriented database management system (DBMS) for online analytical processing of queries (OLAP), which supports best in the industry query performance, while significantly reducing storage requirements through its innovative use of columnar storage and compression. We port ClickHouse ( based on version 23.1 ) as a library, called ‘libch.so’, and Gluten loads this library through JNI as the native engine. In this way, we don’t need to deploy a standalo [...]
     "url": "/docs/clickhouse/getting-started#clickhouse-backend",
     
     "relUrl": "/docs/clickhouse/getting-started#clickhouse-backend"
-  },"20": {
+  },"41": {
     "doc": "Getting Started with ClickHouse Backend",
     "title": "Getting Started with ClickHouse Backend",
     "content": " ",
     "url": "/docs/clickhouse/getting-started",
     
     "relUrl": "/docs/clickhouse/getting-started"
-  },"21": {
+  },"42": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Supported Version",
+    "content": "| Type | Version |——-|——————————| Spark | 3.2.2, 3.3.1 | OS | Ubuntu20.04/22.04, Centos7/8 | jdk | openjdk8 | scala | 2.12 . Spark3.4.0 support is still WIP. TPCH/DS can pass, UT is not yet passed. There are pending PRs for jdk11 support. Currently, the mvn script can automatically fetch and build all dependency libraries incluing Velox. Our nightly build still use Velox under oap-project. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#supported-version",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#supported-version"
+  },"43": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Prerequisite",
+    "content": "Currently, Gluten+Velox backend is only tested on Ubuntu20.04/Ubuntu22.04/Centos8. Other kinds of OS support are still in progress. The long term goal is to support several common OS and conda env deployment. Gluten builds with Spark3.2.x and Spark3.3.x now but only fully tested in CI with 3.2.2 and 3.3.1. We will add/update supported/tested versions according to the upstream changes. we need to set up the JAVA_HOME env. Currently, java 8 is required and the support for j [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#prerequisite",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#prerequisite"
+  },"44": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Build Gluten with Velox Backend",
+    "content": "It’s recommended to use buildbundle-veloxbe.sh to build gluten in one script. Gluten build guide listed the parameters and their default value of build command for your reference. For x86_64 build . cd /path/to/gluten ## The script builds two jars for spark 3.2.2 and 3.3.1./dev/buildbundle-veloxbe.sh ## After a complete build, if you need to re-build the project and only some gluten code is changed, ## you can use the following command to skip building velox and protobuf. [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-velox-backend",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-velox-backend"
+  },"45": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Dependency library deployment",
+    "content": "With config enable_vcpkg=ON, the dependency libraries will be built and statically linked into libvelox.so and libgluten.so, which is packed into the gluten-jar. In this way, only the gluten-jar is needed to add to spark.&lt;driver|executor&gt;.extraClassPath and spark will deploy the jar to each worker node. It’s better to build the static version using a clean docker image without any extra libraries installed. On host with some libraries like jemalloc installed, the sc [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#dependency-library-deployment",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#dependency-library-deployment"
+  },"46": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "HDFS support",
+    "content": "Hadoop hdfs support is ready via the libhdfs3 library. The libhdfs3 provides native API for Hadoop I/O without the drawbacks of JNI. It also provides advanced authentication like Kerberos based. Please note this library has several dependencies which may require extra installations on Driver and Worker node. Build with HDFS support . To build Gluten with HDFS support, below command is suggested: . cd /path/to/gluten ./dev/buildbundle-veloxbe.sh --enable_hdfs=ON . Configur [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#hdfs-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#hdfs-support"
+  },"47": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "AWS S3 support",
+    "content": "Velox supports S3 with the open source AWS C++ SDK and Gluten uses Velox S3 connector to connect with S3. A new build option for S3(enable_s3) is added. Below command is used to enable this feature . cd /path/to/gluten ./dev/buildbundle-veloxbe.sh --enable_s3=ON . Currently there are several ways to asscess S3 in Spark. Please refer Velox S3 part for more detailed configurations . ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#aws-s3-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#aws-s3-support"
+  },"48": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Celeborn support",
+    "content": "Gluten with velox backend supports Celeborn as remote shuffle service. Below introduction is used to enable this feature . First refer to this URL(https://github.com/apache/incubator-celeborn) to setup a celeborn cluster. When compiling the Gluten Java module, it’s required to enable rss profile, as follows: . mvn clean package -Pbackends-velox -Pspark-3.3 -Prss -DskipTests . Then add the Gluten and Spark Celeborn Client packages to your Spark application’s classpath(usua [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#celeborn-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#celeborn-support"
+  },"49": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "DeltaLake Support",
+    "content": "Gluten with velox backend supports DeltaLake table. How to use . First of all, compile gluten-delta module by a delta profile, as follows: . mvn clean package -Pbackends-velox -Pspark-3.3 -Pdelta -DskipTests . Then, put the additional gluten-delta jar to the class path (usually it’s $SPARK_HOME/jars). The gluten-delta jar is in gluten-delta/target directory. After the two steps, you can query delta table by gluten/velox without scan’s fallback. Gluten with velox backends  [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#deltalake-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#deltalake-support"
+  },"50": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Iceberg Support",
+    "content": "Gluten with velox backend supports Iceberg table. Currently, only reading COW (Copy-On-Write) tables is supported. How to use . First of all, compile gluten-iceberg module by a iceberg profile, as follows: . mvn clean package -Pbackends-velox -Pspark-3.3 -Piceberg -DskipTests . Then, put the additional gluten-iceberg jar to the class path (usually it’s $SPARK_HOME/jars). The gluten-iceberg jar is in gluten-iceberg/target directory. After the two steps, you can query icebe [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#iceberg-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#iceberg-support"
+  },"51": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Coverage",
+    "content": "Spark3.3 has 387 functions in total. ~240 are commonly used. Velox’s functions have two category, Presto and Spark. Presto has 124 functions implemented. Spark has 62 functions. Spark functions are verified to have the same result as Vanilla Spark. Some Presto functions have the same result as Vanilla Spark but some others have different. Gluten prefer to use Spark functions firstly. If it’s not in Spark’s list but implemented in Presto, we currently offload to Presto one [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#coverage",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#coverage"
+  },"52": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Spill (Experimental)",
+    "content": "Velox backend supports spilling-to-disk. Using the following configuration options to customize spilling: . | Name | Default Value | Description | . | spark.gluten.sql.columnar.backend.velox.spillStrategy | auto | none: Disable spill on Velox backend; auto: Let Spark memory manager manage Velox’s spilling | . | spark.gluten.sql.columnar.backend.velox.spillFileSystem | local | The filesystem used to store spill data. local: The local file system. heap-over-local: Write fil [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#spill-experimental",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#spill-experimental"
+  },"53": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Velox User-Defined Functions (UDF)",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#velox-user-defined-functions-udf",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#velox-user-defined-functions-udf"
+  },"54": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Introduction",
+    "content": "Velox backend supports User-Defined Functions (UDF). Users can create their own functions using the UDF interface provided in Velox backend and build libraries for these functions. At runtime, the UDF are registered at the start of applications. Once registered, Gluten will be able to parse and offload these UDF into Velox during execution. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#introduction",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#introduction"
+  },"55": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Creating a UDF library",
+    "content": "The following steps demonstrate how to set up a UDF library project: . | Include the UDF Interface Header: First, include the UDF interface header file Udf.h in the project file. The header file defines the UdfEntry struct, along with the macros for declaring the necessary functions to integrate the UDF into Gluten and Velox. | Implement the UDF: Implement UDF. These functions should be able to register to Velox. | Implement the Interface Functions: Implement the followin [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#creating-a-udf-library",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#creating-a-udf-library"
+  },"56": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Building the UDF library",
+    "content": "To build the UDF library, users need to compile the C++ code and link to libvelox.so. It’s recommended to create a CMakeLists.txt for the project. Here’s an example: . project(myudf) set(CMAKE_CXX_STANDARD 17) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(GLUTEN_HOME /path/to/gluten) add_library(myudf SHARED \"MyUDF.cpp\") find_library(VELOX_LIBRARY REQUIRED NAMES velox HINTS ${GLUTEN_HOME}/cpp/build/releases NO_DEFAULT_PATH) target_include_directories(myudf PRIVATE ${GLUTEN_HO [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#building-the-udf-library",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#building-the-udf-library"
+  },"57": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Using UDF in Gluten",
+    "content": "Gluten loads the UDF libraries at runtime. You can upload UDF libraries via --files or --archives, and configure the libray paths using the provided Spark configuration, which accepts comma separated list of library paths. Note if running on Yarn client mode, the uploaded files are not reachable on driver side. Users should copy those files to somewhere reachable for driver and set spark.gluten.sql.columnar.backend.velox.driver.udfLibraryPaths. This configuration is also  [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#using-udf-in-gluten",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#using-udf-in-gluten"
+  },"58": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Try the example",
+    "content": "We provided an Velox UDF example file MyUDF.cpp. After building gluten cpp, you can find the example library at /path/to/gluten/cpp/build/velox/udf/examples/libmyudf.so . Start spark-shell or spark-sql with below configuration . --files /path/to/gluten/cpp/build/velox/udf/examples/libmyudf.so --conf spark.gluten.sql.columnar.backend.velox.udfLibraryPaths=libmyudf.so . Run query. The functions myudf1 and myudf2 increment the input value by a constant of 5 . select myudf1(1 [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#try-the-example",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#try-the-example"
+  },"59": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "High-Bandwidth Memory (HBM) support",
+    "content": "Gluten supports allocating memory on HBM. This feature is optional and is disabled by default. It is implemented on top of Memkind library. You can refer to memkind’s readme for more details. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#high-bandwidth-memory-hbm-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#high-bandwidth-memory-hbm-support"
+  },"60": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Build Gluten with HBM",
+    "content": "Gluten will internally build and link to a specific version of Memkind library and hwloc. Other dependencies should be installed on Driver and Worker node first: . sudo apt install -y autoconf automake g++ libnuma-dev libtool numactl unzip libdaxctl-dev . After the set-up, you can now build Gluten with HBM. Below command is used to enable this feature . cd /path/to/gluten ## The script builds two jars for spark 3.2.2 and 3.3.1./dev/buildbundle-veloxbe.sh --enable_hbm=ON . ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-hbm",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-hbm"
+  },"61": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Configure and enable HBM in Spark Application",
+    "content": "At runtime, MEMKIND_HBW_NODES enviroment variable is detected for configuring HBM NUMA nodes. For the explaination to this variable, please refer to memkind’s manual page. This can be set for all executors through spark conf, e.g. --conf spark.executorEnv.MEMKIND_HBW_NODES=8-15. Note that memory allocation fallback is also supported and cannot be turned off. If HBM is unavailable or fills up, the allocator will use default(DDR) memory. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#configure-and-enable-hbm-in-spark-application",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#configure-and-enable-hbm-in-spark-application"
+  },"62": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Intel® QuickAssist Technology (QAT) support",
+    "content": "Gluten supports using Intel® QuickAssist Technology (QAT) for data compression during Spark Shuffle. It benefits from QAT Hardware-based acceleration on compression/decompression, and uses Gzip as compression format for higher compression ratio to reduce the pressure on disks and network transmission. This feature is based on QAT driver library and QATzip library. Please manually download QAT driver for your system, and follow its README to build and install on all Driver [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#intel-quickassist-technology-qat-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#intel-quickassist-technology-qat-support"
+  },"63": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Software Requirements",
+    "content": ". | Download QAT driver for your system, and follow its README to build and install on all Driver and Worker nodes: Intel® QuickAssist Technology Driver for Linux* – HW Version 2.0. | Below compression libraries need to be installed on all Driver and Worker nodes: . | Zlib* library of version 1.2.7 or higher | ZSTD* library of version 1.5.4 or higher | LZ4* library | . | . ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#software-requirements",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#software-requirements"
+  },"64": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Build Gluten with QAT",
+    "content": ". | Setup ICP_ROOT environment variable to the directory where QAT driver is extracted. This environment variable is required during building Gluten and running Spark applications. It’s recommended to put it in .bashrc on Driver and Worker nodes. | . echo \"export ICP_ROOT=/path/to/QAT_driver\" &gt;&gt; ~/.bashrc source ~/.bashrc # Also set for root if running as non-root user sudo su - echo \"export ICP_ROOT=/path/to/QAT_driver\" &gt;&gt; ~/.bashrc exit . | This step is  [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-qat",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-qat"
+  },"65": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Enable QAT with Gzip/Zstd for shuffle compression",
+    "content": ". | To offload shuffle compression into QAT, first make sure you have the right QAT configuration file at /etc/4xxx_devX.conf. We provide a example configuration file. This configuration sets up to 4 processes that can bind to 1 QAT, and each process can use up to 16 QAT DC instances. | . ## run as root ## Overwrite QAT configuration file. cd /etc for i in {0..7}; do echo \"4xxx_dev$i.conf\"; done | xargs -i cp -f /path/to/gluten/docs/qat/4x16.conf {} ## Restart QAT after [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#enable-qat-with-gzipzstd-for-shuffle-compression",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#enable-qat-with-gzipzstd-for-shuffle-compression"
+  },"66": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "QAT driver references",
+    "content": "Documentation . README Text Files (README_QAT20.L.1.0.0-00021.txt) . Release Notes . Check out the Intel® QuickAssist Technology Software for Linux* - Release Notes for the latest changes in this release. Getting Started Guide . Check out the Intel® QuickAssist Technology Software for Linux* - Getting Started Guide for detailed installation instructions. Programmer’s Guide . Check out the Intel® QuickAssist Technology Software for Linux* - Programmer’s Guide for software  [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#qat-driver-references",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#qat-driver-references"
+  },"67": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Intel® In-memory Analytics Accelerator (IAA/IAX) support",
+    "content": "Similar to Intel® QAT, Gluten supports using Intel® In-memory Analytics Accelerator (IAA, also called IAX) for data compression during Spark Shuffle. It benefits from IAA Hardware-based acceleration on compression/decompression, and uses Gzip as compression format for higher compression ratio to reduce the pressure on disks and network transmission. This feature is based on Intel® QPL. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#intel-in-memory-analytics-accelerator-iaaiax-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#intel-in-memory-analytics-accelerator-iaaiax-support"
+  },"68": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Build Gluten with IAA",
+    "content": "Gluten will internally build and link to a specific version of QPL library, but extra environment setup is still required. Please refer to QPL Installation Guide to install dependencies and configure accelerators. This step is required if your application is running as Non-root user. Create a group for the users who have privilege to use IAA, and grant group iaa read/write access to the IAA Work-Queues. sudo groupadd iaa sudo usermod -aG iaa username # need to relogin sud [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-iaa",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#build-gluten-with-iaa"
+  },"69": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Enable IAA with Gzip Compression for shuffle compression",
+    "content": ". | To enable QAT at run-time, first make sure you have configured the IAA Work-Queues correctly, and the file permissions of /dev/iax/wqX.0 are correct. | . sudo ls -l /dev/iax . The output should be like: . total 0 crw-rw---- 1 root iaa 509, 0 Apr 5 18:54 wq1.0 crw-rw---- 1 root iaa 509, 5 Apr 5 18:54 wq11.0 crw-rw---- 1 root iaa 509, 6 Apr 5 18:54 wq13.0 crw-rw---- 1 root iaa 509, 7 Apr 5 18:54 wq15.0 crw-rw---- 1 root iaa 509, 1 Apr 5 18:54 wq3.0 crw-rw---- 1 root iaa [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#enable-iaa-with-gzip-compression-for-shuffle-compression",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#enable-iaa-with-gzip-compression-for-shuffle-compression"
+  },"70": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "IAA references",
+    "content": "Intel® IAA Enabling Guide . Check out the Intel® In-Memory Analytics Accelerator (Intel® IAA) Enabling Guide . Intel® QPL Documentation . Check out the Intel® Query Processing Library (Intel® QPL) Documentation . ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#iaa-references",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#iaa-references"
+  },"71": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Test TPC-H or TPC-DS on Gluten with Velox backend",
+    "content": "All TPC-H and TPC-DS queries are supported in Gluten Velox backend. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#test-tpc-h-or-tpc-ds-on-gluten-with-velox-backend",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#test-tpc-h-or-tpc-ds-on-gluten-with-velox-backend"
+  },"72": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Data preparation",
+    "content": "The data generation scripts are TPC-H dategen script and TPC-DS dategen script. The used TPC-H and TPC-DS queries are the original ones, and can be accessed from TPC-DS queries and TPC-H queries. Some other versions of TPC-DS queries are also provided, but are not recommended for testing, including: . | the modified TPC-DS queries with “Decimal-to-Double”: TPC-DS non-decimal queries (outdated). | . ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#data-preparation",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#data-preparation"
+  },"73": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Submit the Spark SQL job",
+    "content": "Submit test script from spark-shell. You can find the scala code to Run TPC-H as an example. Please remember to modify the location of TPC-H files as well as TPC-H queries before you run the testing. var parquet_file_path = \"/PATH/TO/TPCH_PARQUET_PATH\" var gluten_root = \"/PATH/TO/GLUTEN\" . Below script shows an example about how to run the testing, you should modify the parameters such as executor cores, memory, offHeap size based on your environment. export GLUTEN_JA [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#submit-the-spark-sql-job",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#submit-the-spark-sql-job"
+  },"74": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Result",
+    "content": "wholestagetransformer indicates that the offload works. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#result",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#result"
+  },"75": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Performance",
+    "content": "Below table shows the TPC-H Q1 and Q6 Performance in a multiple-thread test (–num-executors 6 –executor-cores 6) for Velox and vanilla Spark. Both Parquet and ORC datasets are sf1024. | Query Performance (s) | Velox (ORC) | Vanilla Spark (Parquet) | Vanilla Spark (ORC) | . | TPC-H Q6 | 13.6 | 21.6 | 34.9 | . | TPC-H Q1 | 26.1 | 76.7 | 84.9 | . ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#performance",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#performance"
+  },"76": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "External reference setup",
+    "content": "TO ease your first-hand experience of using Gluten, we have set up an external reference cluster. If you are interested, please contact Weiting.Chen@intel.com. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#external-reference-setup",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#external-reference-setup"
+  },"77": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Gluten UI",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#gluten-ui",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#gluten-ui"
+  },"78": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Gluten event",
+    "content": "Gluten provides two events GlutenBuildInfoEvent and GlutenPlanFallbackEvent: . | GlutenBuildInfoEvent, it contains the Gluten build information so that we are able to be aware of the environment when doing some debug. It includes Java Version, Scala Version, GCC Version, Gluten Version, Spark Version, Hadoop Version, Gluten Revision, Backend, Backend Revision, etc. | GlutenPlanFallbackEvent, it contains the fallback information for each query execution. Note, if the query [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#gluten-event",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#gluten-event"
+  },"79": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "SQL tab",
+    "content": "Gluten provides a tab based on Spark UI, named Gluten SQL / DataFrame . This tab contains two parts: . | The Gluten build information. | SQL/Dataframe queries fallback information. | . If you want to disable Gluten UI, add a config when submitting --conf spark.gluten.ui.enabled=false. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#sql-tab",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#sql-tab"
+  },"80": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "History server",
+    "content": "Gluten UI also supports Spark history server. Add gluten-ui jar into the history server classpath, e.g., $SPARK_HOME/jars, then restart history server. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#history-server",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#history-server"
+  },"81": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Native plan string",
+    "content": "Gluten supports inject native plan string into Spark explain with formatted mode by setting --conf spark.gluten.sql.injectNativePlanStringToExplain=true. Here is an example, how Gluten show the native plan string. (9) WholeStageCodegenTransformer (2) Input [6]: [c1#0L, c2#1L, c3#2L, c1#3L, c2#4L, c3#5L] Arguments: false Native Plan: -- Project[expressions: (n3_6:BIGINT, \"n0_0\"), (n3_7:BIGINT, \"n0_1\"), (n3_8:BIGINT, \"n0_2\"), (n3_9:BIGINT, \"n1_0\"), (n3_10:BIGINT, \" [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#native-plan-string",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#native-plan-string"
+  },"82": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Native plan with stats",
+    "content": "Gluten supports print native plan with stats to executor system output stream by setting --conf spark.gluten.sql.debug=true. Note that, the plan string with stats is task level which may cause executor log size big. Here is an example, how Gluten show the native plan string with stats. I20231121 10:19:42.348845 90094332 WholeStageResultIterator.cc:220] Native Plan with stats for: [Stage: 1 TID: 16] -- Project[expressions: (n3_6:BIGINT, \"n0_0\"), (n3_7:BIGINT, \"n0_1\"),  [...]
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#native-plan-with-stats",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#native-plan-with-stats"
+  },"83": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "Gluten Implicits",
+    "content": "Gluten provides a helper class to get the fallback summary from a Spark Dataset. import org.apache.spark.sql.execution.GlutenImplicits._ val df = spark.sql(\"SELECT * FROM t\") df.fallbackSummary . Note that, if AQE is enabled, but the query is not materialized, then it will re-plan the query execution with disabled AQE. It is a workaround to get the final plan, and it may cause the inconsistent results with a materialized query. However, we have no choice. ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/#gluten-implicits",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/#gluten-implicits"
+  },"84": {
+    "doc": "v1.1.1/Getting-Started with Velox Backend",
+    "title": "v1.1.1/Getting-Started with Velox Backend",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/getting-started/",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/getting-started/"
+  },"85": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Supported Version",
     "content": "| Type | Version |——-|——————————| Spark | 3.2.2, 3.3.1 | OS | Ubuntu20.04/22.04, Centos7/8 | jdk | openjdk8 | scala | 2.12 . Spark3.4.0 support is still WIP. TPCH/DS can pass, UT is not yet passed. There are pending PRs for jdk11 support. Currently, the mvn script can automatically fetch and build all dependency libraries incluing Velox. Our nightly build still use Velox under oap-project. ",
     "url": "/docs/velox/getting-started#supported-version",
     
     "relUrl": "/docs/velox/getting-started#supported-version"
-  },"22": {
+  },"86": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Prerequisite",
     "content": "Currently, Gluten+Velox backend is only tested on Ubuntu20.04/Ubuntu22.04/Centos8. Other kinds of OS support are still in progress. The long term goal is to support several common OS and conda env deployment. Gluten builds with Spark3.2.x and Spark3.3.x now but only fully tested in CI with 3.2.2 and 3.3.1. We will add/update supported/tested versions according to the upstream changes. we need to set up the JAVA_HOME env. Currently, java 8 is required and the support for j [...]
     "url": "/docs/velox/getting-started#prerequisite",
     
     "relUrl": "/docs/velox/getting-started#prerequisite"
-  },"23": {
+  },"87": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Build Gluten with Velox Backend",
     "content": "It’s recommended to use buildbundle-veloxbe.sh to build gluten in one script. Gluten build guide listed the parameters and their default value of build command for your reference. For x86_64 build . cd /path/to/gluten ## The script builds two jars for spark 3.2.2 and 3.3.1./dev/buildbundle-veloxbe.sh ## After a complete build, if you need to re-build the project and only some gluten code is changed, ## you can use the following command to skip building velox and protobuf. [...]
     "url": "/docs/velox/getting-started#build-gluten-with-velox-backend",
     
     "relUrl": "/docs/velox/getting-started#build-gluten-with-velox-backend"
-  },"24": {
+  },"88": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Dependency library deployment",
     "content": "With config enable_vcpkg=ON, the dependency libraries will be built and statically linked into libvelox.so and libgluten.so, which is packed into the gluten-jar. In this way, only the gluten-jar is needed to add to spark.&lt;driver|executor&gt;.extraClassPath and spark will deploy the jar to each worker node. It’s better to build the static version using a clean docker image without any extra libraries installed. On host with some libraries like jemalloc installed, the sc [...]
     "url": "/docs/velox/getting-started#dependency-library-deployment",
     
     "relUrl": "/docs/velox/getting-started#dependency-library-deployment"
-  },"25": {
+  },"89": {
     "doc": "Getting-Started with Velox Backend",
     "title": "HDFS support",
     "content": "Hadoop hdfs support is ready via the libhdfs3 library. The libhdfs3 provides native API for Hadoop I/O without the drawbacks of JNI. It also provides advanced authentication like Kerberos based. Please note this library has several dependencies which may require extra installations on Driver and Worker node. Build with HDFS support . To build Gluten with HDFS support, below command is suggested: . cd /path/to/gluten ./dev/buildbundle-veloxbe.sh --enable_hdfs=ON . Configur [...]
     "url": "/docs/velox/getting-started#hdfs-support",
     
     "relUrl": "/docs/velox/getting-started#hdfs-support"
-  },"26": {
+  },"90": {
     "doc": "Getting-Started with Velox Backend",
     "title": "AWS S3 support",
     "content": "Velox supports S3 with the open source AWS C++ SDK and Gluten uses Velox S3 connector to connect with S3. A new build option for S3(enable_s3) is added. Below command is used to enable this feature . cd /path/to/gluten ./dev/buildbundle-veloxbe.sh --enable_s3=ON . Currently there are several ways to asscess S3 in Spark. Please refer Velox S3 part for more detailed configurations . ",
     "url": "/docs/velox/getting-started#aws-s3-support",
     
     "relUrl": "/docs/velox/getting-started#aws-s3-support"
-  },"27": {
+  },"91": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Celeborn support",
     "content": "Gluten with velox backend supports Celeborn as remote shuffle service. Below introduction is used to enable this feature . First refer to this URL(https://github.com/apache/incubator-celeborn) to setup a celeborn cluster. When compiling the Gluten Java module, it’s required to enable rss profile, as follows: . mvn clean package -Pbackends-velox -Pspark-3.3 -Prss -DskipTests . Then add the Gluten and Spark Celeborn Client packages to your Spark application’s classpath(usua [...]
     "url": "/docs/velox/getting-started#celeborn-support",
     
     "relUrl": "/docs/velox/getting-started#celeborn-support"
-  },"28": {
+  },"92": {
     "doc": "Getting-Started with Velox Backend",
     "title": "DeltaLake Support",
     "content": "Gluten with velox backend supports DeltaLake table. How to use . First of all, compile gluten-delta module by a delta profile, as follows: . mvn clean package -Pbackends-velox -Pspark-3.3 -Pdelta -DskipTests . Then, put the additional gluten-delta jar to the class path (usually it’s $SPARK_HOME/jars). The gluten-delta jar is in gluten-delta/target directory. After the two steps, you can query delta table by gluten/velox without scan’s fallback. Gluten with velox backends  [...]
     "url": "/docs/velox/getting-started#deltalake-support",
     
     "relUrl": "/docs/velox/getting-started#deltalake-support"
-  },"29": {
+  },"93": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Iceberg Support",
     "content": "Gluten with velox backend supports Iceberg table. Currently, only reading COW (Copy-On-Write) tables is supported. How to use . First of all, compile gluten-iceberg module by a iceberg profile, as follows: . mvn clean package -Pbackends-velox -Pspark-3.3 -Piceberg -DskipTests . Then, put the additional gluten-iceberg jar to the class path (usually it’s $SPARK_HOME/jars). The gluten-iceberg jar is in gluten-iceberg/target directory. After the two steps, you can query icebe [...]
     "url": "/docs/velox/getting-started#iceberg-support",
     
     "relUrl": "/docs/velox/getting-started#iceberg-support"
-  },"30": {
+  },"94": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Coverage",
     "content": "Spark3.3 has 387 functions in total. ~240 are commonly used. Velox’s functions have two category, Presto and Spark. Presto has 124 functions implemented. Spark has 62 functions. Spark functions are verified to have the same result as Vanilla Spark. Some Presto functions have the same result as Vanilla Spark but some others have different. Gluten prefer to use Spark functions firstly. If it’s not in Spark’s list but implemented in Presto, we currently offload to Presto one [...]
     "url": "/docs/velox/getting-started#coverage",
     
     "relUrl": "/docs/velox/getting-started#coverage"
-  },"31": {
+  },"95": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Spill (Experimental)",
     "content": "Velox backend supports spilling-to-disk. Using the following configuration options to customize spilling: . | Name | Default Value | Description | . | spark.gluten.sql.columnar.backend.velox.spillStrategy | auto | none: Disable spill on Velox backend; auto: Let Spark memory manager manage Velox’s spilling | . | spark.gluten.sql.columnar.backend.velox.spillFileSystem | local | The filesystem used to store spill data. local: The local file system. heap-over-local: Write fil [...]
     "url": "/docs/velox/getting-started#spill-experimental",
     
     "relUrl": "/docs/velox/getting-started#spill-experimental"
-  },"32": {
+  },"96": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Velox User-Defined Functions (UDF)",
     "content": " ",
     "url": "/docs/velox/getting-started#velox-user-defined-functions-udf",
     
     "relUrl": "/docs/velox/getting-started#velox-user-defined-functions-udf"
-  },"33": {
+  },"97": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Introduction",
     "content": "Velox backend supports User-Defined Functions (UDF). Users can create their own functions using the UDF interface provided in Velox backend and build libraries for these functions. At runtime, the UDF are registered at the start of applications. Once registered, Gluten will be able to parse and offload these UDF into Velox during execution. ",
     "url": "/docs/velox/getting-started#introduction",
     
     "relUrl": "/docs/velox/getting-started#introduction"
-  },"34": {
+  },"98": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Creating a UDF library",
     "content": "The following steps demonstrate how to set up a UDF library project: . | Include the UDF Interface Header: First, include the UDF interface header file Udf.h in the project file. The header file defines the UdfEntry struct, along with the macros for declaring the necessary functions to integrate the UDF into Gluten and Velox. | Implement the UDF: Implement UDF. These functions should be able to register to Velox. | Implement the Interface Functions: Implement the followin [...]
     "url": "/docs/velox/getting-started#creating-a-udf-library",
     
     "relUrl": "/docs/velox/getting-started#creating-a-udf-library"
-  },"35": {
+  },"99": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Building the UDF library",
     "content": "To build the UDF library, users need to compile the C++ code and link to libvelox.so. It’s recommended to create a CMakeLists.txt for the project. Here’s an example: . project(myudf) set(CMAKE_CXX_STANDARD 17) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(GLUTEN_HOME /path/to/gluten) add_library(myudf SHARED \"MyUDF.cpp\") find_library(VELOX_LIBRARY REQUIRED NAMES velox HINTS ${GLUTEN_HOME}/cpp/build/releases NO_DEFAULT_PATH) target_include_directories(myudf PRIVATE ${GLUTEN_HO [...]
     "url": "/docs/velox/getting-started#building-the-udf-library",
     
     "relUrl": "/docs/velox/getting-started#building-the-udf-library"
-  },"36": {
+  },"100": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Using UDF in Gluten",
     "content": "Gluten loads the UDF libraries at runtime. You can upload UDF libraries via --files or --archives, and configure the libray paths using the provided Spark configuration, which accepts comma separated list of library paths. Note if running on Yarn client mode, the uploaded files are not reachable on driver side. Users should copy those files to somewhere reachable for driver and set spark.gluten.sql.columnar.backend.velox.driver.udfLibraryPaths. This configuration is also  [...]
     "url": "/docs/velox/getting-started#using-udf-in-gluten",
     
     "relUrl": "/docs/velox/getting-started#using-udf-in-gluten"
-  },"37": {
+  },"101": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Try the example",
     "content": "We provided an Velox UDF example file MyUDF.cpp. After building gluten cpp, you can find the example library at /path/to/gluten/cpp/build/velox/udf/examples/libmyudf.so . Start spark-shell or spark-sql with below configuration . --files /path/to/gluten/cpp/build/velox/udf/examples/libmyudf.so --conf spark.gluten.sql.columnar.backend.velox.udfLibraryPaths=libmyudf.so . Run query. The functions myudf1 and myudf2 increment the input value by a constant of 5 . select myudf1(1 [...]
     "url": "/docs/velox/getting-started#try-the-example",
     
     "relUrl": "/docs/velox/getting-started#try-the-example"
-  },"38": {
+  },"102": {
     "doc": "Getting-Started with Velox Backend",
     "title": "High-Bandwidth Memory (HBM) support",
     "content": "Gluten supports allocating memory on HBM. This feature is optional and is disabled by default. It is implemented on top of Memkind library. You can refer to memkind’s readme for more details. ",
     "url": "/docs/velox/getting-started#high-bandwidth-memory-hbm-support",
     
     "relUrl": "/docs/velox/getting-started#high-bandwidth-memory-hbm-support"
-  },"39": {
+  },"103": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Build Gluten with HBM",
     "content": "Gluten will internally build and link to a specific version of Memkind library and hwloc. Other dependencies should be installed on Driver and Worker node first: . sudo apt install -y autoconf automake g++ libnuma-dev libtool numactl unzip libdaxctl-dev . After the set-up, you can now build Gluten with HBM. Below command is used to enable this feature . cd /path/to/gluten ## The script builds two jars for spark 3.2.2 and 3.3.1./dev/buildbundle-veloxbe.sh --enable_hbm=ON . ",
     "url": "/docs/velox/getting-started#build-gluten-with-hbm",
     
     "relUrl": "/docs/velox/getting-started#build-gluten-with-hbm"
-  },"40": {
+  },"104": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Configure and enable HBM in Spark Application",
     "content": "At runtime, MEMKIND_HBW_NODES enviroment variable is detected for configuring HBM NUMA nodes. For the explaination to this variable, please refer to memkind’s manual page. This can be set for all executors through spark conf, e.g. --conf spark.executorEnv.MEMKIND_HBW_NODES=8-15. Note that memory allocation fallback is also supported and cannot be turned off. If HBM is unavailable or fills up, the allocator will use default(DDR) memory. ",
     "url": "/docs/velox/getting-started#configure-and-enable-hbm-in-spark-application",
     
     "relUrl": "/docs/velox/getting-started#configure-and-enable-hbm-in-spark-application"
-  },"41": {
+  },"105": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Intel® QuickAssist Technology (QAT) support",
     "content": "Gluten supports using Intel® QuickAssist Technology (QAT) for data compression during Spark Shuffle. It benefits from QAT Hardware-based acceleration on compression/decompression, and uses Gzip as compression format for higher compression ratio to reduce the pressure on disks and network transmission. This feature is based on QAT driver library and QATzip library. Please manually download QAT driver for your system, and follow its README to build and install on all Driver [...]
     "url": "/docs/velox/getting-started#intel-quickassist-technology-qat-support",
     
     "relUrl": "/docs/velox/getting-started#intel-quickassist-technology-qat-support"
-  },"42": {
+  },"106": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Software Requirements",
     "content": ". | Download QAT driver for your system, and follow its README to build and install on all Driver and Worker nodes: Intel® QuickAssist Technology Driver for Linux* – HW Version 2.0. | Below compression libraries need to be installed on all Driver and Worker nodes: . | Zlib* library of version 1.2.7 or higher | ZSTD* library of version 1.5.4 or higher | LZ4* library | . | . ",
     "url": "/docs/velox/getting-started#software-requirements",
     
     "relUrl": "/docs/velox/getting-started#software-requirements"
-  },"43": {
+  },"107": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Build Gluten with QAT",
     "content": ". | Setup ICP_ROOT environment variable to the directory where QAT driver is extracted. This environment variable is required during building Gluten and running Spark applications. It’s recommended to put it in .bashrc on Driver and Worker nodes. | . echo \"export ICP_ROOT=/path/to/QAT_driver\" &gt;&gt; ~/.bashrc source ~/.bashrc # Also set for root if running as non-root user sudo su - echo \"export ICP_ROOT=/path/to/QAT_driver\" &gt;&gt; ~/.bashrc exit . | This step is  [...]
     "url": "/docs/velox/getting-started#build-gluten-with-qat",
     
     "relUrl": "/docs/velox/getting-started#build-gluten-with-qat"
-  },"44": {
+  },"108": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Enable QAT with Gzip/Zstd for shuffle compression",
     "content": ". | To offload shuffle compression into QAT, first make sure you have the right QAT configuration file at /etc/4xxx_devX.conf. We provide a example configuration file. This configuration sets up to 4 processes that can bind to 1 QAT, and each process can use up to 16 QAT DC instances. | . ## run as root ## Overwrite QAT configuration file. cd /etc for i in {0..7}; do echo \"4xxx_dev$i.conf\"; done | xargs -i cp -f /path/to/gluten/docs/qat/4x16.conf {} ## Restart QAT after [...]
     "url": "/docs/velox/getting-started#enable-qat-with-gzipzstd-for-shuffle-compression",
     
     "relUrl": "/docs/velox/getting-started#enable-qat-with-gzipzstd-for-shuffle-compression"
-  },"45": {
+  },"109": {
     "doc": "Getting-Started with Velox Backend",
     "title": "QAT driver references",
     "content": "Documentation . README Text Files (README_QAT20.L.1.0.0-00021.txt) . Release Notes . Check out the Intel® QuickAssist Technology Software for Linux* - Release Notes for the latest changes in this release. Getting Started Guide . Check out the Intel® QuickAssist Technology Software for Linux* - Getting Started Guide for detailed installation instructions. Programmer’s Guide . Check out the Intel® QuickAssist Technology Software for Linux* - Programmer’s Guide for software  [...]
     "url": "/docs/velox/getting-started#qat-driver-references",
     
     "relUrl": "/docs/velox/getting-started#qat-driver-references"
-  },"46": {
+  },"110": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Intel® In-memory Analytics Accelerator (IAA/IAX) support",
     "content": "Similar to Intel® QAT, Gluten supports using Intel® In-memory Analytics Accelerator (IAA, also called IAX) for data compression during Spark Shuffle. It benefits from IAA Hardware-based acceleration on compression/decompression, and uses Gzip as compression format for higher compression ratio to reduce the pressure on disks and network transmission. This feature is based on Intel® QPL. ",
     "url": "/docs/velox/getting-started#intel-in-memory-analytics-accelerator-iaaiax-support",
     
     "relUrl": "/docs/velox/getting-started#intel-in-memory-analytics-accelerator-iaaiax-support"
-  },"47": {
+  },"111": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Build Gluten with IAA",
     "content": "Gluten will internally build and link to a specific version of QPL library, but extra environment setup is still required. Please refer to QPL Installation Guide to install dependencies and configure accelerators. This step is required if your application is running as Non-root user. Create a group for the users who have privilege to use IAA, and grant group iaa read/write access to the IAA Work-Queues. sudo groupadd iaa sudo usermod -aG iaa username # need to relogin sud [...]
     "url": "/docs/velox/getting-started#build-gluten-with-iaa",
     
     "relUrl": "/docs/velox/getting-started#build-gluten-with-iaa"
-  },"48": {
+  },"112": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Enable IAA with Gzip Compression for shuffle compression",
     "content": ". | To enable QAT at run-time, first make sure you have configured the IAA Work-Queues correctly, and the file permissions of /dev/iax/wqX.0 are correct. | . sudo ls -l /dev/iax . The output should be like: . total 0 crw-rw---- 1 root iaa 509, 0 Apr 5 18:54 wq1.0 crw-rw---- 1 root iaa 509, 5 Apr 5 18:54 wq11.0 crw-rw---- 1 root iaa 509, 6 Apr 5 18:54 wq13.0 crw-rw---- 1 root iaa 509, 7 Apr 5 18:54 wq15.0 crw-rw---- 1 root iaa 509, 1 Apr 5 18:54 wq3.0 crw-rw---- 1 root iaa [...]
     "url": "/docs/velox/getting-started#enable-iaa-with-gzip-compression-for-shuffle-compression",
     
     "relUrl": "/docs/velox/getting-started#enable-iaa-with-gzip-compression-for-shuffle-compression"
-  },"49": {
+  },"113": {
     "doc": "Getting-Started with Velox Backend",
     "title": "IAA references",
     "content": "Intel® IAA Enabling Guide . Check out the Intel® In-Memory Analytics Accelerator (Intel® IAA) Enabling Guide . Intel® QPL Documentation . Check out the Intel® Query Processing Library (Intel® QPL) Documentation . ",
     "url": "/docs/velox/getting-started#iaa-references",
     
     "relUrl": "/docs/velox/getting-started#iaa-references"
-  },"50": {
+  },"114": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Test TPC-H or TPC-DS on Gluten with Velox backend",
     "content": "All TPC-H and TPC-DS queries are supported in Gluten Velox backend. ",
     "url": "/docs/velox/getting-started#test-tpc-h-or-tpc-ds-on-gluten-with-velox-backend",
     
     "relUrl": "/docs/velox/getting-started#test-tpc-h-or-tpc-ds-on-gluten-with-velox-backend"
-  },"51": {
+  },"115": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Data preparation",
     "content": "The data generation scripts are TPC-H dategen script and TPC-DS dategen script. The used TPC-H and TPC-DS queries are the original ones, and can be accessed from TPC-DS queries and TPC-H queries. Some other versions of TPC-DS queries are also provided, but are not recommended for testing, including: . | the modified TPC-DS queries with “Decimal-to-Double”: TPC-DS non-decimal queries (outdated). | . ",
     "url": "/docs/velox/getting-started#data-preparation",
     
     "relUrl": "/docs/velox/getting-started#data-preparation"
-  },"52": {
+  },"116": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Submit the Spark SQL job",
     "content": "Submit test script from spark-shell. You can find the scala code to Run TPC-H as an example. Please remember to modify the location of TPC-H files as well as TPC-H queries before you run the testing. var parquet_file_path = \"/PATH/TO/TPCH_PARQUET_PATH\" var gluten_root = \"/PATH/TO/GLUTEN\" . Below script shows an example about how to run the testing, you should modify the parameters such as executor cores, memory, offHeap size based on your environment. export GLUTEN_JA [...]
     "url": "/docs/velox/getting-started#submit-the-spark-sql-job",
     
     "relUrl": "/docs/velox/getting-started#submit-the-spark-sql-job"
-  },"53": {
+  },"117": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Result",
     "content": "wholestagetransformer indicates that the offload works. ",
     "url": "/docs/velox/getting-started#result",
     
     "relUrl": "/docs/velox/getting-started#result"
-  },"54": {
+  },"118": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Performance",
     "content": "Below table shows the TPC-H Q1 and Q6 Performance in a multiple-thread test (–num-executors 6 –executor-cores 6) for Velox and vanilla Spark. Both Parquet and ORC datasets are sf1024. | Query Performance (s) | Velox (ORC) | Vanilla Spark (Parquet) | Vanilla Spark (ORC) | . | TPC-H Q6 | 13.6 | 21.6 | 34.9 | . | TPC-H Q1 | 26.1 | 76.7 | 84.9 | . ",
     "url": "/docs/velox/getting-started#performance",
     
     "relUrl": "/docs/velox/getting-started#performance"
-  },"55": {
+  },"119": {
     "doc": "Getting-Started with Velox Backend",
     "title": "External reference setup",
     "content": "TO ease your first-hand experience of using Gluten, we have set up an external reference cluster. If you are interested, please contact Weiting.Chen@intel.com. ",
     "url": "/docs/velox/getting-started#external-reference-setup",
     
     "relUrl": "/docs/velox/getting-started#external-reference-setup"
-  },"56": {
+  },"120": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Gluten UI",
     "content": " ",
     "url": "/docs/velox/getting-started#gluten-ui",
     
     "relUrl": "/docs/velox/getting-started#gluten-ui"
-  },"57": {
+  },"121": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Gluten event",
     "content": "Gluten provides two events GlutenBuildInfoEvent and GlutenPlanFallbackEvent: . | GlutenBuildInfoEvent, it contains the Gluten build information so that we are able to be aware of the environment when doing some debug. It includes Java Version, Scala Version, GCC Version, Gluten Version, Spark Version, Hadoop Version, Gluten Revision, Backend, Backend Revision, etc. | GlutenPlanFallbackEvent, it contains the fallback information for each query execution. Note, if the query [...]
     "url": "/docs/velox/getting-started#gluten-event",
     
     "relUrl": "/docs/velox/getting-started#gluten-event"
-  },"58": {
+  },"122": {
     "doc": "Getting-Started with Velox Backend",
     "title": "SQL tab",
     "content": "Gluten provides a tab based on Spark UI, named Gluten SQL / DataFrame . This tab contains two parts: . | The Gluten build information. | SQL/Dataframe queries fallback information. | . If you want to disable Gluten UI, add a config when submitting --conf spark.gluten.ui.enabled=false. ",
     "url": "/docs/velox/getting-started#sql-tab",
     
     "relUrl": "/docs/velox/getting-started#sql-tab"
-  },"59": {
+  },"123": {
     "doc": "Getting-Started with Velox Backend",
     "title": "History server",
     "content": "Gluten UI also supports Spark history server. Add gluten-ui jar into the history server classpath, e.g., $SPARK_HOME/jars, then restart history server. ",
     "url": "/docs/velox/getting-started#history-server",
     
     "relUrl": "/docs/velox/getting-started#history-server"
-  },"60": {
+  },"124": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Native plan string",
     "content": "Gluten supports inject native plan string into Spark explain with formatted mode by setting --conf spark.gluten.sql.injectNativePlanStringToExplain=true. Here is an example, how Gluten show the native plan string. (9) WholeStageCodegenTransformer (2) Input [6]: [c1#0L, c2#1L, c3#2L, c1#3L, c2#4L, c3#5L] Arguments: false Native Plan: -- Project[expressions: (n3_6:BIGINT, \"n0_0\"), (n3_7:BIGINT, \"n0_1\"), (n3_8:BIGINT, \"n0_2\"), (n3_9:BIGINT, \"n1_0\"), (n3_10:BIGINT, \" [...]
     "url": "/docs/velox/getting-started#native-plan-string",
     
     "relUrl": "/docs/velox/getting-started#native-plan-string"
-  },"61": {
+  },"125": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Native plan with stats",
     "content": "Gluten supports print native plan with stats to executor system output stream by setting --conf spark.gluten.sql.debug=true. Note that, the plan string with stats is task level which may cause executor log size big. Here is an example, how Gluten show the native plan string with stats. I20231121 10:19:42.348845 90094332 WholeStageResultIterator.cc:220] Native Plan with stats for: [Stage: 1 TID: 16] -- Project[expressions: (n3_6:BIGINT, \"n0_0\"), (n3_7:BIGINT, \"n0_1\"),  [...]
     "url": "/docs/velox/getting-started#native-plan-with-stats",
     
     "relUrl": "/docs/velox/getting-started#native-plan-with-stats"
-  },"62": {
+  },"126": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Gluten Implicits",
     "content": "Gluten provides a helper class to get the fallback summary from a Spark Dataset. import org.apache.spark.sql.execution.GlutenImplicits._ val df = spark.sql(\"SELECT * FROM t\") df.fallbackSummary . Note that, if AQE is enabled, but the query is not materialized, then it will re-plan the query execution with disabled AQE. It is a workaround to get the final plan, and it may cause the inconsistent results with a materialized query. However, we have no choice. ",
     "url": "/docs/velox/getting-started#gluten-implicits",
     
     "relUrl": "/docs/velox/getting-started#gluten-implicits"
-  },"63": {
+  },"127": {
     "doc": "Getting-Started with Velox Backend",
     "title": "Getting-Started with Velox Backend",
     "content": " ",
     "url": "/docs/velox/getting-started",
     
     "relUrl": "/docs/velox/getting-started"
-  },"64": {
+  },"128": {
     "doc": "How To Use Gluten",
     "title": "How to understand the key work of Gluten?",
     "content": "The Gluten worked as the role of bridge, it’s a middle layer between the Spark and the native execution library. The Gluten is responsibility for validating whether the operators of the Spark plan can be executed by the native engine or not. If yes, the Gluten transforms Spark plan to Substrait plan, and then send the Substrait plan to the native engine. The Gluten codes consist of two parts: the C++ codes and the Java/Scala codes. | All C++ codes are placed under the dir [...]
     "url": "/developers/HowTo.html#how-to-understand-the-key-work-of-gluten",
     
     "relUrl": "/developers/HowTo.html#how-to-understand-the-key-work-of-gluten"
-  },"65": {
+  },"129": {
     "doc": "How To Use Gluten",
     "title": "How to debug in Gluten?",
     "content": " ",
     "url": "/developers/HowTo.html#how-to-debug-in-gluten",
     
     "relUrl": "/developers/HowTo.html#how-to-debug-in-gluten"
-  },"66": {
+  },"130": {
     "doc": "How To Use Gluten",
     "title": "1 How to debug C++",
     "content": "If you don’t concern about the Scala/Java codes and just want to debug the C++ codes executed in native engine, you may debug the C++ via benchmarks with GDB. To debug C++, you have to generate the example files, the example files consist of: . | A file contained Substrait plan in JSON format | One or more input data files in Parquet format | . You can generate the example files by the following steps: . | build Velox and Gluten CPP gluten_home/dev/builddeps-veloxbe.sh -- [...]
     "url": "/developers/HowTo.html#1-how-to-debug-c",
     
     "relUrl": "/developers/HowTo.html#1-how-to-debug-c"
-  },"67": {
+  },"131": {
     "doc": "How To Use Gluten",
     "title": "2 How to debug plan validation process",
     "content": "Gluten will validate generated plan before execute it, and validation usually happens in native side, so we provide a utility to help debug validation process in native side. | Run query with conf spark.gluten.sql.debug=true, and you will find generated plan be printed in stderr with json format, save it as plan.json for example. | Compile cpp part with --build_benchmarks=ON, then check plan_validator_util executable file in gluten_home/cpp/build/velox/benchmarks/. | Run  [...]
     "url": "/developers/HowTo.html#2-how-to-debug-plan-validation-process",
     
     "relUrl": "/developers/HowTo.html#2-how-to-debug-plan-validation-process"
-  },"68": {
+  },"132": {
     "doc": "How To Use Gluten",
     "title": "3 How to debug Java/Scala",
     "content": "wait to add . ",
     "url": "/developers/HowTo.html#3-how-to-debug-javascala",
     
     "relUrl": "/developers/HowTo.html#3-how-to-debug-javascala"
-  },"69": {
+  },"133": {
     "doc": "How To Use Gluten",
     "title": "4 How to debug with core-dump",
     "content": "wait to complete . cd the_directory_of_core_file_generated gdb gluten_home/cpp/build/releases/libgluten.so 'core-Executor task l-2000883-1671542526' . | the core-Executor task l-2000883-1671542526 represents the core file name. | . ",
     "url": "/developers/HowTo.html#4-how-to-debug-with-core-dump",
     
     "relUrl": "/developers/HowTo.html#4-how-to-debug-with-core-dump"
-  },"70": {
+  },"134": {
     "doc": "How To Use Gluten",
     "title": "How to run TPC-H on Velox backend",
     "content": "Now, both Parquet and DWRF format files are supported, related scripts and files are under the directory of gluten_home/backends-velox/workload/tpch. The file README.md under gluten_home/backends-velox/workload/tpch offers some useful help but it’s still not enough and exact. One way of run TPC-H test is to run velox-be by workflow, you can refer to velox_be.yml . Here will explain how to run TPC-H on Velox backend with the Parquet file format. | First step, prepare the d [...]
     "url": "/developers/HowTo.html#how-to-run-tpc-h-on-velox-backend",
     
     "relUrl": "/developers/HowTo.html#how-to-run-tpc-h-on-velox-backend"
-  },"71": {
+  },"135": {
     "doc": "How To Use Gluten",
     "title": "How to run TPC-DS",
     "content": "wait to add . ",
     "url": "/developers/HowTo.html#how-to-run-tpc-ds",
     
     "relUrl": "/developers/HowTo.html#how-to-run-tpc-ds"
-  },"72": {
+  },"136": {
     "doc": "How To Use Gluten",
     "title": "How to track the memory exhaust problem",
     "content": "When your gluten spark jobs failed because of OOM, you can track the memory allocation’s call stack by configuring spark.gluten.backtrace.allocation = true. The above configuration will use BacktraceAllocationListener wrapping from SparkAllocationListener to create VeloxMemoryManager. BacktraceAllocationListener will check every allocation, if a single allocation bytes exceeds a fixed value or the accumulative allocation bytes exceeds 1/2/3…G, the call stack of memory all [...]
     "url": "/developers/HowTo.html#how-to-track-the-memory-exhaust-problem",
     
     "relUrl": "/developers/HowTo.html#how-to-track-the-memory-exhaust-problem"
-  },"73": {
+  },"137": {
     "doc": "How To Use Gluten",
     "title": "How To Use Gluten",
     "content": "There are some common questions about developing, debugging and testing been asked again and again. In order to help the developers to contribute to Gluten as soon as possible, we collected these frequently asked questions, and organized them in the form of Q&amp;A. It’s convenient for the developers to check and learn. when you encountered a new problem and then resolved it, please add a new item to this document if you think it may be helpful to the other developers. We [...]
     "url": "/developers/HowTo.html",
     
     "relUrl": "/developers/HowTo.html"
-  },"74": {
+  },"138": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "How to understand the key work of Gluten?",
+    "content": "The Gluten worked as the role of bridge, it’s a middle layer between the Spark and the native execution library. The Gluten is responsibility for validating whether the operators of the Spark plan can be executed by the native engine or not. If yes, the Gluten transforms Spark plan to Substrait plan, and then send the Substrait plan to the native engine. The Gluten codes consist of two parts: the C++ codes and the Java/Scala codes. | All C++ codes are placed under the dir [...]
+    "url": "/archives/v1.1.1/developers/howto/#how-to-understand-the-key-work-of-gluten",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#how-to-understand-the-key-work-of-gluten"
+  },"139": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "How to debug in Gluten?",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/howto/#how-to-debug-in-gluten",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#how-to-debug-in-gluten"
+  },"140": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "1 How to debug C++",
+    "content": "If you don’t concern about the Scala/Java codes and just want to debug the C++ codes executed in native engine, you may debug the C++ via benchmarks with GDB. To debug C++, you have to generate the example files, the example files consist of: . | A file contained Substrait plan in JSON format | One or more input data files in Parquet format | . You can generate the example files by the following steps: . | build Velox and Gluten CPP gluten_home/dev/builddeps-veloxbe.sh -- [...]
+    "url": "/archives/v1.1.1/developers/howto/#1-how-to-debug-c",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#1-how-to-debug-c"
+  },"141": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "2 How to debug plan validation process",
+    "content": "Gluten will validate generated plan before execute it, and validation usually happens in native side, so we provide a utility to help debug validation process in native side. | Run query with conf spark.gluten.sql.debug=true, and you will find generated plan be printed in stderr with json format, save it as plan.json for example. | Compile cpp part with --build_benchmarks=ON, then check plan_validator_util executable file in gluten_home/cpp/build/velox/benchmarks/. | Run  [...]
+    "url": "/archives/v1.1.1/developers/howto/#2-how-to-debug-plan-validation-process",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#2-how-to-debug-plan-validation-process"
+  },"142": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "3 How to debug Java/Scala",
+    "content": "wait to add . ",
+    "url": "/archives/v1.1.1/developers/howto/#3-how-to-debug-javascala",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#3-how-to-debug-javascala"
+  },"143": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "4 How to debug with core-dump",
+    "content": "wait to complete . cd the_directory_of_core_file_generated gdb gluten_home/cpp/build/releases/libgluten.so 'core-Executor task l-2000883-1671542526' . | the core-Executor task l-2000883-1671542526 represents the core file name. | . ",
+    "url": "/archives/v1.1.1/developers/howto/#4-how-to-debug-with-core-dump",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#4-how-to-debug-with-core-dump"
+  },"144": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "How to run TPC-H on Velox backend",
+    "content": "Now, both Parquet and DWRF format files are supported, related scripts and files are under the directory of gluten_home/backends-velox/workload/tpch. The file README.md under gluten_home/backends-velox/workload/tpch offers some useful help but it’s still not enough and exact. One way of run TPC-H test is to run velox-be by workflow, you can refer to velox_be.yml . Here will explain how to run TPC-H on Velox backend with the Parquet file format. | First step, prepare the d [...]
+    "url": "/archives/v1.1.1/developers/howto/#how-to-run-tpc-h-on-velox-backend",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#how-to-run-tpc-h-on-velox-backend"
+  },"145": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "How to run TPC-DS",
+    "content": "wait to add . ",
+    "url": "/archives/v1.1.1/developers/howto/#how-to-run-tpc-ds",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#how-to-run-tpc-ds"
+  },"146": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "How to track the memory exhaust problem",
+    "content": "When your gluten spark jobs failed because of OOM, you can track the memory allocation’s call stack by configuring spark.gluten.backtrace.allocation = true. The above configuration will use BacktraceAllocationListener wrapping from SparkAllocationListener to create VeloxMemoryManager. BacktraceAllocationListener will check every allocation, if a single allocation bytes exceeds a fixed value or the accumulative allocation bytes exceeds 1/2/3…G, the call stack of memory all [...]
+    "url": "/archives/v1.1.1/developers/howto/#how-to-track-the-memory-exhaust-problem",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/#how-to-track-the-memory-exhaust-problem"
+  },"147": {
+    "doc": "v1.1.1/How To Use Gluten",
+    "title": "v1.1.1/How To Use Gluten",
+    "content": "There are some common questions about developing, debugging and testing been asked again and again. In order to help the developers to contribute to Gluten as soon as possible, we collected these frequently asked questions, and organized them in the form of Q&amp;A. It’s convenient for the developers to check and learn. when you encountered a new problem and then resolved it, please add a new item to this document if you think it may be helpful to the other developers. We [...]
+    "url": "/archives/v1.1.1/developers/howto/",
+    
+    "relUrl": "/archives/v1.1.1/developers/howto/"
+  },"148": {
     "doc": "How To Release",
     "title": "How to Release",
     "content": "This section outlines the steps for releasing Apache Gluten (incubating) according to the Apache release guidelines. All projects under the Apache umbrella must adhere to the Apache Release Policy. This guide is designed to assist you in comprehending the policy and navigating the process of releasing projects at Apache. ",
     "url": "/developers/HowToRelease.html#how-to-release",
     
     "relUrl": "/developers/HowToRelease.html#how-to-release"
-  },"75": {
+  },"149": {
     "doc": "How To Release",
     "title": "Release Process",
     "content": ". | Prepare the release artifacts. | Upload the release artifacts to the SVN repository. | Verify the release artifacts. | Initiate a release vote. | Announce the results and the release. | . Prepare the release artifacts. | Create a branch from the target git repository. | Tag a RC and draft the release notes. | Build and Sign the release artifacts (including source archives, binaries, …etc). | Generate checksums for the artifacts. | . How to Sign the release artifacts.  [...]
     "url": "/developers/HowToRelease.html#release-process",
     
     "relUrl": "/developers/HowToRelease.html#release-process"
-  },"76": {
+  },"150": {
     "doc": "How To Release",
     "title": "How To Release",
     "content": " ",
     "url": "/developers/HowToRelease.html",
     
     "relUrl": "/developers/HowToRelease.html"
-  },"77": {
+  },"151": {
+    "doc": "v1.1.1/How To Release",
+    "title": "How to Release",
+    "content": "This section outlines the steps for releasing Apache Gluten (incubating) according to the Apache release guidelines. All projects under the Apache umbrella must adhere to the Apache Release Policy. This guide is designed to assist you in comprehending the policy and navigating the process of releasing projects at Apache. ",
+    "url": "/archives/v1.1.1/developers/howtorelease/#how-to-release",
+    
+    "relUrl": "/archives/v1.1.1/developers/howtorelease/#how-to-release"
+  },"152": {
+    "doc": "v1.1.1/How To Release",
+    "title": "Release Process",
+    "content": ". | Prepare the release artifacts. | Upload the release artifacts to the SVN repository. | Verify the release artifacts. | Initiate a release vote. | Announce the results and the release. | . Prepare the release artifacts. | Create a branch from the target git repository. | Tag a RC and draft the release notes. | Build and Sign the release artifacts (including source archives, binaries, …etc). | Generate checksums for the artifacts. | . How to Sign the release artifacts.  [...]
+    "url": "/archives/v1.1.1/developers/howtorelease/#release-process",
+    
+    "relUrl": "/archives/v1.1.1/developers/howtorelease/#release-process"
+  },"153": {
+    "doc": "v1.1.1/How To Release",
+    "title": "v1.1.1/How To Release",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/howtorelease/",
+    
+    "relUrl": "/archives/v1.1.1/developers/howtorelease/"
+  },"154": {
     "doc": "Micro Benchmarks for Velox Backend",
     "title": "Generate Micro Benchmarks for Velox Backend",
     "content": "This document explains how to use the existing micro benchmark template in Gluten Cpp. A micro benchmark for Velox backend is provided in Gluten Cpp to simulate the execution of a first or middle stage in Spark. It serves as a more convenient alternative to debug in Gluten Cpp comparing with directly debugging in a Spark job. Developers can use it to create their own workloads, debug in native process, profile the hotspot and do optimizations. To simulate a first stage, y [...]
     "url": "/developers/MicroBenchmarks.html#generate-micro-benchmarks-for-velox-backend",
     
     "relUrl": "/developers/MicroBenchmarks.html#generate-micro-benchmarks-for-velox-backend"
-  },"78": {
+  },"155": {
     "doc": "Micro Benchmarks for Velox Backend",
     "title": "Try the example",
     "content": "To run a micro benchmark, user should provide one file that contains the Substrait plan in JSON format, and optional one or more input data files in parquet format. The commands below help to generate example input files: . cd /path/to/gluten/ ./dev/buildbundle-veloxbe.sh --build_tests=ON --build_benchmarks=ON # Run test to generate input data files. If you are using spark 3.3, replace -Pspark-3.2 with -Pspark-3.3 mvn test -Pspark-3.2 -Pbackends-velox -Prss -pl backends-v [...]
     "url": "/developers/MicroBenchmarks.html#try-the-example",
     
     "relUrl": "/developers/MicroBenchmarks.html#try-the-example"
-  },"79": {
+  },"156": {
     "doc": "Micro Benchmarks for Velox Backend",
     "title": "Generate Substrait plan and input for any query",
     "content": "First, build Gluten with --build_benchmarks=ON. cd /path/to/gluten/ ./dev/buildbundle-veloxbe.sh --build_benchmarks=ON # For debugging purpose, rebuild Gluten with build type `Debug`./dev/buildbundle-veloxbe.sh --build_benchmarks=ON --build_type=Debug . First, get the Stage Id from spark UI for the stage you want to simulate. And then re-run the query with below configurations to dump the inputs to micro benchmark. | Parameters | Description | Recommend Setting | . | spar [...]
     "url": "/developers/MicroBenchmarks.html#generate-substrait-plan-and-input-for-any-query",
     
     "relUrl": "/developers/MicroBenchmarks.html#generate-substrait-plan-and-input-for-any-query"
-  },"80": {
+  },"157": {
     "doc": "Micro Benchmarks for Velox Backend",
     "title": "Save ouput to parquet to analyze",
     "content": "You can save the output to a parquet file to analyze. cd /path/to/gluten/cpp/build/velox/benchmarks ./generic_benchmark \\ --plan /absolute_path/to/plan.json \\ --data /absolute_path/to/data.parquet --threads 1 --noprint-result --write-file=/absolute_path/to/result.parquet . ",
     "url": "/developers/MicroBenchmarks.html#save-ouput-to-parquet-to-analyze",
     
     "relUrl": "/developers/MicroBenchmarks.html#save-ouput-to-parquet-to-analyze"
-  },"81": {
+  },"158": {
     "doc": "Micro Benchmarks for Velox Backend",
     "title": "Add shuffle write process",
     "content": "You can add the shuffle write process at the end of this stage. Note that this will ignore the --write-file option. cd /path/to/gluten/cpp/build/velox/benchmarks ./generic_benchmark \\ --plan /absolute_path/to/plan.json \\ --split /absolute_path/to/split.json \\ --threads 1 --noprint-result --with-shuffle . By default, the compression codec for shuffle outputs is LZ4. You can switch to other codecs by adding one of the following argument flags to the command: . | –zstd: Z [...]
     "url": "/developers/MicroBenchmarks.html#add-shuffle-write-process",
     
     "relUrl": "/developers/MicroBenchmarks.html#add-shuffle-write-process"
-  },"82": {
+  },"159": {
     "doc": "Micro Benchmarks for Velox Backend",
     "title": "Simulate Spark with multiple processes and threads",
     "content": "You can use below command to launch several processes and threads to simulate parallel execution on Spark. Each thread in the same process will be pinned to the core number starting from --cpu. Suppose running on a baremetal machine with 48C, 2-socket, HT-on, launching below command will utilize all vcores. processes=24 # Same value of spark.executor.instances threads=8 # Same value of spark.executor.cores for ((i=0; i&lt;${processes}; i++)); do ./generic_benchmark --plan [...]
     "url": "/developers/MicroBenchmarks.html#simulate-spark-with-multiple-processes-and-threads",
     
     "relUrl": "/developers/MicroBenchmarks.html#simulate-spark-with-multiple-processes-and-threads"
-  },"83": {
+  },"160": {
     "doc": "Micro Benchmarks for Velox Backend",
     "title": "Micro Benchmarks for Velox Backend",
     "content": " ",
     "url": "/developers/MicroBenchmarks.html",
     
     "relUrl": "/developers/MicroBenchmarks.html"
-  },"84": {
+  },"161": {
+    "doc": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "title": "Generate Micro Benchmarks for Velox Backend",
+    "content": "This document explains how to use the existing micro benchmark template in Gluten Cpp. A micro benchmark for Velox backend is provided in Gluten Cpp to simulate the execution of a first or middle stage in Spark. It serves as a more convenient alternative to debug in Gluten Cpp comparing with directly debugging in a Spark job. Developers can use it to create their own workloads, debug in native process, profile the hotspot and do optimizations. To simulate a first stage, y [...]
+    "url": "/archives/v1.1.1/developers/microbenchmark/#generate-micro-benchmarks-for-velox-backend",
+    
+    "relUrl": "/archives/v1.1.1/developers/microbenchmark/#generate-micro-benchmarks-for-velox-backend"
+  },"162": {
+    "doc": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "title": "Try the example",
+    "content": "To run a micro benchmark, user should provide one file that contains the Substrait plan in JSON format, and optional one or more input data files in parquet format. The commands below help to generate example input files: . cd /path/to/gluten/ ./dev/buildbundle-veloxbe.sh --build_tests=ON --build_benchmarks=ON # Run test to generate input data files. If you are using spark 3.3, replace -Pspark-3.2 with -Pspark-3.3 mvn test -Pspark-3.2 -Pbackends-velox -Prss -pl backends-v [...]
+    "url": "/archives/v1.1.1/developers/microbenchmark/#try-the-example",
+    
+    "relUrl": "/archives/v1.1.1/developers/microbenchmark/#try-the-example"
+  },"163": {
+    "doc": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "title": "Generate Substrait plan and input for any query",
+    "content": "First, build Gluten with --build_benchmarks=ON. cd /path/to/gluten/ ./dev/buildbundle-veloxbe.sh --build_benchmarks=ON # For debugging purpose, rebuild Gluten with build type `Debug`./dev/buildbundle-veloxbe.sh --build_benchmarks=ON --build_type=Debug . First, get the Stage Id from spark UI for the stage you want to simulate. And then re-run the query with below configurations to dump the inputs to micro benchmark. | Parameters | Description | Recommend Setting | . | spar [...]
+    "url": "/archives/v1.1.1/developers/microbenchmark/#generate-substrait-plan-and-input-for-any-query",
+    
+    "relUrl": "/archives/v1.1.1/developers/microbenchmark/#generate-substrait-plan-and-input-for-any-query"
+  },"164": {
+    "doc": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "title": "Save ouput to parquet to analyze",
+    "content": "You can save the output to a parquet file to analyze. cd /path/to/gluten/cpp/build/velox/benchmarks ./generic_benchmark \\ --plan /absolute_path/to/plan.json \\ --data /absolute_path/to/data.parquet --threads 1 --noprint-result --write-file=/absolute_path/to/result.parquet . ",
+    "url": "/archives/v1.1.1/developers/microbenchmark/#save-ouput-to-parquet-to-analyze",
+    
+    "relUrl": "/archives/v1.1.1/developers/microbenchmark/#save-ouput-to-parquet-to-analyze"
+  },"165": {
+    "doc": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "title": "Add shuffle write process",
+    "content": "You can add the shuffle write process at the end of this stage. Note that this will ignore the --write-file option. cd /path/to/gluten/cpp/build/velox/benchmarks ./generic_benchmark \\ --plan /absolute_path/to/plan.json \\ --split /absolute_path/to/split.json \\ --threads 1 --noprint-result --with-shuffle . By default, the compression codec for shuffle outputs is LZ4. You can switch to other codecs by adding one of the following argument flags to the command: . | –zstd: Z [...]
+    "url": "/archives/v1.1.1/developers/microbenchmark/#add-shuffle-write-process",
+    
+    "relUrl": "/archives/v1.1.1/developers/microbenchmark/#add-shuffle-write-process"
+  },"166": {
+    "doc": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "title": "Simulate Spark with multiple processes and threads",
+    "content": "You can use below command to launch several processes and threads to simulate parallel execution on Spark. Each thread in the same process will be pinned to the core number starting from --cpu. Suppose running on a baremetal machine with 48C, 2-socket, HT-on, launching below command will utilize all vcores. processes=24 # Same value of spark.executor.instances threads=8 # Same value of spark.executor.cores for ((i=0; i&lt;${processes}; i++)); do ./generic_benchmark --plan [...]
+    "url": "/archives/v1.1.1/developers/microbenchmark/#simulate-spark-with-multiple-processes-and-threads",
+    
+    "relUrl": "/archives/v1.1.1/developers/microbenchmark/#simulate-spark-with-multiple-processes-and-threads"
+  },"167": {
+    "doc": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "title": "v1.1.1/Micro Benchmarks for Velox Backend",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/microbenchmark/",
+    
+    "relUrl": "/archives/v1.1.1/developers/microbenchmark/"
+  },"168": {
     "doc": "New To Gluten",
     "title": "Environment",
     "content": "Now gluten supports Ubuntu20.04, Ubuntu22.04, centos8, centos7 and macOS. ",
     "url": "/developers/NewToGluten.html#environment",
     
     "relUrl": "/developers/NewToGluten.html#environment"
-  },"85": {
+  },"169": {
     "doc": "New To Gluten",
     "title": "Openjdk8",
     "content": "Environment setting . For root user, the environment variables file is /etc/profile, it will make effect for all the users. For other user, you can set in ~/.bashrc. Guide for ubuntu . The default JDK version in ubuntu is java11, we need to set to java8. apt install openjdk-8-jdk update-alternatives --config java java -version . --config java to config java executable path, javac and other commands can also use this command to config. For some other uses, we suggest to se [...]
     "url": "/developers/NewToGluten.html#openjdk8",
     
     "relUrl": "/developers/NewToGluten.html#openjdk8"
-  },"86": {
+  },"170": {
     "doc": "New To Gluten",
     "title": "Maven 3.6.3 or above",
     "content": "Maven Dowload Page And then set the environment setting. ",
     "url": "/developers/NewToGluten.html#maven-363-or-above",
     
     "relUrl": "/developers/NewToGluten.html#maven-363-or-above"
-  },"87": {
+  },"171": {
     "doc": "New To Gluten",
     "title": "GCC 9.4 or above",
     "content": " ",
     "url": "/developers/NewToGluten.html#gcc-94-or-above",
     
     "relUrl": "/developers/NewToGluten.html#gcc-94-or-above"
-  },"88": {
+  },"172": {
     "doc": "New To Gluten",
     "title": "Compile gluten using debug mode",
     "content": "If you want to just debug java/scala code, there is no need to compile cpp code with debug mode. You can just refer to build-gluten-with-velox-backend. If you need to debug cpp code, please compile the backend code and gluten cpp code with debug mode. ## compile velox backend with benchmark and tests to debug gluten_home/dev/builddeps-veloxbe.sh --build_tests=ON --build_benchmarks=ON --build_type=Debug . If you need to debug the tests in /gluten-ut, You need to compile ja [...]
     "url": "/developers/NewToGluten.html#compile-gluten-using-debug-mode",
     
     "relUrl": "/developers/NewToGluten.html#compile-gluten-using-debug-mode"
-  },"89": {
+  },"173": {
     "doc": "New To Gluten",
     "title": "Java/scala code development with Intellij",
     "content": " ",
     "url": "/developers/NewToGluten.html#javascala-code-development-with-intellij",
     
     "relUrl": "/developers/NewToGluten.html#javascala-code-development-with-intellij"
-  },"90": {
+  },"174": {
     "doc": "New To Gluten",
     "title": "Linux intellij local debug",
     "content": "Install the linux intellij version, and debug code locally. | Ask your linux maintainer to install the desktop, and then restart the server. | If you use Moba-XTerm to connect linux server, you don’t need to install x11 server, If not (e.g. putty), please follow this guide: X11 Forwarding: Setup Instructions for Linux and Mac . | Download intellij linux community version to linux server | Start Idea, bash &lt;idea_dir&gt;/idea.sh | . Notes: Sometimes, your desktop may sto [...]
     "url": "/developers/NewToGluten.html#linux-intellij-local-debug",
     
     "relUrl": "/developers/NewToGluten.html#linux-intellij-local-debug"
-  },"91": {
+  },"175": {
     "doc": "New To Gluten",
     "title": "Windows/Mac intellij remote debug",
     "content": "If you have Ultimate intellij, you can try to debug remotely. ",
     "url": "/developers/NewToGluten.html#windowsmac-intellij-remote-debug",
     
     "relUrl": "/developers/NewToGluten.html#windowsmac-intellij-remote-debug"
-  },"92": {
+  },"176": {
     "doc": "New To Gluten",
     "title": "Set up gluten project",
     "content": ". | Make sure you have compiled gluten. | Load the gluten by File-&gt;Open, select &lt;gluten_home/pom.xml&gt;. | Activate your profiles such as , and Reload Maven Project, you will find all your need modules have been activated. | Create breakpoint and debug as you wish, maybe you can try CTRL+N to find TestOperator to start your test. | . ",
     "url": "/developers/NewToGluten.html#set-up-gluten-project",
     
     "relUrl": "/developers/NewToGluten.html#set-up-gluten-project"
-  },"93": {
+  },"177": {
     "doc": "New To Gluten",
     "title": "Java/Scala code style",
     "content": "Intellij IDE supports importing settings for Java/Scala code style. You can import intellij-codestyle.xml to your IDE. See Intellij guide. To generate a fix for Java/Scala code style, you can run one or more of the below commands according to the code modules involved in your PR. For Velox backend: . mvn spotless:apply -Pbackends-velox -Prss -Pspark-3.2 -Pspark-ut -DskipTests mvn spotless:apply -Pbackends-velox -Prss -Pspark-3.3 -Pspark-ut -DskipTests . For Clickhouse bac [...]
     "url": "/developers/NewToGluten.html#javascala-code-style",
     
     "relUrl": "/developers/NewToGluten.html#javascala-code-style"
-  },"94": {
+  },"178": {
     "doc": "New To Gluten",
     "title": "CPP code development with Visual Studio Code",
     "content": "This guide is for remote debug. We will connect the remote linux server by SSH. Download the windows vscode software The important leftside bar is: . | Explorer (Project structure) | Search | Run and Debug | Extensions (Install C/C++ Extension Pack, Remote Development, GitLens at least, C++ Test Mate is also suggested) | Remote Explorer (Connect linux server by ssh command, click +, then input ssh user@10.1.7.003) | Manage (Settings) | . Input your password in the above p [...]
     "url": "/developers/NewToGluten.html#cpp-code-development-with-visual-studio-code",
     
     "relUrl": "/developers/NewToGluten.html#cpp-code-development-with-visual-studio-code"
-  },"95": {
+  },"179": {
     "doc": "New To Gluten",
     "title": "Usage",
     "content": "Set up project . File-&gt;Open Folder // select gluten folder Select cpp/CmakeList.txt as command prompt Select gcc version as command prompt . Settings . VSCode support 2 ways to set user setting. | Manage-&gt;Command Palette(Open settings.json, search by Preferences: Open Settings (JSON)) | Manage-&gt;Settings (Common setting) | . Build by vscode . VSCode will try to compile the debug version in /build. And we need to compile velox debug mode before, if you have compile [...]
     "url": "/developers/NewToGluten.html#usage",
     
     "relUrl": "/developers/NewToGluten.html#usage"
-  },"96": {
+  },"180": {
     "doc": "New To Gluten",
     "title": "Usefule notes",
     "content": "Upgrade vscode . No need to upgrade vscode version, if upgraded, will download linux server again, switch update mode to off Search update in Manage-&gt;Settings to turn off update mode . Colour setting . \"workbench.colorTheme\": \"Quiet Light\", \"files.autoSave\": \"afterDelay\", \"workbench.colorCustomizations\": { \"editor.wordHighlightBackground\": \"#063ef7\", // \"editor.selectionBackground\": \"#d1d1c6\", // \"tab.activeBackground\": \"#b8b9988c\", \"editor.selec [...]
     "url": "/developers/NewToGluten.html#usefule-notes",
     
     "relUrl": "/developers/NewToGluten.html#usefule-notes"
-  },"97": {
+  },"181": {
     "doc": "New To Gluten",
     "title": "Debug cpp code with coredump",
     "content": "mkdir -p /mnt/DP_disk1/core sysctl -w kernel.core_pattern=/mnt/DP_disk1/core/core-%e-%p-%t cat /proc/sys/kernel/core_pattern # set the core file to unlimited size echo \"ulimit -c unlimited\" &gt;&gt; ~/.bashrc # then you will get the core file at `/mnt/DP_disk1/core` when the program crashes # gdb -c corefile # gdb &lt;gluten_home&gt;/cpp/build/releases/libgluten.so 'core-Executor task l-2000883-1671542526' . ‘core-Executor task l-2000883-1671542526’ is the generated cor [...]
     "url": "/developers/NewToGluten.html#debug-cpp-code-with-coredump",
     
     "relUrl": "/developers/NewToGluten.html#debug-cpp-code-with-coredump"
-  },"98": {
+  },"182": {
     "doc": "New To Gluten",
     "title": "Debug cpp with gdb",
     "content": "You can use gdb to debug tests and benchmarks. And also you can debug jni call. Place the following code to your debug path. pid_t pid = getpid(); printf(\"----------------------------------pid: %lun\", pid); sleep(10); . You can also get the pid by java command or grep java program when executing unit test. jps 1375551 ScalaTestRunner ps ux | grep TestOperator . Execute gdb command to debug: . gdb attach &lt;pid&gt; . gdb attach 1375551 wait to attach.... (gdb) b &lt;vel [...]
     "url": "/developers/NewToGluten.html#debug-cpp-with-gdb",
     
     "relUrl": "/developers/NewToGluten.html#debug-cpp-with-gdb"
-  },"99": {
+  },"183": {
     "doc": "New To Gluten",
     "title": "Run TPC-H and TPC-DS",
     "content": "We supply &lt;gluten_home&gt;/tools/gluten-it to execute these queries Refer to velox_be.yml . ",
     "url": "/developers/NewToGluten.html#run-tpc-h-and-tpc-ds",
     
     "relUrl": "/developers/NewToGluten.html#run-tpc-h-and-tpc-ds"
-  },"100": {
+  },"184": {
     "doc": "New To Gluten",
     "title": "Run gluten+velox on clean machine",
     "content": "We can run gluten + velox on clean machine by one command (supported OS: Ubuntu20.04/22.04, Centos 7/8, etc.). spark-shell --name run_gluten \\ --master yarn --deploy-mode client \\ --conf spark.plugins=io.glutenproject.GlutenPlugin \\ --conf spark.memory.offHeap.enabled=true \\ --conf spark.memory.offHeap.size=20g \\ --jars https://github.com/oap-project/gluten/releases/download/v1.0.0/gluten-velox-bundle-spark3.2_2.12-ubuntu_20.04_x86_64-1.0.0.jar \\ --conf spark.shuffl [...]
     "url": "/developers/NewToGluten.html#run-glutenvelox-on-clean-machine",
     
     "relUrl": "/developers/NewToGluten.html#run-glutenvelox-on-clean-machine"
-  },"101": {
+  },"185": {
     "doc": "New To Gluten",
     "title": "New To Gluten",
     "content": "Help users to debug and test with gluten. For intel internal developer, you could refer to internal wiki New Employee Guide to get more information such as proxy settings, Gluten has cpp code and java/scala code, we can use some useful IDE to read and debug. ",
     "url": "/developers/NewToGluten.html",
     
     "relUrl": "/developers/NewToGluten.html"
-  },"102": {
+  },"186": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Environment",
+    "content": "Now gluten supports Ubuntu20.04, Ubuntu22.04, centos8, centos7 and macOS. ",
+    "url": "/archives/v1.1.1/developers/newto/#environment",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#environment"
+  },"187": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Openjdk8",
+    "content": "Environment setting . For root user, the environment variables file is /etc/profile, it will make effect for all the users. For other user, you can set in ~/.bashrc. Guide for ubuntu . The default JDK version in ubuntu is java11, we need to set to java8. apt install openjdk-8-jdk update-alternatives --config java java -version . --config java to config java executable path, javac and other commands can also use this command to config. For some other uses, we suggest to se [...]
+    "url": "/archives/v1.1.1/developers/newto/#openjdk8",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#openjdk8"
+  },"188": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Maven 3.6.3 or above",
+    "content": "Maven Dowload Page And then set the environment setting. ",
+    "url": "/archives/v1.1.1/developers/newto/#maven-363-or-above",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#maven-363-or-above"
+  },"189": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "GCC 9.4 or above",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/newto/#gcc-94-or-above",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#gcc-94-or-above"
+  },"190": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Compile gluten using debug mode",
+    "content": "If you want to just debug java/scala code, there is no need to compile cpp code with debug mode. You can just refer to build-gluten-with-velox-backend. If you need to debug cpp code, please compile the backend code and gluten cpp code with debug mode. ## compile velox backend with benchmark and tests to debug gluten_home/dev/builddeps-veloxbe.sh --build_tests=ON --build_benchmarks=ON --build_type=Debug . If you need to debug the tests in /gluten-ut, You need to compile ja [...]
+    "url": "/archives/v1.1.1/developers/newto/#compile-gluten-using-debug-mode",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#compile-gluten-using-debug-mode"
+  },"191": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Java/scala code development with Intellij",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/newto/#javascala-code-development-with-intellij",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#javascala-code-development-with-intellij"
+  },"192": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Linux intellij local debug",
+    "content": "Install the linux intellij version, and debug code locally. | Ask your linux maintainer to install the desktop, and then restart the server. | If you use Moba-XTerm to connect linux server, you don’t need to install x11 server, If not (e.g. putty), please follow this guide: X11 Forwarding: Setup Instructions for Linux and Mac . | Download intellij linux community version to linux server | Start Idea, bash &lt;idea_dir&gt;/idea.sh | . Notes: Sometimes, your desktop may sto [...]
+    "url": "/archives/v1.1.1/developers/newto/#linux-intellij-local-debug",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#linux-intellij-local-debug"
+  },"193": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Windows/Mac intellij remote debug",
+    "content": "If you have Ultimate intellij, you can try to debug remotely. ",
+    "url": "/archives/v1.1.1/developers/newto/#windowsmac-intellij-remote-debug",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#windowsmac-intellij-remote-debug"
+  },"194": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Set up gluten project",
+    "content": ". | Make sure you have compiled gluten. | Load the gluten by File-&gt;Open, select &lt;gluten_home/pom.xml&gt;. | Activate your profiles such as , and Reload Maven Project, you will find all your need modules have been activated. | Create breakpoint and debug as you wish, maybe you can try CTRL+N to find TestOperator to start your test. | . ",
+    "url": "/archives/v1.1.1/developers/newto/#set-up-gluten-project",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#set-up-gluten-project"
+  },"195": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Java/Scala code style",
+    "content": "Intellij IDE supports importing settings for Java/Scala code style. You can import intellij-codestyle.xml to your IDE. See Intellij guide. To generate a fix for Java/Scala code style, you can run one or more of the below commands according to the code modules involved in your PR. For Velox backend: . mvn spotless:apply -Pbackends-velox -Prss -Pspark-3.2 -Pspark-ut -DskipTests mvn spotless:apply -Pbackends-velox -Prss -Pspark-3.3 -Pspark-ut -DskipTests . For Clickhouse bac [...]
+    "url": "/archives/v1.1.1/developers/newto/#javascala-code-style",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#javascala-code-style"
+  },"196": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "CPP code development with Visual Studio Code",
+    "content": "This guide is for remote debug. We will connect the remote linux server by SSH. Download the windows vscode software The important leftside bar is: . | Explorer (Project structure) | Search | Run and Debug | Extensions (Install C/C++ Extension Pack, Remote Development, GitLens at least, C++ Test Mate is also suggested) | Remote Explorer (Connect linux server by ssh command, click +, then input ssh user@10.1.7.003) | Manage (Settings) | . Input your password in the above p [...]
+    "url": "/archives/v1.1.1/developers/newto/#cpp-code-development-with-visual-studio-code",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#cpp-code-development-with-visual-studio-code"
+  },"197": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Usage",
+    "content": "Set up project . File-&gt;Open Folder // select gluten folder Select cpp/CmakeList.txt as command prompt Select gcc version as command prompt . Settings . VSCode support 2 ways to set user setting. | Manage-&gt;Command Palette(Open settings.json, search by Preferences: Open Settings (JSON)) | Manage-&gt;Settings (Common setting) | . Build by vscode . VSCode will try to compile the debug version in /build. And we need to compile velox debug mode before, if you have compile [...]
+    "url": "/archives/v1.1.1/developers/newto/#usage",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#usage"
+  },"198": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Usefule notes",
+    "content": "Upgrade vscode . No need to upgrade vscode version, if upgraded, will download linux server again, switch update mode to off Search update in Manage-&gt;Settings to turn off update mode . Colour setting . \"workbench.colorTheme\": \"Quiet Light\", \"files.autoSave\": \"afterDelay\", \"workbench.colorCustomizations\": { \"editor.wordHighlightBackground\": \"#063ef7\", // \"editor.selectionBackground\": \"#d1d1c6\", // \"tab.activeBackground\": \"#b8b9988c\", \"editor.selec [...]
+    "url": "/archives/v1.1.1/developers/newto/#usefule-notes",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#usefule-notes"
+  },"199": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Debug cpp code with coredump",
+    "content": "mkdir -p /mnt/DP_disk1/core sysctl -w kernel.core_pattern=/mnt/DP_disk1/core/core-%e-%p-%t cat /proc/sys/kernel/core_pattern # set the core file to unlimited size echo \"ulimit -c unlimited\" &gt;&gt; ~/.bashrc # then you will get the core file at `/mnt/DP_disk1/core` when the program crashes # gdb -c corefile # gdb &lt;gluten_home&gt;/cpp/build/releases/libgluten.so 'core-Executor task l-2000883-1671542526' . ‘core-Executor task l-2000883-1671542526’ is the generated cor [...]
+    "url": "/archives/v1.1.1/developers/newto/#debug-cpp-code-with-coredump",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#debug-cpp-code-with-coredump"
+  },"200": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Debug cpp with gdb",
+    "content": "You can use gdb to debug tests and benchmarks. And also you can debug jni call. Place the following code to your debug path. pid_t pid = getpid(); printf(\"----------------------------------pid: %lun\", pid); sleep(10); . You can also get the pid by java command or grep java program when executing unit test. jps 1375551 ScalaTestRunner ps ux | grep TestOperator . Execute gdb command to debug: . gdb attach &lt;pid&gt; . gdb attach 1375551 wait to attach.... (gdb) b &lt;vel [...]
+    "url": "/archives/v1.1.1/developers/newto/#debug-cpp-with-gdb",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#debug-cpp-with-gdb"
+  },"201": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Run TPC-H and TPC-DS",
+    "content": "We supply &lt;gluten_home&gt;/tools/gluten-it to execute these queries Refer to velox_be.yml . ",
+    "url": "/archives/v1.1.1/developers/newto/#run-tpc-h-and-tpc-ds",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#run-tpc-h-and-tpc-ds"
+  },"202": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "Run gluten+velox on clean machine",
+    "content": "We can run gluten + velox on clean machine by one command (supported OS: Ubuntu20.04/22.04, Centos 7/8, etc.). spark-shell --name run_gluten \\ --master yarn --deploy-mode client \\ --conf spark.plugins=io.glutenproject.GlutenPlugin \\ --conf spark.memory.offHeap.enabled=true \\ --conf spark.memory.offHeap.size=20g \\ --jars https://github.com/oap-project/gluten/releases/download/v1.0.0/gluten-velox-bundle-spark3.2_2.12-ubuntu_20.04_x86_64-1.0.0.jar \\ --conf spark.shuffl [...]
+    "url": "/archives/v1.1.1/developers/newto/#run-glutenvelox-on-clean-machine",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/#run-glutenvelox-on-clean-machine"
+  },"203": {
+    "doc": "v1.1.1/New To Gluten",
+    "title": "v1.1.1/New To Gluten",
+    "content": "Help users to debug and test with gluten. For intel internal developer, you could refer to internal wiki New Employee Guide to get more information such as proxy settings, Gluten has cpp code and java/scala code, we can use some useful IDE to read and debug. ",
+    "url": "/archives/v1.1.1/developers/newto/",
+    
+    "relUrl": "/archives/v1.1.1/developers/newto/"
+  },"204": {
     "doc": "Substrait Modifications",
     "title": "Substrait Modifications in Gluten",
     "content": "Substrait is a project aiming to create a well-defined, cross-language specification for data compute operations. Since it is still under active development, there are some lacking representations for Gluten needed computing operations. At the same time, some existing representations need to be modified a bit to satisfy the needs of computing. In Gluten, the base version of Substrait is v0.23.0. This page records all the Gluten changes to Substrait proto files for referen [...]
     "url": "/developers/SubstraitModifications.html#substrait-modifications-in-gluten",
     
     "relUrl": "/developers/SubstraitModifications.html#substrait-modifications-in-gluten"
-  },"103": {
+  },"205": {
     "doc": "Substrait Modifications",
     "title": "Modifications to algebra.proto",
     "content": ". | Added JsonReadOptions and TextReadOptions in FileOrFiles(#1584). | Changed join type JOIN_TYPE_SEMI to JOIN_TYPE_LEFT_SEMI and JOIN_TYPE_RIGHT_SEMI(#408). | Added WindowRel, added column_name and window_type in WindowFunction, changed Unbounded in WindowFunction into Unbounded_Preceding and Unbounded_Following, and added WindowType(#485). | Added output_schema in RelRoot(#1901). | Added ExpandRel(#1361). | Added GenerateRel(#574). | Added PartitionColumn in LocalFiles [...]
     "url": "/developers/SubstraitModifications.html#modifications-to-algebraproto",
     
     "relUrl": "/developers/SubstraitModifications.html#modifications-to-algebraproto"
-  },"104": {
+  },"206": {
     "doc": "Substrait Modifications",
     "title": "Modifications to type.proto",
     "content": ". | Added Nothing in Type(#791). | Added names in Struct(#1878). | Added PartitionColumns in NamedStruct(#320). | Remove PartitionColumns and add column_types in NamedStruct(#2405). | . ",
     "url": "/developers/SubstraitModifications.html#modifications-to-typeproto",
     
     "relUrl": "/developers/SubstraitModifications.html#modifications-to-typeproto"
-  },"105": {
+  },"207": {
     "doc": "Substrait Modifications",
     "title": "Substrait Modifications",
     "content": " ",
     "url": "/developers/SubstraitModifications.html",
     
     "relUrl": "/developers/SubstraitModifications.html"
-  },"106": {
+  },"208": {
+    "doc": "v1.1.1/Substrait Modifications",
+    "title": "Substrait Modifications in Gluten",
+    "content": "Substrait is a project aiming to create a well-defined, cross-language specification for data compute operations. Since it is still under active development, there are some lacking representations for Gluten needed computing operations. At the same time, some existing representations need to be modified a bit to satisfy the needs of computing. In Gluten, the base version of Substrait is v0.23.0. This page records all the Gluten changes to Substrait proto files for referen [...]
+    "url": "/archives/v1.1.1/developers/substrait/#substrait-modifications-in-gluten",
+    
+    "relUrl": "/archives/v1.1.1/developers/substrait/#substrait-modifications-in-gluten"
+  },"209": {
+    "doc": "v1.1.1/Substrait Modifications",
+    "title": "Modifications to algebra.proto",
+    "content": ". | Added JsonReadOptions and TextReadOptions in FileOrFiles(#1584). | Changed join type JOIN_TYPE_SEMI to JOIN_TYPE_LEFT_SEMI and JOIN_TYPE_RIGHT_SEMI(#408). | Added WindowRel, added column_name and window_type in WindowFunction, changed Unbounded in WindowFunction into Unbounded_Preceding and Unbounded_Following, and added WindowType(#485). | Added output_schema in RelRoot(#1901). | Added ExpandRel(#1361). | Added GenerateRel(#574). | Added PartitionColumn in LocalFiles [...]
+    "url": "/archives/v1.1.1/developers/substrait/#modifications-to-algebraproto",
+    
+    "relUrl": "/archives/v1.1.1/developers/substrait/#modifications-to-algebraproto"
+  },"210": {
+    "doc": "v1.1.1/Substrait Modifications",
+    "title": "Modifications to type.proto",
+    "content": ". | Added Nothing in Type(#791). | Added names in Struct(#1878). | Added PartitionColumns in NamedStruct(#320). | Remove PartitionColumns and add column_types in NamedStruct(#2405). | . ",
+    "url": "/archives/v1.1.1/developers/substrait/#modifications-to-typeproto",
+    
+    "relUrl": "/archives/v1.1.1/developers/substrait/#modifications-to-typeproto"
+  },"211": {
+    "doc": "v1.1.1/Substrait Modifications",
+    "title": "v1.1.1/Substrait Modifications",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/substrait/",
+    
+    "relUrl": "/archives/v1.1.1/developers/substrait/"
+  },"212": {
+    "doc": "v1.1.1/Velox Backend",
+    "title": "Gluten Velox Backend Documents",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/#gluten-velox-backend-documents",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/#gluten-velox-backend-documents"
+  },"213": {
+    "doc": "v1.1.1/Velox Backend",
+    "title": "v1.1.1/Velox Backend",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/"
+  },"214": {
     "doc": "Velox Backend",
     "title": "Gluten Velox Backend Documents",
     "content": " ",
     "url": "/docs/velox/#gluten-velox-backend-documents",
     
     "relUrl": "/docs/velox/#gluten-velox-backend-documents"
-  },"107": {
+  },"215": {
     "doc": "Velox Backend",
     "title": "Velox Backend",
     "content": " ",
     "url": "/docs/velox/",
     
     "relUrl": "/docs/velox/"
-  },"108": {
+  },"216": {
+    "doc": "v1.1.1/Build Parameters for Velox Backend",
+    "title": "Build Parameters",
+    "content": "Native build parameters for buildbundle-veloxbe.sh or builddeps-veloxbe.sh . Please set them via --, e.g. --build_type=Release. | Parameters | Description | Default | . | build_type | Build type for Velox &amp; gluten cpp, CMAKE_BUILD_TYPE. | Release | . | build_tests | Build gluten cpp tests. | OFF | . | build_examples | Build udf example. | OFF | . | build_benchmarks | Build gluten cpp benchmarks. | OFF | . | build_jemalloc | Build with jemalloc. | ON | . | build_protob [...]
+    "url": "/archives/v1.1.1/docs/velox/build_parameters/#build-parameters",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/build_parameters/#build-parameters"
+  },"217": {
+    "doc": "v1.1.1/Build Parameters for Velox Backend",
+    "title": "Gluten Jar for Deployment",
+    "content": "The gluten jar built out is under GLUTEN_SRC/package/target/. It’s name pattern is gluten-&lt;backend_type&gt;-bundle-spark&lt;spark.bundle.version&gt;_&lt;scala.binary.version&gt;-&lt;os.detected.release&gt;_&lt;os.detected.release.version&gt;-&lt;project.version&gt;.jar. | Spark Version | spark.bundle.version | scala.binary.version | . | 3.2.2 | 3.2 | 2.12 | . | 3.3.1 | 3.3 | 2.12 | . | 3.4.2 | 3.4 | 2.12 | . ",
+    "url": "/archives/v1.1.1/docs/velox/build_parameters/#gluten-jar-for-deployment",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/build_parameters/#gluten-jar-for-deployment"
+  },"218": {
+    "doc": "v1.1.1/Build Parameters for Velox Backend",
+    "title": "v1.1.1/Build Parameters for Velox Backend",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/build_parameters/",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/build_parameters/"
+  },"219": {
     "doc": "Build Parameters for Velox Backend",
     "title": "Build Parameters",
     "content": "Native build parameters for buildbundle-veloxbe.sh or builddeps-veloxbe.sh . Please set them via --, e.g. --build_type=Release. | Parameters | Description | Default | . | build_type | Build type for Velox &amp; gluten cpp, CMAKE_BUILD_TYPE. | Release | . | build_tests | Build gluten cpp tests. | OFF | . | build_examples | Build udf example. | OFF | . | build_benchmarks | Build gluten cpp benchmarks. | OFF | . | build_jemalloc | Build with jemalloc. | ON | . | build_protob [...]
     "url": "/docs/velox/build_parameters#build-parameters",
     
     "relUrl": "/docs/velox/build_parameters#build-parameters"
-  },"109": {
+  },"220": {
     "doc": "Build Parameters for Velox Backend",
     "title": "Gluten Jar for Deployment",
     "content": "The gluten jar built out is under GLUTEN_SRC/package/target/. It’s name pattern is gluten-&lt;backend_type&gt;-bundle-spark&lt;spark.bundle.version&gt;_&lt;scala.binary.version&gt;-&lt;os.detected.release&gt;_&lt;os.detected.release.version&gt;-&lt;project.version&gt;.jar. | Spark Version | spark.bundle.version | scala.binary.version | . | 3.2.2 | 3.2 | 2.12 | . | 3.3.1 | 3.3 | 2.12 | . | 3.4.2 | 3.4 | 2.12 | . ",
     "url": "/docs/velox/build_parameters#gluten-jar-for-deployment",
     
     "relUrl": "/docs/velox/build_parameters#gluten-jar-for-deployment"
-  },"110": {
+  },"221": {
     "doc": "Build Parameters for Velox Backend",
     "title": "Build Parameters for Velox Backend",
     "content": " ",
     "url": "/docs/velox/build_parameters",
     
     "relUrl": "/docs/velox/build_parameters"
-  },"111": {
+  },"222": {
+    "doc": "v1.1.1/Using GCS with Gluten",
+    "title": "Working with GCS",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/gcs/#working-with-gcs",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/gcs/#working-with-gcs"
+  },"223": {
+    "doc": "v1.1.1/Using GCS with Gluten",
+    "title": "Installing the gcloud CLI",
+    "content": "To access GCS Objects using Gluten and Velox, first you have to [download an install the gcloud CLI] (https://cloud.google.com/sdk/docs/install). ",
+    "url": "/archives/v1.1.1/docs/velox/gcs/#installing-the-gcloud-cli",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/gcs/#installing-the-gcloud-cli"
+  },"224": {
+    "doc": "v1.1.1/Using GCS with Gluten",
+    "title": "Configuring GCS using a user account",
+    "content": "This is recommended for regular users, follow the instructions to authorize a user account. After these steps, no specific configuration is required for Gluten, since the authorization was handled entirely by the gcloud tool. ",
+    "url": "/archives/v1.1.1/docs/velox/gcs/#configuring-gcs-using-a-user-account",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/gcs/#configuring-gcs-using-a-user-account"
+  },"225": {
+    "doc": "v1.1.1/Using GCS with Gluten",
+    "title": "Configuring GCS using a credential file",
+    "content": "For workloads that need to be fully automated, manually authorizing can be problematic. For such cases it is better to use a json file with the credentials. This is described in the [instructions to configure a service account]https://cloud.google.com/sdk/docs/authorizing#service-account. Such json file with the credetials can be passed to Gluten: . spark.hadoop.fs.gs.auth.type SERVICE_ACCOUNT_JSON_KEYFILE spark.hadoop.fs.gs.auth.service.account.json.keyfile // path to th [...]
+    "url": "/archives/v1.1.1/docs/velox/gcs/#configuring-gcs-using-a-credential-file",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/gcs/#configuring-gcs-using-a-credential-file"
+  },"226": {
+    "doc": "v1.1.1/Using GCS with Gluten",
+    "title": "Configuring GCS endpoints",
+    "content": "For cases when a GCS mock is used, an optional endpoint can be provided: . spark.hadoop.fs.gs.storage.root.url // url to the mock gcs service including starting with http or https . ",
+    "url": "/archives/v1.1.1/docs/velox/gcs/#configuring-gcs-endpoints",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/gcs/#configuring-gcs-endpoints"
+  },"227": {
+    "doc": "v1.1.1/Using GCS with Gluten",
+    "title": "v1.1.1/Using GCS with Gluten",
+    "content": "Object stores offered by CSPs such as GCS are important for users of Gluten to store their data. This doc will discuss all details of configs, and use cases around using Gluten with object stores. In order to use a GCS endpoint as your data source, please ensure you are using the following GCS configs in your spark-defaults.conf. If you’re experiencing any issues authenticating to GCS with additional auth mechanisms, please reach out to us using the ‘Issues’ tab. ",
+    "url": "/archives/v1.1.1/docs/velox/gcs/",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/gcs/"
+  },"228": {
     "doc": "Using GCS with Gluten",
     "title": "Working with GCS",
     "content": " ",
     "url": "/docs/velox/gcs#working-with-gcs",
     
     "relUrl": "/docs/velox/gcs#working-with-gcs"
-  },"112": {
+  },"229": {
     "doc": "Using GCS with Gluten",
     "title": "Installing the gcloud CLI",
     "content": "To access GCS Objects using Gluten and Velox, first you have to [download an install the gcloud CLI] (https://cloud.google.com/sdk/docs/install). ",
     "url": "/docs/velox/gcs#installing-the-gcloud-cli",
     
     "relUrl": "/docs/velox/gcs#installing-the-gcloud-cli"
-  },"113": {
+  },"230": {
     "doc": "Using GCS with Gluten",
     "title": "Configuring GCS using a user account",
     "content": "This is recommended for regular users, follow the instructions to authorize a user account. After these steps, no specific configuration is required for Gluten, since the authorization was handled entirely by the gcloud tool. ",
     "url": "/docs/velox/gcs#configuring-gcs-using-a-user-account",
     
     "relUrl": "/docs/velox/gcs#configuring-gcs-using-a-user-account"
-  },"114": {
+  },"231": {
     "doc": "Using GCS with Gluten",
     "title": "Configuring GCS using a credential file",
     "content": "For workloads that need to be fully automated, manually authorizing can be problematic. For such cases it is better to use a json file with the credentials. This is described in the [instructions to configure a service account]https://cloud.google.com/sdk/docs/authorizing#service-account. Such json file with the credetials can be passed to Gluten: . spark.hadoop.fs.gs.auth.type SERVICE_ACCOUNT_JSON_KEYFILE spark.hadoop.fs.gs.auth.service.account.json.keyfile // path to th [...]
     "url": "/docs/velox/gcs#configuring-gcs-using-a-credential-file",
     
     "relUrl": "/docs/velox/gcs#configuring-gcs-using-a-credential-file"
-  },"115": {
+  },"232": {
     "doc": "Using GCS with Gluten",
     "title": "Configuring GCS endpoints",
     "content": "For cases when a GCS mock is used, an optional endpoint can be provided: . spark.hadoop.fs.gs.storage.root.url // url to the mock gcs service including starting with http or https . ",
     "url": "/docs/velox/gcs#configuring-gcs-endpoints",
     
     "relUrl": "/docs/velox/gcs#configuring-gcs-endpoints"
-  },"116": {
+  },"233": {
     "doc": "Using GCS with Gluten",
     "title": "Using GCS with Gluten",
     "content": "Object stores offered by CSPs such as GCS are important for users of Gluten to store their data. This doc will discuss all details of configs, and use cases around using Gluten with object stores. In order to use a GCS endpoint as your data source, please ensure you are using the following GCS configs in your spark-defaults.conf. If you’re experiencing any issues authenticating to GCS with additional auth mechanisms, please reach out to us using the ‘Issues’ tab. ",
     "url": "/docs/velox/gcs",
     
     "relUrl": "/docs/velox/gcs"
-  },"117": {
+  },"234": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "Working with S3",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/velox/s3/#working-with-s3",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/#working-with-s3"
+  },"235": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "Configuring S3 endpoint",
+    "content": "S3 provides the endpoint based method to access the files, here’s the example configuration. Users may need to modify some values based on real setup. spark.hadoop.fs.s3a.impl org.apache.hadoop.fs.s3a.S3AFileSystem spark.hadoop.fs.s3a.aws.credentials.provider org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider spark.hadoop.fs.s3a.access.key XXXXXXXXX spark.hadoop.fs.s3a.secret.key XXXXXXXXX spark.hadoop.fs.s3a.endpoint https://s3.us-west-1.amazonaws.com spark.hadoop.fs. [...]
+    "url": "/archives/v1.1.1/docs/velox/s3/#configuring-s3-endpoint",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/#configuring-s3-endpoint"
+  },"236": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "Configuring S3 instance credentials",
+    "content": "S3 also provides other methods for accessing, you can also use instance credentials by setting the following config . spark.hadoop.fs.s3a.use.instance.credentials true . Note that in this case, “spark.hadoop.fs.s3a.endpoint” won’t take affect as Gluten will use the endpoint set during instance creation. ",
+    "url": "/archives/v1.1.1/docs/velox/s3/#configuring-s3-instance-credentials",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/#configuring-s3-instance-credentials"
+  },"237": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "Configuring S3 IAM roles",
+    "content": "You can also use iam role credentials by setting the following configurations. Instance credentials have higher priority than iam credentials. spark.hadoop.fs.s3a.iam.role xxxx spark.hadoop.fs.s3a.iam.role.session.name xxxx . Note that spark.hadoop.fs.s3a.iam.role.session.name is optional. ",
+    "url": "/archives/v1.1.1/docs/velox/s3/#configuring-s3-iam-roles",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/#configuring-s3-iam-roles"
+  },"238": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "Other authentatication methods are not supported yet",
+    "content": ". | AWS temporary credential | . ",
+    "url": "/archives/v1.1.1/docs/velox/s3/#other-authentatication-methods-are-not-supported-yet",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/#other-authentatication-methods-are-not-supported-yet"
+  },"239": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "Log granularity of AWS C++ SDK in velox",
+    "content": "You can change log granularity of AWS C++ SDK by setting the spark.gluten.velox.awsSdkLogLevel configuration. The Allowed values are: . | OFF | FATAL | ERROR | WARN | INFO | DEBUG | TRACE | . ",
+    "url": "/archives/v1.1.1/docs/velox/s3/#log-granularity-of-aws-c-sdk-in-velox",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/#log-granularity-of-aws-c-sdk-in-velox"
+  },"240": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "Local Caching support",
+    "content": "Velox supports a local cache when reading data from HDFS/S3. The feature is very useful if remote storage is slow, e.g., reading from a public S3 bucket and stronger performance is desired. With this feature, Velox can asynchronously cache the data on local disk when reading from remote storage, and the future reading requests on already cached blocks will be serviced from local cache files. To enable the local caching feature, below configurations are required: . spark.g [...]
+    "url": "/archives/v1.1.1/docs/velox/s3/#local-caching-support",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/#local-caching-support"
+  },"241": {
+    "doc": "v1.1.1/Using S3 with Gluten",
+    "title": "v1.1.1/Using S3 with Gluten",
+    "content": "Object stores offered by CSPs such as AWS S3 are important for users of Gluten to store their data. This doc will discuss all details of configs, and use cases around using Gluten with object stores. In order to use an S3 endpoint as your data source, please ensure you are using the following S3 configs in your spark-defaults.conf. If you’re experiencing any issues authenticating to S3 with additional auth mechanisms, please reach out to us using the ‘Issues’ tab. ",
+    "url": "/archives/v1.1.1/docs/velox/s3/",
+    
+    "relUrl": "/archives/v1.1.1/docs/velox/s3/"
+  },"242": {
     "doc": "Using S3 with Gluten",
     "title": "Working with S3",
     "content": " ",
     "url": "/docs/velox/s3#working-with-s3",
     
     "relUrl": "/docs/velox/s3#working-with-s3"
-  },"118": {
+  },"243": {
     "doc": "Using S3 with Gluten",
     "title": "Configuring S3 endpoint",
     "content": "S3 provides the endpoint based method to access the files, here’s the example configuration. Users may need to modify some values based on real setup. spark.hadoop.fs.s3a.impl org.apache.hadoop.fs.s3a.S3AFileSystem spark.hadoop.fs.s3a.aws.credentials.provider org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider spark.hadoop.fs.s3a.access.key XXXXXXXXX spark.hadoop.fs.s3a.secret.key XXXXXXXXX spark.hadoop.fs.s3a.endpoint https://s3.us-west-1.amazonaws.com spark.hadoop.fs. [...]
     "url": "/docs/velox/s3#configuring-s3-endpoint",
     
     "relUrl": "/docs/velox/s3#configuring-s3-endpoint"
-  },"119": {
+  },"244": {
     "doc": "Using S3 with Gluten",
     "title": "Configuring S3 instance credentials",
     "content": "S3 also provides other methods for accessing, you can also use instance credentials by setting the following config . spark.hadoop.fs.s3a.use.instance.credentials true . Note that in this case, “spark.hadoop.fs.s3a.endpoint” won’t take affect as Gluten will use the endpoint set during instance creation. ",
     "url": "/docs/velox/s3#configuring-s3-instance-credentials",
     
     "relUrl": "/docs/velox/s3#configuring-s3-instance-credentials"
-  },"120": {
+  },"245": {
     "doc": "Using S3 with Gluten",
     "title": "Configuring S3 IAM roles",
     "content": "You can also use iam role credentials by setting the following configurations. Instance credentials have higher priority than iam credentials. spark.hadoop.fs.s3a.iam.role xxxx spark.hadoop.fs.s3a.iam.role.session.name xxxx . Note that spark.hadoop.fs.s3a.iam.role.session.name is optional. ",
     "url": "/docs/velox/s3#configuring-s3-iam-roles",
     
     "relUrl": "/docs/velox/s3#configuring-s3-iam-roles"
-  },"121": {
+  },"246": {
     "doc": "Using S3 with Gluten",
     "title": "Other authentatication methods are not supported yet",
     "content": ". | AWS temporary credential | . ",
     "url": "/docs/velox/s3#other-authentatication-methods-are-not-supported-yet",
     
     "relUrl": "/docs/velox/s3#other-authentatication-methods-are-not-supported-yet"
-  },"122": {
+  },"247": {
     "doc": "Using S3 with Gluten",
     "title": "Log granularity of AWS C++ SDK in velox",
     "content": "You can change log granularity of AWS C++ SDK by setting the spark.gluten.velox.awsSdkLogLevel configuration. The Allowed values are: . | OFF | FATAL | ERROR | WARN | INFO | DEBUG | TRACE | . ",
     "url": "/docs/velox/s3#log-granularity-of-aws-c-sdk-in-velox",
     
     "relUrl": "/docs/velox/s3#log-granularity-of-aws-c-sdk-in-velox"
-  },"123": {
+  },"248": {
     "doc": "Using S3 with Gluten",
     "title": "Local Caching support",
     "content": "Velox supports a local cache when reading data from HDFS/S3. The feature is very useful if remote storage is slow, e.g., reading from a public S3 bucket and stronger performance is desired. With this feature, Velox can asynchronously cache the data on local disk when reading from remote storage, and the future reading requests on already cached blocks will be serviced from local cache files. To enable the local caching feature, below configurations are required: . spark.g [...]
     "url": "/docs/velox/s3#local-caching-support",
     
     "relUrl": "/docs/velox/s3#local-caching-support"
-  },"124": {
+  },"249": {
     "doc": "Using S3 with Gluten",
     "title": "Using S3 with Gluten",
     "content": "Object stores offered by CSPs such as AWS S3 are important for users of Gluten to store their data. This doc will discuss all details of configs, and use cases around using Gluten with object stores. In order to use an S3 endpoint as your data source, please ensure you are using the following S3 configs in your spark-defaults.conf. If you’re experiencing any issues authenticating to S3 with additional auth mechanisms, please reach out to us using the ‘Issues’ tab. ",
     "url": "/docs/velox/s3",
     
     "relUrl": "/docs/velox/s3"
-  },"125": {
+  },"250": {
     "doc": "About",
     "title": "About",
     "content": "This is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at jekyllrb.com . You can find the source code for Minima at GitHub: jekyll / minima . You can find the source code for Jekyll at GitHub: jekyll / jekyll . ",
     "url": "/about/",
     
     "relUrl": "/about/"
-  },"126": {
+  },"251": {
     "doc": "Apache Software Foundation",
     "title": "Apache Software Foundation",
     "content": "Apache Software Foundation(ASF) . License . Event . Sponsorship . Thanks . Security . Privacy . ",
     "url": "/asf/",
     
     "relUrl": "/asf/"
-  },"127": {
+  },"252": {
     "doc": "Contact Us",
     "title": "Contact Us",
     "content": "This plugin is still under active development now, and doesn’t have a stable release. Welcome to evaluate it. If you encounter any issues or have any suggestions, please submit to our issue list. We’d love to hear your feedback . Apache has meticulously set up dedicated mailing lists for every project, underscoring the pivotal role of these platforms in fostering communication within the Apache community. Mailing lists serve as the backbone for numerous aspects of communi [...]
     "url": "/contact-us.html",
     
     "relUrl": "/contact-us.html"
-  },"128": {
+  },"253": {
     "doc": "Contact Us",
     "title": "How to subscribe Gluten community",
     "content": "To subscribe to the dev@gluten.apache.org mailing list as an example, please follow these steps: . | Send a blank email to dev-subscribe@gluten.apache.org | Check your inbox for an email titled confirm subscribe to dev@gluten.apache.org If not received within a reasonable time, ensure it’s not blocked by your email provider. If not blocked and no reply is received after a while, repeat step 1 | Reply directly to the confirmation email without altering the subject or addin [...]
     "url": "/contact-us.html#how-to-subscribe-gluten-community",
     
     "relUrl": "/contact-us.html#how-to-subscribe-gluten-community"
-  },"129": {
+  },"254": {
     "doc": "Contact Us",
     "title": "Issues and Discussions",
     "content": "We use github to track bugs, feature requests, and answer questions. File an issue for a bug or feature request. ",
     "url": "/contact-us.html#issues-and-discussions",
     
     "relUrl": "/contact-us.html#issues-and-discussions"
-  },"130": {
+  },"255": {
     "doc": "Contributing to Gluten",
     "title": "How to become a committer",
     "content": "To initiate your contributions to Gluten, understand the contribution process—any individual can submit patches, documentation, and examples to the project. The PMC routinely incorporates fresh committers from the pool of active contributors, assessing their contributions to Gluten. The criteria for new committers encompass: . | The Scope of Contribution: To expand contributions beyond pull requests, individuals can engage in various activities including reviewing other p [...]
     "url": "/contributing.html#how-to-become-a-committer",
     
     "relUrl": "/contributing.html#how-to-become-a-committer"
-  },"131": {
+  },"256": {
     "doc": "Contributing to Gluten",
     "title": "Contributing to Gluten",
     "content": " ",
     "url": "/contributing.html",
     
     "relUrl": "/contributing.html"
-  },"132": {
+  },"257": {
     "doc": "Docker script for CentOS 7",
     "title": "Docker script for CentOS 7",
     "content": "Here is a docker script we verified to build Gluten+Velox backend on CentOS 7: . Run on host as root user: . docker pull centos:7 docker run -itd --name gluten centos:7 /bin/bash docker attach gluten . Run in docker: . yum -y install epel-release centos-release-scl yum -y install \\ git \\ dnf \\ cmake3 \\ devtoolset-9 \\ java-1.8.0-openjdk \\ java-1.8.0-openjdk-devel \\ ninja-build \\ wget \\ sudo # gluten need maven version &gt;=3.6.3 wget https://downloads.apache.org/m [...]
     "url": "/developers/docker_centos7.html",
     
     "relUrl": "/developers/docker_centos7.html"
-  },"133": {
+  },"258": {
+    "doc": "v1.1.1/Docker script for CentOS 7",
+    "title": "v1.1.1/Docker script for CentOS 7",
+    "content": "Here is a docker script we verified to build Gluten+Velox backend on CentOS 7: . Run on host as root user: . docker pull centos:7 docker run -itd --name gluten centos:7 /bin/bash docker attach gluten . Run in docker: . yum -y install epel-release centos-release-scl yum -y install \\ git \\ dnf \\ cmake3 \\ devtoolset-9 \\ java-1.8.0-openjdk \\ java-1.8.0-openjdk-devel \\ ninja-build \\ wget \\ sudo # gluten need maven version &gt;=3.6.3 wget https://downloads.apache.org/m [...]
+    "url": "/archives/v1.1.1/developers/docker_centos7/",
+    
+    "relUrl": "/archives/v1.1.1/developers/docker_centos7/"
+  },"259": {
     "doc": "Docker script for CentOS 8",
     "title": "Docker script for CentOS 8",
     "content": "Here is a docker script we verified to build Gluten+Velox backend on Centos8: . Run on host as root user: . docker pull centos:8 docker run -itd --name gluten centos:8 /bin/bash docker attach gluten . Run in docker: . #update mirror sed -i -e \"s|mirrorlist=|#mirrorlist=|g\" /etc/yum.repos.d/CentOS-* sed -i -e \"s|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g\" /etc/yum.repos.d/CentOS-* dnf install -y epel-release sudo yum install -y dnf-plugins-core [...]
     "url": "/developers/docker_centos8.html",
     
     "relUrl": "/developers/docker_centos8.html"
-  },"134": {
+  },"260": {
+    "doc": "v1.1.1/Docker script for CentOS 8",
+    "title": "v1.1.1/Docker script for CentOS 8",
+    "content": "Here is a docker script we verified to build Gluten+Velox backend on Centos8: . Run on host as root user: . docker pull centos:8 docker run -itd --name gluten centos:8 /bin/bash docker attach gluten . Run in docker: . #update mirror sed -i -e \"s|mirrorlist=|#mirrorlist=|g\" /etc/yum.repos.d/CentOS-* sed -i -e \"s|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g\" /etc/yum.repos.d/CentOS-* dnf install -y epel-release sudo yum install -y dnf-plugins-core [...]
+    "url": "/archives/v1.1.1/developers/docker_centos8",
+    
+    "relUrl": "/archives/v1.1.1/developers/docker_centos8"
+  },"261": {
     "doc": "Docker script for Ubuntu 22.04/20.04",
     "title": "Docker script for Ubuntu 22.04/20.04",
     "content": "To the first build, it’s suggested to build Gluten in a clean docker image. Otherwise it’s easy to run into library version conflict issues. Here is a docker script we verified to build Gluten+Velox backend on Ubuntu22.04/20.04: . Run on host as root user: . docker pull ubuntu:22.04 docker run -itd --network host --name gluten ubuntu:22.04 /bin/bash docker attach gluten . Run in docker: . apt-get update #install gcc and libraries to build arrow apt install software-proper [...]
     "url": "/developers/docker_ubuntu22.04.html",
     
     "relUrl": "/developers/docker_ubuntu22.04.html"
-  },"135": {
+  },"262": {
+    "doc": "v1.1.1/Docker script for Ubuntu 22.04/20.04",
+    "title": "v1.1.1/Docker script for Ubuntu 22.04/20.04",
+    "content": "To the first build, it’s suggested to build Gluten in a clean docker image. Otherwise it’s easy to run into library version conflict issues. Here is a docker script we verified to build Gluten+Velox backend on Ubuntu22.04/20.04: . Run on host as root user: . docker pull ubuntu:22.04 docker run -itd --network host --name gluten ubuntu:22.04 /bin/bash docker attach gluten . Run in docker: . apt-get update #install gcc and libraries to build arrow apt install software-proper [...]
+    "url": "/archives/v1.1.1/developers/docker_ubuntu/",
+    
+    "relUrl": "/archives/v1.1.1/developers/docker_ubuntu/"
+  },"263": {
     "doc": "Developers",
     "title": "Gluten Developers",
     "content": "This document provides a developer overview of the project and covers the following topics: . ",
     "url": "/developers/#gluten-developers",
     
     "relUrl": "/developers/#gluten-developers"
-  },"136": {
+  },"264": {
     "doc": "Developers",
     "title": "Developers",
     "content": " ",
     "url": "/developers/",
     
     "relUrl": "/developers/"
-  },"137": {
+  },"265": {
+    "doc": "v1.1.1/Developers",
+    "title": "Gluten Developers",
+    "content": "This document provides a developer overview of the project and covers the following topics: . ",
+    "url": "/archives/v1.1.1/developers/#gluten-developers",
+    
+    "relUrl": "/archives/v1.1.1/developers/#gluten-developers"
+  },"266": {
+    "doc": "v1.1.1/Developers",
+    "title": "v1.1.1/Developers",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/",
+    
+    "relUrl": "/archives/v1.1.1/developers/"
+  },"267": {
+    "doc": "v1.1.1/Documentation",
+    "title": "Gluten Documents by version",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/#gluten-documents-by-version",
+    
+    "relUrl": "/archives/v1.1.1/docs/#gluten-documents-by-version"
+  },"268": {
+    "doc": "v1.1.1/Documentation",
+    "title": "v1.1.1/Documentation",
+    "content": " ",
+    "url": "/archives/v1.1.1/docs/",
+    
+    "relUrl": "/archives/v1.1.1/docs/"
+  },"269": {
+    "doc": "v1.1.1",
+    "title": "Gluten Documents by version",
+    "content": " ",
+    "url": "/archives/v1.1.1/#gluten-documents-by-version",
+    
+    "relUrl": "/archives/v1.1.1/#gluten-documents-by-version"
+  },"270": {
+    "doc": "v1.1.1",
+    "title": "v1.1.1",
+    "content": " ",
+    "url": "/archives/v1.1.1/",
+    
+    "relUrl": "/archives/v1.1.1/"
+  },"271": {
+    "doc": "Archives",
+    "title": "Gluten Documents by version",
+    "content": " ",
+    "url": "/archives/#gluten-documents-by-version",
+    
+    "relUrl": "/archives/#gluten-documents-by-version"
+  },"272": {
+    "doc": "Archives",
+    "title": "Archives",
+    "content": " ",
+    "url": "/archives/",
+    
+    "relUrl": "/archives/"
+  },"273": {
     "doc": "Documentation",
     "title": "Gluten Documents by version",
     "content": " ",
     "url": "/docs/#gluten-documents-by-version",
     
     "relUrl": "/docs/#gluten-documents-by-version"
-  },"138": {
+  },"274": {
     "doc": "Documentation",
     "title": "Documentation",
     "content": " ",
     "url": "/docs/",
     
     "relUrl": "/docs/"
-  },"139": {
+  },"275": {
     "doc": "Home",
     "title": "Overview",
     "content": "Apache Gluten(incubating) is a middle layer responsible for offloading JVM-based SQL engines’ execution to native engines. ",
     "url": "/#overview",
     
     "relUrl": "/#overview"
-  },"140": {
+  },"276": {
     "doc": "Home",
     "title": "1 Introduction",
     "content": " ",
     "url": "/#1-introduction",
     
     "relUrl": "/#1-introduction"
-  },"141": {
+  },"277": {
     "doc": "Home",
     "title": "1.1 Problem Statement",
     "content": "Apache Spark is a stable, mature project that has been developed for many years. It is one of the best frameworks to scale out for processing petabyte-scale datasets. However, the Spark community has had to address performance challenges that require various optimizations over time. As a key optimization in Spark 2.0, Whole Stage Code Generation is introduced to replace Volcano Model, which achieves 2x speedup. Henceforth, most optimizations are at query plan level. Singl [...]
     "url": "/#11-problem-statement",
     
     "relUrl": "/#11-problem-statement"
-  },"142": {
+  },"278": {
     "doc": "Home",
     "title": "1.2 Gluten’s Solution",
     "content": "“Gluten” is Latin for glue. The main goal of Gluten project is to “glue” native libraries with SparkSQL. Thus, we can benefit from high scalability of Spark SQL framework and high performance of native libraries. The basic rule of Gluten’s design is that we would reuse spark’s whole control flow and as many JVM code as possible but offload the compute-intensive data processing part to native code. Here is what Gluten does: . | Transform Spark’s whole stage physical plan t [...]
     "url": "/#12-glutens-solution",
     
     "relUrl": "/#12-glutens-solution"
-  },"143": {
+  },"279": {
     "doc": "Home",
     "title": "1.3 Target User",
     "content": "Gluten’s target user is anyone who wants to accelerate SparkSQL fundamentally. As a plugin to Spark, Gluten doesn’t require any change for dataframe API or SQL query, but only requires user to make correct configuration. See Gluten configuration properties here. ",
     "url": "/#13-target-user",
     
     "relUrl": "/#13-target-user"
-  },"144": {
+  },"280": {
     "doc": "Home",
     "title": "1.4 References",
     "content": "You can click below links for more related information. | Gluten Intro Video at Data AI Summit 2022 | Gluten Intro Article at Medium.com | Gluten Intro Article at Kyligence.io(in Chinese) | Velox Intro from Meta | . ",
     "url": "/#14-references",
     
     "relUrl": "/#14-references"
-  },"145": {
+  },"281": {
     "doc": "Home",
     "title": "2 Architecture",
     "content": "The overview chart is like below. Substrait provides a well-defined cross-language specification for data compute operations (see more details here). Spark physical plan is transformed to Substrait plan. Then Substrait plan is passed to native through JNI call. On native side, the native operator chain will be built out and offloaded to native engine. Gluten will return Columnar Batch to Spark and Spark Columnar API (since Spark-3.0) will be used at execution time. Gluten [...]
     "url": "/#2-architecture",
     
     "relUrl": "/#2-architecture"
-  },"146": {
+  },"282": {
     "doc": "Home",
     "title": "Home",
     "content": " ",
     "url": "/",
     
     "relUrl": "/"
-  },"147": {
+  },"283": {
     "doc": "Gluten Release",
     "title": "Latest release for velox backend",
     "content": ". | Gluten-1.1.1 (Mar. 2 2024, non-Apache release) | . ",
     "url": "/release.html#latest-release-for-velox-backend",
     
     "relUrl": "/release.html#latest-release-for-velox-backend"
-  },"148": {
+  },"284": {
     "doc": "Gluten Release",
     "title": "Archived releases",
     "content": ". | Gluten-1.1.0 (Nov. 30 2023, non-Apache release) | Gluten-1.0.0 (Jul. 13 2023, non-Apache release) | Gluten-0.5.0 (Apr. 7 2023, non-Apache release) | . ",
     "url": "/release.html#archived-releases",
     
     "relUrl": "/release.html#archived-releases"
-  },"149": {
+  },"285": {
     "doc": "Gluten Release",
     "title": "Gluten Release",
     "content": "Gluten is a plugin for Apache Spark to double SparkSQL’s performance. ",
     "url": "/release.html",
     
     "relUrl": "/release.html"
-  },"150": {
+  },"286": {
     "doc": "Velox Function Development",
     "title": "Developer Guide for Implementing Spark Built-in SQL Functions in Velox",
     "content": "In velox, two folders prestosql &amp; sparksql are holding most sql functions, respective for presto and spark. Gluten will ask velox to firstly register prestosql functions, then sparksql functions. So if prestosql and sparksql share same signature for a function, the sparksql function will overwrite the corresponding prestosql function. If the required function is lacking in both folders (exceptions are some common functions defined outside, like cast), we need to imple [...]
     "url": "/developers/velox-function-development-guide.html#developer-guide-for-implementing-spark-built-in-sql-functions-in-velox",
     
     "relUrl": "/developers/velox-function-development-guide.html#developer-guide-for-implementing-spark-built-in-sql-functions-in-velox"
-  },"151": {
+  },"287": {
     "doc": "Velox Function Development",
     "title": "Velox Function Development",
     "content": " ",
     "url": "/developers/velox-function-development-guide.html",
     
     "relUrl": "/developers/velox-function-development-guide.html"
+  },"288": {
+    "doc": "v1.1.1/Velox Function Development",
+    "title": "Developer Guide for Implementing Spark Built-in SQL Functions in Velox",
+    "content": "In velox, two folders prestosql &amp; sparksql are holding most sql functions, respective for presto and spark. Gluten will ask velox to firstly register prestosql functions, then sparksql functions. So if prestosql and sparksql share same signature for a function, the sparksql function will overwrite the corresponding prestosql function. If the required function is lacking in both folders (exceptions are some common functions defined outside, like cast), we need to imple [...]
+    "url": "/archives/v1.1.1/developers/velox_function_development/#developer-guide-for-implementing-spark-built-in-sql-functions-in-velox",
+    
+    "relUrl": "/archives/v1.1.1/developers/velox_function_development/#developer-guide-for-implementing-spark-built-in-sql-functions-in-velox"
+  },"289": {
+    "doc": "v1.1.1/Velox Function Development",
+    "title": "v1.1.1/Velox Function Development",
+    "content": " ",
+    "url": "/archives/v1.1.1/developers/velox_function_development/",
+    
+    "relUrl": "/archives/v1.1.1/developers/velox_function_development/"
   }
 }
diff --git a/output/clickhouse/index.html b/output/clickhouse/index.html
index 7fb3257..08b3273 100644
--- a/output/clickhouse/index.html
+++ b/output/clickhouse/index.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/contact-us.html b/output/contact-us.html
index 081d9ab..0286f1a 100644
--- a/output/contact-us.html
+++ b/output/contact-us.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(6)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(8)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/contributing.html b/output/contributing.html
index bcb7429..3653ba6 100644
--- a/output/contributing.html
+++ b/output/contributing.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(5)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(6)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/developers/CppCodingStyle.html b/output/developers/CppCodingStyle.html
index 9c3bc05..c8d01f9 100644
--- a/output/developers/CppCodingStyle.html
+++ b/output/developers/CppCodingStyle.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(4)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(4)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/developers/HowTo.html b/output/developers/HowTo.html
index 2f72cc3..1a5c43f 100644
--- a/output/developers/HowTo.html
+++ b/output/developers/HowTo.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
 </code></pre></div> </div> <ul> <li>Compiling with <code class="language-plaintext highlighter-rouge">--build_type=Debug</code> is good for debugging.</li> <li>The executable file <code class="language-plaintext highlighter-rouge">generic_benchmark</code> will be generated under the directory of <code class="language-plaintext highlighter-rouge">gluten_home/cpp/build/velox/benchmarks/</code>.</li> </ul> </li> <li>build Gluten and generate the example files <div class="language-plaintext  [...]
 mvn clean package -Pspark-3.2 -Pbackends-velox -Prss
 mvn test -Pspark-3.2 -Pbackends-velox -Prss -pl backends-velox -am -DtagsToInclude="io.glutenproject.tags.GenerateExample" -Dtest=none -DfailIfNoTests=false -Darrow.version=11.0.0-gluten -Dexec.skip
diff --git a/output/developers/HowToRelease.html b/output/developers/HowToRelease.html
index 352e992..7fae847 100644
--- a/output/developers/HowToRelease.html
+++ b/output/developers/HowToRelease.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(10)) > a, .site-nav > ul.nav-list:first-child > li > ul > li [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(10)) > a, .site-nav > ul.nav-list:first-child > li > ul > li [...]
 $ gpg --full-generate-key
 
 # list the GPG keys
diff --git a/output/developers/MicroBenchmarks.html b/output/developers/MicroBenchmarks.html
index c7fa75e..7d636ce 100644
--- a/output/developers/MicroBenchmarks.html
+++ b/output/developers/MicroBenchmarks.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(3)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(3)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
 ./dev/buildbundle-veloxbe.sh <span class="nt">--build_tests</span><span class="o">=</span>ON <span class="nt">--build_benchmarks</span><span class="o">=</span>ON
 
 <span class="c"># Run test to generate input data files. If you are using spark 3.3, replace -Pspark-3.2 with -Pspark-3.3</span>
diff --git a/output/developers/NewToGluten.html b/output/developers/NewToGluten.html
index a49b2aa..26904b3 100644
--- a/output/developers/NewToGluten.html
+++ b/output/developers/NewToGluten.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
 update-alternatives <span class="nt">--config</span> java
 java <span class="nt">-version</span>
 </code></pre></div></div> <p><code class="language-plaintext highlighter-rouge">--config java</code> to config java executable path, <code class="language-plaintext highlighter-rouge">javac</code> and other commands can also use this command to config. For some other uses, we suggest to set <code class="language-plaintext highlighter-rouge">JAVA_HOME</code>.</p> <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">export </span [...]
diff --git a/output/developers/SubstraitModifications.html b/output/developers/SubstraitModifications.html
index c0b0ae2..e9db5fa 100644
--- a/output/developers/SubstraitModifications.html
+++ b/output/developers/SubstraitModifications.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(9)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(9)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/developers/UsingGperftoolsInCH.html b/output/developers/UsingGperftoolsInCH.html
index 4c50c77..13521fc 100644
--- a/output/developers/UsingGperftoolsInCH.html
+++ b/output/developers/UsingGperftoolsInCH.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
 export LD_PRELOAD=$tcmalloc_path,libch.so # load the library in the driver
 --files $tcmalloc_path # upload the library to the cluster
 --conf spark.executorEnv.LD_PRELOAD=./libtcmalloc_and_profiler.so,libch.so # load the library in the executor
diff --git a/output/developers/UsingJemallocWithCH.html b/output/developers/UsingJemallocWithCH.html
index c6b5e14..e024c04 100644
--- a/output/developers/UsingJemallocWithCH.html
+++ b/output/developers/UsingJemallocWithCH.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
  # At the time ClickHouse uses LLVM libunwind which follows libgcc's way of backtracking.
  #
  # ClickHouse has to provide `unw_backtrace` method by the means of [commit 8e2b31e](https://github.com/ClickHouse/libunwind/commit/8e2b31e766dd502f6df74909e04a7dbdf5182eb1).
diff --git a/output/developers/docker_centos7.html b/output/developers/docker_centos7.html
index 28d9b82..02555aa 100644
--- a/output/developers/docker_centos7.html
+++ b/output/developers/docker_centos7.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(8)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(8)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
 docker run -itd --name gluten centos:7 /bin/bash
 docker attach gluten
 </code></pre></div></div> <p>Run in docker:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>yum -y install epel-release centos-release-scl
diff --git a/output/developers/docker_centos8.html b/output/developers/docker_centos8.html
index 4c0f475..e8052b0 100644
--- a/output/developers/docker_centos8.html
+++ b/output/developers/docker_centos8.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(7)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(7)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
 docker run -itd --name gluten centos:8 /bin/bash
 docker attach gluten
 </code></pre></div></div> <p>Run in docker:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>#update mirror
diff --git a/output/developers/docker_ubuntu22.04.html b/output/developers/docker_ubuntu22.04.html
index 87be17b..d7cd3e7 100644
--- a/output/developers/docker_ubuntu22.04.html
+++ b/output/developers/docker_ubuntu22.04.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(6)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(6)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
 docker run -itd --network host --name gluten ubuntu:22.04 /bin/bash
 docker attach gluten
 </code></pre></div></div> <p>Run in docker:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>apt-get update
diff --git a/output/developers/index.html b/output/developers/index.html
index f8adb51..f3ef4c9 100644
--- a/output/developers/index.html
+++ b/output/developers/index.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(3)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(3)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/developers/velox-function-development-guide.html b/output/developers/velox-function-development-guide.html
index 5faf7df..d4a1748 100644
--- a/output/developers/velox-function-development-guide.html
+++ b/output/developers/velox-function-development-guide.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(5)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(5)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
 struct BitwiseAndFunction {
   template &lt;typename TInput&gt;
   // For void return type, it indicates null result will never be obtained for non-null input.
diff --git a/output/docs/clickhouse/getting-started.html b/output/docs/clickhouse/getting-started.html
index 5057d06..2dd7cb1 100644
--- a/output/docs/clickhouse/getting-started.html
+++ b/output/docs/clickhouse/getting-started.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
 </code></pre></div></div> <h4 id="setup-clickhouse-backend-development-environment"> <a href="#setup-clickhouse-backend-development-environment" class="anchor-heading" aria-labelledby="setup-clickhouse-backend-development-environment"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Setup ClickHouse backend development environment </h4> <p>If you don’t care about development environment, you can skip this part.</p> <p>Otherwise, do:</p> <ol> <li>cl [...]
  git clone --recursive --shallow-submodules -b clickhouse_backend https://github.com/Kyligence/ClickHouse.git
 </code></pre></div> </div> </li> <li> <p>Configure cpp-ch ${GLUTEN_SOURCE}/cpp-ch can be treated as an add-on of Kyligence/Clickhouse</p> <p>First, initialize some configuration for this add-on:</p> <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="nb">export </span><span class="nv">GLUTEN_SOURCE</span><span class="o">=</span>/path/to/gluten
diff --git a/output/docs/index.html b/output/docs/index.html
index 1e350db..28f332b 100644
--- a/output/docs/index.html
+++ b/output/docs/index.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(2)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/docs/velox/build_parameters.html b/output/docs/velox/build_parameters.html
index 9d790e2..f10a51b 100644
--- a/output/docs/velox/build_parameters.html
+++ b/output/docs/velox/build_parameters.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
diff --git a/output/docs/velox/gcs.html b/output/docs/velox/gcs.html
index 0c3310d..0b237ff 100644
--- a/output/docs/velox/gcs.html
+++ b/output/docs/velox/gcs.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
 spark.hadoop.fs.gs.auth.service.account.json.keyfile // path to the json file with the credentials.
 </code></pre></div></div> <h2 id="configuring-gcs-endpoints"> <a href="#configuring-gcs-endpoints" class="anchor-heading" aria-labelledby="configuring-gcs-endpoints"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Configuring GCS endpoints </h2> <p>For cases when a GCS mock is used, an optional endpoint can be provided:</p> <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>spark.hadoop.fs.gs.storage.roo [...]
 </code></pre></div></div> </main> <hr> <footer> <p><a href="#top" id="back-to-top">Back to top</a></p> <a href="https://incubator.apache.org/">Apache Incubator</a> <p class="text-small text-grey-dk-100 mb-0">Copyright © 2024 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache Gluten, Gluten, Apache, the Apache feather logo, and the Apache Gluten project logo are either registered trademarks or trademarks of the Apache Software Foundation in the United S [...]
diff --git a/output/docs/velox/getting-started.html b/output/docs/velox/getting-started.html
index 4454749..fe7c1e8 100644
--- a/output/docs/velox/getting-started.html
+++ b/output/docs/velox/getting-started.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
 <span class="nb">export </span><span class="nv">JAVA_HOME</span><span class="o">=</span>/usr/lib/jvm/java-8-openjdk-amd64
 <span class="nb">export </span><span class="nv">PATH</span><span class="o">=</span><span class="nv">$JAVA_HOME</span>/bin:<span class="nv">$PATH</span>
 </code></pre></div></div> <p><strong>For aarch64</strong></p> <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">## make sure jdk8 is used</span>
diff --git a/output/docs/velox/index.html b/output/docs/velox/index.html
index 6f275c1..a475fcd 100644
--- a/output/docs/velox/index.html
+++ b/output/docs/velox/index.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/docs/velox/s3.html b/output/docs/velox/s3.html
index aecb15c..d3490fe 100644
--- a/output/docs/velox/s3.html
+++ b/output/docs/velox/s3.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li > ul > li:not(:nth- [...]
 spark.hadoop.fs.s3a.aws.credentials.provider    org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider
 spark.hadoop.fs.s3a.access.key                  XXXXXXXXX
 spark.hadoop.fs.s3a.secret.key                  XXXXXXXXX
diff --git a/output/feed.xml b/output/feed.xml
index e366651..2ba7f5c 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.9.3">Jekyll</generator><link href="https://gluten.apache.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://gluten.apache.org/" rel="alternate" type="text/html" /><updated>2024-07-30T05:37:25+00:00</updated><id>https://gluten.apache.org/feed.xml</id><title type="html">Apache Gluten incubating</title><subtitle>Gluten is a middle layer r [...]
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.9.3">Jekyll</generator><link href="https://gluten.apache.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://gluten.apache.org/" rel="alternate" type="text/html" /><updated>2024-08-07T15:35:38+00:00</updated><id>https://gluten.apache.org/feed.xml</id><title type="html">Apache Gluten incubating</title><subtitle>Gluten is a middle layer r [...]
 
 &lt;p&gt;Jekyll requires blog post files to be named according to the following format:&lt;/p&gt;
 
diff --git a/output/index.html b/output/index.html
index 67183d7..eb4ac0e 100644
--- a/output/index.html
+++ b/output/index.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(1)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
diff --git a/output/jekyll/update/2024/02/08/welcome-to-jekyll.html b/output/jekyll/update/2024/02/08/welcome-to-jekyll.html
index 11bff3f..a3d971c 100644
--- a/output/jekyll/update/2024/02/08/welcome-to-jekyll.html
+++ b/output/jekyll/update/2024/02/08/welcome-to-jekyll.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav ul li a { background-image: none; } </style> <script src="/assets/js/vendor/lunr.min.js"></script> <script src="/assets/js/just-the-docs.js"></script> <meta name= [...]
   <span class="nb">puts</span> <span class="s2">"Hi, </span><span class="si">#{</span><span class="nb">name</span><span class="si">}</span><span class="s2">"</span>
 <span class="k">end</span>
 <span class="n">print_hi</span><span class="p">(</span><span class="s1">'Tom'</span><span class="p">)</span>
diff --git a/output/release.html b/output/release.html
index 67cedc5..46f6aac 100644
--- a/output/release.html
+++ b/output/release.html
@@ -1 +1 @@
-<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(4)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]
+<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <link rel="stylesheet" href="/assets/css/just-the-docs-default.css"> <link rel="stylesheet" href="/assets/css/just-the-docs-head-nav.css" id="jtd-head-nav-stylesheet"> <style id="jtd-nav-activation"> .site-nav > ul.nav-list:first-child > li:not(:nth-child(5)) > a, .site-nav > ul.nav-list:first-child > li > ul > li > a, .site-nav > ul.nav-list:first-child > li > ul > li  [...]


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@gluten.apache.org
For additional commands, e-mail: commits-help@gluten.apache.org