This is an automated email from the ASF dual-hosted git repository.
hansva pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/hop.git
The following commit(s) were added to refs/heads/main by this push:
new 09e3b18c57 Spark pages: local[*] as a passthrough so the asterisk no
longer starts bold text. #9235 (#9236)
09e3b18c57 is described below
commit 09e3b18c570a039e0ec4b0df5f75a8d856d79493
Author: Adalennis <[email protected]>
AuthorDate: Tue Nov 3 11:07:27 2026 +0100
Spark pages: local[*] as a passthrough so the asterisk no longer starts
bold text. #9235 (#9236)
---
.../native-spark-pipeline-engine.adoc | 12 ++++++------
.../pipeline/spark/cluster-mapping-walkthrough.adoc | 2 +-
.../ROOT/pages/pipeline/spark/databricks.adoc | 2 +-
.../spark/getting-started-with-native-spark.adoc | 20 ++++++++++----------
.../modules/ROOT/pages/pipeline/spark/lakehouse.adoc | 6 +++---
.../pipeline/spark/local-standalone-cluster.adoc | 6 +++---
.../pages/pipeline/spark/paths-and-filesystems.adoc | 2 +-
.../pages/pipeline/transforms/spark-file-input.adoc | 2 +-
.../pages/pipeline/transforms/spark-file-output.adoc | 4 ++--
.../pipeline/transforms/spark-lake-table-input.adoc | 2 +-
10 files changed, 29 insertions(+), 29 deletions(-)
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/native-spark-pipeline-engine.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/native-spark-pipeline-engine.adoc
index 9b98824b65..9b270756e5 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/native-spark-pipeline-engine.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/native-spark-pipeline-engine.adoc
@@ -26,7 +26,7 @@ under the License.
The native Spark pipeline engine executes batch Hop pipelines on *Apache Spark
4.1.x* without Apache Beam.
It builds a Spark SQL Dataset graph from the pipeline and runs transforms via
native Dataset operators or generic `mapPartitions` mini-pipelines.
-For a full introduction — concepts, `local[*]`, fat jar, `spark-submit`, Spark
File I/O, `${Internal.Transform.ID}`, metrics, limitations, and
integration-test examples — see
+For a full introduction — concepts, `+local[*]+`, fat jar, `spark-submit`,
Spark File I/O, `${Internal.Transform.ID}`, metrics, limitations, and
integration-test examples — see
xref:pipeline/spark/getting-started-with-native-spark.adoc[Getting started
with the native Spark pipeline engine].
Paths on *Spark File* and *Lake Table* transforms are **Spark/Hadoop URIs**,
not Hop VFS schemes — see
@@ -39,7 +39,7 @@
image::pipeline/spark/native-spark-pipeline-engine-run-configurtion-editor.png[N
=== Requirements
* Java 21
-* Spark 4.1.x (bundled under `plugins/engines/spark/lib` for `local[*]`)
+* Spark 4.1.x (bundled under `plugins/engines/spark/lib` for `+local[*]+`)
=== Options
@@ -47,10 +47,10 @@
image::pipeline/spark/native-spark-pipeline-engine-run-configurtion-editor.png[N
Use **Load configuration template** to fill the fields below from a common
deployment style:
-* *Local execution* — `local[*]`, Spark UI off (embedded Spark in Hop)
+* *Local execution* — `+local[*]+`, Spark UI off (embedded Spark in Hop)
* *Local (capped cores)* — `local[4]`
* *Spark standalone server* — `spark://host:7077` (replace host), sample
driver/executor memory. Also set *Fat jar file location* to a `native-provided`
fat jar; the template leaves it empty. See
xref:pipeline/spark/local-standalone-cluster.adoc[Local standalone cluster].
-* *spark-submit (cluster)* — master **empty** so `spark-submit --master` wins;
use a `native-provided` fat jar. Outside `spark-submit` (Hop GUI, `hop-run`,
Hop Server) an empty master runs on `local[*]` in that process, and the log
warns about it.
+* *spark-submit (cluster)* — master **empty** so `spark-submit --master` wins;
use a `native-provided` fat jar. Outside `spark-submit` (Hop GUI, `hop-run`,
Hop Server) an empty master runs on `+local[*]+` in that process, and the log
warns about it.
* *Databricks* — submit-oriented placeholders (master empty); set
workspace-specific values yourself
* *YARN client* — master `yarn`, client deploy mode. Also set *Hadoop
configuration folder* (or `HADOOP_CONF_DIR`) and a `native-provided` fat jar.
See xref:pipeline/spark/yarn.adoc[Run native Spark pipelines on YARN].
* *Lakehouse local* — same as local; Delta/Iceberg connectors live on the
plugin classpath
@@ -64,8 +64,8 @@ For named Iceberg/Delta catalogs used by Lake Table
transforms in **TABLE** mode
|Option |Description |Default
|Spark master
-|Spark master URL: `local[*]`, `local[4]`, `spark://host:7077` or `yarn`.
Leave empty under `spark-submit` so the CLI master is used; outside
`spark-submit` an empty master runs on `local[*]`.
-|`local[*]`
+|Spark master URL: `+local[*]+`, `local[4]`, `spark://host:7077` or `yarn`.
Leave empty under `spark-submit` so the CLI master is used; outside
`spark-submit` an empty master runs on `+local[*]+`.
+|`+local[*]+`
|Application name
|Spark application name.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/cluster-mapping-walkthrough.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/cluster-mapping-walkthrough.adoc
index 4b1fb032e2..6156f2771a 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/cluster-mapping-walkthrough.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/cluster-mapping-walkthrough.adoc
@@ -21,7 +21,7 @@ under the License.
= Cluster demo walk-through (Native Spark)
-This walk-through shows that the Native Spark **project package** design works
on a *real multi-node* Spark 4.1 cluster — not only on `local[*]`.
+This walk-through shows that the Native Spark **project package** design works
on a *real multi-node* Spark 4.1 cluster — not only on `+local[*]+`.
You will:
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/databricks.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/databricks.adoc
index 3b2f02ac7b..611a82012d 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/databricks.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/databricks.adoc
@@ -26,7 +26,7 @@ This page captures practical lessons for running **Hop native
Spark** pipelines
It is not a full Databricks admin guide. It focuses on what usually goes wrong
when connecting Hop to Free / trial / serverless-oriented workspaces versus a
**classic-cluster-capable** (e.g. Premium) workspace suitable for Spark 4.1 and
modern Java.
-For general native Spark concepts (engine, fat jar, `local[*]` first), start
with
+For general native Spark concepts (engine, fat jar, `+local[*]+` first), start
with
xref:pipeline/spark/getting-started-with-native-spark.adoc[Getting started
with the native Spark engine].
== Sample project shape
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/getting-started-with-native-spark.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/getting-started-with-native-spark.adoc
index e8cf2a44ce..2ca4429486 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/getting-started-with-native-spark.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/getting-started-with-native-spark.adoc
@@ -26,7 +26,7 @@ under the License.
This guide is for data engineers who already know the basics of Hop pipelines
(transforms, hops, run configurations, metadata) and want to run *batch*
pipelines on https://spark.apache.org[Apache Spark] using Hop’s *native* Spark
engine.
-It walks you from “what is this?” through a `local[*]` first run, cluster
`spark-submit`, Spark-oriented I/O, metrics, limitations, and concrete examples
from the `integration-tests/spark-native` project.
+It walks you from “what is this?” through a `+local[*]+` first run, cluster
`spark-submit`, Spark-oriented I/O, metrics, limitations, and concrete examples
from the `integration-tests/spark-native` project.
For **Delta Lake** and **Apache Iceberg** (ACID tables, catalogs, time travel,
MERGE, maintenance), see the dedicated
xref:pipeline/spark/lakehouse.adoc[lakehouse guide] after you have a working
native Spark run configuration.
@@ -125,7 +125,7 @@ You still design pipelines *visually* in Hop. Spark’s role
is the distributed
====
*Java:* Hop requires *Java 21* for the GUI, `hop-run`, and the fat jar
executed on the Spark driver/executors. Your Spark cluster must also run a JVM
that can load that bytecode (Java 21).
-*Spark:* The native engine is built and tested against *Spark 4.1.x*
(currently *4.1.3* in the Hop source tree, Scala *2.13*). For `local[*]` runs,
Spark libraries are packaged under `plugins/engines/spark/lib`, so you do *not*
need a separate Spark install on your laptop.
+*Spark:* The native engine is built and tested against *Spark 4.1.x*
(currently *4.1.3* in the Hop source tree, Scala *2.13*). For `+local[*]+`
runs, Spark libraries are packaged under `plugins/engines/spark/lib`, so you do
*not* need a separate Spark install on your laptop.
====
[options="header",cols="1,1,2,2"]
@@ -159,9 +159,9 @@ Do *not* mix this engine with Beam’s Spark 3.5 fat-jar
packs or an accidental
== How to use it
-=== Create a `local[*]` pipeline run configuration
+=== Create a `+local[*]+` pipeline run configuration
-This is the fastest way to learn: Spark runs *inside* the Hop process using
all local cores (`local[*]`), with no cluster and no fat jar.
+This is the fastest way to learn: Spark runs *inside* the Hop process using
all local cores (`+local[*]+`), with no cluster and no fat jar.
TIP: On the Native Spark engine options tab, **Load configuration template**
can pre-fill common setups (*Local execution*, *Spark standalone server*,
*spark-submit*, *Databricks*, *YARN*, …). See
xref:pipeline/pipeline-run-configurations/native-spark-pipeline-engine.adoc[Native
Spark pipeline engine].
@@ -177,13 +177,13 @@ TIP: For Iceberg **TABLE** mode, create a
xref:metadata-types/spark-catalog.adoc
|Option |Suggested first value
|Spark master
-|`local[*]` (or `local[4]` to cap cores)
+|`+local[*]+` (or `local[4]` to cap cores)
|Application name
|`Apache Hop` (or your project name)
|Fat jar file location
-|Leave *empty* for pure `local[*]`
+|Leave *empty* for pure `+local[*]+`
|Spark config
|Optional; one `key=value` per line (advanced tuning)
@@ -204,7 +204,7 @@
image::pipeline/spark/native-spark-pipeline-engine-run-configurtion-editor.png[N
Full option reference:
xref:pipeline/pipeline-run-configurations/native-spark-pipeline-engine.adoc[Native
Spark pipeline engine].
-=== First pipeline on `local[*]`
+=== First pipeline on `+local[*]+`
. Create a small batch pipeline, for example:
** *Spark file input* — CSV path under your project, header and separator,
field list
@@ -409,7 +409,7 @@ Common options:
|Option |Notes
|Spark path (Hadoop URI)
-|File, directory, or glob visible to Spark (local path on `local[*]`; cluster
URI such as `hdfs://…` or `s3a://…` on submit). **Not** a Hop VFS path — see
xref:pipeline/spark/paths-and-filesystems.adoc[Paths and file systems].
+|File, directory, or glob visible to Spark (local path on `+local[*]+`;
cluster URI such as `hdfs://…` or `s3a://…` on submit). **Not** a Hop VFS path
— see xref:pipeline/spark/paths-and-filesystems.adoc[Paths and file systems].
|Format
|`csv`, `parquet`, `json`, `orc`, `text`
@@ -533,7 +533,7 @@ If the location is file-based and you need *samples from
cluster workers*, the r
On **Databricks**, a practical pattern is a **Caching File** location whose
root is a named Databricks VFS URI on a UC Volume (driver writes execution JSON
via the Files API; laptop GUI opens the same location). Walkthrough:
xref:pipeline/spark/databricks.adoc#exec-info-on-volume[Execution information
on a UC Volume].
-On `local[*]`, Spark’s Jackson libraries must not shadow Hop’s Jackson under
the plugin classloader. The Spark plugin packaging excludes core Jackson jars
so sampling and `HopJson` keep working.
+On `+local[*]+`, Spark’s Jackson libraries must not shadow Hop’s Jackson under
the plugin classloader. The Spark plugin packaging excludes core Jackson jars
so sampling and `HopJson` keep working.
== How transforms map to Spark
@@ -703,7 +703,7 @@ image::pipeline/spark/spark-native-0099-complex.png[0099
complex sample,width=95
* [ ] Java 21; Hop 2.19+ with `plugins/engines/spark`
* [ ] Run configuration engine = *Native Spark* (not Beam Spark)
-* [ ] First success on `local[*]` with Spark file input → transform → Spark
file output
+* [ ] First success on `+local[*]+` with Spark file input → transform → Spark
file output
* [ ] Execution information location attached if you need history and samples
* [ ] Cluster: fat jar with `--spark-client-version=native-provided`
* [ ] Cluster: `SPARK_HOME` pinned to Spark *4.1.x*
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/lakehouse.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/lakehouse.adoc
index 7f798e1254..2d7330342f 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/lakehouse.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/lakehouse.adoc
@@ -25,7 +25,7 @@ under the License.
This guide covers **Delta Lake** and **Apache Iceberg** support on Hop’s
xref:pipeline/spark/getting-started-with-native-spark.adoc[native Spark
pipeline engine] (Spark *4.1.x*, no Beam).
-It assumes you already have a working *Native Spark* pipeline run
configuration (`local[*]` or cluster `spark-submit`). Classic file formats
(CSV, Parquet, JSON, ORC, text) stay on *Spark file input* / *Spark file
output*. Lakehouse work uses dedicated **Lake Table** transforms.
+It assumes you already have a working *Native Spark* pipeline run
configuration (`+local[*]+` or cluster `spark-submit`). Classic file formats
(CSV, Parquet, JSON, ORC, text) stay on *Spark file input* / *Spark file
output*. Lakehouse work uses dedicated **Lake Table** transforms.
== What you get
@@ -80,7 +80,7 @@ $HOP_HOME/plugins/engines/spark/lib/iceberg/ # Iceberg
runtime jar
`SparkPipelineEngine` builds `SparkSession` under that classloader (`lib/`
recursive + `dependencies.xml` folders). A sibling plugin folder alone is
**not** enough.
-hop-run / Hop Gui (`local[*]`) therefore need **no manual connector install**
after a normal Hop install or rebuild of `plugins/engines/spark`.
+hop-run / Hop Gui (`+local[*]+`) therefore need **no manual connector
install** after a normal Hop install or rebuild of `plugins/engines/spark`.
=== Shipped jar list
@@ -251,7 +251,7 @@ Injection keys are documented on each transform page.
Shared identity keys: `FOR
=== Quick PATH round-trip (Delta)
. Install Delta jars (see above) and restart Hop.
-. Create a *Native Spark* run configuration (`local[*]`).
+. Create a *Native Spark* run configuration (`+local[*]+`).
. Pipeline: *Row Generator* (or *Spark file input*) → *Lake table output*
** Format: `delta`
** Identifier mode: `PATH`
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/local-standalone-cluster.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/local-standalone-cluster.adoc
index f6774c009f..2bf48bcb8b 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/local-standalone-cluster.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/local-standalone-cluster.adoc
@@ -23,11 +23,11 @@ under the License.
= Run pipelines on a local Spark standalone cluster
-`local[*]` runs Spark inside the Hop process. A *standalone cluster* runs a
Spark master and one or more workers as separate processes, the way a real
cluster does: your pipeline is split into tasks, shipped to executors, and the
Hop code those tasks need travels in a fat jar.
+`+local[*]+` runs Spark inside the Hop process. A *standalone cluster* runs a
Spark master and one or more workers as separate processes, the way a real
cluster does: your pipeline is split into tasks, shipped to executors, and the
Hop code those tasks need travels in a fat jar.
This page sets up such a cluster on one machine and runs a pipeline on it from
Hop GUI or `hop-run`. Hop is the Spark *driver*: you design and start the
pipeline in Hop as usual, and the work runs on the workers.
-Do this after your first `local[*]` run (see
xref:pipeline/spark/getting-started-with-native-spark.adoc[Getting started with
the native Spark engine]). To submit with `spark-submit` inside Docker
containers instead, see the
xref:pipeline/spark/cluster-mapping-walkthrough.adoc[cluster demo
walk-through]. To run on a Hadoop YARN cluster, see
xref:pipeline/spark/yarn.adoc[Run native Spark pipelines on YARN].
+Do this after your first `+local[*]+` run (see
xref:pipeline/spark/getting-started-with-native-spark.adoc[Getting started with
the native Spark engine]). To submit with `spark-submit` inside Docker
containers instead, see the
xref:pipeline/spark/cluster-mapping-walkthrough.adoc[cluster demo
walk-through]. To run on a Hadoop YARN cluster, see
xref:pipeline/spark/yarn.adoc[Run native Spark pipelines on YARN].
== What you need
@@ -325,7 +325,7 @@ Every executor copies the fat jar twice:
|The project has a *Workflow Log* that lists specific workflows (the samples
project does), and the workflow was sent without its file. Turn on *Export
linked resources to server* in the remote workflow run configuration, or
disable the Workflow Log.
|The log shows `WARNING: run configuration '...' has no Spark master and this
pipeline does not run under spark-submit`
-|An empty *Spark master* means `local[*]` inside the Hop process (Hop GUI,
`hop-run` or Hop Server). Set the master, for example `spark://localhost:7077`.
The *spark-submit (cluster)* template leaves it empty on purpose, for
`spark-submit`.
+|An empty *Spark master* means `+local[*]+` inside the Hop process (Hop GUI,
`hop-run` or Hop Server). Set the master, for example `spark://localhost:7077`.
The *spark-submit (cluster)* template leaves it empty on purpose, for
`spark-submit`.
|===
== Related pages
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/paths-and-filesystems.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/paths-and-filesystems.adoc
index 6152c9eac8..00044b2ec1 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/paths-and-filesystems.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/spark/paths-and-filesystems.adoc
@@ -83,7 +83,7 @@ For the full list of Hop VFS schemes, see
xref:vfs.adoc[Virtual File Systems].
On Windows, Hadoop's local file system sets POSIX permissions by running
`winutils.exe` from `HADOOP_HOME` (or the `hadoop.home.dir` system property).
Spark file output hits that call when the commit creates the output directory.
With neither variable set, the write fails with `HADOOP_HOME and
hadoop.home.dir are unset`.
-When Hop creates the Spark session on Windows and `winutils.exe` is not
installed, local `file:///` reads and writes skip those permission changes.
Listing a directory during the output commit uses Java file checks as well.
Hadoop's own listing calls `NativeIO.Windows.access`, which needs `hadoop.dll`
and throws `UnsatisfiedLinkError` when that library is not installed. The files
keep the permissions of the Hop process. You do not need a Hadoop installation
for `local[*]`.
+When Hop creates the Spark session on Windows and `winutils.exe` is not
installed, local `file:///` reads and writes skip those permission changes.
Listing a directory during the output commit uses Java file checks as well.
Hadoop's own listing calls `NativeIO.Windows.access`, which needs `hadoop.dll`
and throws `UnsatisfiedLinkError` when that library is not installed. The files
keep the permissions of the Hop process. You do not need a Hadoop installation
for `+local[*]+`.
A `file:///` path is this same local file system. A variable such as
`+${PROJECT_HOME}+` is often stored as a `file:///` URI, and resolving it keeps
that prefix. Spark File Output passes the resolved URI to Hadoop. A drive path
such as `C:/output` uses the same file system.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-input.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-input.adoc
index 737f766e60..c2ef5a7faa 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-input.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-input.adoc
@@ -29,7 +29,7 @@ It is the bulk input of the native Spark engine: Spark reads
the files in parall
This transform is **not** available on the local Hop engine or on the Beam
engines.
-The path is a Spark/Hadoop `FileSystem` URI that must be visible to every
executor, **not** a Hop VFS path: a local path on `local[*]`, `hdfs://…` or
`s3a://…` on a cluster.
+The path is a Spark/Hadoop `FileSystem` URI that must be visible to every
executor, **not** a Hop VFS path: a local path on `+local[*]+`, `hdfs://…` or
`s3a://…` on a cluster.
Hop-only schemes such as `s3://`, `azure://` or a named MinIO connection do
not work here; see xref:pipeline/spark/paths-and-filesystems.adoc[Paths and
file systems] for the mapping and for the *Path scheme map* on the run
configuration.
== Options
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-output.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-output.adoc
index d070eca710..40fd4709a3 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-output.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-file-output.adoc
@@ -30,8 +30,8 @@ It is the bulk output of the native Spark engine: Spark
writes one part file per
This transform is **not** available on the local Hop engine or on the Beam
engines.
It is a leaf: the write is executed as a Spark action when the engine
materialises the pipeline, and no rows are passed on.
-The path is a Spark/Hadoop `FileSystem` URI that must be writable from every
executor, **not** a Hop VFS path: a local directory on `local[*]`, `hdfs://…`
or `s3a://…` on a cluster.
-On Windows, a `local[*]` path does not require `HADOOP_HOME` or
`winutils.exe`. See
xref:pipeline/spark/paths-and-filesystems.adoc#windows-local-paths[Windows and
local mode].
+The path is a Spark/Hadoop `FileSystem` URI that must be writable from every
executor, **not** a Hop VFS path: a local directory on `+local[*]+`, `hdfs://…`
or `s3a://…` on a cluster.
+On Windows, a `+local[*]+` path does not require `HADOOP_HOME` or
`winutils.exe`. See
xref:pipeline/spark/paths-and-filesystems.adoc#windows-local-paths[Windows and
local mode].
Spark always writes a **directory** of part files at that location, never a
single file with that name; see <<single-file>> below.
See xref:pipeline/spark/paths-and-filesystems.adoc[Paths and file systems] for
the scheme mapping and for the *Path scheme map* on the run configuration.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-lake-table-input.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-lake-table-input.adoc
index 836a1bfbed..2084f1eaf3 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-lake-table-input.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/spark-lake-table-input.adoc
@@ -54,7 +54,7 @@ The transform is part of the Lakehouse plugin
(`hop-tech-lakehouse`). On the nat
`TABLE` — catalog-qualified name (e.g. `lake.db.orders`).
|Table path
-|Used when mode is PATH. Must be visible to Spark workers (local path on
`local[*]`; shared URI on cluster).
+|Used when mode is PATH. Must be visible to Spark workers (local path on
`+local[*]+`; shared URI on cluster).
|Table identifier
|Used when mode is TABLE. Multi-part name: `catalog.namespace.table`.