Skip to content

v2.5 - Search and lineage improvements
Compare
Choose a tag to compare
@cmgrote cmgrote released this 16 Dec 15:27
v2.5
84d7bed
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

🎉 New features

  • Adds stage variable lineage handling to the DataStage connector
  • Implements independent process hierarchy handling to improve efficiency of DataStage connector
  • Improves paging consistency for IGC searches, by defaulting to a sort by GUID if no other sort criteria is specified
  • Allows searching IGC based on instance header properties (eg. updateTime, createdBy, etc)
  • Adds a limitToLineageEnabledJobs parameter to the DataStage connector to only include jobs for which lineage is enabled

🐞 Bug fixes

  • Fixes an issue where the lineage mappings included for a stage were not limited to that stage's input / output data stores
  • Fixes issues handling embedded fields (deflated:...) and consistency in qualifiedNames in the DataStage connector
  • Addresses edge cases searching for hosts and users in IGC
  • Improves logging of underlying IGC REST client library (by propagating checked exceptions)
  • Avoids producing any relationship from IGC where one end of the relationship is unmapped (avoiding relationships with null ends)
  • Fixes issue where a search by property against IGC without criteria caused an NPE

🔒 Security fixes

  • Adds a maximum length validation to qualifiedNames before attempting to blindly tokenize them

🔨 Dependencies

Assets 2
Loading