chore(deps): Bump io.openlineage:openlineage-java from 1.50.0 to 1.51.0

[dependabot]

Bumps io.openlineage:openlineage-java from 1.50.0 to 1.51.0.

Changelog

Sourced from io.openlineage:openlineage-java's changelog.

1.51.0

Added

• Dbt: Capture dbt model meta/config values [#4653](https://github.com/OpenLineage/OpenLineage/issues/4653) @​mobuchowski Capture per-model config values (e.g. materialized, access, owner, group) and the user-defined meta map from the dbt manifest into a new dbt_model dataset facet, attached in both the legacy/local and structured-logs dbt processors.
• Spark: Add support for open source Unity Catalog (Spark 4.0) [#3674](https://github.com/OpenLineage/OpenLineage/issues/3674) @​arturowczarek Add a catalog handler for the open source Unity Catalog's UCSingleCatalog Spark catalog so output dataset facets are produced when using OSS Unity Catalog, which cannot reuse the existing DeltaHandler implementation.
• Spec: Extend jobTypeJobFacet to capture event emission lifecycle [#4592](https://github.com/OpenLineage/OpenLineage/issues/4592) @​jakub-moravec Extend the Job Type facet so producers, particularly streaming producers that emit a single event covering a time period rather than START/RUNNING/COMPLETE events, can document the lifecycle of the OpenLineage events consumers should expect.

Fixed

• Spark: Fix missing output lineage for insertInto with append mode [#4676](https://github.com/OpenLineage/OpenLineage/issues/4676) @​mishrasangeeta87 Fix a bug where df.write.mode("append").insertInto(table) did not emit an output dataset, by extracting the target table directly from the AppendData logical plan, aligning append-mode handling with overwrite-mode.
• Spark: Fix Unity Catalog symlink metadata on Databricks [#4660](https://github.com/OpenLineage/OpenLineage/issues/4660) @​mishrasangeeta87 Build Databricks Unity Catalog table symlinks using the fully qualified table name and a unity-catalog namespace instead of one derived from the underlying storage path, giving lineage consumers stable, catalog-qualified identifiers.
• Client/Java: Change shaded paths to avoid conflicts when using composite transport [#4652](https://github.com/OpenLineage/OpenLineage/issues/4652) @​tnazarew Relocate shaded classes per-transport (e.g. io.openlineage.client.transports.gcs.shaded.x) instead of to a single shared shaded package, fixing Google library version conflicts when combining gcs and gcplineage transports in a composite transport.
• Client/Java: Normalize abfs/wasb to abfss/wasbs in ObjectStorageDatasetExtractor [#4661](https://github.com/OpenLineage/OpenLineage/issues/4661) @​arturowczarek Treat abfs:// and wasb:// URIs the same as their TLS variants (abfss/wasbs) when deriving the object-storage namespace, since they point at the same underlying files and only differ in transport.
• Client/Java: Stop swallowing actual cause when using CompositeTransport [#4666](https://github.com/OpenLineage/OpenLineage/issues/4666) @​mobuchowski Preserve the underlying exception instead of only its message when a CompositeTransport emit fails, so the real cause is visible instead of being lost.
• Common: Handle trailing command options [#4624](https://github.com/OpenLineage/OpenLineage/issues/4624) @​hcthakur2004 Avoid indexing past the end of command-line arguments when a trailing option has no value.
• Common: Preserve nullable chain input [#4627](https://github.com/OpenLineage/OpenLineage/issues/4627) @​hcthakur2004 Avoid mutating the caller-provided chain in get_from_nullable_chain, keeping it reusable after lookup.
• GreatExpectations: Preserve datasource URL ports [#4679](https://github.com/OpenLineage/OpenLineage/issues/4679) @​hcthakur2004 Preserve the port on a datasource URL when Great Expectations strips credentials from it.
• Python: Isolate Datadog config defaults [#4586](https://github.com/OpenLineage/OpenLineage/issues/4586) @​hcthakur2004 Replace shared, mutable Datadog config dictionary defaults with per-instance factories so retry and async transport rule defaults aren't accidentally shared across instances.
• Python: Support file URI transport paths [#4656](https://github.com/OpenLineage/OpenLineage/issues/4656) @​hcthakur2004 Normalize local file:// URIs before opening file transport paths so events can be appended through a file:// log path.
• Spark: Fix Iceberg handler detection to probe SparkCatalog instead of Catalog [#4665](https://github.com/OpenLineage/OpenLineage/issues/4665) @​arturowczarek Detect Iceberg by the presence of the iceberg-spark SparkCatalog class rather than iceberg-core's Catalog, so the Iceberg handler no longer activates in environments where iceberg-core is on the classpath without iceberg-spark.

Commits

• 3fad7be Prepare for release 1.51.0
• 97e1e4b changelog for release 1.51.0 (#4693)
• 8af99be fix(great-expectations): preserve datasource url ports (#4679)
• b574c9a fix(dependabot): correctly exclude spark bumps that break the build (#4688)
• 468d9c3 build(deps): bump click from 8.4.1 to 8.4.2 in /dev in the dev group (#4685)
• d5be392 build(deps): bump the website group in /website with 5 updates (#4686)
• 52ae142 build(deps): bump golang.org/x/net from 0.50.0 to 0.55.0 in /client/go (#4681)
• 7b0383b build(deps): bump the client-java group in /client/java with 10 updates (#4684)
• 490f315 feat(spark): support open source Unity Catalog (spark40) (#3674)
• eac1232 build(deps): bump the client-java group across 1 directory with 15 updates (#...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: maven org.apache.httpcomponents.core5:httpcore5 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → maven/software.amazon.awssdk/s3@2.46.15 → maven/org.apache.httpcomponents.core5/httpcore5@5.4.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.apache.httpcomponents.core5/httpcore5@5.4.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report