Stateful ingestion for glossary terms Is it suppor...
# troubleshoot
f
Stateful ingestion for glossary terms Is it supported? I have my glossaries managed in the yml files in the git repo. Is there any way I could leverage stateful ingestion to get rid of the unused ones? What I would like to achieve is when I remove a term from yml and run my, let's say
datahub ingest -c recipes/glossaries/glossary_recipe.yml
, it also gets removed from the DataHub instance. I know I could probably somehow use graphQL for that but I am looking for simpler solution at the moment. Thanks!
1
g
It's not supported yet. But, one thing maybe it's easy to do is to enable somehow in the YAML file to ingest the status aspect. With this feature, you can enable/disable your glossary terms within the yaml file configuration. What do you think about ?
f
Yes, adding such a field like status to glossary terms source yml would do the job (
active, decommissioned, deprecated, etc)
This is definitely an option, I was just wondering if I could somehow avoid this custom coding.
g
I think just SQL sources have stateful ingestion support. For now, other source types must use graphql to extract the current state or gather the latest ingestion metadata to calculate the drift.
Controlling the status or deprecation aspect via config it's the fastest way to attend to your aims. Perhaps, I can try to contribute to that(improve the glossary term ingestion). Here we are planning to use this ingestion source.