You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see in the image below the column should be named __is_new_cased_reported_from_initial_area
Another example. Note both investigation forms share the same schema in mongodb but there's an issue when mapped to postgres
Expected behavior
Proper column names should be in the destination table in postgres
Steps to reproduce
This uses the mongodb to postgres tutorial. My mongodb collection has alot nested entries most of which go two levels deep. Happy to share a dump for someone to reproduce this
Operating system
macOS
Runtime environment
Local
Python version
3.11
dlt data source
Mongodb
dlt destination
Postgres
Other deployment details
I'm using dagster to trigger the runs
Additional information
No response
The text was updated successfully, but these errors were encountered:
@briankariuki unfortunately postgres has 64 characters identifier table limit. we are inserting a short tag when we shorten the name to fit into that limit. I'm afraid it cannot be avoided (without recompiling postgres with higher limit)
you could also condifer adding max table nesting level option to limit number of unnested tables. then maybe you do not generate such long names
dlt version
1.3.0
Describe the problem
As you can see in the image below the column should be named
__is_new_cased_reported_from_initial_area
Another example. Note both investigation forms share the same schema in mongodb but there's an issue when mapped to postgres
![image](https://private-user-images.githubusercontent.com/34672053/386674285-63db87d0-0011-4b55-bcfa-643853a84c6f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk4NTUwMTMsIm5iZiI6MTczOTg1NDcxMywicGF0aCI6Ii8zNDY3MjA1My8zODY2NzQyODUtNjNkYjg3ZDAtMDAxMS00YjU1LWJjZmEtNjQzODUzYTg0YzZmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE4VDA0NTgzM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY4ZDk3MWM4ZmM1ZGU0NjI0ZTJmN2IzZjhjMzUyYjkwNzQ4YTI2ZWUwMDdmMjFhMzI4ZTUzYTZlZGRkNTkxYWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.-qbfj4N_AQywVvTp-OLznugOlbJyvB2dK8LQ2oQObNg)
Expected behavior
Proper column names should be in the destination table in postgres
Steps to reproduce
This uses the mongodb to postgres tutorial. My mongodb collection has alot nested entries most of which go two levels deep. Happy to share a dump for someone to reproduce this
Operating system
macOS
Runtime environment
Local
Python version
3.11
dlt data source
Mongodb
dlt destination
Postgres
Other deployment details
I'm using dagster to trigger the runs
Additional information
No response
The text was updated successfully, but these errors were encountered: