Lineage V3 Feature Flag in alation_conf¶
Applies from version 2021.4
You can enable Lineage V3 using alation_conf on a new installation of Alation where there is no lineage data yet.
However, if your instance has lineage data, do not use alation_conf to enable Lineage V3. Instead, perform lineage data migration from V2 to V3.
To enable the Lineage V3 feature flag using alation_conf on a new Alation instance:
Use SSH to connect to the Alation server.
Enter the Alation shell using the following command:
sudo /etc/init.d/alation shell
Run the command given below to enable Lineage V3:
alation_conf -s True lineage-service.enabled
Restart the Celery component:
alation_supervisor restart celery:*
Ensure that the lineage service is running:
alation_supervisor status lineage
This command should return the status Running, for example:
(env) PROD [admin@ip-177-71-27-47 /]$ alation_supervisor status lineage lineage RUNNING pid 1184, uptime 5 days, 19:10:35
If it’s in the Stopped state, then restart it:
alation_supervisor restart lineage
If Lineage V3 service is in the Running state with the Lineage V3 feature flag enabled, this means that all sources for lineage data, such as MDE, QLI, Compose, and Lineage V2 APIs are now using the lineage service.