<?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: results are being truncated in join query in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486301#M136049</link>
    <description>&lt;P&gt;The default for subsearch is as follows.&lt;BR /&gt;
I think that it is good to use the LOOKUP command by setting the LOOKUP definition.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.1/Search/Aboutsubsearches"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.1/Search/Aboutsubsearches&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[subsearch]
maxout = &amp;lt;integer&amp;gt;

Maximum number of results to return from a subsearch.
This value cannot be greater than or equal to 10500.
Defaults to 10000.
maxtime = &amp;lt;integer&amp;gt;

Maximum number of seconds to run a subsearch before finalizing
Defaults to 60.
ttl = &amp;lt;integer&amp;gt;

Time to cache a given subsearch's results, in seconds.
Do not set this below 120 seconds.
Defaults to 300.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 26 Sep 2019 05:20:30 GMT</pubDate>
    <dc:creator>HiroshiSatoh</dc:creator>
    <dc:date>2019-09-26T05:20:30Z</dc:date>
    <item>
      <title>results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486300#M136048</link>
      <description>&lt;P&gt;Problem: &lt;/P&gt;

&lt;P&gt;i have 200000 splunk events  from which i only want 15000 events ( like vlookup in excel)&lt;/P&gt;

&lt;P&gt;Splunk events contain(200000 hosts ) : host version kernel &lt;BR /&gt;
lookuptable contain (15000 hosts): host window&lt;BR /&gt;
i only want result for the host listed in lookup table(15000)&lt;/P&gt;

&lt;P&gt;i tried using join  but it truncates the result .&lt;/P&gt;

&lt;P&gt;Query : | inputlookup "host.csv" | rename HOST as host | join host [search index=server_info platform=redhat message="SYSINFO*" host="*"  ] | table host version kernel window | where window != " "&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:15:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486300#M136048</guid>
      <dc:creator>manishyadav91</dc:creator>
      <dc:date>2020-09-30T02:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486301#M136049</link>
      <description>&lt;P&gt;The default for subsearch is as follows.&lt;BR /&gt;
I think that it is good to use the LOOKUP command by setting the LOOKUP definition.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.1/Search/Aboutsubsearches"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.1/Search/Aboutsubsearches&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[subsearch]
maxout = &amp;lt;integer&amp;gt;

Maximum number of results to return from a subsearch.
This value cannot be greater than or equal to 10500.
Defaults to 10000.
maxtime = &amp;lt;integer&amp;gt;

Maximum number of seconds to run a subsearch before finalizing
Defaults to 60.
ttl = &amp;lt;integer&amp;gt;

Time to cache a given subsearch's results, in seconds.
Do not set this below 120 seconds.
Defaults to 300.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 26 Sep 2019 05:20:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486301#M136049</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2019-09-26T05:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486302#M136050</link>
      <description>&lt;P&gt;yes , the default maxout is 50000 but my search output is 2450000. so i get the first 50000 which includes non relevant events. &lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2019 05:24:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486302#M136050</guid>
      <dc:creator>manishyadav91</dc:creator>
      <dc:date>2019-09-26T05:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486303#M136051</link>
      <description>&lt;P&gt;Is there a problem with using the lookup command?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index=server_info platform=redhat message="SYSINFO*" host="*"
|lookup host.csv host OUTPUT XXX,XXX,XXX
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 26 Sep 2019 05:35:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486303#M136051</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2019-09-26T05:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486304#M136052</link>
      <description>&lt;P&gt;index=server_info platform=redhat message="SYSINFO*" host="*"  |lookup host.csv host OUTPUT Window | table host Window kernel version |where Window != " "&lt;/P&gt;

&lt;P&gt;i tried this too, it only give partial results 4400 instead of 15000 host in csv lookup table.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:15:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486304#M136052</guid>
      <dc:creator>manishyadav91</dc:creator>
      <dc:date>2020-09-30T02:15:59Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486305#M136053</link>
      <description>&lt;P&gt;Please double-check the events that have not been set up and the contents of the lookup.&lt;/P&gt;

