G sheets, ingested files with the same name saved in the same schema

nairabhishek73 commented 3 months ago

In Adhyayan's case, Each state has its own google sheet, each google sheet's first tab would be names sheet 1. After ingest, if connection is created to the same schema, staging for example, then in the UI4T warehouse store they are indistinguishable from each other.

Currently the solution is to save each sheet to a separate schema so that they can be distinguished from each other. But this is not a long term solution.

As discussed in https://github.com/DalgoT4D/webapp/issues/1070 we should consider alert whenever a table of the same name is being saved to the same schema and then also consider allowing folks to rename at connection creation, this renamed table could be an intermediate table, just the journey for renaming needs to present itself differently (at ingestion) so that in the store on UI4T I see the renamed file easily.

fatchat commented 3 months ago

so you're saying

there are multiple connections all of which contain a single stream
all these streams have the same name
upon sync the destination tables are named after each stream and therefore end up having the same name

is that right?

let's solve this as stated here and leave ui4t out of it

nairabhishek73 commented 3 months ago

Can suggest for now that folks just change the name for the tab in the sheet, else save to separate schemas.

Concerns:

Orgs who use a lot of google sheets have many formulas on sheets which are dependent on tab names and so changing the tab name has many downstream effects for them.
Saviung to multiple schemas for more than 10 sheets sheets will be cumbersome

DalgoT4D / webapp

G sheets, ingested files with the same name saved in the same schema #1101