-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
1s1t CatalogParser should handle raw table name collisions #27798
Comments
Related:
|
Grooming meeting 6/28: |
Thanks Ed! |
I think they're slightly different and worth having separate issues. This issue is: within a single connection, user has two streams Your issue is: across multiple connections (or even outside of airbyte entirely) the user has an |
When working on this ticket, consider cleaning up the |
Grooming:
|
In 1s1t, two streams may want to write to the same raw table. E.g.
public.users_foo
andpublic_users.foo
would both naively want to write toairbyte.public_users_foo
.CatalogParserTest#rawNameCollision
captures this, but is currently disabled.Decide how we want to resolve these collisions, then implement that decision in
CatalogParser#parseCatalog
. Maybe options:airbyte.public__airbyte_raw__users_foo
+airbyte.public_users__airbyte_raw__foo
)The text was updated successfully, but these errors were encountered: