Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: MongoDB: Add ability to avoid duplicate column name clashes

Answered
Robert Bramwell User

MongoDB collections which contain an ID field named anything like '@ID' currently resolve to the same name as the internal MongoDB id field '_id'. 

This could indicate a wider issue where special characters all resolve to underscores, creating column name clashes in the destination.

Adding the ability to avoid the duplicate column name clashes or determine destination column names would mean users will be able to import their full dataset. 

The problem is outlined more clearly in internal helpdesk ticket T-839992. (https://support.fivetran.com/hc/en-us/requests/234343)

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Rean Fivetranner

    Hi Robert, 

    Thank you for sharing this request and outlining the issue so clearly! I’m Rean from the product team, and I appreciate you bringing this up.

    We’re currently testing a new feature in private preview that preserves the original source names of schemas, tables, and columns during the sync process. I’d love to learn more about your use case and whether this feature would address the column name clashes you’re experiencing.

    If you're interested, we can explore whether this private preview would be a good fit for your needs. Let me know!

    Best regards,
    Rean