<?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: Lookups and Wildcard Entries in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Lookups-and-Wildcard-Entries/m-p/490420#M136944</link>
    <description>&lt;P&gt;There is a maximum match in the settings in the lookup file. Can't use this?&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jan 2020 06:36:10 GMT</pubDate>
    <dc:creator>HiroshiSatoh</dc:creator>
    <dc:date>2020-01-23T06:36:10Z</dc:date>
    <item>
      <title>Lookups and Wildcard Entries</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookups-and-Wildcard-Entries/m-p/490419#M136943</link>
      <description>&lt;P&gt;I'm currently setting up an alert using a CSV lookup file with wildcard entries. I followed the instructions provided from the other questions and was able to make them work. Here's a sample of my CSV lookup file:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;KEY1,KEY2,VALUE&lt;/STRONG&gt;&lt;BR /&gt;
AAA,111,Value 1&lt;BR /&gt;
AAA,112,Value 2&lt;BR /&gt;
AAA,*,Value 3&lt;/P&gt;

&lt;P&gt;Using fields KEY1 and KEY2 for the lookup -- if the query produces the values KEY1="AAA" and KEY2="111", then it should pick up  "Value 1" for the VALUE field -- which it correctly does. However, it also picks up the entry corresponding to KEY1="AAA, KEY2="*" since it technically matches.&lt;/P&gt;

&lt;P&gt;Is it possible to configure the lookup that if it already finds a match, it won't go through the rest of the lookup file? For the query, I'm just using a straight forward lookup command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| lookup &amp;lt;Lookup&amp;gt; KEY1 AS KEY1, KEY2 AS KEY2 OUTPUTNEW VALUE
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Your inputs would be very much appreciated, thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jan 2020 02:01:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookups-and-Wildcard-Entries/m-p/490419#M136943</guid>
      <dc:creator>pwguinto</dc:creator>
      <dc:date>2020-01-23T02:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: Lookups and Wildcard Entries</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookups-and-Wildcard-Entries/m-p/490420#M136944</link>
      <description>&lt;P&gt;There is a maximum match in the settings in the lookup file. Can't use this?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jan 2020 06:36:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookups-and-Wildcard-Entries/m-p/490420#M136944</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2020-01-23T06:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: Lookups and Wildcard Entries</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookups-and-Wildcard-Entries/m-p/490421#M136945</link>
      <description>&lt;P&gt;I'll try this one, and will let you know -- though I think this should work. I just can't replicate the scenario immediately due to how the data is being fed. Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jan 2020 09:24:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookups-and-Wildcard-Entries/m-p/490421#M136945</guid>
      <dc:creator>pwguinto</dc:creator>
      <dc:date>2020-01-23T09:24:59Z</dc:date>
    </item>
  </channel>
</rss>

