<?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: case insensitive search in inputlookup from a KV store in Splunk Cloud Platform</title>
    <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/744519#M3752</link>
    <description>&lt;P&gt;Looks like I was not completely true. It's more complicated. But there is a way:&lt;/P&gt;&lt;P&gt;From &lt;FONT face="courier new,courier"&gt;transforms.conf.spec&lt;/FONT&gt; file:&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;NOTE: For KV Store lookups, a setting of 'case_sensitive_match=false' is honored only when the data in the KV Store lookup table is entirely in lower case. The input data can be in any case.&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Context:&lt;/P&gt;&lt;PRE&gt;case_sensitive_match = &amp;lt;boolean&amp;gt;
* If set to true, Splunk software performs case sensitive matching for all
  fields in a lookup table.
* If set to false, Splunk software performs case insensitive matching for all
  fields in a lookup table.
* NOTE: For KV Store lookups, a setting of 'case_sensitive_match=false' is
  honored only when the data in the KV Store lookup table is entirely in lower
  case. The input data can be in any case.
* For case sensitive field matching in reverse lookups see
  reverse_lookup_honor_case_sensitive_match.
* Default: true&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 18 Apr 2025 21:34:57 GMT</pubDate>
    <dc:creator>tmoser</dc:creator>
    <dc:date>2025-04-18T21:34:57Z</dc:date>
    <item>
      <title>case insensitive search in inputlookup from a KV store</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/531623#M371</link>
      <description>&lt;P&gt;We are currently using an inputlookup command to populate a list based on some wild card searches using input tokens from a KV store lookup with customer details like below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| inputlookup $site$-patrondetails WHERE FirstName=$firstname|s$
patron = $patron_id|s$
LastName = $patron_surname|s$
ResAddr = $patron_address|s$
MobilePhone = $patron_mobile|s$&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;where the token values are based on the value the user types into an input text box and the site token is a drop down value.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;until recently we havinputlookup&amp;nbsp;&lt;SPAN&gt;e had 2 sites where all the data in the source system is stored in uppercase but we have recently onboarded a 3rd site where the data is stored in both upper and lower case values.&amp;nbsp; as it turns out the where clause in is case sensitive.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I have tried adding&amp;nbsp;case_sensitive_match = false to the transform.conf stanza for this patrondetails lookup definition but this has not seemed to have any effect on the results being returned from the search. Have I missed something with this config or is there something else I need to add&lt;/P&gt;&lt;P&gt;Any help would be appreciated,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2020 04:16:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/531623#M371</guid>
      <dc:creator>TomWhite</dc:creator>
      <dc:date>2020-12-02T04:16:59Z</dc:date>
    </item>
    <item>
      <title>Re: case insensitive search in inputlookup from a KV store</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/539009#M500</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/229338"&gt;@TomWhite&lt;/a&gt;I'm facing the same problem. Have you ever found a resolution for this?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2021 15:28:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/539009#M500</guid>
      <dc:creator>dominikatvastli</dc:creator>
      <dc:date>2021-02-08T15:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: case insensitive search in inputlookup from a KV store</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/542318#M551</link>
      <description>&lt;P&gt;Me too. I also set&amp;nbsp;&lt;SPAN&gt;case_sensitive_match = false.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As written in the documentation, I changed the values to lower ones in the KV Store. An exact match is working, but also when all values are lower ones in KV store i cannot use an Upper value to search for.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;| inputlookup XXX where field=value&amp;nbsp; does not work case insensitive&lt;/P&gt;&lt;P&gt;| inputlookup XXX | search field=value does work case insensitive&lt;/P&gt;&lt;P&gt;So it seems to be a bug in where&lt;/P&gt;</description>
      <pubDate>Thu, 04 Mar 2021 09:10:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/542318#M551</guid>
      <dc:creator>dschroeter</dc:creator>
      <dc:date>2021-03-04T09:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: case insensitive search in inputlookup from a KV store</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/542429#M552</link>
      <description>&lt;P&gt;unfortunately the lookup I'm searching has 5 million rows and 25ish columns so Loading the whole lookup is not a practical solution&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 00:34:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/542429#M552</guid>
      <dc:creator>TomWhite</dc:creator>
      <dc:date>2021-03-05T00:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: case insensitive search in inputlookup from a KV store</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/558833#M732</link>
      <description>&lt;P&gt;Same issue here.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jul 2021 12:56:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/558833#M732</guid>
      <dc:creator>tomasmoser</dc:creator>
      <dc:date>2021-07-09T12:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: case insensitive search in inputlookup from a KV store</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/744518#M3751</link>
      <description>&lt;P&gt;KV Store supports only case sensitive content:&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/DefineaKVStorelookupinSplunkWeb" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/DefineaKVStorelookupinSplunkWeb&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2025 21:28:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/744518#M3751</guid>
      <dc:creator>tmoser</dc:creator>
      <dc:date>2025-04-18T21:28:51Z</dc:date>
    </item>
    <item>
      <title>Re: case insensitive search in inputlookup from a KV store</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/744519#M3752</link>
      <description>&lt;P&gt;Looks like I was not completely true. It's more complicated. But there is a way:&lt;/P&gt;&lt;P&gt;From &lt;FONT face="courier new,courier"&gt;transforms.conf.spec&lt;/FONT&gt; file:&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;NOTE: For KV Store lookups, a setting of 'case_sensitive_match=false' is honored only when the data in the KV Store lookup table is entirely in lower case. The input data can be in any case.&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Context:&lt;/P&gt;&lt;PRE&gt;case_sensitive_match = &amp;lt;boolean&amp;gt;
* If set to true, Splunk software performs case sensitive matching for all
  fields in a lookup table.
* If set to false, Splunk software performs case insensitive matching for all
  fields in a lookup table.
* NOTE: For KV Store lookups, a setting of 'case_sensitive_match=false' is
  honored only when the data in the KV Store lookup table is entirely in lower
  case. The input data can be in any case.
* For case sensitive field matching in reverse lookups see
  reverse_lookup_honor_case_sensitive_match.
* Default: true&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2025 21:34:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/case-insensitive-search-in-inputlookup-from-a-KV-store/m-p/744519#M3752</guid>
      <dc:creator>tmoser</dc:creator>
      <dc:date>2025-04-18T21:34:57Z</dc:date>
    </item>
  </channel>
</rss>

