<?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: Fix Error: IndexScopedSearch? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Fix-Error-IndexScopedSearch/m-p/674102#M230758</link>
    <description>&lt;P&gt;did you fix it ?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jan 2024 18:09:38 GMT</pubDate>
    <dc:creator>abedcx</dc:creator>
    <dc:date>2024-01-12T18:09:38Z</dc:date>
    <item>
      <title>Fix Error: IndexScopedSearch?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Fix-Error-IndexScopedSearch/m-p/632910#M219846</link>
      <description>&lt;P&gt;Hello Splunk enjoyers!&lt;BR /&gt;I loaded some data(10 000 000), with fields: updated_time, info, user and discription,&amp;nbsp; to my new index "data_tmp".&lt;BR /&gt;&lt;BR /&gt;So when i search, i got a problem&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;Error in 'IndexScopedSearch': The search failed. More than 1000000 events found at time 1677582000.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;My search:&lt;BR /&gt;&lt;BR /&gt;So i tried to extract by updated_time like:&lt;BR /&gt;index = data_tmp&lt;BR /&gt;&amp;nbsp;eval _time = strftime(updated,"%Y-%m-%d %H:%M:%S.%3N")&lt;BR /&gt;| convert ctime(_time)&lt;BR /&gt;| fieldformat _time = strftime(updated,"%Y-%m-%d %H:%M:%S.%3N")&lt;BR /&gt;&lt;BR /&gt;but nothing works.&lt;BR /&gt;Can somebody help me with that?&lt;BR /&gt;thank you!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 15:32:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Fix-Error-IndexScopedSearch/m-p/632910#M219846</guid>
      <dc:creator>splunk_enjoyer</dc:creator>
      <dc:date>2023-03-02T15:32:38Z</dc:date>
    </item>
    <item>
      <title>Re: Fix Error: IndexScopedSearch?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Fix-Error-IndexScopedSearch/m-p/674102#M230758</link>
      <description>&lt;P&gt;did you fix it ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 18:09:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Fix-Error-IndexScopedSearch/m-p/674102#M230758</guid>
      <dc:creator>abedcx</dc:creator>
      <dc:date>2024-01-12T18:09:38Z</dc:date>
    </item>
    <item>
      <title>Re: Fix Error: IndexScopedSearch?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Fix-Error-IndexScopedSearch/m-p/674105#M230759</link>
      <description>&lt;P&gt;This is a fundamental problem with the data badly ingested into Splunk.&lt;/P&gt;&lt;P&gt;Splunk returns results in reverse chronological order so it needs to be able to sort the results properly based on the _original_ value of the _time field. (afterwards the _time field can be rewritten during the search pipeline and it won't affect the result order). If you have several hundred thousand events indexed at the same point in time, Splunk cannot sort them due to memory constraints.&lt;/P&gt;&lt;P&gt;It's not a problem with the search as such but it's a problem with the data - fix your data onboarding.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 18:28:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Fix-Error-IndexScopedSearch/m-p/674105#M230759</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-01-12T18:28:16Z</dc:date>
    </item>
  </channel>
</rss>

