<?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: Raw json file getting truncated in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372978#M161676</link>
    <description>&lt;P&gt;Try setting the TRUNCATE to 0 to remove the limit, we also had an issue when bringing in large amounts of json data via a REST API which was resolved by setting the "response handler" to "JSONArrayHandler", which specifically handles large amounts of json data... although I am unsure if this relates purely to the REST API&lt;/P&gt;</description>
    <pubDate>Fri, 07 Apr 2017 09:23:06 GMT</pubDate>
    <dc:creator>paulbannister</dc:creator>
    <dc:date>2017-04-07T09:23:06Z</dc:date>
    <item>
      <title>Raw json file getting truncated</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372976#M161674</link>
      <description>&lt;P&gt;Using splunk developer version.  I've set TRUNCATE to 25000 and max_events to a large number as well, but the information keeps getting truncated in the event window.  I'm basically trying to import large amounts of json data from a single file.  I know I'm not the only one working with json data so I'm sure the fix is nice and easy.  &lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2017 17:17:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372976#M161674</guid>
      <dc:creator>jimbolya</dc:creator>
      <dc:date>2017-03-24T17:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: Raw json file getting truncated</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372977#M161675</link>
      <description>&lt;P&gt;Do you have an extraction_cutoff value set anywhere in your limits.conf files?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2017 22:14:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372977#M161675</guid>
      <dc:creator>briancronrath</dc:creator>
      <dc:date>2017-03-27T22:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: Raw json file getting truncated</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372978#M161676</link>
      <description>&lt;P&gt;Try setting the TRUNCATE to 0 to remove the limit, we also had an issue when bringing in large amounts of json data via a REST API which was resolved by setting the "response handler" to "JSONArrayHandler", which specifically handles large amounts of json data... although I am unsure if this relates purely to the REST API&lt;/P&gt;</description>
      <pubDate>Fri, 07 Apr 2017 09:23:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372978#M161676</guid>
      <dc:creator>paulbannister</dc:creator>
      <dc:date>2017-04-07T09:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: Raw json file getting truncated</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372979#M161677</link>
      <description>&lt;P&gt;You can handle it via props configuration for your specific source type. &lt;BR /&gt;
i.e I am using following stanza which is able to extract raw JSON file of &amp;gt; 8MB.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[cmxmap]
TRUNCATE = 0
KV_MODE = json
NO_BINARY_CHECK = true
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 07 Apr 2017 12:14:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Raw-json-file-getting-truncated/m-p/372979#M161677</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2017-04-07T12:14:58Z</dc:date>
    </item>
  </channel>
</rss>

