<?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: DB Connect MySQL can't parse timestamp in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330641#M39616</link>
    <description>&lt;P&gt;Did you resolve this ? I have the exact same problem at the moment. My same query worked in version 2.4 we upgraded to 3.1.1 and now same query same data input doesn't work due to time format with the same error you had.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Mar 2018 20:14:48 GMT</pubDate>
    <dc:creator>EmEdwards</dc:creator>
    <dc:date>2018-03-28T20:14:48Z</dc:date>
    <item>
      <title>DB Connect MySQL can't parse timestamp</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330638#M39613</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am using DB connect 3.1.1 to get data from MySQL. I have 15 working inputs with rising id column and timestamp (DATETIME) to index data. Server and table structure is same for all inputs.&lt;BR /&gt;
But for 4 next inputs, I get this message in db_connect_server.log :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2018-01-23 00:39:47.459 +0100  [QuartzScheduler_Worker-28] ERROR org.easybatch.core.job.BatchJob - Unable to open record reader
java.time.format.DateTimeParseException: Text '2017-12-04 10:58:57.0' could not be parsed, unparsed text found at index 19
    at java.time.format.DateTimeFormatter.parseResolved0(Unknown Source)
    at java.time.format.DateTimeFormatter.parse(Unknown Source)
    at com.splunk.dbx.server.dbinput.recordreader.columnprocessor.RowWithTimeProcessor.extractTimestampFromString(RowWithTimeProcessor.java:88)
    at com.splunk.dbx.server.dbinput.recordreader.columnprocessor.RowWithTimeProcessor.apply(RowWithTimeProcessor.java:70)
    at com.splunk.dbx.server.dbinput.recordreader.columnprocessor.RowWithTimeProcessor.apply(RowWithTimeProcessor.java:28)
    at com.google.common.collect.Iterators$7.transform(Iterators.java:750)
    at com.google.common.collect.TransformedIterator.next(TransformedIterator.java:47)
    at com.google.common.collect.Iterators$6.computeNext(Iterators.java:616)
    at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:145)
    at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:140)
    at com.splunk.dbx.server.dbinput.recordreader.iterator.EventPayloadRecordIterator.hasNext(EventPayloadRecordIterator.java:76)
    at com.splunk.dbx.server.dbinput.recordreader.DbInputRecordReader.open(DbInputRecordReader.java:92)
    at org.easybatch.core.job.BatchJob.openReader(BatchJob.java:117)
    at org.easybatch.core.job.BatchJob.call(BatchJob.java:74)
    at org.easybatch.extensions.quartz.Job.execute(Job.java:59)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
2018-01-23 00:39:47.459 +0100  [QuartzScheduler_Worker-28] INFO  org.easybatch.core.job.BatchJob - Job 'psa-wfk-lc_04307600_xx' finished with status: FAILED
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The timestamp column is also DATETIME and everything is fine in GUI wizard to select column for timestamp.  Please do you have any idea what can be wrong?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 17:49:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330638#M39613</guid>
      <dc:creator>rapmancz</dc:creator>
      <dc:date>2020-09-29T17:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect MySQL can't parse timestamp</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330639#M39614</link>
      <description>&lt;P&gt;Could you try converting timestamp field in sql query?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2018 04:44:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330639#M39614</guid>
      <dc:creator>p_gurav</dc:creator>
      <dc:date>2018-01-23T04:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect MySQL can't parse timestamp</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330640#M39615</link>
      <description>&lt;P&gt;"Index 19" is, if I count correctly, the "." separating seconds from the "0" for tenths of a second.   That brings up a couple of possibilities.  First, double check against a known-good one (one that works) exactly what type of data the data and time is coming from.  Then check exactly what the query is you are running.  I'll bet either the column types are different, or there's a cast/convert (or whatever MySQL uses for that) in the ones that work.  For that matter, what's the timestamp time specifier you put into the GUI?  (Do you still have to do that?)&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2018 02:50:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330640#M39615</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2018-01-29T02:50:07Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect MySQL can't parse timestamp</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330641#M39616</link>
      <description>&lt;P&gt;Did you resolve this ? I have the exact same problem at the moment. My same query worked in version 2.4 we upgraded to 3.1.1 and now same query same data input doesn't work due to time format with the same error you had.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 20:14:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-MySQL-can-t-parse-timestamp/m-p/330641#M39616</guid>
      <dc:creator>EmEdwards</dc:creator>
      <dc:date>2018-03-28T20:14:48Z</dc:date>
    </item>
  </channel>
</rss>

