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 23c6399711 Website updated to 674c410
23c6399711 is described below
commit 23c63997115c3f5cd6cbbb6752a92d7ba14b3753
Author: jenkins <[email protected]>
AuthorDate: Mon Oct 19 20:15:16 2026 +0000
Website updated to 674c410
---
manual/next/database/databases/snowflake.html | 2 +-
manual/next/logging/logging-basics.html | 19 ++++++++++++++++++-
.../beam-dataflow-pipeline-engine.html | 9 +++++++++
3 files changed, 28 insertions(+), 2 deletions(-)
diff --git a/manual/next/database/databases/snowflake.html
b/manual/next/database/databases/snowflake.html
index b425d1cc3e..c44f8e28e4 100644
--- a/manual/next/database/databases/snowflake.html
+++ b/manual/next/database/databases/snowflake.html
@@ -3046,7 +3046,7 @@ programmatically.</p>
<h3 id="_download_the_snowflake_jdbc_driver_an_crypto_libraries"><a
class="link"
href="#_download_the_snowflake_jdbc_driver_an_crypto_libraries">Download the
Snowflake JDBC driver an Crypto Libraries</a></h3>
<div class="paragraph">
<p><a href="https://repo1.maven.org/maven2/net/snowflake/snowflake-jdbc/";
target="_blank" rel="noopener">Download</a> a current Snowflake JDBC Driver.
-The filename has the naming pattern
<strong>snowflake-jdbc-3.19.0.jar</strong></p>
+The filename has the naming pattern
<strong>snowflake-jdbc-4.4.0.jar</strong></p>
</div>
<div class="paragraph">
<p>To support certificate based authentication, we also need to <a
href="https://www.bouncycastle.org/download/bouncy-castle-java-lts/";
target="_blank" rel="noopener">download</a>
diff --git a/manual/next/logging/logging-basics.html
b/manual/next/logging/logging-basics.html
index bed0b9e41c..6f5bc6bd5e 100644
--- a/manual/next/logging/logging-basics.html
+++ b/manual/next/logging/logging-basics.html
@@ -3046,7 +3046,24 @@ It is also possible to use the debug plugin to set
custom logging levels on a tr
<h2 id="_tools_logging"><a class="link" href="#_tools_logging">Tools
logging</a></h2>
<div class="sectionbody">
<div class="paragraph">
-<p>If you want to send logging of tools like hop-run or hop-conf to a logging
file you need to do this simply by piping the text stream to a file.</p>
+<p>Command line tools like hop-run, hop-conf and hop-server write their log to
the console.
+To keep it in a file, for example when Hop runs on a server, redirect the
output and the errors to a file.
+On Linux and macOS, this example writes every run to a new file named after
the current date and time:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<div class="code-lang" data-pagefind-ignore>bash</div><pre class="highlightjs
highlight is-highlighted"><code class="language-bash hljs"
data-lang="bash">./hop-run.sh -j my-project -r <span
class="hljs-built_in">local</span> -f my-workflow.hwf &> <span
class="hljs-string">"hop-run-<span class="hljs-subst">$(date
+%Y-%m-%d_%H-%M-%S)</span>.log"</span></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>On Windows, use <code>> hop-run.log 2>&1</code> after the
command.</p>
+</div>
+<div class="paragraph">
+<p><a href="../hop-run/index.html" class="xref page">hop-run</a> can also
write its log to a file itself, with <code>--logfile</code>.</p>
+</div>
+<div class="paragraph">
+<p>Behind the scenes Hop also sends its log to SLF4J, with Log4j2.
+To change the format or send the log to another system, bring your own Log4j2
configuration, as described in <a
href="../../../dev-manual/next/architecture/logging-and-debugging.html#_slf4j_and_the_log4j2_binding"
class="xref page">SLF4J and the Log4j2 binding</a> in the developer manual.</p>
</div>
</div>
</div>
diff --git
a/manual/next/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.html
b/manual/next/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.html
index 3cb54754b4..af62f9b67c 100644
---
a/manual/next/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.html
+++
b/manual/next/pipeline/pipeline-run-configurations/beam-dataflow-pipeline-engine.html
@@ -3060,6 +3060,15 @@ Must be a valid Cloud Storage URL, beginning with gs://.
This is a different option from the general <code>Temp location</code>
below.</p></td>
</tr>
<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">GCS upload
buffer size (MB)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The size,
in megabytes, of the chunks in which files are uploaded to Cloud Storage, from
1 to 1024.
+Each chunk is a separate request, so a larger size makes staging the fat jar
faster, especially on high-latency connections.
+128 MB is a good value for staging.
+When left empty, Apache Beam’s default is used, which stages in chunks
of 1 MB and so limits staging to about 1 MB per request round trip.
+The size is passed to the workers as well: every file they write to Cloud
Storage, for example file output or BigQuery file loads, holds one buffer of
this size in memory.
+Keep it moderate when a pipeline writes many files at the same time.</p></td>
+</tr>
+<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Initial
number of workers</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">The
initial number of Google Compute Engine instances to use when executing your
pipeline.
This option determines how many workers the Dataflow service starts up when
your job begins.</p></td>
