<?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: Hunk - gz indexation in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Hunk-gz-indexation/m-p/163584#M33160</link>
    <description>&lt;P&gt;Cool Petter.&lt;BR /&gt;
I know in Hunk all extractions and properties are applied at search time but wanted to make sure how this usual Splunk safeguard is handled using Hadoop/HDFS (which I'm still learning the ropes)&lt;BR /&gt;
Always better to confirm.&lt;/P&gt;

&lt;P&gt;Cheers&lt;/P&gt;</description>
    <pubDate>Thu, 05 Mar 2015 11:22:32 GMT</pubDate>
    <dc:creator>splunk_zen</dc:creator>
    <dc:date>2015-03-05T11:22:32Z</dc:date>
    <item>
      <title>Hunk - gz indexation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Hunk-gz-indexation/m-p/163582#M33158</link>
      <description>&lt;P&gt;Does the Splunk .gz sequential indexation constraint (a file at a time) apply while having Hadoop as an External Result Provider?&lt;BR /&gt;
Having HDFS as the "indexer" makes this somewhat of a gray area to me.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2015 11:33:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Hunk-gz-indexation/m-p/163582#M33158</guid>
      <dc:creator>splunk_zen</dc:creator>
      <dc:date>2015-03-04T11:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Hunk - gz indexation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Hunk-gz-indexation/m-p/163583#M33159</link>
      <description>&lt;P&gt;There's no index step for Hunk. You can just place your files in HDFS and search them right away!&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2015 18:54:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Hunk-gz-indexation/m-p/163583#M33159</guid>
      <dc:creator>Petter_Eriksson</dc:creator>
      <dc:date>2015-03-04T18:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: Hunk - gz indexation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Hunk-gz-indexation/m-p/163584#M33160</link>
      <description>&lt;P&gt;Cool Petter.&lt;BR /&gt;
I know in Hunk all extractions and properties are applied at search time but wanted to make sure how this usual Splunk safeguard is handled using Hadoop/HDFS (which I'm still learning the ropes)&lt;BR /&gt;
Always better to confirm.&lt;/P&gt;

&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2015 11:22:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Hunk-gz-indexation/m-p/163584#M33160</guid>
      <dc:creator>splunk_zen</dc:creator>
      <dc:date>2015-03-05T11:22:32Z</dc:date>
    </item>
  </channel>
</rss>

