<?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 Splunk bug with lookups matching on fields that include spaces in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200723#M58199</link>
    <description>&lt;P&gt;OK one of our devs discovered a weird bug where if a lookup is being performed on a CSV where the field to match contained spaces.&lt;/P&gt;

&lt;P&gt;The results are consistently weird between Linux and Windows.&lt;/P&gt;

&lt;P&gt;It doesn't matter if the CSV lookup is&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Unix or Windows format (ie CRLF or just LF newlines)&lt;/LI&gt;
&lt;LI&gt;Placing the lookup field in quotes makes no difference.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;I have a sample app here which demonstrates the bug using internal Splunk data.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.phoenixdigital.com/splunk/lookup_bug.spl"&gt;http://www.phoenixdigital.com/splunk/lookup_bug.spl&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The screenshot shows the bug in action.&lt;BR /&gt;
(see attached screenshot)&lt;/P&gt;

&lt;P&gt;You can see in this example the group=pipeline data does not appear in the results on the left however it does on the data on the right when you change&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;group_is_it_searchable=no
to
group_is_it_searchable=*no
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I will put the major components here for clarity though.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[splunkd]

LOOKUP-1-first = group_extend group OUTPUT group_spaced, group_bug_prediction
LOOKUP-2-second = spacing_issue group_spaced OUTPUT group_is_it_searchable
&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;[group_extend]
filename = group_extend.csv

[spacing_issue]
filename = spacing_issue.csv
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;group_extend.csv&lt;/STRONG&gt; (This lookup creates a field 'group_spaced' which will be used for the next lookup)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;group,group_spaced,group_bug_prediction
pipeline,pipe line,this will break
queue,queue,this will work
per_host_thruput,per host thruput,this will break
tpool,tpool,this will work
deploy-connections,deploy connections,this will break
map,map,this will work
per_source_thruput,per source thruput,this will break
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;spacing_issue,csv&lt;/STRONG&gt; (The second lookup which provides inconsistent results)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;group_spaced,group_is_it_searchable
queue,yes
per host thruput,no
tpool,yes
pipe line,no
deploy connections,no
map,yes
per source thruput,no
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 27 Oct 2015 05:15:20 GMT</pubDate>
    <dc:creator>phoenixdigital</dc:creator>
    <dc:date>2015-10-27T05:15:20Z</dc:date>
    <item>
      <title>Splunk bug with lookups matching on fields that include spaces</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200723#M58199</link>
      <description>&lt;P&gt;OK one of our devs discovered a weird bug where if a lookup is being performed on a CSV where the field to match contained spaces.&lt;/P&gt;

&lt;P&gt;The results are consistently weird between Linux and Windows.&lt;/P&gt;

&lt;P&gt;It doesn't matter if the CSV lookup is&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Unix or Windows format (ie CRLF or just LF newlines)&lt;/LI&gt;
&lt;LI&gt;Placing the lookup field in quotes makes no difference.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;I have a sample app here which demonstrates the bug using internal Splunk data.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.phoenixdigital.com/splunk/lookup_bug.spl"&gt;http://www.phoenixdigital.com/splunk/lookup_bug.spl&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The screenshot shows the bug in action.&lt;BR /&gt;
(see attached screenshot)&lt;/P&gt;

&lt;P&gt;You can see in this example the group=pipeline data does not appear in the results on the left however it does on the data on the right when you change&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;group_is_it_searchable=no
to
group_is_it_searchable=*no
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I will put the major components here for clarity though.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[splunkd]

LOOKUP-1-first = group_extend group OUTPUT group_spaced, group_bug_prediction
LOOKUP-2-second = spacing_issue group_spaced OUTPUT group_is_it_searchable
&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;[group_extend]
filename = group_extend.csv

[spacing_issue]
filename = spacing_issue.csv
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;group_extend.csv&lt;/STRONG&gt; (This lookup creates a field 'group_spaced' which will be used for the next lookup)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;group,group_spaced,group_bug_prediction
pipeline,pipe line,this will break
queue,queue,this will work
per_host_thruput,per host thruput,this will break
tpool,tpool,this will work
deploy-connections,deploy connections,this will break
map,map,this will work
per_source_thruput,per source thruput,this will break
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;spacing_issue,csv&lt;/STRONG&gt; (The second lookup which provides inconsistent results)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;group_spaced,group_is_it_searchable
queue,yes
per host thruput,no
tpool,yes
pipe line,no
deploy connections,no
map,yes
per source thruput,no
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 27 Oct 2015 05:15:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200723#M58199</guid>
      <dc:creator>phoenixdigital</dc:creator>
      <dc:date>2015-10-27T05:15:20Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk bug with lookups matching on fields that include spaces</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200724#M58200</link>
      <description>&lt;P&gt;Hi @phoenixdigital&lt;/P&gt;

&lt;P&gt;Did you already submit the bug here? &lt;BR /&gt;
&lt;A href="http://www.splunk.com/r/bugs"&gt;http://www.splunk.com/r/bugs&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Posting on Answers won't really help to get it looked at. Also, if other users have previously submitted this bug as well, it'll help build traction on the issue.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2015 17:54:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200724#M58200</guid>
      <dc:creator>ppablo</dc:creator>
      <dc:date>2015-10-27T17:54:41Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk bug with lookups matching on fields that include spaces</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200725#M58201</link>
      <description>&lt;P&gt;I will post there just wanted to see if there was anything obviously wrong with my test before I did.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2015 21:26:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200725#M58201</guid>
      <dc:creator>phoenixdigital</dc:creator>
      <dc:date>2015-10-27T21:26:47Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk bug with lookups matching on fields that include spaces</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200726#M58202</link>
      <description>&lt;P&gt;ohh ok no worries. Thanks for being thoughtful &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Oct 2015 22:44:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200726#M58202</guid>
      <dc:creator>ppablo</dc:creator>
      <dc:date>2015-10-28T22:44:03Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk bug with lookups matching on fields that include spaces</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200727#M58203</link>
      <description>&lt;P&gt;Hi phoenixdigital, this looks like a well thought out and demonstrated bug report. As ppablo mentioned, you should submit a report at &lt;A href="http://www.splunk.com/r/bugs"&gt;http://www.splunk.com/r/bugs&lt;/A&gt;. I'll be interested to hear how it goes! &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Oct 2015 01:24:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200727#M58203</guid>
      <dc:creator>muebel</dc:creator>
      <dc:date>2015-10-29T01:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk bug with lookups matching on fields that include spaces</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200728#M58204</link>
      <description>&lt;P&gt;Thanks meubel and ppablo submitted as a bug pending response................&lt;/P&gt;</description>
      <pubDate>Fri, 30 Oct 2015 03:01:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200728#M58204</guid>
      <dc:creator>phoenixdigital</dc:creator>
      <dc:date>2015-10-30T03:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk bug with lookups matching on fields that include spaces</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200729#M58205</link>
      <description>&lt;P&gt;This turned out to be an issue of "nested lookups" which is not supported in any of splunk versions as of this writing.&lt;BR /&gt;&lt;BR /&gt;
You would see inconsistent results - The situation is it works under certain instance and not on another. Please avoid any chain lookups.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 00:40:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-bug-with-lookups-matching-on-fields-that-include-spaces/m-p/200729#M58205</guid>
      <dc:creator>sylim_splunk</dc:creator>
      <dc:date>2016-06-06T00:40:01Z</dc:date>
    </item>
  </channel>
</rss>

