<?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: data model acceleration in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/data-model-acceleration/m-p/525772#M9415</link>
    <description>&lt;P&gt;Well, its not permanent&amp;nbsp;&lt;/P&gt;&lt;P&gt;we want to run some statistics over data older than a year&lt;/P&gt;</description>
    <pubDate>Wed, 21 Oct 2020 12:59:12 GMT</pubDate>
    <dc:creator>sarit_s</dc:creator>
    <dc:date>2020-10-21T12:59:12Z</dc:date>
    <item>
      <title>data model acceleration</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/data-model-acceleration/m-p/525728#M9413</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have data model that i want to change the acceleration time to all time.&lt;/P&gt;&lt;P&gt;since im working with kubernetece the change has to be in the config files directly and not through the ui.&lt;/P&gt;&lt;P&gt;i saw in the documentation that empty string for&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;acceleration.earliest_time&lt;/PRE&gt;&lt;P&gt;means all time&lt;/P&gt;&lt;P&gt;but when i change this field to be empty, the configuration in the ui changed to be 1 day instead of all time as it should.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;any ideas ?&lt;/P&gt;&lt;P&gt;thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2020 10:05:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/data-model-acceleration/m-p/525728#M9413</guid>
      <dc:creator>sarit_s</dc:creator>
      <dc:date>2020-10-21T10:05:14Z</dc:date>
    </item>
    <item>
      <title>Re: data model acceleration</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/data-model-acceleration/m-p/525768#M9414</link>
      <description>&lt;P&gt;Searching All Time rarely is a good idea, especially for datamodels.&amp;nbsp; The goal of DMA is to make accessing your data faster in routine searches.&amp;nbsp; One-off and non-routine searches usually can wait the extra time it takes to gather the data.&amp;nbsp; Otherwise, you're putting extra work on your system to search (and store) more than is necessary.&lt;/P&gt;&lt;P&gt;What is the use case for having All Time data accelerated?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2020 12:53:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/data-model-acceleration/m-p/525768#M9414</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-10-21T12:53:58Z</dc:date>
    </item>
    <item>
      <title>Re: data model acceleration</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/data-model-acceleration/m-p/525772#M9415</link>
      <description>&lt;P&gt;Well, its not permanent&amp;nbsp;&lt;/P&gt;&lt;P&gt;we want to run some statistics over data older than a year&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2020 12:59:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/data-model-acceleration/m-p/525772#M9415</guid>
      <dc:creator>sarit_s</dc:creator>
      <dc:date>2020-10-21T12:59:12Z</dc:date>
    </item>
  </channel>
</rss>

