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 e0dc674751 Publish built docs triggered by
09b44ad6fa17f58f4bbccf958c5cf02d790f7334
e0dc674751 is described below
commit e0dc674751ee638cb1c4d03d6f6022ad5e5261cc
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Sep 21 18:01:20 2026 +0000
Publish built docs triggered by 09b44ad6fa17f58f4bbccf958c5cf02d790f7334
---
.../mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg | 2 +-
.../expression-audits/datetime_funcs.md.txt | 10 ++++++++++
_sources/contributor-guide/spark_configs_support.md.txt | 3 ++-
.../compatibility/expressions/spark-3.4/datetime.md.txt | 4 ++--
.../compatibility/expressions/spark-3.5/datetime.md.txt | 4 ++--
.../compatibility/expressions/spark-4.0/datetime.md.txt | 8 ++------
.../compatibility/expressions/spark-4.1/datetime.md.txt | 8 ++------
_sources/user-guide/latest/expressions.md.txt | 2 +-
contributor-guide/expression-audits/datetime_funcs.html | 13 +++++++++++++
contributor-guide/spark_configs_support.html | 3 ++-
searchindex.js | 2 +-
.../compatibility/expressions/spark-3.4/datetime.html | 4 ++--
.../compatibility/expressions/spark-3.5/datetime.html | 4 ++--
.../compatibility/expressions/spark-4.0/datetime.html | 8 ++------
.../compatibility/expressions/spark-4.1/datetime.html | 8 ++------
user-guide/latest/expressions.html | 4 ++--
16 files changed, 48 insertions(+), 39 deletions(-)
diff --git a/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg
b/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg
index 6bd32b44e8..5c01043340 100644
--- a/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg
+++ b/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg
@@ -1 +1 @@
-<svg id="my-svg" width="100%" xmlns="http://www.w3.org/2000/svg";
xmlns:xlink="http://www.w3.org/1999/xlink"; class="flowchart" style="max-width:
511.73px; background-color: transparent;" viewBox="0 0 511.7299499511719 942"
role="graphics-document document"
aria-roledescription="flowchart-v2"><style>#my-svg{font-family:"trebuchet
ms",verdana,arial,sans-serif;font-size:16px;fill:#333;}@keyframes
edge-animation-frame{from{stroke-dashoffset:0;}}@keyframes
dash{to{stroke-dashoffset:0;}}#my-svg [...]
\ No newline at end of file
+<svg id="my-svg" width="100%" xmlns="http://www.w3.org/2000/svg";
xmlns:xlink="http://www.w3.org/1999/xlink"; class="flowchart" style="max-width:
511.73px; background-color: transparent;" viewBox="0 0 511.7299499511719 942"
role="graphics-document document"
aria-roledescription="flowchart-v2"><style>#my-svg{font-family:"trebuchet
ms",verdana,arial,sans-serif;font-size:16px;fill:#333;}@keyframes
edge-animation-frame{from{stroke-dashoffset:0;}}@keyframes
dash{to{stroke-dashoffset:0;}}#my-svg [...]
\ No newline at end of file
diff --git a/_sources/contributor-guide/expression-audits/datetime_funcs.md.txt
b/_sources/contributor-guide/expression-audits/datetime_funcs.md.txt
index b285c4067b..242fd7e6c3 100644
--- a/_sources/contributor-guide/expression-audits/datetime_funcs.md.txt
+++ b/_sources/contributor-guide/expression-audits/datetime_funcs.md.txt
@@ -111,6 +111,16 @@
- Rewrites to `Cast(..., EvalMode.LEGACY)` (no format, native) or
`GetTimestamp(..., failOnError = false)` (with format, via the codegen
dispatcher) before Comet sees the plan. In non-ANSI mode the rewritten tree is
identical to `to_timestamp`; invalid inputs return NULL to match Spark.
+## unix_timestamp
+
+- Spark 3.4.3 (audited 2026-09-13): baseline. String inputs accept literal or
column formats. Date, timestamp, and timestamp without time zone inputs ignore
the format argument.
+- Spark 3.5.8 (audited 2026-09-13): parsing failures use structured timestamp
parsing errors.
+- Spark 4.0.1 (audited 2026-09-13): `inputTypes` widened to
`StringTypeWithCollation` for the input and format arguments.
+- Spark 4.1.1 (audited 2026-09-13): same input types and parsing behavior as
Spark 4.0.1.
+- String inputs use Spark's generated parser through codegen dispatch,
including collated strings and formats. Literal and column formats preserve
null handling, ANSI errors, parser policy, and session time zone.
+- Date, timestamp, and timestamp without time zone inputs retain native
execution and ignore the format, including its collation. String input stays
unsupported by the native serializer so `allowIncompatible=true` cannot send it
to the native kernel.
+- Native timestamp conversion truncates fractional seconds toward zero,
matching Spark's `ToTimestamp`. This fixes the previous use of floor division
for negative fractional timestamps: at UTC, `1969-12-31 23:59:58.5` produces
`-1`, not `-2`. Casting a timestamp to `BIGINT` deliberately uses floor
division in Spark and Comet, so that cast still produces `-2`.
+
[Spark Expression Support]: ../../user-guide/latest/expressions.md
## weekday
diff --git a/_sources/contributor-guide/spark_configs_support.md.txt
b/_sources/contributor-guide/spark_configs_support.md.txt
index b2c55bc146..92107975ba 100644
--- a/_sources/contributor-guide/spark_configs_support.md.txt
+++ b/_sources/contributor-guide/spark_configs_support.md.txt
@@ -124,7 +124,8 @@ and fallback paths:
`spark.comet.expression.FromUnixTime.allowIncompatible=true` is set;
otherwise
it routes through the codegen dispatcher.
- `unix_timestamp(<timestamp_or_date>)` does not call the formatter at all; the
- string-input overload falls back.
+ string-input overload routes through the codegen dispatcher and preserves
Spark's
+ selected parser policy.
- `to_unix_timestamp` routes through the codegen dispatcher.
If a Comet contributor adds native string-format parsing or extends the
date_format
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 7cf2b36f5a..997f33bf5c 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
@@ -139,7 +139,7 @@ The following cases have no native implementation and
always run in the JVM usin
## UnixTimestamp
-The following cases are not supported by Comet and always fall back to Spark,
regardless of any `allowIncompatible` setting:
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
-- Only `DateType`, `TimestampType`, and `TimestampNTZType` inputs are
supported.
+- String inputs, including collated strings, have no native implementation.
<!--END:EXPR_COMPAT-->
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 7cf2b36f5a..997f33bf5c 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
@@ -139,7 +139,7 @@ The following cases have no native implementation and
always run in the JVM usin
## UnixTimestamp
-The following cases are not supported by Comet and always fall back to Spark,
regardless of any `allowIncompatible` setting:
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
-- Only `DateType`, `TimestampType`, and `TimestampNTZType` inputs are
supported.
+- String inputs, including collated strings, have no native implementation.
<!--END:EXPR_COMPAT-->
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 b2782b6c6b..8c5dff1dcd 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
@@ -161,11 +161,7 @@ The following cases have no native implementation and
always run in the JVM usin
## UnixTimestamp
-The following incompatibilities cause `UnixTimestamp` to fall back to Spark by
default. Set `spark.comet.expression.UnixTimestamp.allowIncompatible=true` to
enable Comet acceleration despite these differences.
-
-- unix_timestamp does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)
-
-The following cases are not supported by Comet and always fall back to Spark,
regardless of any `allowIncompatible` setting:
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
-- Only `DateType`, `TimestampType`, and `TimestampNTZType` inputs are
supported.
+- String inputs, including collated strings, have no native implementation.
<!--END:EXPR_COMPAT-->
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 b2782b6c6b..8c5dff1dcd 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
@@ -161,11 +161,7 @@ The following cases have no native implementation and
always run in the JVM usin
## UnixTimestamp
-The following incompatibilities cause `UnixTimestamp` to fall back to Spark by
default. Set `spark.comet.expression.UnixTimestamp.allowIncompatible=true` to
enable Comet acceleration despite these differences.
-
-- unix_timestamp does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)
-
-The following cases are not supported by Comet and always fall back to Spark,
regardless of any `allowIncompatible` setting:
+The following cases have no native implementation and always run in the JVM
using Spark's code-generated implementation (inside the Comet pipeline):
-- Only `DateType`, `TimestampType`, and `TimestampNTZType` inputs are
supported.
+- String inputs, including collated strings, have no native implementation.
<!--END:EXPR_COMPAT-->
diff --git a/_sources/user-guide/latest/expressions.md.txt
b/_sources/user-guide/latest/expressions.md.txt
index e9c840cea3..087bd57a62 100644
--- a/_sources/user-guide/latest/expressions.md.txt
+++ b/_sources/user-guide/latest/expressions.md.txt
@@ -317,7 +317,7 @@ The type-name conversion functions (`bigint`, `binary`,
`boolean`, `date`, `deci
| `unix_micros` | ✅ | Codegen dispatch | |
| `unix_millis` | ✅ | Codegen dispatch | |
| `unix_seconds` | ✅ | Codegen dispatch | |
-| `unix_timestamp` | ✅ | Native | |
+| `unix_timestamp` | ✅ | Hybrid | String parsing uses Spark's codegen and
honors the time parser policy, ANSI mode, and session time zone. Date and
timestamp inputs ignore the format and use native execution. |
| `weekday` | ✅ | Native | |
| `weekofyear` | ✅ | Native | |
| `window` | ✅ | — | Batch tumbling and sliding time-window grouping runs
natively |
diff --git a/contributor-guide/expression-audits/datetime_funcs.html
b/contributor-guide/expression-audits/datetime_funcs.html
index 8abe2a232b..bc75e232f1 100644
--- a/contributor-guide/expression-audits/datetime_funcs.html
+++ b/contributor-guide/expression-audits/datetime_funcs.html
@@ -686,6 +686,18 @@ under the License.
<li><p>Rewrites to <code class="docutils literal notranslate"><span
class="pre">Cast(...,</span> <span class="pre">EvalMode.LEGACY)</span></code>
(no format, native) or <code class="docutils literal notranslate"><span
class="pre">GetTimestamp(...,</span> <span class="pre">failOnError</span> <span
class="pre">=</span> <span class="pre">false)</span></code> (with format, via
the codegen dispatcher) before Comet sees the plan. In non-ANSI mode the
rewritten tree is identical to <code class= [...]
</ul>
</section>
+<section id="unix-timestamp">
+<h2>unix_timestamp<a class="headerlink" href="#unix-timestamp" title="Link to
this heading">#</a></h2>
+<ul class="simple">
+<li><p>Spark 3.4.3 (audited 2026-09-13): baseline. String inputs accept
literal or column formats. Date, timestamp, and timestamp without time zone
inputs ignore the format argument.</p></li>
+<li><p>Spark 3.5.8 (audited 2026-09-13): parsing failures use structured
timestamp parsing errors.</p></li>
+<li><p>Spark 4.0.1 (audited 2026-09-13): <code class="docutils literal
notranslate"><span class="pre">inputTypes</span></code> widened to <code
class="docutils literal notranslate"><span
class="pre">StringTypeWithCollation</span></code> for the input and format
arguments.</p></li>
+<li><p>Spark 4.1.1 (audited 2026-09-13): same input types and parsing behavior
as Spark 4.0.1.</p></li>
+<li><p>String inputs use Spark’s generated parser through codegen dispatch,
including collated strings and formats. Literal and column formats preserve
null handling, ANSI errors, parser policy, and session time zone.</p></li>
+<li><p>Date, timestamp, and timestamp without time zone inputs retain native
execution and ignore the format, including its collation. String input stays
unsupported by the native serializer so <code class="docutils literal
notranslate"><span class="pre">allowIncompatible=true</span></code> cannot send
it to the native kernel.</p></li>
+<li><p>Native timestamp conversion truncates fractional seconds toward zero,
matching Spark’s <code class="docutils literal notranslate"><span
class="pre">ToTimestamp</span></code>. This fixes the previous use of floor
division for negative fractional timestamps: at UTC, <code class="docutils
literal notranslate"><span class="pre">1969-12-31</span> <span
class="pre">23:59:58.5</span></code> produces <code class="docutils literal
notranslate"><span class="pre">-1</span></code>, not <code [...]
+</ul>
+</section>
<section id="weekday">
<h2>weekday<a class="headerlink" href="#weekday" title="Link to this
heading">#</a></h2>
<ul class="simple">
@@ -762,6 +774,7 @@ under the License.
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#try-make-timestamp">try_make_timestamp</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#try-to-date">try_to_date</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#try-to-timestamp">try_to_timestamp</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#unix-timestamp">unix_timestamp</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#weekday">weekday</a></li>
</ul>
</nav></div>
diff --git a/contributor-guide/spark_configs_support.html
b/contributor-guide/spark_configs_support.html
index 0d6129721a..2854420739 100644
--- a/contributor-guide/spark_configs_support.html
+++ b/contributor-guide/spark_configs_support.html
@@ -658,7 +658,8 @@ Other formats route through the codegen dispatcher.</p></li>
<code class="docutils literal notranslate"><span
class="pre">spark.comet.expression.FromUnixTime.allowIncompatible=true</span></code>
is set; otherwise
it routes through the codegen dispatcher.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">unix_timestamp(<timestamp_or_date>)</span></code> does not
call the formatter at all; the
-string-input overload falls back.</p></li>
+string-input overload routes through the codegen dispatcher and preserves
Spark’s
+selected parser policy.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">to_unix_timestamp</span></code> routes through the codegen
dispatcher.</p></li>
</ul>
<p>If a Comet contributor adds native string-format parsing or extends the
date_format
diff --git a/searchindex.js b/searchindex.js
index 00d6ca6fac..38a2bd02d8 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles": {"!": [[56, "id1"]], "%": [[54, "id1"]], "&":
[[44, "id1"]], "*": [[54, "id2"]], "+": [[54, "id3"]], "-": [[54, "id4"]], "/":
[[54, "id5"]], "1. Format Your Code": [[41, "format-your-code"]], "1. Install
Comet": [[62, "install-comet"], [73, "install-comet"]], "1. Native Operators
(nativeExecs map)": [[28, "native-operators-nativeexecs-map"]], "2. Build and
Verify": [[41, "build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[62,
"clone-iceberg-and-apply- [...]
\ No newline at end of file
+Search.setIndex({"alltitles": {"!": [[56, "id1"]], "%": [[54, "id1"]], "&":
[[44, "id1"]], "*": [[54, "id2"]], "+": [[54, "id3"]], "-": [[54, "id4"]], "/":
[[54, "id5"]], "1. Format Your Code": [[41, "format-your-code"]], "1. Install
Comet": [[62, "install-comet"], [73, "install-comet"]], "1. Native Operators
(nativeExecs map)": [[28, "native-operators-nativeexecs-map"]], "2. Build and
Verify": [[41, "build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[62,
"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 3665ece74b..150ac54000 100644
--- a/user-guide/latest/compatibility/expressions/spark-3.4/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-3.4/datetime.html
@@ -913,9 +913,9 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
</section>
<section id="unixtimestamp">
<h2>UnixTimestamp<a class="headerlink" href="#unixtimestamp" title="Link to
this heading">#</a></h2>
-<p>The following cases are not supported by Comet and always fall back to
Spark, regardless of any <code class="docutils literal notranslate"><span
class="pre">allowIncompatible</span></code> setting:</p>
+<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 <code class="docutils literal notranslate"><span
class="pre">DateType</span></code>, <code class="docutils literal
notranslate"><span class="pre">TimestampType</span></code>, and <code
class="docutils literal notranslate"><span
class="pre">TimestampNTZType</span></code> inputs are supported.</p></li>
+<li><p>String inputs, including collated strings, have no native
implementation.</p></li>
</ul>
<!--END:EXPR_COMPAT-->
</section>
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 073485c3d4..bb7173fe1b 100644
--- a/user-guide/latest/compatibility/expressions/spark-3.5/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-3.5/datetime.html
@@ -913,9 +913,9 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
</section>
<section id="unixtimestamp">
<h2>UnixTimestamp<a class="headerlink" href="#unixtimestamp" title="Link to
this heading">#</a></h2>
-<p>The following cases are not supported by Comet and always fall back to
Spark, regardless of any <code class="docutils literal notranslate"><span
class="pre">allowIncompatible</span></code> setting:</p>
+<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 <code class="docutils literal notranslate"><span
class="pre">DateType</span></code>, <code class="docutils literal
notranslate"><span class="pre">TimestampType</span></code>, and <code
class="docutils literal notranslate"><span
class="pre">TimestampNTZType</span></code> inputs are supported.</p></li>
+<li><p>String inputs, including collated strings, have no native
implementation.</p></li>
</ul>
<!--END:EXPR_COMPAT-->
</section>
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 ce3ae0e092..a788fff54f 100644
--- a/user-guide/latest/compatibility/expressions/spark-4.0/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-4.0/datetime.html
@@ -938,13 +938,9 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
</section>
<section id="unixtimestamp">
<h2>UnixTimestamp<a class="headerlink" href="#unixtimestamp" title="Link to
this heading">#</a></h2>
-<p>The following incompatibilities cause <code class="docutils literal
notranslate"><span class="pre">UnixTimestamp</span></code> to fall back to
Spark by default. Set <code class="docutils literal notranslate"><span
class="pre">spark.comet.expression.UnixTimestamp.allowIncompatible=true</span></code>
to enable Comet acceleration despite these differences.</p>
-<ul class="simple">
-<li><p>unix_timestamp does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)</p></li>
-</ul>
-<p>The following cases are not supported by Comet and always fall back to
Spark, regardless of any <code class="docutils literal notranslate"><span
class="pre">allowIncompatible</span></code> setting:</p>
+<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 <code class="docutils literal notranslate"><span
class="pre">DateType</span></code>, <code class="docutils literal
notranslate"><span class="pre">TimestampType</span></code>, and <code
class="docutils literal notranslate"><span
class="pre">TimestampNTZType</span></code> inputs are supported.</p></li>
+<li><p>String inputs, including collated strings, have no native
implementation.</p></li>
</ul>
<!--END:EXPR_COMPAT-->
</section>
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 fb4cebe2b6..af7549d138 100644
--- a/user-guide/latest/compatibility/expressions/spark-4.1/datetime.html
+++ b/user-guide/latest/compatibility/expressions/spark-4.1/datetime.html
@@ -938,13 +938,9 @@ with Spark. For dates beyond this range, functions that
involve timezone-aware c
</section>
<section id="unixtimestamp">
<h2>UnixTimestamp<a class="headerlink" href="#unixtimestamp" title="Link to
this heading">#</a></h2>
-<p>The following incompatibilities cause <code class="docutils literal
notranslate"><span class="pre">UnixTimestamp</span></code> to fall back to
Spark by default. Set <code class="docutils literal notranslate"><span
class="pre">spark.comet.expression.UnixTimestamp.allowIncompatible=true</span></code>
to enable Comet acceleration despite these differences.</p>
-<ul class="simple">
-<li><p>unix_timestamp does not support non-UTF8_BINARY collations
(https://github.com/apache/datafusion-comet/issues/4646)</p></li>
-</ul>
-<p>The following cases are not supported by Comet and always fall back to
Spark, regardless of any <code class="docutils literal notranslate"><span
class="pre">allowIncompatible</span></code> setting:</p>
+<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 <code class="docutils literal notranslate"><span
class="pre">DateType</span></code>, <code class="docutils literal
notranslate"><span class="pre">TimestampType</span></code>, and <code
class="docutils literal notranslate"><span
class="pre">TimestampNTZType</span></code> inputs are supported.</p></li>
+<li><p>String inputs, including collated strings, have no native
implementation.</p></li>
</ul>
<!--END:EXPR_COMPAT-->
</section>
diff --git a/user-guide/latest/expressions.html
b/user-guide/latest/expressions.html
index d5f6619b92..879f9c3c83 100644
--- a/user-guide/latest/expressions.html
+++ b/user-guide/latest/expressions.html
@@ -1905,8 +1905,8 @@ expressions. The following function families are
<strong>not currently planned</
</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">unix_timestamp</span></code></p></td>
<td><p>✅</p></td>
-<td><p>Native</p></td>
-<td><p></p></td>
+<td><p>Hybrid</p></td>
+<td><p>String parsing uses Spark’s codegen and honors the time parser policy,
ANSI mode, and session time zone. Date and timestamp inputs ignore the format
and use native execution.</p></td>
</tr>
<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">weekday</span></code></p></td>
<td><p>✅</p></td>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