&lt;P&gt;Or ...&lt;BR /&gt;
LOOKUP does not exclude events. In the case of a distributed configuration, the LOOKUP table may not be synchronized on the indexer side.&lt;/P&gt;

&lt;P&gt;Try setting "local=true"&lt;/P&gt;

&lt;P&gt;Optional arguments&lt;BR /&gt;
local&lt;BR /&gt;
Syntax: local=&lt;BR /&gt;
Description: If local=true, forces the lookup to run on the search head and not on any remote peers.&lt;BR /&gt;
Default: false&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2019 06:08:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486305#M136053</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2019-09-26T06:08:02Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486306#M136054</link>
      <description>&lt;P&gt;Can this be done in any other way ?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2019 06:20:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486306#M136054</guid>
      <dc:creator>manishyadav91</dc:creator>
      <dc:date>2019-09-26T06:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486307#M136055</link>
      <description>&lt;P&gt;It will synchronize after a while. See the following blog for commands.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://www.splunk.com/blog/2017/06/08/syncing-lookups-using-pure-spl.html"&gt;https://www.splunk.com/blog/2017/06/08/syncing-lookups-using-pure-spl.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2019 06:35:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486307#M136055</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2019-09-26T06:35:19Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486308#M136056</link>
      <description>&lt;P&gt;Do not inputlookup and join. Do the search and use lookup as a lookup. You are breaking map reduce in several ways plus hitting limits. &lt;/P&gt;

&lt;P&gt;SearchHere | lookup host.csv HOST as host OUTPUT HOST as isFound | where isnotnull(isFound) | stats count by host version kernel window | fields - count &lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2019 07:20:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486308#M136056</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2019-09-26T07:20:01Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486309#M136057</link>
      <description>&lt;P&gt;Hi manishyadav91,&lt;BR /&gt;
In subsearches you have the limit of 50,000 results so you must put the search as first.&lt;BR /&gt;
Then to use the join command with many events isn't a good idea becaus your search will be very slow.&lt;BR /&gt;
So you could change your search like the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=server_info platform=redhat message="SYSINFO*" host="*"  [ | inputlookup "host.csv" | rename HOST as host | fields host ]
| lookup host.csv HOST AS host OUTPUT version kernel window 
| table host version kernel window
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2019 11:19:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486309#M136057</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-09-26T11:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: results are being truncated in join query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486310#M136058</link>
      <description>&lt;P&gt;Hi Giuseppe,&lt;/P&gt;

&lt;P&gt;Search 1 :  index=server_info platform=redhat message="SYSINFO*" host="*"&lt;BR /&gt;&lt;BR /&gt;
                  | dedup host | table host Window kernel version&lt;BR /&gt;
results 29467&lt;/P&gt;

&lt;P&gt;Search 2 :  | inputlookup Host-Q3.csv | table host Window&lt;BR /&gt;
Result: 15679&lt;/P&gt;

&lt;P&gt;Search combined : index=cba_chef platform=redhat message="SYSINFO*" host="*"&lt;BR /&gt;&lt;BR /&gt;
                                | lookup Host-Q3.csv  host OUTPUT  Window | where Window != " " | dedup host | &lt;BR /&gt;
                                table host Window kernel version&lt;BR /&gt;
results  3599&lt;/P&gt;

&lt;P&gt;i dont know why the results are not complete, ideally combined searc should give 15000 events but it doesn't , i have tried all the solutions listed below but same results .&lt;/P&gt;

&lt;P&gt;is there any other way to to search only limited events/host from the whole load of events.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:16:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/results-are-being-truncated-in-join-query/m-p/486310#M136058</guid>
      <dc:creator>manishyadav91</dc:creator>
      <dc:date>2020-09-30T02:16:48Z</dc:date>
    </item>
  </channel>
</rss>

