<?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 Indexed data twice! Suggestions to remove data from being searched? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexed-data-twice-Suggestions-to-remove-data-from-being/m-p/211634#M41652</link>
    <description>&lt;P&gt;Lets say we have forwarded events that are exactly the same and show in Splunk as duplicates. Running a &lt;CODE&gt;| dedup _raw&lt;/CODE&gt; would resolve the duplicate events at search time. Would it make sense to run &lt;CODE&gt;index=main | deduce _raw | delete&lt;/CODE&gt; so that we won't have to run a dedup every single time on that time range of events?&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2016 17:09:13 GMT</pubDate>
    <dc:creator>ben_leung</dc:creator>
    <dc:date>2016-02-23T17:09:13Z</dc:date>
    <item>
      <title>Indexed data twice! Suggestions to remove data from being searched?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexed-data-twice-Suggestions-to-remove-data-from-being/m-p/211634#M41652</link>
      <description>&lt;P&gt;Lets say we have forwarded events that are exactly the same and show in Splunk as duplicates. Running a &lt;CODE&gt;| dedup _raw&lt;/CODE&gt; would resolve the duplicate events at search time. Would it make sense to run &lt;CODE&gt;index=main | deduce _raw | delete&lt;/CODE&gt; so that we won't have to run a dedup every single time on that time range of events?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2016 17:09:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexed-data-twice-Suggestions-to-remove-data-from-being/m-p/211634#M41652</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2016-02-23T17:09:13Z</dc:date>
    </item>
    <item>
      <title>Re: Indexed data twice! Suggestions to remove data from being searched?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexed-data-twice-Suggestions-to-remove-data-from-being/m-p/211635#M41653</link>
      <description>&lt;P&gt;The reason I ask this is because &lt;CODE&gt;| delete&lt;/CODE&gt; would remove the events returned from the prior search. I would assume it would "delete" the duplicate AND the original events. Does anyone know the behavior of this kind of scenario? &lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2016 17:12:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexed-data-twice-Suggestions-to-remove-data-from-being/m-p/211635#M41653</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2016-02-23T17:12:08Z</dc:date>
    </item>
    <item>
      <title>Re: Indexed data twice! Suggestions to remove data from being searched?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexed-data-twice-Suggestions-to-remove-data-from-being/m-p/211636#M41654</link>
      <description>&lt;P&gt;I wouldn't advise scheduling a delete.  For one, delete is expensive to run.  Second, possibly dangerous in that you may wind up deleting something by accident.  Third, fix the reason for duplicate events instead.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2016 17:17:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexed-data-twice-Suggestions-to-remove-data-from-being/m-p/211636#M41654</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2016-02-23T17:17:18Z</dc:date>
    </item>
  </channel>
</rss>

