[release] Bumped to release 9.7.0#921
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release notes prepended to
HISTORY.md;pyatlan/version.txtbumped from9.6.0→9.7.0.9.7.0 (April 30, 2026)
New Features
GENERIC_OPENLINEAGEconnector type: AddedAtlanConnectorType.GENERIC_OPENLINEAGE = ("generic-openlineage", AtlanConnectionCategory.ELT)so the SDK can target the marketplacegeneric-openlineage(GOLC) ingestion endpoint at/events/openlineage/generic-openlineage/api/v1/lineage. Mirrored inpyatlan_v9.OpenLineageEvent.emit()acceptsconnector_type:emit()andemit_async()now take an optionalconnector_typekwarg (defaulting toSPARK), matching the pattern already used byemit_raw()/emit_raw_async(). Removes the previous hardcoded SPARK assumption so callers can route events to any OpenLineage-compatible connector.Bug Fixes
DbtMeasureextendsSemanticMeasure, notDbt: The Atlas type hierarchy isDbtMeasure → SemanticMeasure → Semantic, but the generator pickedDbtas the Python parent because the typedef listssuperTypes=["Dbt", "SemanticMeasure"](Dbt first). This brokeatlan-publish-app's ordering graph —DbtSemanticModel → DbtMeasureedges were never created via thesemantic_measuresrelationship, causing publish to fail with ATLAS-404 onsemanticModellookup. Sibling types (DbtDimension(SemanticDimension),DbtEntity(SemanticEntity)) already follow this pattern. Fix changes the parent class indbt_measure.pyand adds_SUPERCLASS_OVERRIDEStoclass_generator.py+ a Jinja template change so future regenerations preserve the fix. Includes 7 regression tests.Experimental:
pyatlan_v9Test plan
pytest tests/unit -qpasses./qa-checkspasses (ruff format / ruff check / mypy)