[IGNITE-11035] Web console: Implemement improvements for query page controller.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: wizards
• Assignee: Andrey Novikov
• Reporter: Vasiliy Sisko
• Created: 23/Jan/19 03:47
• Updated: 06/Aug/20 04:37
• Resolved: 11/Mar/19 11:20

Description

1. Implement processing of query result task without one level recursion.
2. Explicit serialization to JSON of Paragraph object. Possible Paragraph.prototype.toJSON should be implemented.
3. Try to use RXJS operator chain instead of direct usage of subscription object.
4. On query cancel task unlock UI in Promise.prototype.finally.
5. Check initialization of queryId and resultNodeId on execute of refresh in auto refresh mode.
6. Some paragraph manipulation methods should be moved into Paragraph class: _initQueryResult, _showLoading. Check other methods with paragraph as argument.
7. Check clearing of data in _initQueryResult method. Try to not use direct calling of grid API. Possible we should show “Query execution” stub instead.
8. Remove “beforeunload” listener on leave of Queries page.
9. Possible we should cancel queries when client session is over.
10. Add docs for return values of queries task in agent manager. F.e:

    /*
    @returns {Promise<QueryFetchFirstPageResult>}
    */

1. Confirm on leaving of Queries page when running queries exist:

   You have running queries. Are you sure you want to cancel them?
   

Issue Links

• breaks: IGNITE-11636 Web console: incorrect value is restored after Refresh
• is duplicated by: IGNITE-5637 Web Console: Reset previous results when executing new query
• relates to: IGNITE-11496 Long running SQL queries could be randomly canceled from WC
• links to: GitHub Pull Request #6021