<?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: Search time field extractions of structured data in csv format in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375654#M68039</link>
    <description>&lt;P&gt;Thank you for your answer. If I modify the sourcetype to fit the new data format then i won't be able to search the data in previous format properly. Unless i can apply multiple sourcetypes depending on the time range the data is stored for.&lt;/P&gt;</description>
    <pubDate>Sat, 05 May 2018 19:53:17 GMT</pubDate>
    <dc:creator>kiril123</dc:creator>
    <dc:date>2018-05-05T19:53:17Z</dc:date>
    <item>
      <title>Search time field extractions of structured data in csv format</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375651#M68036</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am indexing data which arrives to the index in csv format.&lt;BR /&gt;
I am using a search time filed extraction method. I have specified a list of the fields in the transforms.conf &lt;BR /&gt;
What will happen in a new column gets added to a csv file or the order of columns changes? I can change a transforms.conf file by modifying the fields list, but the new transform would not work for the csv data before column order has changed.&lt;/P&gt;

&lt;P&gt;What is the best method for csv files fields extraction assuming the order of columns can change in the future?&lt;/P&gt;

&lt;P&gt;Thank you. &lt;/P&gt;</description>
      <pubDate>Sat, 05 May 2018 12:19:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375651#M68036</guid>
      <dc:creator>kiril123</dc:creator>
      <dc:date>2018-05-05T12:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: Search time field extractions of structured data in csv format</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375652#M68037</link>
      <description>&lt;P&gt;For CSV-like data, DELIMS work pretty well. Take a look at this for example:&lt;BR /&gt;
&lt;A href="https://www.splunk.com/blog/2013/03/11/quick-n-dirty-delimited-data-sourcetypes-and-you.html"&gt;https://www.splunk.com/blog/2013/03/11/quick-n-dirty-delimited-data-sourcetypes-and-you.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;However, if your data changes its format, that might be problematic. If the new column gets appended last, it might work just defining more fields in your transforms.&lt;BR /&gt;
Basically, when your data changes its format, you should ingest it with a different custom sourcetype that fits your data. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 05 May 2018 13:32:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375652#M68037</guid>
      <dc:creator>xpac</dc:creator>
      <dc:date>2018-05-05T13:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: Search time field extractions of structured data in csv format</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375653#M68038</link>
      <description>&lt;P&gt;The best that you can do is WATCH for it, then fix it.  Here is what you do.  In every CSV RegEx, Add &lt;CODE&gt;(?:,(?&amp;lt;FIXME_EXPANSION&amp;gt;[^,]+))?&lt;/CODE&gt;.  Then have a search with &lt;CODE&gt;FIXME_EXPANSION=*&lt;/CODE&gt; that runs all the time and emails you if the results are ever non-zero.&lt;/P&gt;</description>
      <pubDate>Sat, 05 May 2018 14:54:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375653#M68038</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2018-05-05T14:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: Search time field extractions of structured data in csv format</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375654#M68039</link>
      <description>&lt;P&gt;Thank you for your answer. If I modify the sourcetype to fit the new data format then i won't be able to search the data in previous format properly. Unless i can apply multiple sourcetypes depending on the time range the data is stored for.&lt;/P&gt;</description>
      <pubDate>Sat, 05 May 2018 19:53:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Search-time-field-extractions-of-structured-data-in-csv-format/m-p/375654#M68039</guid>
      <dc:creator>kiril123</dc:creator>
      <dc:date>2018-05-05T19:53:17Z</dc:date>
    </item>
  </channel>
</rss>

