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
Shema inference should work with dab export --generate command, currently it throws the below error and also shows successful message as schema generated successfully
Version
1.3.13-rc
What database are you using?
CosmosDB NoSQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
No response
Relevant log output
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Please fix the error message also show relevant message (In this case all connection string, account name, database name, container name was part of the config)
From a functionality perspective, we had previously decided (you might recall this discussion) to support only a single/global container configuration for now, with plans to expand support based on customer requests in the future. This is why the error occurs when container name information is missing. ref [Bug]: Improve schema inference experience for azure cosmosdb #2477
It seems we now need to add that support. Therefore, I am including these changes in my new PR.
What happened?
Shema inference should work with dab export --generate command, currently it throws the below error and also shows successful message as schema generated successfully
Version
1.3.13-rc
What database are you using?
CosmosDB NoSQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
No response
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: