databrickslabs / databrickslabs/ontos
[Bug]: Whenever schema inference from UC is active in a given contract - the UI that renders the contract becomes very unresponsive
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 212
- Forks
- 71
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 43
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
In some cases, the Ontos Application becomes very unresponsive - ex: waiting times of +2min to render a contract in the UI on the screen
It happens often in the Contract objects - especially when a schema (of 1 or a few tables) was inferred via the unity catalog functionality.
Expected Behavior
Faster response times - seamless navigation between windows with sub-second waiting times
Side note: App itself was running on serverless - backend database should have been started up (mid-session)
Steps To Reproduce
1 Create a new contract
2 Add a Schema to the contract - by inferring a table from Unity catalog
3 Close the contract
4 re-open the contract again
In step for it can take up to more than a minute before the contract opens
Cloud
Azure
Browser
Chrome
Version
latest
Relevant log output
No error message
Eventually the UI renders the information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the delay by reopening a contract containing a schema inferred from Unity Catalog, using the issue's Chrome and Azure setup. Inspect the contract-rendering and schema-inference paths while profiling the reopen operation; done means the contract opens without minute-long waits and navigation approaches the stated sub-second expectation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud, frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100