Jira (PDB-4937) Add a default statement timeout to user queries

[Rob Browning (Jira)]

Title: Message Title

Rob Browning commented on PDB-4937   Re: Add a default statement timeout to user queries We're setting this work aside until/unless we come up with a more sophisticated approach.  That is, with streaming responses, we can't return a custom status (say 503) to indicate a timeout once we've started streaming, and we might also want to provide a finer distinction than just 503. In order to pursue this further, we might want to investigate chunked transfer encoding "trailing headers", where we could report a timeout.  Alternately, we could change our output format in order to allow us to send an indication of the timeout in the result stream itself that the client could then detect and handle. The rest of the work went fairly smoothly, so were we able to come up with a palatable solution to this question, then we should be able to resume the effort. Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.375530.1603302604000.73170.1604601900100%40Atlassian.JIRA.