<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Finalize action for searchscript? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Finalize-action-for-searchscript/m-p/9116#M19</link>
    <description>&lt;P&gt;Never completing (endless input) would be fine.  The data would keep being quantized acceptably.  However, the last unfinished quanta must be processed somehow.  Only handling maxinputs is not really acceptable.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jan 2010 10:14:25 GMT</pubDate>
    <dc:creator>jrodman</dc:creator>
    <dc:date>2010-01-15T10:14:25Z</dc:date>
    <item>
      <title>Finalize action for searchscript?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finalize-action-for-searchscript/m-p/9114#M17</link>
      <description>&lt;P&gt;I wrote a search operator that takes actions external to splunk.  It has to take an action to 'complete' its operations.  How can my search operator know when it is done being called, given that it could be called any number of times?&lt;/P&gt;

&lt;P&gt;The search operator is currently 'streaming = true' since it could be handling extremely large data volumes.  Can this perhaps be set to false for this purpose?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2010 03:02:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finalize-action-for-searchscript/m-p/9114#M17</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-01-15T03:02:57Z</dc:date>
    </item>
    <item>
      <title>Re: Finalize action for searchscript?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finalize-action-for-searchscript/m-p/9115#M18</link>
      <description>&lt;P&gt;I don't know the answer to whether it can be told whether it is "complete". (And with 4.1 real-time search, it may actually never be complete.)&lt;/P&gt;

&lt;P&gt;However, setting "streaming = false" will simply limit your script to being called just once with at most "maxinputs" results.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2010 03:08:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finalize-action-for-searchscript/m-p/9115#M18</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-01-15T03:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: Finalize action for searchscript?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finalize-action-for-searchscript/m-p/9116#M19</link>
      <description>&lt;P&gt;Never completing (endless input) would be fine.  The data would keep being quantized acceptably.  However, the last unfinished quanta must be processed somehow.  Only handling maxinputs is not really acceptable.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2010 10:14:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finalize-action-for-searchscript/m-p/9116#M19</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-01-15T10:14:25Z</dc:date>
    </item>
  </channel>
</rss>

