<?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: Uppercase, Lowercase confusion in Splunk commands in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Uppercase-Lowercase-confusion-in-Splunk-commands/m-p/540525#M4997</link>
    <description>&lt;P&gt;Usually, you find this info in notes under each documentation about commands/operators.&lt;BR /&gt;&lt;BR /&gt;Example you can check this link:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/8.1.2012/Search/Booleanexpressions" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/8.1.2012/Search/Booleanexpressions&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Here the document says:&amp;nbsp;&lt;STRONG&gt;The operators must be capitalized.&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;It is best to use capital letters for all clauses like AS, BY, IN and operators (OR, AND, NOT).&lt;/P&gt;</description>
    <pubDate>Fri, 19 Feb 2021 13:12:01 GMT</pubDate>
    <dc:creator>manjunathmeti</dc:creator>
    <dc:date>2021-02-19T13:12:01Z</dc:date>
    <item>
      <title>Uppercase, Lowercase confusion in Splunk commands</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Uppercase-Lowercase-confusion-in-Splunk-commands/m-p/540515#M4995</link>
      <description>&lt;P&gt;Is there any reason that there are some command parameters that needs uppercase to work and some can use both lower and uppercase?&lt;/P&gt;&lt;P&gt;Eks both of this does work&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;| timechart count by index&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;| timechart count BY index&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Same with these, works fine.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;| lookup dnslookup clientip as src_ip&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;| lookup dnslookup clientip AS src_ip&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;But this fails&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;index in (test1 test2)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Needs to be uppercase&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;index IN (test1 test2)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This fails&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;cat or dog&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Needs to be uppercase&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;cat OR dog&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Where do I find a list and regulation on when to use upper/Lowercase (IN OR AND BY AS etc)?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 12:45:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Uppercase-Lowercase-confusion-in-Splunk-commands/m-p/540515#M4995</guid>
      <dc:creator>jotne</dc:creator>
      <dc:date>2021-02-19T12:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: Uppercase, Lowercase confusion in Splunk commands</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Uppercase-Lowercase-confusion-in-Splunk-commands/m-p/540525#M4997</link>
      <description>&lt;P&gt;Usually, you find this info in notes under each documentation about commands/operators.&lt;BR /&gt;&lt;BR /&gt;Example you can check this link:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/8.1.2012/Search/Booleanexpressions" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/8.1.2012/Search/Booleanexpressions&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Here the document says:&amp;nbsp;&lt;STRONG&gt;The operators must be capitalized.&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;It is best to use capital letters for all clauses like AS, BY, IN and operators (OR, AND, NOT).&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 13:12:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Uppercase-Lowercase-confusion-in-Splunk-commands/m-p/540525#M4997</guid>
      <dc:creator>manjunathmeti</dc:creator>
      <dc:date>2021-02-19T13:12:01Z</dc:date>
    </item>
  </channel>
</rss>

