<?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 Large Joins in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Large-Joins/m-p/23405#M4183</link>
    <description>&lt;P&gt;Hey Splunkers,&lt;/P&gt;

&lt;P&gt;I am trying to join / lookup a large set of data to each other.&lt;/P&gt;

&lt;P&gt;For example , transaction data to 20 million customer info.&lt;BR /&gt;
so I have to lookup every transactions to 20 million customer info.&lt;/P&gt;

&lt;P&gt;I have tried many ways to tackle this but haven't found the best solutions to this.  lookups didn't work because the customer info records sized up to 2 GB.  In order for splunk to be a big data engine, this seems to be a limitation. &lt;/P&gt;

&lt;P&gt;I appreciate your expert advice.  Cheers!&lt;/P&gt;</description>
    <pubDate>Thu, 02 Aug 2012 00:16:07 GMT</pubDate>
    <dc:creator>clyde772</dc:creator>
    <dc:date>2012-08-02T00:16:07Z</dc:date>
    <item>
      <title>Large Joins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Large-Joins/m-p/23405#M4183</link>
      <description>&lt;P&gt;Hey Splunkers,&lt;/P&gt;

&lt;P&gt;I am trying to join / lookup a large set of data to each other.&lt;/P&gt;

&lt;P&gt;For example , transaction data to 20 million customer info.&lt;BR /&gt;
so I have to lookup every transactions to 20 million customer info.&lt;/P&gt;

&lt;P&gt;I have tried many ways to tackle this but haven't found the best solutions to this.  lookups didn't work because the customer info records sized up to 2 GB.  In order for splunk to be a big data engine, this seems to be a limitation. &lt;/P&gt;

&lt;P&gt;I appreciate your expert advice.  Cheers!&lt;/P&gt;</description>
      <pubDate>Thu, 02 Aug 2012 00:16:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Large-Joins/m-p/23405#M4183</guid>
      <dc:creator>clyde772</dc:creator>
      <dc:date>2012-08-02T00:16:07Z</dc:date>
    </item>
    <item>
      <title>Re: Large Joins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Large-Joins/m-p/23406#M4184</link>
      <description>&lt;P&gt;More information is needed! Can you give a (sanitized) example of your data and the search that you need to do?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Aug 2012 02:27:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Large-Joins/m-p/23406#M4184</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2012-08-02T02:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: Large Joins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Large-Joins/m-p/23407#M4185</link>
      <description>&lt;P&gt;Just an idea: you could sort and split your lookup file in more, smaller files. Then apply multiple lookups in the search. &lt;/P&gt;

&lt;P&gt;Otherwise, you could load your customer data to a REDIS cache, then use the &lt;A href="http://splunk-base.splunk.com/apps/27106/redis-lookup"&gt;REDIS lookup app&lt;/A&gt; to match it to transactions. The same approach might work with MySQL and the MySQL app, though more complex.&lt;/P&gt;

&lt;P&gt;Let us know if you solved the problem!&lt;/P&gt;</description>
      <pubDate>Thu, 02 Aug 2012 10:45:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Large-Joins/m-p/23407#M4185</guid>
      <dc:creator>Paolo_Prigione</dc:creator>
      <dc:date>2012-08-02T10:45:28Z</dc:date>
    </item>
  </channel>
</rss>

