Troubleshooting "RecursionError: maximum recursion depth exceeded in comparison" during metadata ingestion

Original Slack Thread

Has anyone received the error “RecursionError: maximum recursion depth exceeded in comparison” when ingesting metadata. My specific use case is with Snowflake and the datahub cli

Hey there! :wave: Make sure your message includes the following information if relevant, so we can help more effectively!

  1. Are you using UI or CLI for ingestion?
  2. Which DataHub version are you using? (e.g. 0.12.0)
  3. What data source(s) are you integrating with DataHub? (e.g. BigQuery)

<@U06TM7M40RK> Can you help with the questions in this thread?


:information_source: We’re experimenting with a new AI assistant for questions in the <#CUMUWQU66> channel to help you track down helpful resources more quickly. Keep in mind that responses may not always be spot-on; feel free to ask it follow-up questions and don’t forget to provide its responses a :thumbsup: or :thumbsdown: so other folks in the Community know if you’re still looking for help on the topic!

To help you more effectively, could you please provide the following information:

  1. Are you using the UI or CLI for ingestion?
  2. Which DataHub version are you using? (e.g., 0.12.0)?
  3. What data source(s) are you integrating with DataHub? (e.g., Snowflake)?

This information will help narrow down the potential causes and solutions for the “RecursionError: maximum recursion depth exceeded in comparison” error you’re encountering.

Additionally, based on a similar issue reported in the DataHub community, there might be a need to check the hierarchy of groups or the complexity of the metadata being ingested, as it can sometimes lead to such recursion errors (<Issues · datahub-project/datahub · GitHub Issue>).

Would you like more detailed troubleshooting steps based on your specific setup?

Sources: