<?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: Field Values Case Sensitve in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289962#M87688</link>
    <description>&lt;P&gt;The answer I was looking for was to use an automatic lookup and force case sensitive matching. I'm sure I worded the question poorly, and this is what the working config looks like:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[mysourcetype]
LOOKUP-SFDC-USER_NAME1 = lookup_usernames USER_ID AS USER_ID 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[lookup_usernames]
filename = lookup_usernames.csv
case_sensitive_match=true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The way to search a table for a specific username is accepted above. &lt;/P&gt;</description>
    <pubDate>Wed, 12 Jul 2017 16:21:54 GMT</pubDate>
    <dc:creator>tmarlette</dc:creator>
    <dc:date>2017-07-12T16:21:54Z</dc:date>
    <item>
      <title>Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289953#M87679</link>
      <description>&lt;P&gt;I have a lookup table, with an ID field that has case specific alphanumeric values in it. &lt;/P&gt;

&lt;P&gt;I'm attempting to search for a single user id, however when I put one in, I see at least two results for each, due to splunk seeing the values as case insensitive. &lt;/P&gt;

&lt;P&gt;Here is an image. &lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/3151iA57BF92CF8F455B9/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;You'll notice the last letter's being of different case, yet even when using " around the field values, I still get this result set. Is there something that I am missing? &lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2017 18:12:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289953#M87679</guid>
      <dc:creator>tmarlette</dc:creator>
      <dc:date>2017-07-05T18:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289954#M87680</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;P&gt;Searching for fields values is not case sensitive, use the "where" command (in your case with the same syntax) or CASE():&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|  makeresults |  eval foo="bar Bar" |  makemv foo | mvexpand foo
|  where foo=bar
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|  makeresults |  eval foo="bar Bar" |  makemv foo | mvexpand foo
|  search foo=CASE(bar)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Cheers,&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2017 18:34:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289954#M87680</guid>
      <dc:creator>guilmxm</dc:creator>
      <dc:date>2017-07-05T18:34:07Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289955#M87681</link>
      <description>&lt;P&gt;Use &lt;CODE&gt;| where&lt;/CODE&gt;  instead of &lt;CODE&gt;| search&lt;/CODE&gt;. &lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2017 19:37:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289955#M87681</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-07-05T19:37:00Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289956#M87682</link>
      <description>&lt;P&gt;Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| inputlookup xxx.csv | regex USER_ID="05000xpmX"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 05 Jul 2017 23:15:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289956#M87682</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-07-05T23:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289957#M87683</link>
      <description>&lt;P&gt;| inputlookup xxx.csv  | eval USER_ID=case(05000xpmX) &lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2017 23:15:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289957#M87683</guid>
      <dc:creator>sbbadri</dc:creator>
      <dc:date>2017-07-05T23:15:32Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289958#M87684</link>
      <description>&lt;P&gt;I tried this, and it doesn't work, Thank you! &lt;/P&gt;</description>
      <pubDate>Thu, 06 Jul 2017 17:06:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289958#M87684</guid>
      <dc:creator>tmarlette</dc:creator>
      <dc:date>2017-07-06T17:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289959#M87685</link>
      <description>&lt;P&gt;Nice.  I wouldn't have thought of &lt;CODE&gt;regex&lt;/CODE&gt; as a solution.  Works, as long as the user id does not have special characters that translate differently in regex-land, in which case they need to be escaped.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jul 2017 18:12:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289959#M87685</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-07-06T18:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289960#M87686</link>
      <description>&lt;P&gt;This works for an individual user id, but how would I make an automatic lookup case sensitive?  Is there a way? &lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2017 16:30:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289960#M87686</guid>
      <dc:creator>tmarlette</dc:creator>
      <dc:date>2017-07-07T16:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289961#M87687</link>
      <description>&lt;P&gt;This works for any number of users ID, just use booleans as usually:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|  where foo=bar OR foo=bar2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;OR:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|  search foo=CASE(bar) OR foo=CASE(bar2)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The search command will always be case non sensitive, whenever the fields comes an automatic lookup.&lt;BR /&gt;
The only difference with automatic lookup fields will be the the field name (not the field value) will be case sensitive if it comes from a lookup. (while it is not the case with a raw data field)&lt;/P&gt;

&lt;P&gt;Guilhem&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2017 10:38:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289961#M87687</guid>
      <dc:creator>guilmxm</dc:creator>
      <dc:date>2017-07-11T10:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289962#M87688</link>
      <description>&lt;P&gt;The answer I was looking for was to use an automatic lookup and force case sensitive matching. I'm sure I worded the question poorly, and this is what the working config looks like:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[mysourcetype]
LOOKUP-SFDC-USER_NAME1 = lookup_usernames USER_ID AS USER_ID 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[lookup_usernames]
filename = lookup_usernames.csv
case_sensitive_match=true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The way to search a table for a specific username is accepted above. &lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2017 16:21:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289962#M87688</guid>
      <dc:creator>tmarlette</dc:creator>
      <dc:date>2017-07-12T16:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: Field Values Case Sensitve</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289963#M87689</link>
      <description>&lt;P&gt;This worked, thank you! &lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2017 16:22:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-Values-Case-Sensitve/m-p/289963#M87689</guid>
      <dc:creator>tmarlette</dc:creator>
      <dc:date>2017-07-12T16:22:29Z</dc:date>
    </item>
  </channel>
</rss>

