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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Destination MSSQL: failing with cannot participate in a columnstore index #14493

Closed
harshithmullapudi opened this issue Jul 7, 2022 · 5 comments
Assignees

Comments

@harshithmullapudi
Copy link
Contributor

https://discuss.airbyte.io/t/csv-files-source-special-settings-needed-to-sync-to-ms-sql/1720

@harshithmullapudi
Copy link
Contributor Author

logs-35.txt
logs-47.txt

Here are the logs

@mmoole
Copy link

mmoole commented Jul 19, 2022

pardon, since this is about MS SQL and not MySQL, would it be possible to adjust the title accordingly?

@grishick grishick changed the title Destination MySQL: failing with cannot participate in a columnstore index Destination MSSQL: failing with cannot participate in a columnstore index Jul 27, 2022
@harshithmullapudi harshithmullapudi changed the title Destination MSSQL: failing with cannot participate in a columnstore index Destination MySQL: failing with cannot participate in a columnstore index Jul 27, 2022
@harshithmullapudi harshithmullapudi changed the title Destination MySQL: failing with cannot participate in a columnstore index Destination MSSQL: failing with cannot participate in a columnstore index Jul 27, 2022
@mmoole
Copy link

mmoole commented Jul 29, 2022

with a newer version of Airbyte and the connector this error regarding MSSQL seems to be no more reproducible 馃憤馃徏

@etsybaev etsybaev self-assigned this Aug 1, 2022
@etsybaev
Copy link
Contributor

etsybaev commented Aug 2, 2022

Based on provided example (see link below) I see that we have 2 columns with the same name "Jahr;Jahr;"
https://opendata.dwd.de/climate_environment/CDC/regional_averages_DE/annual/sunshine_duration/regional_averages_sd_year.txt

The issue may be similar to #5171. The only point in case of 5171 it's related to stream names, meanwhile in our case it's related to column names

@etsybaev
Copy link
Contributor

etsybaev commented Aug 3, 2022

It seems to work now. I assume that previously it failed as we had 2 fields with the same name and different types. But please be aware that there is some minor name transforming that will be done to make names a little bit different.

Selection_407.png
Selection_408.png

@etsybaev etsybaev closed this as completed Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants