- Newest
- Most votes
- Most comments
To capture lineage from AWS Glue tables and reflect it in AWS DataZone asset lineage, you're on the right track with your approach. However, since you're experiencing issues after a recent update, there are a few things you can try to resolve the problem:
- OpenLineage JAR files: Ensure you're using the most up-to-date OpenLineage JAR files. The latest compatible versions for AWS Glue are:
- openlineage-spark_2.12-1.9.1.jar
- openlineage-spark-1.8.0.jar
-
AWS Glue version: Use AWS Glue version 3.0 or later, as these versions are compatible with the OpenLineage integration.
-
Job parameters: Double-check that you've set the required job parameters correctly. These typically include:
- --conf spark.extraListeners=io.openlineage.spark.agent.OpenLineageSparkListener
- --conf spark.openlineage.host=https://api.datazone.[YOUR_REGION].amazonaws.com
- --conf spark.openlineage.namespace=[YOUR_DATAZONE_DOMAIN_ID]
-
AWS DataZone configuration: Ensure that data lineage is enabled for your AWS DataZone domain and that you have the necessary permissions to capture and view lineage data.
-
Use Spark DataFrames: The OpenLineage Spark plugin may not be able to extract data lineage from AWS Glue Spark jobs that use AWS Glue DynamicFrames. Instead, use Spark SQL DataFrames in your Glue jobs.
-
Check CloudWatch Logs: Review the Glue job's CloudWatch logs for any error messages or warnings that might indicate why the lineage capture is failing.
-
Update extract_glue_spark_lineage.py: Ensure you're using the latest version of this script, as it may have been updated to work with the new AWS DataZone version.
-
API compatibility: Verify that you're using the correct API endpoints and methods for the updated version of AWS DataZone.
If you're still encountering issues after trying these steps, you may need to contact AWS support for further assistance, as there could be specific changes in the latest update that require additional configuration or troubleshooting.
Remember to test your changes in a non-production environment first to ensure they work as expected before applying them to your production workflows.
Sources
Amazon DataZone introduces OpenLineage-compatible data lineage visualization in preview | AWS Big Data Blog
Data lineage in Amazon DataZone (Preview) - Amazon DataZone
Amazon DataZone introduces API-driven, OpenLineage-compatible data lineage visualization in preview - AWS
answered 2 years ago
Relevant content
asked a year ago
asked a year ago
asked 2 years ago
asked a year ago

The above solution is not working there is issue with aws glue job error logs due to formatting lineage event is getting captured in two seperate error logs block due to which current provided python script provided by aws doesn't work, please provide updated script to extract_glue_spark_lineage.py file. Since the existing is not working and able to capture lineage from error logs