|
Once the plugin knows that it can't connect to a ColumnStore instance in the configuration dialog, it won't try again and again to request (and timeout -> slow down the UI) the table meta-data. Instead an error is thrown and the request is skipped. If the configuration dialog is opened a second time, a new check is issued if ColumnStore is available.
This case was also not well handled in the check step and injection step, and has been modified to display more understandable error messages.
For QA:
- execute the test suite
- manually check that the error case of valid Columnstore.xml but offline ColumnStore instance is handled better in the plugin's configuration dialog, injection process, and check step process.
|