<?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: syntax for outputlookup when defined in transforms.conf? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470144#M132294</link>
    <description>&lt;P&gt;Yes, Can use either way. If your results are not getting to file that might be some permission issues that are defined in transforms.conf.&lt;/P&gt;

&lt;P&gt;Hope this helps, Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 25 Oct 2019 18:37:52 GMT</pubDate>
    <dc:creator>sandeepmakkena</dc:creator>
    <dc:date>2019-10-25T18:37:52Z</dc:date>
    <item>
      <title>syntax for outputlookup when defined in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470141#M132291</link>
      <description>&lt;P&gt;I have a transforms as follows which defines a lookup &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[ABC]
filename = ABC.csv
case_sensitive_match = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Now, I am writing a saved search which updates the above lookup after executing the search. &lt;/P&gt;

&lt;P&gt;now, which among the below should I need to specify at the end of saved search and why?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| outputlookup ABC
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;OR&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| outputlookup ABC.csv
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 25 Oct 2019 17:45:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470141#M132291</guid>
      <dc:creator>pavanae</dc:creator>
      <dc:date>2019-10-25T17:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: syntax for outputlookup when defined in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470142#M132292</link>
      <description>&lt;P&gt;You can use either. But it is good form to only use the transform definition name. &lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2019 18:10:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470142#M132292</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2019-10-25T18:10:36Z</dc:date>
    </item>
    <item>
      <title>Re: syntax for outputlookup when defined in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470143#M132293</link>
      <description>&lt;P&gt;thanks for the response @starcher . So when you say transform definition name it means It's better to use the below right?&lt;/P&gt;

&lt;P&gt;My_Search | | outputlookup ABC&lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2019 18:35:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470143#M132293</guid>
      <dc:creator>pavanae</dc:creator>
      <dc:date>2019-10-25T18:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: syntax for outputlookup when defined in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470144#M132294</link>
      <description>&lt;P&gt;Yes, Can use either way. If your results are not getting to file that might be some permission issues that are defined in transforms.conf.&lt;/P&gt;

&lt;P&gt;Hope this helps, Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2019 18:37:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470144#M132294</guid>
      <dc:creator>sandeepmakkena</dc:creator>
      <dc:date>2019-10-25T18:37:52Z</dc:date>
    </item>
    <item>
      <title>Re: syntax for outputlookup when defined in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470145#M132295</link>
      <description>&lt;P&gt;Either works.  If you have multiple &lt;CODE&gt;Lookup Definitions&lt;/CODE&gt; referencing the same &lt;CODE&gt;Lookup File&lt;/CODE&gt;, then I would use the &lt;CODE&gt;Lookup File&lt;/CODE&gt;; if it is one-to-one, then I would use the &lt;CODE&gt;Lookup Definition&lt;/CODE&gt; so that people understand that there is one.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2019 19:47:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470145#M132295</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-10-25T19:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: syntax for outputlookup when defined in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470146#M132296</link>
      <description>&lt;P&gt;That is correct.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 17:35:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/syntax-for-outputlookup-when-defined-in-transforms-conf/m-p/470146#M132296</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2020-02-20T17:35:20Z</dc:date>
    </item>
  </channel>
</rss>

