Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema change detection: "something went wrong fetching info" #1365

Open
nairabhishek73 opened this issue Jan 3, 2025 · 1 comment
Open
Labels
bug Something isn't working

Comments

@nairabhishek73
Copy link

nairabhishek73 commented Jan 3, 2025

https://jam.dev/c/be101ce3-4f78-4e46-9b41-92d4d0ce0ca4

Screenshot 2025-01-03 at 3 41 09 PM

This is on production - Dalgo demo org

@fatchat
Copy link
Contributor

fatchat commented Jan 3, 2025

2025-01-03 10:49:39 platform > ERROR i.a.i.b.AirbyteExceptionHandler(uncaughtException):26 Something went wrong in the connector. See the logs for more details. java.lang.Exception: Verification error(s) occurred for DISCOVER. Errors: [$.database: is missing but it is required]

The source config form in Airbyte shows MongoDb v0.2.5 and

image

but the form in Dalgo shows v1.5.12 and all fields are populated

the global version is v1.5.12 but the version for this source is v0.2.5. so we should be rendering (and saving!) the form for v0.2.5. but it looks like we are doing this for the new version instead and therefore the container can't read the fields it needs from the saved config

@himanshudube97 can you investigate further please

@fatchat fatchat added the bug Something isn't working label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

2 participants