Closed AntonChernyaevArammeem closed 1 year ago
Hh it's really bug, if i use into recipe
pipeline_name: DWH_USAGE
this not works beacuse already this ingestion was into datahub (but i delete this ingestion from ui and this ingestion was created from UI)
But if i use thi
pipeline_name: CLI_DWH_USAGE
all works and i can see this into UI.
it's really looks like a bug.
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
Looks like the underlying error message is ERROR: could not serialize access due to concurrent update
. The bug that caused that has been fixed in 0.11.0.
I'm going to close this issue for now, but let me know (1) what issues you ran into with upgrading and (2) once you upgrade to 0.11.0, if you see this issue again.
env kubernetes 1.24/helm datahub 10.4 (cant't update to 10.5 a lot of ussiues but it's not current issue) Created igestion on sandbox all running well in production not. Only one [CLI] igestions into list into UI All others CLI ingestion through kubernetes jobs not show after apply If i remove one as currently present into UI and run again kubernetes job - will see this ingestion.
Could someone helps with this?)
ERRORS