[CORE-276] get Query result instance id not found error on a running query Created: 26/Oct/17 Updated: 02/Feb/18 Resolved: 29/Nov/17 |
|
| Status: | Closed |
| Project: | i2b2 Core Software |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.09c |
| Type: | Bug | Priority: | Major |
| Reporter: | Mike Mendis | Assignee: | Mike Mendis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participant/s: |
| Description |
|
The issue is when a breakdown is selected and the user drag the recently run previous query back to the query tool before it can complete, the client sends CRC_QRY_getResultDocument_fromResultInstanceId with a query_result_instance_id. The xml_result table has not been run so the crc sends back
<ns4:response xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns4:crc_xml_result_responseType"> <status> <condition type="ERROR">Query result instance id 9657 not found</condition> </status> </ns4:response> |
| Comments |
| Comment by Mike Mendis [ 26/Oct/17 ] |
|
My fix:
If Check to see if the results are there and return them (the current code) Else Run a query linking the qt_query_result_instance and the qt_query_result_type to get the name of the breakdown. If I get a result than the query is currently running and than return the following xml <ns10:result name="PATIENT_GENDER_COUNT_XML"> <data type="int" column="Processing">-1</data> <ns10:result> Else assume that id send it is not valid and return the code Query result instance id 123 not found message |
| Comment by Janice Donahoe [ 29/Nov/17 ] |
| Tested in both the local i2b2 testing environment and a SHRINE network and the fix appears to be working correctly. Users will no longer see an error when expanding the results of a previous query that is still running or when they drag a previous query to the query tool before it has completed. If it is a SHRINE query and some results have been returned from the local i2b2 instances then those results will be made available to the user while the others continue to run. |