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 e10ab06106 Website updated to 674c410
e10ab06106 is described below
commit e10ab06106ed296fbd69509cc695c77382765307
Author: jenkins <[email protected]>
AuthorDate: Wed Oct 21 10:23:34 2026 +0000
Website updated to 674c410
---
dev-manual/next/lineage.html | 7 +++++--
manual/next/technology/openlineage/index.html | 4 ++++
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/dev-manual/next/lineage.html b/dev-manual/next/lineage.html
index fc7685ba95..8ac2f14c79 100644
--- a/dev-manual/next/lineage.html
+++ b/dev-manual/next/lineage.html
@@ -779,7 +779,7 @@ what Hop emits — worth knowing before investigating a
dataset that looks empty
<p><strong>Timestamp</strong> — Milliseconds since epoch.</p>
</li>
<li>
-<p><strong><code>LineageEventKind</code></strong> — One of
<code>RUN_LIFECYCLE</code>, <code>TRANSFORM_SCHEMA</code>,
<code>FILE_IO</code>, <code>RELATIONAL_IO</code>, <code>HTTP_IO</code>.</p>
+<p><strong><code>LineageEventKind</code></strong> — One of
<code>RUN_LIFECYCLE</code>, <code>TRANSFORM_SCHEMA</code>,
<code>FILE_IO</code>, <code>RELATIONAL_IO</code>, <code>HTTP_IO</code>,
<code>PIPELINE_GRAPH</code>. New kinds are only ever appended: a sink must skip
a kind it does not handle rather than fail the batch.</p>
</li>
<li>
<p><strong><code>LineageContext</code></strong> — Who/what produced the
observation (see above).</p>
@@ -807,6 +807,9 @@ what Hop emits — worth knowing before investigating a
dataset that looks empty
<p><strong><code>RunLifecycleLineagePayload</code></strong> —
<code>STARTED</code> / <code>FINISHED</code> plus optional detail text.</p>
</li>
<li>
+<p><strong><code>PipelineGraphLineagePayload</code></strong> — The
pipeline’s hop graph as a list of <code>from</code> → <code>to</code>
transform-name transitions: enabled hops with both ends named, in pipeline
order. Informational hops are included. A sink uses it to attribute datasets to
the transform that touched them and to propagate them along the graph, instead
of pairing all of a pipeline’s inputs with all of its outputs.</p>
+</li>
+<li>
<p><strong><code>TransformSchemaLineagePayload</code></strong> —
<code>INPUT</code> or <code>OUTPUT</code> plus a list of field names, Hop type
names, length, and precision (boundary schema; emitted when a transform
finishes). Fields usually come from runtime row metadata on the transform or
row sets. If input was never observed (e.g. <em>Abort</em> when
<code>getRow()</code> immediately returns null), input is derived via
<code>PipelineMeta#getPrevTransformFields</code>. If output was n [...]
</li>
</ul>
@@ -864,7 +867,7 @@ what Hop emits — worth knowing before investigating a
dataset that looks empty
<div class="ulist">
<ul>
<li>
-<p><strong><code>PipelineStart</code></strong> —
<code>LineageHubPipelineStartXp</code> — phase <code>STARTED</code></p>
+<p><strong><code>PipelineStart</code></strong> —
<code>LineageHubPipelineStartXp</code> — phase <code>STARTED</code>, followed
by one <code>PIPELINE_GRAPH</code> event with the same context when the
pipeline has enabled hops. <code>PipelineStart</code> fires after the transform
threads have started, so the run’s transform <code>STARTED</code> events,
and early I/O such as a Table Input read, can arrive before the graph, possibly
in an earlier batch. A sink that uses the graph colle [...]
</li>
<li>
<p><strong><code>PipelineFinish</code></strong> —
<code>LineageHubPipelineFinishXp</code> — phase <code>FINISHING</code>
(transforms stopped, cleanup)</p>
diff --git a/manual/next/technology/openlineage/index.html
b/manual/next/technology/openlineage/index.html
index 168c154fbf..afc963d022 100644
--- a/manual/next/technology/openlineage/index.html
+++ b/manual/next/technology/openlineage/index.html
@@ -3161,6 +3161,10 @@ properties if needed.</p>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>HTTP_IO</code></p></td>
<td class="tableblock halign-left valign-top"><p
class="tableblock">Skipped.</p></td>
</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>PIPELINE_GRAPH</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Skipped.
Datasets stay on the pipeline job.</p></td>
+</tr>
</tbody>
</table>
<div class="paragraph">
