Error in Postgresql ingestion to GreenPlum with DataHub version 0.12.1

Original Slack Thread

Hello everyone, I really need help. I run ingestion to postgresql, datahub version 0.12.1, I get an error (in the thread)
We use GreenPlum
PostgreSQL 9.4.26 (Greenplum Database 6.23.3 build 6.23.3_arenadata44-1662.gitf7ff7c8.el7) on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit compiled on Apr 25 2023 09:23:04

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)

errorattachment

Can you post what datahub version you’re using and your redacted recipe used for ingestion? Also, is there any stack trace attached to that error in the logs?

Hello, datahub version 0.12.1. This is standard ingestion for postgresql, in the recipe I only limit the data from one schema (data_mart) and remove partitions using a regular expression. I have attached some of the logs where this error occurs

    type: postgres
    config:
        host_port: 'my_host'
        database: reporting
        password: '${datahub_gp_int}'
        username: data_hub
        platform_instance: GP_DEV_data_mart
        env: DEV
        profiling:
            enabled: true
            sample_size: 1000
        schema_pattern:
            allow:
                - data_mart
        table_pattern:
            allow:
                - '^(?!.*_prt).*$'```![attachment](https://files.slack.com/files-pri/TUMKD5EGJ-F06FXCFJML1/exec-urn_li_datahubexecutionrequest_b1389fef-9abe-4a67-99f1-9e958a02ed76_1.log?t=xoxe-973659184562-6705490291811-6708051934148-dd1595bd5f63266bc09e6166373c7a3c)

We recently had a community contribution to get view lineage using this query. It looks like this isn’t supported for your postgres instance, so for now, you can just set include_view_lineage: false to avoid this error. Alternatively, if you can write the query without a recursive DISTINCT query, we’ll be happy to take that contribution