<?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 Indexed CSV wont line break? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexed-CSV-wont-line-break/m-p/20403#M2986</link>
    <description>&lt;P&gt;Im indexing a CSV file and i have SHOULD_LINEMERGE set to "false" so it will break after each new line.&lt;/P&gt;

&lt;P&gt;However per 24 hour period (and about 600,000 events), I get ~50 events which are not line broken correctly and have half of the event as a new event - How is this even happening if I have SHOULD_LINEMERGE=false? Isnt the default to break at a new line?&lt;/P&gt;

&lt;P&gt;The only think I am thinking is that a small subset of the events in the CSV are broken over two lines? (If that's even possible) Or is there a limit to the amount of characters that Splunk will check for a line break, before it just breaks the event at the limit?? So basically meaning that we had a few very long entries in the CSV file which Splunk didn't check all the way to the end due to a limit of some sort??&lt;/P&gt;</description>
    <pubDate>Thu, 05 Apr 2012 17:19:54 GMT</pubDate>
    <dc:creator>jdunlea_splunk</dc:creator>
    <dc:date>2012-04-05T17:19:54Z</dc:date>
    <item>
      <title>Indexed CSV wont line break?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexed-CSV-wont-line-break/m-p/20403#M2986</link>
      <description>&lt;P&gt;Im indexing a CSV file and i have SHOULD_LINEMERGE set to "false" so it will break after each new line.&lt;/P&gt;

&lt;P&gt;However per 24 hour period (and about 600,000 events), I get ~50 events which are not line broken correctly and have half of the event as a new event - How is this even happening if I have SHOULD_LINEMERGE=false? Isnt the default to break at a new line?&lt;/P&gt;

&lt;P&gt;The only think I am thinking is that a small subset of the events in the CSV are broken over two lines? (If that's even possible) Or is there a limit to the amount of characters that Splunk will check for a line break, before it just breaks the event at the limit?? So basically meaning that we had a few very long entries in the CSV file which Splunk didn't check all the way to the end due to a limit of some sort??&lt;/P&gt;</description>
      <pubDate>Thu, 05 Apr 2012 17:19:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexed-CSV-wont-line-break/m-p/20403#M2986</guid>
      <dc:creator>jdunlea_splunk</dc:creator>
      <dc:date>2012-04-05T17:19:54Z</dc:date>
    </item>
    <item>
      <title>Re: Indexed CSV wont line break?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexed-CSV-wont-line-break/m-p/20404#M2987</link>
      <description>&lt;P&gt;The only time I've run into this is when the application that generated the csv file had corrupt data coming in.  Can you post a sample of your data?  &lt;/P&gt;

&lt;P&gt;If you're sure your dataset is clean, you may want to look at enabling SHOULD_LINEMERGE and then tweaking MUST_NOT_BREAK_BEFORE discussed here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Indexmulti-lineevents" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Indexmulti-lineevents&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 11:38:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexed-CSV-wont-line-break/m-p/20404#M2987</guid>
      <dc:creator>jt_splunk</dc:creator>
      <dc:date>2020-09-28T11:38:17Z</dc:date>
    </item>
  </channel>
</rss>

