-
Notifications
You must be signed in to change notification settings - Fork 21
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
bug: Uppercase stream names cause failures #119
Comments
Is this a bug in the SDK? I think in general we should bias towards case-insensitive comparisons. These streams should all land into the same table without error and without duplication:
And these tables should all be considered valid destination tables for a stream named "MyStream":
We can (optionally!) let the target decide how/if to normalize casing, but regardless of casing preferences of the destination system, we should find and load to existing tables even if casing is not a match. |
I'd bet on it being something on the postgres target specifically. I agree it should work regardless of casing but I do think the case should follow whatever was initially set, maybe I care about something that doesn't matter here though. A lot of this comes to the normalization stuff I ripped out. Maybe just tolower and a replace dashes and underscores. That would be an easy fix here but wouldn't fix this generically |
Solved with #138 |
Originally raised in https://meltano.slack.com/archives/C013EKWA2Q1/p1680488722168999
I was able to replicate the behavior. I sent some dummy data to the target using an uppercase stream name
Account
, like this:I see the table created in the database but then immediately get this error:
cc @visch @aaronsteers @edgarrmondragon
The text was updated successfully, but these errors were encountered: