Currently, if a table was previously opened in Wrangler, the sample data is still displayed. The system loads the data, without checking the originating source.
When a connection has timed out the following issues occur:
- If the user tries to navigate back to the connection (from Wrangler) to browse data, none of the conections are available and an error is displayed.
- The user can create a pipeline from Wrangler, using the data originating from the timed out connecitons, however, when the user tries to "get schema" or validate, an error is displayed.
The BE should check if the connection relative to data that is displayed in Wrangler is still active. If not, an error indicating that the connection has timed out should be displayed.
In case of multiple tabs, the error should displayed when the user selects the tab connected to the timed out connection