Uploaded image for project: 'i2b2 Core Software'
  1. i2b2 Core Software
  2. CORE-276

get Query result instance id not found error on a running query

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.7.09c
    • None
    • None

    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>

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          mem61 Mike Mendis created issue -
          mem61 Mike Mendis added a comment -
          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
          mem61 Mike Mendis added a comment - 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
          mem61 Mike Mendis made changes -
          Field Original Value New Value
          Status New [ 10000 ] Open [ 1 ]
          jmd86 Janice Donahoe made changes -
          Fix Version/s 1.7.09c [ 10713 ]
          jmd86 Janice Donahoe made changes -
          Assignee Mike Mendis [ mem61 ]
          jmd86 Janice Donahoe added a comment -
          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.
          jmd86 Janice Donahoe added a comment - 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.
          jmd86 Janice Donahoe made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          jmd86 Janice Donahoe made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

          People

            mem61 Mike Mendis
            mem61 Mike Mendis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: