<?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 corrupted CSV results / Python API in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/corrupted-CSV-results-Python-API/m-p/77387#M19547</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm using the Python SDK to export some search results to a CSV file, but the results seem to be somehow corrupted unless I specify an exact list of fields. So for example this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=myindex field=pattern
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;produces corrupted results but this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=myindex field=pattern | table field_a, field_b
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;works just fine. The corruption looks a bit like a randomly scattered newline characters - the line suddenly ends (in the middle of a field), then there's a part of the original line missing and the remainder is on the next line. (or something like that, I'm not sure what is the exact corruption).&lt;/P&gt;

&lt;P&gt;The data do not contain newline characters - when exporting to JSON everything is peachy. Also there are no mixed Windows/Unix line ends (I'm on Linux).&lt;/P&gt;</description>
    <pubDate>Mon, 18 Jun 2012 08:55:35 GMT</pubDate>
    <dc:creator>tomasv</dc:creator>
    <dc:date>2012-06-18T08:55:35Z</dc:date>
    <item>
      <title>corrupted CSV results / Python API</title>
      <link>https://community.splunk.com/t5/Splunk-Search/corrupted-CSV-results-Python-API/m-p/77387#M19547</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm using the Python SDK to export some search results to a CSV file, but the results seem to be somehow corrupted unless I specify an exact list of fields. So for example this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=myindex field=pattern
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;produces corrupted results but this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=myindex field=pattern | table field_a, field_b
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;works just fine. The corruption looks a bit like a randomly scattered newline characters - the line suddenly ends (in the middle of a field), then there's a part of the original line missing and the remainder is on the next line. (or something like that, I'm not sure what is the exact corruption).&lt;/P&gt;

&lt;P&gt;The data do not contain newline characters - when exporting to JSON everything is peachy. Also there are no mixed Windows/Unix line ends (I'm on Linux).&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jun 2012 08:55:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/corrupted-CSV-results-Python-API/m-p/77387#M19547</guid>
      <dc:creator>tomasv</dc:creator>
      <dc:date>2012-06-18T08:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: corrupted CSV results / Python API</title>
      <link>https://community.splunk.com/t5/Splunk-Search/corrupted-CSV-results-Python-API/m-p/77388#M19548</link>
      <description>&lt;P&gt;Question: I've seen JSON output and it appears to have "nice-afied" the "\n" new lines. Could you capture a CSV and XML portion and send to &lt;A href="mailto:devinfo@splunk.com"&gt;devinfo@splunk.com&lt;/A&gt;? &lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Wim&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jul 2012 16:23:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/corrupted-CSV-results-Python-API/m-p/77388#M19548</guid>
      <dc:creator>wcolgate_splunk</dc:creator>
      <dc:date>2012-07-06T16:23:32Z</dc:date>
    </item>
  </channel>
</rss>

