Version Compatibility Considerations for Ingestion and Action Frameworks in UI-based DataHub Ingestions

Original Slack Thread

Hello <@U06TM7M40RK>
I would like to know, if there is some recommendation for the version of ingestion framework to use in UI-based ingestions (action pod).
Should I stick to the minor version of the DATAHUB version I am using, or better take a newer one to have latest bugfixes and features`?

I know that the ingestion framework code is kind of part of datahub code base, so I assume it needs to match ?!

Same for the action framework version (which is used for the action pod as container image) … are there any constrains with current Datahub version,
or is it good to go with latest version ? (currently I am using the default version from HELM chart, which is quite old)

Thx for info

It seems likely that when using the DataHub ingestion framework, especially in a UI-based ingestion setup with the action pod, there are some version compatibility considerations to keep in mind.

My understanding is that the DataHub server uses a three-digit versioning scheme, while the CLI uses a four-digit scheme. For example, if you’re using DataHub server version 0.10.0, you should use a CLI version like 0.10.0.x, where x is a patch version. This is because CLI releases occur more frequently than server releases, and maintaining compatibility is crucial. This is mentioned in the <https://datahubproject.io/docs/0.13.1/metadata-ingestion/cli-ingestion|CLI Ingestion Guide>.

Regarding the actions framework, it seems that the DataHub Actions pod is maintained on a slightly different versioning system. According to a <Slack discussion>, the actions pod internally runs ingestion using a specific version of the DataHub CLI, which can be customized using the Advanced section in the UI. It is suggested to use the latest version of the actions pod that is compatible with your DataHub version. For example, the <https://github.com/datahub-project/datahub/blob/master/docs/actions/quickstart.md|DataHub Actions Quickstart> mentions that the Actions Framework requires a version of acryl-datahub >= v0.8.34.

For the action framework version, it seems that the actions pod is maintained on a slightly different versioning system. As per the <Slack discussion>, you should ensure that the actions pod version is compatible with your DataHub version. The <https://github.com/datahub-project/datahub/blob/master/docs/actions/quickstart.md|DataHub Actions Quickstart> provides guidance on installing the DataHub Actions CLI, which is an extension of the base datahub CLI commands.

If you are using Helm for deployment, it might be beneficial to check the <https://datahubproject.io/docs/deploy/kubernetes/|Helm deployment guide> to ensure that all components are updated to compatible versions. It seems that the actions pod is a deployment kind in the Helm chart and is enabled by default, as mentioned in a <Slack discussion>.

Would you like more detailed guidance on any specific part of the process, such as updating the CLI or actions pod version?

Sources:

  • <Slack discussion> :+1: 0 button :-1: 0 button :bulb: Hint: Mention @runllm in the thread for followups.

Hi <@U05SC3BGK8S>, how did my answer work out for you? Need any more assistance? You can also tag <@U07FV3UHE4D> to let your fellow community members know you’re still looking for guidance.

Hi :slight_smile: ! Did this interaction resolve your issue or do you still require assistance ?

Please tag @ RunLLM if you still need further assistance !

Or tag @Datahub Community Support if you require a person to take a look :slight_smile:

Hope this helps ! ><