<?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: Fillnull doesn't work without specfying a field in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366445#M108098</link>
    <description>&lt;P&gt;Hi @kamlesh_vaghela &lt;/P&gt;

&lt;P&gt;the documentation states: &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;Description&lt;BR /&gt;
Replaces null values with a specified value. Null values are field values that are missing in a particular result but present in another result. Use fillnull to replace null field values with a string. &lt;STRONG&gt;If you do not specify a field list, fillnull replaces all null values with 0 (the default) or a user-supplied string.&lt;/STRONG&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;The last sentence in bold is interesting. &lt;/P&gt;

&lt;P&gt;But your example is also quite good, which leads me to believe that either the documentation is unclear on this, and should be updated, or, this is a bug.  &lt;/P&gt;</description>
    <pubDate>Sat, 18 Aug 2018 13:57:37 GMT</pubDate>
    <dc:creator>anirbandasdeb</dc:creator>
    <dc:date>2018-08-18T13:57:37Z</dc:date>
    <item>
      <title>Why does Fillnull not work without specifying a field?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366440#M108093</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;If I try to run this search, the value of my_null_field doesn't change to "?"&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;| makeresults 
| table _time my_null_field
| fillnull value="?"
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;The fillnull documentation says that if you don't specify a field it should apply to all fields. Strangely when I specify that field it works!&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;| makeresults 
| table _time my_null_field
| fillnull my_null_field value="?"
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;Even if I do&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;| eval my_null_field = null()
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;before the fillnull, it's still not adding the question mark.&lt;/P&gt;
&lt;P&gt;Does anyone know if I'm missing something or if this is a bug?&lt;BR /&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2023 18:23:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366440#M108093</guid>
      <dc:creator>606866581</dc:creator>
      <dc:date>2023-08-01T18:23:57Z</dc:date>
    </item>
    <item>
      <title>Re: Fillnull doesn't work without specfying a field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366441#M108094</link>
      <description>&lt;P&gt;I can reproduce on 7.0.3, so it seems like it's a bug in fillnull.&lt;BR /&gt;&lt;BR /&gt;
Will check 7.1 after I get the kids off to school.  If it fails there, then I'd file a docs feedback on the fillnull page and let them confirm, and/or a support ticket and make them fix it.&lt;/P&gt;

&lt;P&gt;Nice catch!&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2018 11:35:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366441#M108094</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2018-04-27T11:35:11Z</dc:date>
    </item>
    <item>
      <title>Re: Fillnull doesn't work without specfying a field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366442#M108095</link>
      <description>&lt;P&gt;Seems that for some reason the behavior is different, based on what the original data type was. I got the same results for the queries that you tried. Same problem when starting with a lookup. But starting with indexed data worked, so something like &lt;BR /&gt;
    &lt;CODE&gt;index=_internal&lt;BR /&gt;
    | table _time, field_that_definitely_doesnt_exist &lt;BR /&gt;
    | fillnull value="?"&lt;/CODE&gt;&lt;BR /&gt;
produced the expected result with the field_that_definitely_doesnt_exist field filled with "?".&lt;/P&gt;

&lt;P&gt;Edit: For me the above query, that starts from indexed data, works in 7.0.3, but not in 7.1.0. Weird.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 19:17:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366442#M108095</guid>
      <dc:creator>janispelss</dc:creator>
      <dc:date>2020-09-29T19:17:01Z</dc:date>
    </item>
    <item>
      <title>Re: Fillnull doesn't work without specfying a field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366443#M108096</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;You are right, i test in Splunk Entreprise 7.1 i have the same probleme,&lt;BR /&gt;
You can use if function&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| makeresults 
 | table _time my_null_field | eval my_null_field =if(isnull(my_null_field),"?","")
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 27 Apr 2018 11:45:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366443#M108096</guid>
      <dc:creator>TISKAR</dc:creator>
      <dc:date>2018-04-27T11:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: Fillnull doesn't work without specfying a field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366444#M108097</link>
      <description>&lt;P&gt;HI @606866581 ,&lt;/P&gt;

&lt;P&gt;Yeah It's strange. &lt;/P&gt;

&lt;P&gt;But when I go through documentation I found a sentence in description.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Null values are field values that are missing in a particular result but present in another result&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Description
Replaces null values with a specified value. **Null values are field values that are missing in a particular result but present in another result**. Use fillnull to replace null field values with a string. If you do not specify a field list, fillnull replaces all null values with 0 (the default) or a user-supplied string
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I think it is considering those field who has value from whole result.&lt;/P&gt;

&lt;P&gt;Please execute below search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| makeresults 
| eval my_null_field = "Test" 
| table _time my_null_field 
| append 
    [| makeresults 
    | table _time my_null_field 
        ] 
| fillnull value=NULL
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Documentation Link : &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/fillnull"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/fillnull&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Happy Splunking&lt;/STRONG&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2018 11:51:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366444#M108097</guid>
      <dc:creator>kamlesh_vaghela</dc:creator>
      <dc:date>2018-04-27T11:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: Fillnull doesn't work without specfying a field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366445#M108098</link>
      <description>&lt;P&gt;Hi @kamlesh_vaghela &lt;/P&gt;

&lt;P&gt;the documentation states: &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;Description&lt;BR /&gt;
Replaces null values with a specified value. Null values are field values that are missing in a particular result but present in another result. Use fillnull to replace null field values with a string. &lt;STRONG&gt;If you do not specify a field list, fillnull replaces all null values with 0 (the default) or a user-supplied string.&lt;/STRONG&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;The last sentence in bold is interesting. &lt;/P&gt;

&lt;P&gt;But your example is also quite good, which leads me to believe that either the documentation is unclear on this, and should be updated, or, this is a bug.  &lt;/P&gt;</description>
      <pubDate>Sat, 18 Aug 2018 13:57:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-Fillnull-not-work-without-specifying-a-field/m-p/366445#M108098</guid>
      <dc:creator>anirbandasdeb</dc:creator>
      <dc:date>2018-08-18T13:57:37Z</dc:date>
    </item>
  </channel>
</rss>

