Hi we're having troubles with Postgres ingests, th...
# troubleshoot
e
Hi we're having troubles with Postgres ingests, they fail with error
"ImportError: cannot import name 'Distribution' from 'pkg_resources' (unknown location)\n",
. Any idea why that might be happening? They used to ingest successfully before, and the failes started about two weeks ago or so
a
Hi @elegant-salesmen-99143, what version are you on, and have you recently upgraded?
e
now we're on 0.9.6, but the errors started on 0.9.5. on which we upgraded in december.
@astonishing-answer-96712 ok from what I got from googling (git link), looks like pkg_resources is known to cause such issues and is 'semi-deprecated and are mostly unsupported'. Is there a reason why Datahub is using it and is there a way to work around using it in ingests?
a
@elegant-salesmen-99143, it’s not us, but one of our dependencies- could you post some of the logs from the failed ingestion runs?
e
a
Ok thanks! CC: @gray-shoe-75895 seems like a GE dependency issue
g
Looks like this line https://github.com/great-expectations/great_expectations/blob/develop/great_expectations/util.py#L55 has been in GE for a while. My guess is this is somehow using a new/old of setuptools, but unfortunately I don’t think there’s a ton that we can do
e
@gray-shoe-75895 but now it intervenes all our postgres ingests with profiling - they all fail with this error (but ingest succussfully if I disable profiling). Profiling is a part of basic Datahub functionality in my understanding, is there really nothing that can be done?
g
I just tested postgres ingestion with profiling enabled and it seems to have worked ok on my end. Are you on the latest datahub version, and do you have any “cli version” set in the advanced part of your config?
e
@gray-shoe-75895 hmmm, that's strange. We're on 0.9.6 and we don't have and cli version set in advanced configs. What else can I check? Maybe we should specify a cli version?
@gray-shoe-75895 I set the 0.9.6 CLI version in the advanced part and it worked, thank you! I the only question that remains now is why Datahub doesn't automatically use CLI version in accord with the release version, but uses an old one, which leads to errors🤔
g
That is very strange - we should be keeping them aligned by default so the misalignment is probably a bug - I’ll look into it a bit further