<?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 are values in lookups matched? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10249#M421</link>
    <description>&lt;P&gt;As of Splunk 4.2(?), transforms.conf allows you to specify both &lt;CODE&gt;case_sensitive_match&lt;/CODE&gt; and &lt;CODE&gt;match_type&lt;/CODE&gt; to set the behavior of field matching in lookups:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;case_sensitive_match = &amp;lt;bool&amp;gt;
* If set to false, case insensitive matching will be performed for all fields in a lookup table
* Defaults to true (case sensitive matching)

match_type = &amp;lt;string&amp;gt;
* A comma and space-delimited list of &amp;lt;match_type&amp;gt;(&amp;lt;field_name&amp;gt;) specification to allow for non-exact matching
* The avaiable match_type values are WILDCARD, CIDR, and EXACT.  EXACT is the default and does not need to be specified.  Only fields that should use WILDCARD or CIDR matching should be specified in this list
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;CODE&gt;case_sensitive_match&lt;/CODE&gt; applies to all fields in the lookup.&lt;/P&gt;

&lt;P&gt;What &lt;CODE&gt;match_type&lt;/CODE&gt; means, if I remember correctly, is that if you have &lt;CODE&gt;field1=foobar&lt;/CODE&gt; in your event, and a lookup file with a &lt;CODE&gt;foo*&lt;/CODE&gt; line in it, &lt;CODE&gt;match_type = WILDCARD(field1)&lt;/CODE&gt; will make &lt;CODE&gt;foobar&lt;/CODE&gt; match &lt;CODE&gt;foo*&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Jul 2012 16:45:40 GMT</pubDate>
    <dc:creator>Jason</dc:creator>
    <dc:date>2012-07-13T16:45:40Z</dc:date>
    <item>
      <title>How are values in lookups matched?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10247#M419</link>
      <description>&lt;P&gt;When a field value is passed to a lookup, what are the limits on how it can match the value in the lookup? Specifically:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Is the match case-sensitive? If not, what locale rules are used? Similarly, is it diacritic-sensitive?&lt;/LI&gt;
&lt;LI&gt;Are any kinds of wildcards allowed? Can I use, e.g., &lt;CODE&gt;*&lt;/CODE&gt; or &lt;CODE&gt;Prefix-*&lt;/CODE&gt; in a lookup table and expect it to match an event field value like &lt;CODE&gt;Prefix-1&lt;/CODE&gt;?&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Thu, 18 Mar 2010 04:19:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10247#M419</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-03-18T04:19:40Z</dc:date>
    </item>
    <item>
      <title>Re: How are values in lookups matched?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10248#M420</link>
      <description>&lt;P&gt;Matches are case sensitive as well as diacritic-sensitive.&lt;/P&gt;

&lt;P&gt;No wildcards are allowed at this time.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2010 00:33:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10248#M420</guid>
      <dc:creator>steveyz</dc:creator>
      <dc:date>2010-04-09T00:33:43Z</dc:date>
    </item>
    <item>
      <title>Re: How are values in lookups matched?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10249#M421</link>
      <description>&lt;P&gt;As of Splunk 4.2(?), transforms.conf allows you to specify both &lt;CODE&gt;case_sensitive_match&lt;/CODE&gt; and &lt;CODE&gt;match_type&lt;/CODE&gt; to set the behavior of field matching in lookups:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;case_sensitive_match = &amp;lt;bool&amp;gt;
* If set to false, case insensitive matching will be performed for all fields in a lookup table
* Defaults to true (case sensitive matching)

match_type = &amp;lt;string&amp;gt;
* A comma and space-delimited list of &amp;lt;match_type&amp;gt;(&amp;lt;field_name&amp;gt;) specification to allow for non-exact matching
* The avaiable match_type values are WILDCARD, CIDR, and EXACT.  EXACT is the default and does not need to be specified.  Only fields that should use WILDCARD or CIDR matching should be specified in this list
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;CODE&gt;case_sensitive_match&lt;/CODE&gt; applies to all fields in the lookup.&lt;/P&gt;

&lt;P&gt;What &lt;CODE&gt;match_type&lt;/CODE&gt; means, if I remember correctly, is that if you have &lt;CODE&gt;field1=foobar&lt;/CODE&gt; in your event, and a lookup file with a &lt;CODE&gt;foo*&lt;/CODE&gt; line in it, &lt;CODE&gt;match_type = WILDCARD(field1)&lt;/CODE&gt; will make &lt;CODE&gt;foobar&lt;/CODE&gt; match &lt;CODE&gt;foo*&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jul 2012 16:45:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10249#M421</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2012-07-13T16:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: How are values in lookups matched?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10250#M422</link>
      <description>&lt;P&gt;This is true by default, but you can now change this to some degree.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jul 2012 18:42:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10250#M422</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2012-07-26T18:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: How are values in lookups matched?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10251#M423</link>
      <description>&lt;P&gt;What about a prefixed wildcard instead of suffix?  e.g. will a lookup file with a "*bar" line in it, match_type = WILDCARD(field1) match "foobar"?  I've tried this but can't get it to work, but maybe I've done something else wrong.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2013 18:38:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/10251#M423</guid>
      <dc:creator>bsayatovic</dc:creator>
      <dc:date>2013-02-25T18:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: How are values in lookups matched?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/569212#M198399</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/196579"&gt;@bsayatovic&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;Did you happen to find a solution for the prefix wildcard? I am running into same issue, so wondering if you found a way around it.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Sep 2021 19:16:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-are-values-in-lookups-matched/m-p/569212#M198399</guid>
      <dc:creator>sinvin</dc:creator>
      <dc:date>2021-09-30T19:16:34Z</dc:date>
    </item>
  </channel>
</rss>

