<?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: lookup table issues in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/lookup-table-issues/m-p/38108#M8650</link>
    <description>&lt;P&gt;There are some field name inconsistencies between your description and your example...&lt;/P&gt;

&lt;P&gt;Based on your description, try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;source="A1.txt" | lookup A1_timer field_A AS field_a | table field_A field_b field_B field_C 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Three separate steps: search, lookup, and formatting.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jul 2011 19:06:13 GMT</pubDate>
    <dc:creator>jrwilk01</dc:creator>
    <dc:date>2011-07-06T19:06:13Z</dc:date>
    <item>
      <title>lookup table issues</title>
      <link>https://community.splunk.com/t5/Splunk-Search/lookup-table-issues/m-p/38107#M8649</link>
      <description>&lt;P&gt;I have a lookup table set up like&lt;/P&gt;

&lt;P&gt;lookup table name A1_timer&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;field_a   filed_b
test1     value1
test2     value2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;source A1 looks like&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;field_A = test1  field_B = foo field_C = bar
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I would like my output to look like:&lt;/P&gt;

&lt;P&gt;field_A from source A1, field_b from lookup table A1_timer, field_B from source A1, field_C from source A1&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;source="A1.txt" lookup A1_timer A1_a OUTPUT A1_A A1_timer_b A1_b A1_c
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;the value in the source file A1.txt in filed A1_a is equal to lookup table A1_timer value A1_timer_a&lt;/P&gt;

&lt;P&gt;I'm also getting sourcetype too small on my lookup table&lt;/P&gt;

&lt;P&gt;any ideas?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:42:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/lookup-table-issues/m-p/38107#M8649</guid>
      <dc:creator>fresned</dc:creator>
      <dc:date>2020-09-28T09:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: lookup table issues</title>
      <link>https://community.splunk.com/t5/Splunk-Search/lookup-table-issues/m-p/38108#M8650</link>
      <description>&lt;P&gt;There are some field name inconsistencies between your description and your example...&lt;/P&gt;

&lt;P&gt;Based on your description, try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;source="A1.txt" | lookup A1_timer field_A AS field_a | table field_A field_b field_B field_C 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Three separate steps: search, lookup, and formatting.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2011 19:06:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/lookup-table-issues/m-p/38108#M8650</guid>
      <dc:creator>jrwilk01</dc:creator>
      <dc:date>2011-07-06T19:06:13Z</dc:date>
    </item>
  </channel>
</rss>

