Splunk Search

lookup field value case sensitivity

constantinetamp
Observer

While field values are not case sensitive by default on Splunk, when we use lookups the default setting for the field values is to be case sensitive.

I can't think of any valid use case of that inconsistency, is there any reason that I could possibly be missing?

note: I am aware that you can overwritte the case sensitivity setting when importing a lookup, I am merely wondering why doen't the default option for lookup field values align with the overall Splunk logic of field values being non case sensitive.

0 Karma

to4kawa
SplunkTrust
SplunkTrust

https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Lookup

Syntax:

lookup [local=<bool>] [update=<bool>] <lookup-table-name> ( <lookup-field> [AS <event-field>] )... [ OUTPUT | OUTPUTNEW (<lookup-destfield> [AS <event-destfield>] )... ]

the default setting for the field values is to be case sensitive.
What are you talking about?

0 Karma

constantinetamp
Observer

well what you pasted above is exactly the same thing as I'm stating on my question.

0 Karma

to4kawa
SplunkTrust
SplunkTrust
0 Karma

constantinetamp
Observer

I'm talking about the field values in lookups being case sensitive, the terms fieldname and fieldvalue in the lookup command that you're referring to are irrelevant to my question

0 Karma

to4kawa
SplunkTrust
SplunkTrust

While field values are not case sensitive by default on Splunk
this is wrong assumption.

0 Karma

constantinetamp
Observer

It clearly isn't an assumption that field values are case insentivite and that field names are case sensitive on Splunk, that's clearly stated on the official Splunk documentation, and it's definitely not a wrong one:

https://answers.splunk.com/answers/65/are-field-values-case-sensitive.html

0 Karma