This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion-comet.git
The following commit(s) were added to refs/heads/asf-site by this push:
new ce235a19f5 Publish built docs triggered by
5372d7614836abca5a2c414945154d399c0fdcef
ce235a19f5 is described below
commit ce235a19f506489cf5ea8710f76ea4a06214fad4
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Jul 8 14:37:04 2026 +0000
Publish built docs triggered by 5372d7614836abca5a2c414945154d399c0fdcef
---
.../latest/compatibility/expressions/spark-3.4/datetime.md.txt | 6 +++++-
.../latest/compatibility/expressions/spark-3.5/datetime.md.txt | 6 +++++-
.../latest/compatibility/expressions/spark-4.0/datetime.md.txt | 7 +++++--
.../latest/compatibility/expressions/spark-4.1/datetime.md.txt | 7 +++++--
searchindex.js | 2 +-
.../latest/compatibility/expressions/spark-3.4/datetime.html | 6 +++++-
.../latest/compatibility/expressions/spark-3.5/datetime.html | 6 +++++-
.../latest/compatibility/expressions/spark-4.0/datetime.html | 7 +++++--
.../latest/compatibility/expressions/spark-4.1/datetime.html | 7 +++++--
9 files changed, 41 insertions(+), 13 deletions(-)
diff --git
a/_sources/user-guide/latest/compatibility/expressions/spark-3.4/datetime.md.txt
b/_sources/user-guide/latest/compatibility/expressions/spark-3.4/datetime.md.txt
index 7b0ea3efc1..5b5d157d4b 100644
---
a/_sources/user-guide/latest/compatibility/expressions/spark-3.4/datetime.md.txt
+++
b/_sources/user-guide/latest/compatibility/expressions/spark-3.4/datetime.md.txt
@@ -76,7 +76,11 @@ By default, `FromUTCTimestamp` is evaluated in the JVM using
Spark's own code-ge
By default, `FromUnixTime` is evaluated in the JVM using Spark's own
code-generated implementation (run inside the Comet pipeline), which matches
Spark exactly. Set `spark.comet.expression.FromUnixTime.allowIncompatible=true`
to opt into Comet's native implementation instead, which has the following
differences from Spark:
-- Only supports the default datetime format pattern `yyyy-MM-dd HH:mm:ss`.
DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
+- DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
+
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
+
+- Only the default datetime format pattern `yyyy-MM-dd HH:mm:ss` is supported
## Hours
diff --git
a/_sources/user-guide/latest/compatibility/expressions/spark-3.5/datetime.md.txt
b/_sources/user-guide/latest/compatibility/expressions/spark-3.5/datetime.md.txt
index 7b0ea3efc1..5b5d157d4b 100644
---
a/_sources/user-guide/latest/compatibility/expressions/spark-3.5/datetime.md.txt
+++
b/_sources/user-guide/latest/compatibility/expressions/spark-3.5/datetime.md.txt
@@ -76,7 +76,11 @@ By default, `FromUTCTimestamp` is evaluated in the JVM using
Spark's own code-ge
By default, `FromUnixTime` is evaluated in the JVM using Spark's own
code-generated implementation (run inside the Comet pipeline), which matches
Spark exactly. Set `spark.comet.expression.FromUnixTime.allowIncompatible=true`
to opt into Comet's native implementation instead, which has the following
differences from Spark:
-- Only supports the default datetime format pattern `yyyy-MM-dd HH:mm:ss`.
DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
+- DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
+
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
+
+- Only the default datetime format pattern `yyyy-MM-dd HH:mm:ss` is supported
## Hours
diff --git
a/_sources/user-guide/latest/compatibility/expressions/spark-4.0/datetime.md.txt
b/_sources/user-guide/latest/compatibility/expressions/spark-4.0/datetime.md.txt
index 055b3021c1..9cf5333c96 100644
---
a/_sources/user-guide/latest/compatibility/expressions/spark-4.0/datetime.md.txt
+++
b/_sources/user-guide/latest/compatibility/expressions/spark-4.0/datetime.md.txt
@@ -78,8 +78,11 @@ By default, `FromUTCTimestamp` is evaluated in the JVM using
Spark's own code-ge
By default, `FromUnixTime` is evaluated in the JVM using Spark's own
code-generated implementation (run inside the Comet pipeline), which matches
Spark exactly. Set `spark.comet.expression.FromUnixTime.allowIncompatible=true`
to opt into Comet's native implementation instead, which has the following
differences from Spark:
-- Only supports the default datetime format pattern `yyyy-MM-dd HH:mm:ss`.
DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
-- from_unixtime does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)
+- DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
+
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
+
+- Only the default datetime format pattern `yyyy-MM-dd HH:mm:ss` is supported
## Hours
diff --git
a/_sources/user-guide/latest/compatibility/expressions/spark-4.1/datetime.md.txt
b/_sources/user-guide/latest/compatibility/expressions/spark-4.1/datetime.md.txt
index 055b3021c1..9cf5333c96 100644
---
a/_sources/user-guide/latest/compatibility/expressions/spark-4.1/datetime.md.txt
+++
b/_sources/user-guide/latest/compatibility/expressions/spark-4.1/datetime.md.txt
@@ -78,8 +78,11 @@ By default, `FromUTCTimestamp` is evaluated in the JVM using
Spark's own code-ge
By default, `FromUnixTime` is evaluated in the JVM using Spark's own
code-generated implementation (run inside the Comet pipeline), which matches
Spark exactly. Set `spark.comet.expression.FromUnixTime.allowIncompatible=true`
to opt into Comet's native implementation instead, which has the following
differences from Spark:
-- Only supports the default datetime format pattern `yyyy-MM-dd HH:mm:ss`.
DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
-- from_unixtime does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)
+- DataFusion's valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)
+
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
+
+- Only the default datetime format pattern `yyyy-MM-dd HH:mm:ss` is supported
## Hours
diff --git a/searchindex.js b/searchindex.js
index 0bb8830b96..3831c6c23b 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles": {"!": [[51, "id1"]], "%": [[49, "id1"]], "&":
[[39, "id1"]], "*": [[49, "id2"]], "+": [[49, "id3"]], "-": [[49, "id4"]], "/":
[[49, "id5"]], "1. Format Your Code": [[36, "format-your-code"]], "1. Install
Comet": [[57, "install-comet"], [66, "install-comet"]], "1. Native Operators
(nativeExecs map)": [[25, "native-operators-nativeexecs-map"]], "2. Build and
Verify": [[36, "build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[57,
"clone-iceberg-and-apply- [...]
\ No newline at end of file
+Search.setIndex({"alltitles": {"!": [[51, "id1"]], "%": [[49, "id1"]], "&":
[[39, "id1"]], "*": [[49, "id2"]], "+": [[49, "id3"]], "-": [[49, "id4"]], "/":
[[49, "id5"]], "1. Format Your Code": [[36, "format-your-code"]], "1. Install
Comet": [[57, "install-comet"], [66, "install-comet"]], "1. Native Operators
(nativeExecs map)": [[25, "native-operators-nativeexecs-map"]], "2. Build and
Verify": [[36, "build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[57,
"clone-iceberg-and-apply- [...]
\ No newline at end of file
diff --git
a/user-guide/latest/compatibility/expressions/spark-3.4/datetime.html
b/user-guide/latest/compatibility/expressions/spark-3.4/datetime.html
index 1d384e22de..1455803633 100644
--- a/user-guide/latest/compatibility/expressions/spark-3.4/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-3.4/datetime.html
@@ -806,7 +806,11 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
<h2>FromUnixTime<a class="headerlink" href="#fromunixtime" title="Link to this
heading">#</a></h2>
<p>By default, <code class="docutils literal notranslate"><span
class="pre">FromUnixTime</span></code> is evaluated in the JVM using Spark’s
own code-generated implementation (run inside the Comet pipeline), which
matches Spark exactly. Set <code class="docutils literal notranslate"><span
class="pre">spark.comet.expression.FromUnixTime.allowIncompatible=true</span></code>
to opt into Comet’s native implementation instead, which has the following
differences from Spark:</p>
<ul class="simple">
-<li><p>Only supports the default datetime format pattern <code class="docutils
literal notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code>. DataFusion’s valid timestamp range differs
from Spark (https://github.com/apache/datafusion/issues/16594)</p></li>
+<li><p>DataFusion’s valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)</p></li>
+</ul>
+<p>The following cases have no native implementation and always run in the JVM
using Spark’s code-generated implementation (inside the Comet pipeline):</p>
+<ul class="simple">
+<li><p>Only the default datetime format pattern <code class="docutils literal
notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code> is supported</p></li>
</ul>
</section>
<section id="hours">
diff --git
a/user-guide/latest/compatibility/expressions/spark-3.5/datetime.html
b/user-guide/latest/compatibility/expressions/spark-3.5/datetime.html
index 11d151a453..e45c0ba2cc 100644
--- a/user-guide/latest/compatibility/expressions/spark-3.5/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-3.5/datetime.html
@@ -806,7 +806,11 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
<h2>FromUnixTime<a class="headerlink" href="#fromunixtime" title="Link to this
heading">#</a></h2>
<p>By default, <code class="docutils literal notranslate"><span
class="pre">FromUnixTime</span></code> is evaluated in the JVM using Spark’s
own code-generated implementation (run inside the Comet pipeline), which
matches Spark exactly. Set <code class="docutils literal notranslate"><span
class="pre">spark.comet.expression.FromUnixTime.allowIncompatible=true</span></code>
to opt into Comet’s native implementation instead, which has the following
differences from Spark:</p>
<ul class="simple">
-<li><p>Only supports the default datetime format pattern <code class="docutils
literal notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code>. DataFusion’s valid timestamp range differs
from Spark (https://github.com/apache/datafusion/issues/16594)</p></li>
+<li><p>DataFusion’s valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)</p></li>
+</ul>
+<p>The following cases have no native implementation and always run in the JVM
using Spark’s code-generated implementation (inside the Comet pipeline):</p>
+<ul class="simple">
+<li><p>Only the default datetime format pattern <code class="docutils literal
notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code> is supported</p></li>
</ul>
</section>
<section id="hours">
diff --git
a/user-guide/latest/compatibility/expressions/spark-4.0/datetime.html
b/user-guide/latest/compatibility/expressions/spark-4.0/datetime.html
index 9f141edb6a..d481df36e6 100644
--- a/user-guide/latest/compatibility/expressions/spark-4.0/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-4.0/datetime.html
@@ -808,8 +808,11 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
<h2>FromUnixTime<a class="headerlink" href="#fromunixtime" title="Link to this
heading">#</a></h2>
<p>By default, <code class="docutils literal notranslate"><span
class="pre">FromUnixTime</span></code> is evaluated in the JVM using Spark’s
own code-generated implementation (run inside the Comet pipeline), which
matches Spark exactly. Set <code class="docutils literal notranslate"><span
class="pre">spark.comet.expression.FromUnixTime.allowIncompatible=true</span></code>
to opt into Comet’s native implementation instead, which has the following
differences from Spark:</p>
<ul class="simple">
-<li><p>Only supports the default datetime format pattern <code class="docutils
literal notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code>. DataFusion’s valid timestamp range differs
from Spark (https://github.com/apache/datafusion/issues/16594)</p></li>
-<li><p>from_unixtime does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)</p></li>
+<li><p>DataFusion’s valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)</p></li>
+</ul>
+<p>The following cases have no native implementation and always run in the JVM
using Spark’s code-generated implementation (inside the Comet pipeline):</p>
+<ul class="simple">
+<li><p>Only the default datetime format pattern <code class="docutils literal
notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code> is supported</p></li>
</ul>
</section>
<section id="hours">
diff --git
a/user-guide/latest/compatibility/expressions/spark-4.1/datetime.html
b/user-guide/latest/compatibility/expressions/spark-4.1/datetime.html
index bc5491c3f0..8c9b70831f 100644
--- a/user-guide/latest/compatibility/expressions/spark-4.1/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-4.1/datetime.html
@@ -808,8 +808,11 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
<h2>FromUnixTime<a class="headerlink" href="#fromunixtime" title="Link to this
heading">#</a></h2>
<p>By default, <code class="docutils literal notranslate"><span
class="pre">FromUnixTime</span></code> is evaluated in the JVM using Spark’s
own code-generated implementation (run inside the Comet pipeline), which
matches Spark exactly. Set <code class="docutils literal notranslate"><span
class="pre">spark.comet.expression.FromUnixTime.allowIncompatible=true</span></code>
to opt into Comet’s native implementation instead, which has the following
differences from Spark:</p>
<ul class="simple">
-<li><p>Only supports the default datetime format pattern <code class="docutils
literal notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code>. DataFusion’s valid timestamp range differs
from Spark (https://github.com/apache/datafusion/issues/16594)</p></li>
-<li><p>from_unixtime does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)</p></li>
+<li><p>DataFusion’s valid timestamp range differs from Spark
(https://github.com/apache/datafusion/issues/16594)</p></li>
+</ul>
+<p>The following cases have no native implementation and always run in the JVM
using Spark’s code-generated implementation (inside the Comet pipeline):</p>
+<ul class="simple">
+<li><p>Only the default datetime format pattern <code class="docutils literal
notranslate"><span class="pre">yyyy-MM-dd</span> <span
class="pre">HH:mm:ss</span></code> is supported</p></li>
</ul>
</section>
<section id="hours">
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
