2.2.0
·
7 commits
to release/2.1
since this release
Release notes
- These release notes provide information about new features, fixes, and updates that are included in the latest update release.
- We often roll out features (and sometimes even fixes) to Current over a period of time. If you don’t see something described below right away, you can expect it soon
ADB to Purview Connector Solution Accelerator - Version 2.2
Version 2.2
Features
- Improved the search matching with PR #119 and PR #124
- PR #119 prioritize resource sets first regardless of the top search match returned by Microsoft Purview
query
api. - This can be deactivated by setting the app setting
prioritizeFirstResourceSet
tofalse
.
- PR #119 prioritize resource sets first regardless of the top search match returned by Microsoft Purview
- For very large spark plans, you can remove them from the Atlas / Microsoft Purview payload by setting the app setting
maxQueryPlanSize
to the maximum number of bytes you want to allow.- The maximum size in bytes for event hub is 1 MB
- If you commonly have large, complex queries, you should consider setting the
maxQueryPlanSize
to some value under 1000000.
Major Bug Fixes
- Corrected possible race condition in ARM template with PR #114 (contributed by community member! Thank you!!)
- Removed the ARM template parameter
listenToMessagesFromPurviewKafka
since it was unused and causing confusion with PR #122 .
Other
- Added documentation for enabling Private Endpoints manually.
Upgrade from 2.1 to 2.2
OpenLineage / Databricks Installation
You will need to deploy the updated function code to Azure. You can do so by:
- Cloning the repo and deploying via VS code's Azure Functions Extension.
- Using the Azure CLI to do a zip push deployment with the 2.2.0 zip release artifact.
az functionapp deployment source config-zip \ -g <RESOURCE_GROUP_NAME> \ -n <FUNCTION_SERVICE_NAME> \ --src <PATH_TO_RELEASE_ZIP_FILE>
Changes to Function App Settings
- There were no changes to the
OlToPurviewMappings
file.