Weekly update¶
This week we:
- Brought a new UX to multi-dimensional datasets (cubes), including support in SDKs
- Refactored the custom package config toolkit to be language-agnostic, using Pkl
- Simplified usability of some methods, and fixed numerous bugs
Custom types¶
The new user experience for multi-dimensional datasets (cubes) is now live. These can now be ingested and manipulated via SDKs, and are visible with their own dedicated types and navigation in the user interface.
Python¶
We've added:
- Methods to update enumerations with additional valid values.
- Methods to retrieve a specific type definition from Atlan, by its name.
- An option to propagate tags only through lineage (not hierarchies).
We've fixed:
- When attempting to retrieve an enumeration that does not exist from the cache, the SDK now raises a
NotFoundError
(consistent with the way the other caches behave). - An issue where certain structs could cause errors during marshalling and unmarshalling.
- The logic used to generate qualifiedNames for lineage processes, to ensure they are still contained within a connection even if using a generated (hashed) ID.
Kotlin (and Java)¶
We've added:
- The ability to exclude users from search log requests (most viewed assets, most recent viewers, etc).
- Methods to update enumerations with additional valid values.
- An option to propagate tags only through lineage (not hierarchies).
We've fixed:
- Tracking of failed assets during batch operations.
- A missing icon, without which there could be errors during serialization and deserialization of Atlan tags.
- An issue where certain structs could cause errors during serialization and deserialization.
Custom packages¶
We've fixed:
- A
NullPointerException
that could occur when invalid connections exist in a tenant. - An issue in the lineage builder package that was incorrectly parsing any extra fields when using a non-comma-delimited CSV as the input file.
We've improved:
- The admin export package now includes the user-provided designation (role) selected by a user during their initial registration.
Toolkit¶
We've refactored the experimental custom package config toolkit. It now relies entirely on Pkl, so has no language-specific dependencies. This should improve maintainability, speed at which we can add features to the toolkit, and consistency of defining custom packages irrespective of the language chosen to implement their logic.
Atlanian use only
For now, this is for Atlanian use only, but we hope to open it up more broadly in the future.