In our use of the emulator we've encountered complex queries that take longer than 15 seconds to execute. The HTTP server's current configuration will close the connection after a 15 second timeout.
This causes the Python client to retry the request, using the same job id, resulting in the error as noted in #213
In our use of the emulator we've encountered complex queries that take longer than 15 seconds to execute. The HTTP server's current configuration will close the connection after a 15 second timeout.
This causes the Python client to retry the request, using the same job id, resulting in the error as noted in #213
Closes #213