https://community.splunk.com/t5/Splunk-Search/Is-it-possible-to-time-out-a-dbquery-operation/m-p/135784#M184728 <P>We want to protect our underlying database against dangerous operations, but also want to retain the flexibility of allowing the use of <CODE>dbquery</CODE>.</P> <P>We've implemented a query killer on the database side, but it looks like the java bridge swallows up that error and doesn't expose it except in logs, which means a <CODE>select * from table</CODE> shows up as completed, with no errors, but only containing some of the rows in the table... seems like a dangerous non-error.</P> <P>Is there any way we can time out a dbquery operation from the Splunk side?</P> Mon, 03 Feb 2014 23:45:30 GMT VMDX 2014-02-03T23:45:30Z https://community.splunk.com/t5/Splunk-Search/Is-it-possible-to-time-out-a-dbquery-operation/m-p/135784#M184728 <P>We want to protect our underlying database against dangerous operations, but also want to retain the flexibility of allowing the use of <CODE>dbquery</CODE>.</P> <P>We've implemented a query killer on the database side, but it looks like the java bridge swallows up that error and doesn't expose it except in logs, which means a <CODE>select * from table</CODE> shows up as completed, with no errors, but only containing some of the rows in the table... seems like a dangerous non-error.</P> <P>Is there any way we can time out a dbquery operation from the Splunk side?</P> Mon, 03 Feb 2014 23:45:30 GMT https://community.splunk.com/t5/Splunk-Search/Is-it-possible-to-time-out-a-dbquery-operation/m-p/135784#M184728 VMDX 2014-02-03T23:45:30Z https://community.splunk.com/t5/Splunk-Search/Is-it-possible-to-time-out-a-dbquery-operation/m-p/135785#M184729 <P>Not today, but we'll work on something for a future release.</P> Thu, 06 Feb 2014 18:06:09 GMT https://community.splunk.com/t5/Splunk-Search/Is-it-possible-to-time-out-a-dbquery-operation/m-p/135785#M184729 araitz 2014-02-06T18:06:09Z