This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hop-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 50a6c46323 Website updated to 2ff35d7
50a6c46323 is described below
commit 50a6c463231d1c41eb396ffc7820a3cf52c4775b
Author: jenkins <[email protected]>
AuthorDate: Sat Oct 24 10:20:21 2026 +0000
Website updated to 2ff35d7
---
manual/next/pipeline/spark/paths-and-filesystems.html | 17 +++++++++++++++++
manual/next/pipeline/transforms/spark-file-output.html | 3 ++-
2 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/manual/next/pipeline/spark/paths-and-filesystems.html
b/manual/next/pipeline/spark/paths-and-filesystems.html
index 0f050aa43b..3f4c08463f 100644
--- a/manual/next/pipeline/spark/paths-and-filesystems.html
+++ b/manual/next/pipeline/spark/paths-and-filesystems.html
@@ -3068,6 +3068,23 @@ Spark never calls <code>HopVfs</code> for Dataset
<code>load</code> / <code>save
</div>
</div>
<div class="sect1">
+<h2 id="windows-local-paths"><a class="link"
href="#windows-local-paths">Windows and local mode</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>On Windows, Hadoop’s local file system sets POSIX permissions by
running <code>winutils.exe</code> from <code>HADOOP_HOME</code> (or the
<code>hadoop.home.dir</code> system property). Spark file output hits that call
when the commit creates the output directory. With neither variable set, the
write fails with <code>HADOOP_HOME and hadoop.home.dir are unset</code>.</p>
+</div>
+<div class="paragraph">
+<p>When Hop creates the Spark session on Windows and <code>winutils.exe</code>
is not installed, local <code><a href="file:///"
class="bare">file:///</a></code> reads and writes skip those permission
changes. The files keep the permissions of the Hop process. You do not need a
Hadoop installation for <code>local[*]</code>.</p>
+</div>
+<div class="paragraph">
+<p>If <code>HADOOP_HOME</code> points at a directory that contains
<code>bin/winutils.exe</code>, Hop keeps Hadoop’s own local file system
and permissions are applied. To choose a file system yourself, set
<code>spark.hadoop.fs.file.impl</code> in the run configuration. That entry
wins.</p>
+</div>
+<div class="paragraph">
+<p><code>hdfs://</code> and <code>s3a://</code> paths are unchanged. They do
not use winutils.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_scheme_collision_matrix"><a class="link"
href="#_scheme_collision_matrix">Scheme collision matrix</a></h2>
<div class="sectionbody">
<table class="tableblock frame-all grid-all stretch">
diff --git a/manual/next/pipeline/transforms/spark-file-output.html
b/manual/next/pipeline/transforms/spark-file-output.html
index 95a08e7fd6..bd0e6d5bb3 100644
--- a/manual/next/pipeline/transforms/spark-file-output.html
+++ b/manual/next/pipeline/transforms/spark-file-output.html
@@ -3036,8 +3036,9 @@ It is a leaf: the write is executed as a Spark action
when the engine materialis
</div>
<div class="paragraph">
<p>The path is a Spark/Hadoop <code>FileSystem</code> URI that must be
writable from every executor, <strong>not</strong> a Hop VFS path: a local
directory on <code>local[<strong>]</code>, <code>hdfs://…</code> or
<code>s3a://…</code> on a cluster.
+On Windows, a <code>local[</strong>]</code> path does not require
<code>HADOOP_HOME</code> or <code>winutils.exe</code>. See <a
href="../spark/paths-and-filesystems.html#windows-local-paths" class="xref
page">Windows and local mode</a>.
Spark always writes a <strong>directory</strong> of part files at that
location, never a single file with that name; see <a
href="#single-file">Getting a single file</a> below.
-See <a href="../spark/paths-and-filesystems.html" class="xref page">Paths and
file systems</a> for the scheme mapping and for the *Path scheme map</strong>
on the run configuration.</p>
+See <a href="../spark/paths-and-filesystems.html" class="xref page">Paths and
file systems</a> for the scheme mapping and for the <strong>Path scheme
map</strong> on the run configuration.</p>
</div>
</div>
</div>
