<?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: Query about datamodel acceleration and how data is stored in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261912#M2311</link>
    <description>&lt;P&gt;thanks Martin for your help. Accepted your answer.&lt;/P&gt;</description>
    <pubDate>Sat, 26 Mar 2016 09:21:02 GMT</pubDate>
    <dc:creator>koshyk</dc:creator>
    <dc:date>2016-03-26T09:21:02Z</dc:date>
    <item>
      <title>Query about datamodel acceleration and how data is stored</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261908#M2307</link>
      <description>&lt;P&gt;I was going through the documents on Datamodel Acceleration. Can you please help me in confirming if my understanding below is correct?&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;An Addon (TA) does the Data interpretation, classification, enrichment and normalisation.  Most key value pairs are extracted during search-time.&lt;/LI&gt;
&lt;LI&gt; A data model then abstracts/maps multiple such datasets (and brings hierarchy) during &lt;STRONG&gt;search-time&lt;/STRONG&gt; . So datamodel as such does not speed-up searches, but just abstracts to make it easy for end-user.&lt;/LI&gt;
&lt;LI&gt;During  acceleration of datamodel,  key value pairs (which were search-time in Step2) are extracted and stored as  indexed key-value pairs ?&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;The fields stored in .tsidx files, are independent of  TA's and any search on it, should NOT require effort on re-extracting data from _raw?&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Fri, 25 Mar 2016 00:02:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261908#M2307</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2016-03-25T00:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: Query about datamodel acceleration and how data is stored</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261909#M2308</link>
      <description>&lt;OL&gt;
&lt;LI&gt;Yup.&lt;/LI&gt;
&lt;LI&gt;Yeah.&lt;/LI&gt;
&lt;LI&gt;Fields in an accelerated data model still are search-time for most purposes. For example, index-time fields cannot be added retroactively while you can add a field to a data model and use that without re-indexing... though there will be an acceleration rebuild. From the performance point of view they behave like indexed fields, and are available through &lt;CODE&gt;tstats&lt;/CODE&gt;.&lt;/LI&gt;
&lt;LI&gt;I'm not quite sure where you're going for here, data model accelerations &lt;EM&gt;are&lt;/EM&gt; dependent on TAs - see question one. For already-accelerated data there's no need to descend into &lt;CODE&gt;_raw&lt;/CODE&gt;, yes. For very recent data before acceleration happened or for very old data beyond the acceleration window the datamodel-backed search will by default descend into &lt;CODE&gt;_raw&lt;/CODE&gt; to complete the results.&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Sat, 26 Mar 2016 09:03:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261909#M2308</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2016-03-26T09:03:50Z</dc:date>
    </item>
    <item>
      <title>Re: Query about datamodel acceleration and how data is stored</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261910#M2309</link>
      <description>&lt;P&gt;@martin_mueller. Thank you &lt;/P&gt;

&lt;P&gt;Regarding (4) : I meant to ask once the data is in high perfomance store, the extraction is independent of TAs? or during a search, will it still have to go through all TA regex etc?&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2016 09:13:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261910#M2309</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2016-03-26T09:13:08Z</dc:date>
    </item>
    <item>
      <title>Re: Query about datamodel acceleration and how data is stored</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261911#M2310</link>
      <description>&lt;P&gt;It's not going to apply the regexes to the raw data, the values will already have been extracted while the acceleration searches run in the background.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2016 09:19:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261911#M2310</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2016-03-26T09:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: Query about datamodel acceleration and how data is stored</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261912#M2311</link>
      <description>&lt;P&gt;thanks Martin for your help. Accepted your answer.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2016 09:21:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/261912#M2311</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2016-03-26T09:21:02Z</dc:date>
    </item>
    <item>
      <title>Re: Query about datamodel acceleration and how data is stored</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/527864#M4807</link>
      <description>&lt;P&gt;Yes. Once data is in accelerated DM (DMA), in other words data was added into summary index of a given data model (storing in to DM summary index is called saving into so called High Performace Analytics Store (HPA) from marketing perspective) you do NOT need any TA extraction/parsing capabilities as you already filled the fields with values in some form before indexing/writing into summary index. '&lt;/P&gt;&lt;P&gt;Just a comment.&lt;/P&gt;&lt;P&gt;Storing events into a summary index means that data will get new sourcetype - "stash". This data is not count against Splunk license (its seen as internal data). However, when you save data into a summary index under some custom sourcetype (eg. sourcetyp="mysourcetype") using `collect` command then this data might in theory be parsed by TA that has parsing rules for this custom sourcetype.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Nov 2020 09:54:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Query-about-datamodel-acceleration-and-how-data-is-stored/m-p/527864#M4807</guid>
      <dc:creator>tomasmoser</dc:creator>
      <dc:date>2020-11-04T09:54:42Z</dc:date>
    </item>
  </channel>
</rss>

