<?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: Upsert Data on Ingest in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Upsert-Data-on-Ingest/m-p/157277#M97989</link>
    <description>&lt;P&gt;Ah, that makes sense. Thanks for the feedback; this is helpful.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Feb 2014 16:10:52 GMT</pubDate>
    <dc:creator>lampert_marksu</dc:creator>
    <dc:date>2014-02-19T16:10:52Z</dc:date>
    <item>
      <title>Upsert Data on Ingest</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upsert-Data-on-Ingest/m-p/157275#M97987</link>
      <description>&lt;P&gt;I have an index set up and functioning properly on initial ingest. What I'd like to accomplish is the "upsert" of events on future files.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Example&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;
&lt;EM&gt;File 1 (childCount_08-13-2013.txt)&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;
Date, Name, # of Kids&lt;BR /&gt;&lt;BR /&gt;
08/13/2013, Nicky Blank, 4&lt;BR /&gt;&lt;BR /&gt;
08/13/2013, Mike Dorn, 2&lt;BR /&gt;&lt;BR /&gt;
08/13/2013, Les Paul, 1&lt;BR /&gt;&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;File 2 (childCount_08-23-2013.txt)&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;
Date, Name, # of Kids&lt;BR /&gt;&lt;BR /&gt;
08/23/2013, Nicky Blank, 6&lt;BR /&gt;&lt;BR /&gt;
08/23/2013, Phillip Jacks, 3&lt;BR /&gt;&lt;BR /&gt;
08/23/2013, Tina Walls, 1&lt;BR /&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;DESIRED OUTPUT&lt;/STRONG&gt; (Contains all unique entries and updates any existing entries) &lt;BR /&gt;&lt;BR /&gt;
08/23/2013, Nicky Blank, 6&lt;BR /&gt;&lt;BR /&gt;
08/13/2013, Mike Dorn, 2&lt;BR /&gt;&lt;BR /&gt;
08/13/2013, Les Paul, 1&lt;BR /&gt;&lt;BR /&gt;
08/23/2013, Phillip Jacks, 3&lt;BR /&gt;&lt;BR /&gt;
08/23/2013, Tina Walls, 1&lt;BR /&gt;&lt;/P&gt;

&lt;P&gt;Any assistance would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2014 15:04:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upsert-Data-on-Ingest/m-p/157275#M97987</guid>
      <dc:creator>lampert_marksu</dc:creator>
      <dc:date>2014-02-19T15:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: Upsert Data on Ingest</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upsert-Data-on-Ingest/m-p/157276#M97988</link>
      <description>&lt;P&gt;Data in Splunk's index cannot be modified - once it's indexed the data stays the same. What you could do though is create tables like the one you show using stats for instance.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;basesearch&amp;gt; | stats latest(Date) as Date,latest(num_kids) by Name
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 19 Feb 2014 16:01:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upsert-Data-on-Ingest/m-p/157276#M97988</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2014-02-19T16:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: Upsert Data on Ingest</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upsert-Data-on-Ingest/m-p/157277#M97989</link>
      <description>&lt;P&gt;Ah, that makes sense. Thanks for the feedback; this is helpful.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2014 16:10:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upsert-Data-on-Ingest/m-p/157277#M97989</guid>
      <dc:creator>lampert_marksu</dc:creator>
      <dc:date>2014-02-19T16:10:52Z</dc:date>
    </item>
  </channel>
</rss>

