<?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: inputlookup special fields in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557003#M158189</link>
    <description>&lt;P&gt;Yes, there is a difference between &lt;FONT face="courier new,courier"&gt;lookup&lt;/FONT&gt; and &lt;FONT face="courier new,courier"&gt;inputlookup&lt;/FONT&gt;, but it's not that strange.&lt;/P&gt;&lt;P&gt;The &lt;FONT face="courier new,courier"&gt;lookup&lt;/FONT&gt; command searches a lookup table for the given field(s) and returns the corresponding fields for the found value.&amp;nbsp; It's like getting someone's phone number from a telephone directory (remember those?) - find name, return number.&lt;/P&gt;&lt;P&gt;The &lt;FONT face="courier new,courier"&gt;inputlookup&lt;/FONT&gt; command returns the entire contents of the lookup file (unless the &lt;FONT face="courier new,courier"&gt;where&lt;/FONT&gt; option is used).&amp;nbsp; It's the equivalent of saying "read to me the whole phone book".&amp;nbsp; It has nothing to do with how the columns are named.&lt;/P&gt;&lt;P&gt;I hope this explains why your queries behave the way they do.&lt;/P&gt;</description>
    <pubDate>Thu, 24 Jun 2021 14:29:59 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2021-06-24T14:29:59Z</dc:date>
    <item>
      <title>inputlookup special fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/556989#M158183</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I have recently found there is a strange difference between &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;lookup&lt;/FONT&gt; &lt;/STRONG&gt;and &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;inputlookup&lt;/FONT&gt; &lt;/STRONG&gt;commands.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;|makeresults | eval uid="asdf" | lookup mydata uid 

|makeresults | eval uid="asdf" | join uid [| inputlookup mydata] &lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The "&lt;EM&gt;mydata&lt;/EM&gt;" lookup is a kvstore collection, with the following columns&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;uid, name, address, fields&lt;/FONT&gt;&lt;BR /&gt;I was expecting these two queries to have the same results, but no.&lt;BR /&gt;It seems the column "fields" is an array and it's returning a lot of data when used with the &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;inputlookup&lt;/FONT&gt;&lt;/STRONG&gt; command , which is not the case with the first (lookup) query.&lt;/P&gt;&lt;P&gt;The lookup results are like this:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;_key | uid&amp;nbsp; | name | address | fields&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;...&amp;nbsp; | asdf | john | yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | (empty)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;The inputlookup results are like this:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;_key | uid&amp;nbsp; | name | address | fields.town | fields.country&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;...&amp;nbsp; | asdf | john | yes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | chicago&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | usa&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;I didn't find any documentation about this.&lt;BR /&gt;Your input is welcomed.&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 15:08:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/556989#M158183</guid>
      <dc:creator>acadea</dc:creator>
      <dc:date>2021-06-24T15:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: inputlookup special fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557003#M158189</link>
      <description>&lt;P&gt;Yes, there is a difference between &lt;FONT face="courier new,courier"&gt;lookup&lt;/FONT&gt; and &lt;FONT face="courier new,courier"&gt;inputlookup&lt;/FONT&gt;, but it's not that strange.&lt;/P&gt;&lt;P&gt;The &lt;FONT face="courier new,courier"&gt;lookup&lt;/FONT&gt; command searches a lookup table for the given field(s) and returns the corresponding fields for the found value.&amp;nbsp; It's like getting someone's phone number from a telephone directory (remember those?) - find name, return number.&lt;/P&gt;&lt;P&gt;The &lt;FONT face="courier new,courier"&gt;inputlookup&lt;/FONT&gt; command returns the entire contents of the lookup file (unless the &lt;FONT face="courier new,courier"&gt;where&lt;/FONT&gt; option is used).&amp;nbsp; It's the equivalent of saying "read to me the whole phone book".&amp;nbsp; It has nothing to do with how the columns are named.&lt;/P&gt;&lt;P&gt;I hope this explains why your queries behave the way they do.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 14:29:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557003#M158189</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-06-24T14:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: inputlookup special fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557004#M158190</link>
      <description>&lt;P&gt;that's the definition, it's obvious they are different commands&lt;/P&gt;&lt;P&gt;but the results of those two commands should have been the same.&lt;/P&gt;&lt;P&gt;I'm still digging, it seems the "fields" it's an array&lt;/P&gt;&lt;P&gt;that makes me think &lt;FONT face="courier new,courier"&gt;lookup &lt;/FONT&gt;cannot deal with displaying&amp;nbsp; arrays while &lt;FONT face="courier new,courier"&gt;inputlookup &lt;/FONT&gt;can show them&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 14:38:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557004#M158190</guid>
      <dc:creator>acadea</dc:creator>
      <dc:date>2021-06-24T14:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: inputlookup special fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557005#M158191</link>
      <description>&lt;P&gt;I think the difference in output comes from the &lt;FONT face="courier new,courier"&gt;join&lt;/FONT&gt; command,&amp;nbsp; By default, it uses an inner join when perhaps you're expecting an outer join.&lt;/P&gt;&lt;P&gt;Try&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;|makeresults | eval uid="asdf" | join type=outer uid [| inputlookup mydata]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 14:42:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557005#M158191</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-06-24T14:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: inputlookup special fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557007#M158192</link>
      <description>&lt;P&gt;thank you,&lt;BR /&gt;I've edited/updated the initial question with an example&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 14:45:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/inputlookup-special-fields/m-p/557007#M158192</guid>
      <dc:creator>acadea</dc:creator>
      <dc:date>2021-06-24T14:45:26Z</dc:date>
    </item>
  </channel>
</rss>

