<?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: _txn_orphan field missing from transaction command after upgrade in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/txn-orphan-field-missing-from-transaction-command-after-upgrade/m-p/451963#M127979</link>
    <description>&lt;P&gt;Worked with support and while the &lt;CODE&gt;| makeresults&lt;/CODE&gt;-based query doesn't work on 7.0.2 either they confirmed that the behavior of that field changed between the versions.&lt;/P&gt;

&lt;P&gt;More specifically, &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;There was some changes in SPL-159182 for memory management back in 7.1.4.&lt;BR /&gt;
The _txn_orphan still exists, but only if the events aren't part of a transaction (even an incomplete one).&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
    <pubDate>Wed, 30 Sep 2020 00:32:01 GMT</pubDate>
    <dc:creator>eugenek</dc:creator>
    <dc:date>2020-09-30T00:32:01Z</dc:date>
    <item>
      <title>_txn_orphan field missing from transaction command after upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Search/txn-orphan-field-missing-from-transaction-command-after-upgrade/m-p/451962#M127978</link>
      <description>&lt;P&gt;Just upgraded SH from 7.0.2 to 7.2.5.1 (indexers still in progress) and some reports which rely on &lt;CODE&gt;_txn_orphan&lt;/CODE&gt; broke.  If I understand correctly, this should be returning the &lt;CODE&gt;_txn_orphan&lt;/CODE&gt; field.&lt;BR /&gt;
&lt;CODE&gt;| makeresults | eval foo="start;stop;start" | eval start_stop=split(foo,";") | mvexpand start_stop |fields - foo | transaction _time startswith="start_stop=start" endswith="start_stop=stop" keeporphans=true  unifyends=true&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 14:59:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/txn-orphan-field-missing-from-transaction-command-after-upgrade/m-p/451962#M127978</guid>
      <dc:creator>eugenek</dc:creator>
      <dc:date>2019-05-09T14:59:35Z</dc:date>
    </item>
    <item>
      <title>Re: _txn_orphan field missing from transaction command after upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Search/txn-orphan-field-missing-from-transaction-command-after-upgrade/m-p/451963#M127979</link>
      <description>&lt;P&gt;Worked with support and while the &lt;CODE&gt;| makeresults&lt;/CODE&gt;-based query doesn't work on 7.0.2 either they confirmed that the behavior of that field changed between the versions.&lt;/P&gt;

&lt;P&gt;More specifically, &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;There was some changes in SPL-159182 for memory management back in 7.1.4.&lt;BR /&gt;
The _txn_orphan still exists, but only if the events aren't part of a transaction (even an incomplete one).&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:32:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/txn-orphan-field-missing-from-transaction-command-after-upgrade/m-p/451963#M127979</guid>
      <dc:creator>eugenek</dc:creator>
      <dc:date>2020-09-30T00:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: _txn_orphan field missing from transaction command after upgrade</title>
      <link>https://community.splunk.com/t5/Splunk-Search/txn-orphan-field-missing-from-transaction-command-after-upgrade/m-p/451964#M127980</link>
      <description>&lt;P&gt;Thanks for adding the explanation from support!&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2019 19:20:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/txn-orphan-field-missing-from-transaction-command-after-upgrade/m-p/451964#M127980</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2019-06-17T19:20:33Z</dc:date>
    </item>
  </channel>
</rss>

