<?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: What is the order of execution / precedence of multiple TRANSFORMS in this example? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203406#M40181</link>
    <description>&lt;P&gt;The information is here:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.0/admin/propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.0/admin/propsconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The answer is that in the former/single example, the order is left-to-right; in the latter/double example, since you are not using the &lt;CODE&gt;priority&lt;/CODE&gt; configuration to alter the default, it is top-to-bottom.&lt;/P&gt;

&lt;P&gt;The execution does not "stop early" and fields are usually overridden (although I am not sure this has always been the case for all versions) so once an earlier-executed transform has given a field a value, later-executed ones can update/overwrite that original value.&lt;/P&gt;</description>
    <pubDate>Thu, 22 Oct 2015 13:23:42 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-10-22T13:23:42Z</dc:date>
    <item>
      <title>What is the order of execution / precedence of multiple TRANSFORMS in this example?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203405#M40180</link>
      <description>&lt;P&gt;Consider&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::single]
TRANSFORMS-single = transform1, transform2

[source::double]
TRANSFORMS-first = transform1
TRANSFORMS-second = transform2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What's the difference between the two? Specifically, for each of the two sources:&lt;BR /&gt;
 1. What is the order of execution for transforms 1 and 2?&lt;BR /&gt;
 2. Does the execution stop early (i.e. if transform1 matches, transform2 is not evaluated)?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2015 07:17:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203405#M40180</guid>
      <dc:creator>dannestor</dc:creator>
      <dc:date>2015-10-22T07:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: What is the order of execution / precedence of multiple TRANSFORMS in this example?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203406#M40181</link>
      <description>&lt;P&gt;The information is here:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.0/admin/propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.0/admin/propsconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The answer is that in the former/single example, the order is left-to-right; in the latter/double example, since you are not using the &lt;CODE&gt;priority&lt;/CODE&gt; configuration to alter the default, it is top-to-bottom.&lt;/P&gt;

&lt;P&gt;The execution does not "stop early" and fields are usually overridden (although I am not sure this has always been the case for all versions) so once an earlier-executed transform has given a field a value, later-executed ones can update/overwrite that original value.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2015 13:23:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203406#M40181</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-10-22T13:23:42Z</dc:date>
    </item>
    <item>
      <title>Re: What is the order of execution / precedence of multiple TRANSFORMS in this example?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203407#M40182</link>
      <description>&lt;P&gt;Not able to find where is below documented:&lt;BR /&gt;
"Although the execution does not "stop early" fields are not overridden so once an earlier-executed transform has given a field a value, later-executed ones will not update/overwrite that original value."&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2017 06:03:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203407#M40182</guid>
      <dc:creator>nikhiltyagi</dc:creator>
      <dc:date>2017-11-29T06:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: What is the order of execution / precedence of multiple TRANSFORMS in this example?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203408#M40183</link>
      <description>&lt;P&gt;Actually, Splunk applies all transforms in turn, left to right, and it DOES overwrite the set values. So keep this in mind when ordering the transforms!&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 13:25:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203408#M40183</guid>
      <dc:creator>dajomas</dc:creator>
      <dc:date>2018-01-10T13:25:59Z</dc:date>
    </item>
    <item>
      <title>Re: What is the order of execution / precedence of multiple TRANSFORMS in this example?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203409#M40184</link>
      <description>&lt;P&gt;As I understand &lt;BR /&gt;
* priority only works for whole stanzas, not single entries&lt;BR /&gt;
* having multiple TRANSFORMS for one stanza, they are executed in alphabetical order &lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2019 11:49:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/203409#M40184</guid>
      <dc:creator>dvb</dc:creator>
      <dc:date>2019-04-18T11:49:47Z</dc:date>
    </item>
    <item>
      <title>Re: What is the order of execution / precedence of multiple TRANSFORMS in this example?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/526566#M88817</link>
      <description>&lt;P&gt;It should read as woodcock mentioned.&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;Although the execution does not "stop early" fields are not overridden so once an earlier-executed transform has given a field a value, later-executed ones CAN update/overwrite that original value."&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2020 02:59:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-order-of-execution-precedence-of-multiple-TRANSFORMS/m-p/526566#M88817</guid>
      <dc:creator>anwarmian</dc:creator>
      <dc:date>2020-10-27T02:59:32Z</dc:date>
    </item>
  </channel>
</rss>

