Unable to exit onboarding - Stuck on "Set up connection" in #1684
Comments
|
Somehow I get back to this page even after pulling new docker images. No way at all to exit, reconfigure or go to another page. Looks like there is some problem with a column name airbyte-scheduler | 2021-01-17 10:11:21 ERROR i.a.c.i.LineGobbler(voidCall):69 - {job_id=32, job_log_filename=logs.log, job_root=/tmp/workspace/32/0} - Exception in thread "main" java.lang.RuntimeException: Found multiple columns with same name: supplier_id in table: suppliers but the columns are not the same. columns: [ColumnInfo{columnName='publisher_id', columnType=SMALLINT}, ColumnInfo{columnName='supplier_id', columnType=VARCHAR}, ColumnInfo{columnName='org_no', columnType=VARCHAR}, ColumnInfo{columnName='name', columnType=VARCHAR}, ColumnInfo{columnName='city', columnType=VARCHAR}, ColumnInfo{columnName='email', columnType=VARCHAR}, ColumnInfo{columnName='phone', columnType=VARCHAR}, ColumnInfo{columnName='postal_code', columnType=VARCHAR}, ColumnInfo{columnName='created', columnType=TIMESTAMP}, ColumnInfo{columnName='raw', columnType=OTHER}, ColumnInfo{columnName='supplier_id', columnType=INTEGER}, ColumnInfo{columnName='br_id', columnType=INTEGER}, ColumnInfo{columnName='supplier_name', columnType=VARCHAR}] |
|
@duvaldt - The error that is being thrown is because Airbyte is detecting two columns with the same name in a table but they have different types. Looking at the log it looks like one is a varchar and was is an integer. I'm not familiar with why this would be the case. Can you share any insight as to the type of the Specifically if you could run this query as describe in SO and tell me what the paraphrasing from the error message you copied above the relevant information. We are happy to spend some time reproducing this and fixing the issue, but we'll best be able to help if you can help us understand how that column in your database is configured. |
|
Hmm.. been looking around for a while (it's quite a big database), and I think I might have found a "bug". We don't have a table called suppliers with those fields. But, we have many schemas in our database, and two of those schemas contains a table called suppliers. In one of the tables, the first 10 of the listed columns exists:(ColumnInfo{columnName='publisher_id', columnType=SMALLINT}, ColumnInfo{columnName='supplier_id', columnType=VARCHAR}, ColumnInfo{columnName='org_no', columnType=VARCHAR}, ColumnInfo{columnName='name', columnType=VARCHAR}, ColumnInfo{columnName='city', columnType=VARCHAR}, ColumnInfo{columnName='email', columnType=VARCHAR}, ColumnInfo{columnName='phone', columnType=VARCHAR}, ColumnInfo{columnName='postal_code', columnType=VARCHAR}, ColumnInfo{columnName='created', columnType=TIMESTAMP}, ColumnInfo{columnName='raw', columnType=OTHER}) and in the other table, the three remaining exists: ( ColumnInfo{columnName='supplier_id', columnType=INTEGER}, ColumnInfo{columnName='br_id', columnType=INTEGER}, ColumnInfo{columnName='supplier_name', columnType=VARCHAR}] ) They are referring to two different type of suppliers, that's the reason for the design, and different schemas. Could it be possible that Airbyte somehow disregards the schemas? I have a few suggestions:
Thank you for your response, the software seems really great to work with! /Mattias |
|
aha! that's helpful. just to make sure I understanding you have two separate schemas, in one of them is a table called |
|
Yes that is correct :)
…On Tue, Jan 19, 2021, 17:41 Charles ***@***.***> wrote:
aha! that's helpful. just to make sure I understanding you have two
separate schemas, in one of them is a table called suppliers with a
column called supplier_id that is a varchar and then in the other schema
there is a table called suppliers with a column called supplier_id that
is an integer? that's super helpful, i think i have an idea on where the
bug might be. will look into a fix today.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1684 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJYLD2BHJNNJZTXH7W6AY3S2WYZ3ANCNFSM4WF7HZZA>
.
|
|
I have recreated this locally. Looking into what I need to do to fix it now. |
|
Awesome, thanks!
…On Tue, Jan 19, 2021, 22:55 Charles ***@***.***> wrote:
I have recreated this locally. Looking into what I need to do to fix it
now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1684 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJYLD4SY2LIZCYV4QY2VILS2X5WXANCNFSM4WF7HZZA>
.
|
|
A PR is up to fix this. Hoping that it will be merged and released today. If not today it would be tomorrow morning. |
Expected Behavior
I want to be able to skip the onboarding guide, reach some default page or go somewhere other than the last onboarding page.
Current Behavior
In the final step in the onboarding guide where I setup the connection i get an error, "Fetching the schema is failed. Please try again". I'm unable to go back and change any configuration. I've tried to delete cookies, delete docker images and manually entering another url but it always gets me back to the final step, which is not working.
Steps to Reproduce
Severity of the bug for you
Critial - Unable to use the software
Additional context
Ubuntu 20.04, Postgres 12
I have a lot of schemas in my postgres database. Not sure if it's relevant or not.
The text was updated successfully, but these errors were encountered: