<?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: How to store a large search result set into a lookup table? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215973#M63342</link>
    <description>&lt;P&gt;Use the &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.0/SearchReference/Outputlookup"&gt;outputlookup&lt;/A&gt; command.&lt;BR /&gt;
If large means millions of lines, you might be better off specifying .csv.gz in order to create a compressed file that you can later on read with inputlookup.&lt;/P&gt;</description>
    <pubDate>Mon, 18 Apr 2016 18:24:46 GMT</pubDate>
    <dc:creator>javiergn</dc:creator>
    <dc:date>2016-04-18T18:24:46Z</dc:date>
    <item>
      <title>How to store a large search result set into a lookup table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215972#M63341</link>
      <description>&lt;P&gt;I have a large results set of a search which I would like to store as a lookup table. How can I do that? &lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 18:21:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215972#M63341</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-04-18T18:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to store a large search result set into a lookup table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215973#M63342</link>
      <description>&lt;P&gt;Use the &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.0/SearchReference/Outputlookup"&gt;outputlookup&lt;/A&gt; command.&lt;BR /&gt;
If large means millions of lines, you might be better off specifying .csv.gz in order to create a compressed file that you can later on read with inputlookup.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 18:24:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215973#M63342</guid>
      <dc:creator>javiergn</dc:creator>
      <dc:date>2016-04-18T18:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to store a large search result set into a lookup table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215974#M63343</link>
      <description>&lt;P&gt;Great. &lt;/P&gt;

&lt;P&gt;We ran:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=provider tin!=" *" tin!="000000000"  tin="*" | dedup tin | fields - _raw | table * | outputlookup provider_lookup.csv
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It created a 2.2 GBs file on the SH's file system and I can see it under the 'Lookup table files' as -&lt;BR /&gt;
&lt;CODE&gt;/opt/splunk/splunk/etc/apps/search/lookups/provider_lookup.csv&lt;/CODE&gt; &lt;/P&gt;

&lt;P&gt;What should I do now?&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2016 01:50:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215974#M63343</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-04-19T01:50:36Z</dc:date>
    </item>
    <item>
      <title>Re: How to store a large search result set into a lookup table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215975#M63344</link>
      <description>&lt;P&gt;You can use it with either &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Inputlookup"&gt;inputlookup&lt;/A&gt; or just &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Lookup"&gt;lookup&lt;/A&gt;.&lt;BR /&gt;
Keep in mind you will need to create a lookup in order to do that.&lt;BR /&gt;
Take a look at the very detailed &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.0/Knowledge/ConfigureCSVlookups"&gt;documentation&lt;/A&gt; about this topic.&lt;/P&gt;

&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2016 09:13:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215975#M63344</guid>
      <dc:creator>javiergn</dc:creator>
      <dc:date>2016-04-19T09:13:34Z</dc:date>
    </item>
    <item>
      <title>Re: How to store a large search result set into a lookup table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215976#M63345</link>
      <description>&lt;P&gt;also be careful about saving large lookup files on your search head. You may bump into issues with syncing your bundle across indexers if you hit your maximum bundle size. You may need to whitelist the lookup folder within that app &amp;gt; &lt;A href="https://answers.splunk.com/answers/3436/how-could-i-optimize-distributed-replication-of-large-lookup-tables.html"&gt;https://answers.splunk.com/answers/3436/how-could-i-optimize-distributed-replication-of-large-lookup-tables.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2016 13:05:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215976#M63345</guid>
      <dc:creator>rusty009</dc:creator>
      <dc:date>2016-04-19T13:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to store a large search result set into a lookup table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215977#M63346</link>
      <description>&lt;P&gt;Thanks a lot!&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2016 17:58:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215977#M63346</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-04-19T17:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to store a large search result set into a lookup table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215978#M63347</link>
      <description>&lt;P&gt;Thank you javiergn - worked nicely but slow with a lookup table of 2 GBs and physical memory of 16 MBs.&lt;/P&gt;

&lt;P&gt;The lookup part of the command looks like - &lt;BR /&gt;
    | lookup provider_lookup tin as prov_tin OUTPUT adr_ln_1_txt&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 09:27:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-store-a-large-search-result-set-into-a-lookup-table/m-p/215978#M63347</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2020-09-29T09:27:14Z</dc:date>
    </item>
  </channel>
</rss>

