<?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 What fields are displayed when using the &amp;quot;map&amp;quot; command in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113788#M30015</link>
    <description>&lt;P&gt;Hey all,&lt;/P&gt;

&lt;P&gt;I have a search that uses the map command. It looks like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;myBaseSearch&amp;gt;
| map [search index=main sourcetype=perfLogging userID=$userId$ splunk_server=$splunk_server$]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The resulting table displays a bunch of fields that aren't part of the perfLogging sourcetype; they are part of other sourcetypes in the main index though. These fields are empty, which leads me to believe the search is correct, but I am curious...&lt;/P&gt;

&lt;P&gt;Is this expected behavior for the map command? In other words, should the resulting table have a column for &lt;EM&gt;all&lt;/EM&gt; fields discovered in the index?&lt;/P&gt;</description>
    <pubDate>Fri, 20 Jun 2014 18:12:01 GMT</pubDate>
    <dc:creator>bruceclarke</dc:creator>
    <dc:date>2014-06-20T18:12:01Z</dc:date>
    <item>
      <title>What fields are displayed when using the "map" command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113788#M30015</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;

&lt;P&gt;I have a search that uses the map command. It looks like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;myBaseSearch&amp;gt;
| map [search index=main sourcetype=perfLogging userID=$userId$ splunk_server=$splunk_server$]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The resulting table displays a bunch of fields that aren't part of the perfLogging sourcetype; they are part of other sourcetypes in the main index though. These fields are empty, which leads me to believe the search is correct, but I am curious...&lt;/P&gt;

&lt;P&gt;Is this expected behavior for the map command? In other words, should the resulting table have a column for &lt;EM&gt;all&lt;/EM&gt; fields discovered in the index?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jun 2014 18:12:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113788#M30015</guid>
      <dc:creator>bruceclarke</dc:creator>
      <dc:date>2014-06-20T18:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: What fields are displayed when using the "map" command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113789#M30016</link>
      <description>&lt;P&gt;I've found the generic display of results after &lt;CODE&gt;map&lt;/CODE&gt; weird at times - but you can rely on any computation done afterwards to be correct, for example a &lt;CODE&gt;stats&lt;/CODE&gt; applied to the results.&lt;/P&gt;

&lt;P&gt;Why are you using &lt;CODE&gt;map&lt;/CODE&gt; for that though? It seems to me as if you could just use the base search as a subsearch producing a large filter in the now mapped search.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jun 2014 18:50:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113789#M30016</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-06-20T18:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: What fields are displayed when using the "map" command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113790#M30017</link>
      <description>&lt;P&gt;Sorry, I didn't post the complete search. The base search actually provides time constraints for the mapped search.&lt;/P&gt;

&lt;P&gt;Also, we are going to do more computation on the results, but I noticed the weird display first and wanted to see if anyone else saw this issue.&lt;/P&gt;

&lt;P&gt;Thanks for the explanation.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jun 2014 18:55:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113790#M30017</guid>
      <dc:creator>bruceclarke</dc:creator>
      <dc:date>2014-06-20T18:55:27Z</dc:date>
    </item>
    <item>
      <title>Re: What fields are displayed when using the "map" command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113791#M30018</link>
      <description>&lt;P&gt;Ah, I see. In that case using &lt;CODE&gt;map&lt;/CODE&gt; likely is the way to go.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jun 2014 18:58:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-fields-are-displayed-when-using-the-quot-map-quot-command/m-p/113791#M30018</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-06-20T18:58:52Z</dc:date>
    </item>
  </channel>
</rss>

