<?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: Error with Redshift Timestamp in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Error-with-Redshift-Timestamp/m-p/2204635#M5441</link>
    <description>This may or may not be of use to you, but I ran into the same problem trying to create a table today.&lt;BR /&gt;The reason in my case, was trying to create a table with a timestamp field that was defaulting to CURRENT_TIMESTAMP. My theory is the redshift implementation tries to implement this in the underlying postgres nodes by using timestampz and that's not being supported by whatever version of postgres they use (aka a bug on their side).&amp;nbsp;&lt;BR /&gt;In my case, I was loading a massive dump of data that all included timestamps, so I could get around it by setting DEFAULT NULL on the table definition.</description>
    <pubDate>Fri, 03 Feb 2017 10:28:11 GMT</pubDate>
    <dc:creator>_AnonymousUser</dc:creator>
    <dc:date>2017-02-03T10:28:11Z</dc:date>
    <item>
      <title>Error with Redshift Timestamp</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Error-with-Redshift-Timestamp/m-p/2204634#M5440</link>
      <description>I'm encountering the following error doing a bulk insert to redshift:&lt;BR /&gt;Exception in component tRedshiftOutputBulkExec_1_tRBE&lt;BR /&gt;java.sql.SQLException: (500310) Invalid operation: timestamp or timestamptz do not support precision.;&lt;BR /&gt;Any idea what it is?</description>
      <pubDate>Fri, 27 Jan 2017 00:40:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Error-with-Redshift-Timestamp/m-p/2204634#M5440</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2017-01-27T00:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: Error with Redshift Timestamp</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Error-with-Redshift-Timestamp/m-p/2204635#M5441</link>
      <description>This may or may not be of use to you, but I ran into the same problem trying to create a table today.&lt;BR /&gt;The reason in my case, was trying to create a table with a timestamp field that was defaulting to CURRENT_TIMESTAMP. My theory is the redshift implementation tries to implement this in the underlying postgres nodes by using timestampz and that's not being supported by whatever version of postgres they use (aka a bug on their side).&amp;nbsp;&lt;BR /&gt;In my case, I was loading a massive dump of data that all included timestamps, so I could get around it by setting DEFAULT NULL on the table definition.</description>
      <pubDate>Fri, 03 Feb 2017 10:28:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Error-with-Redshift-Timestamp/m-p/2204635#M5441</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2017-02-03T10:28:11Z</dc:date>
    </item>
    <item>
      <title>Re: Error with Redshift Timestamp</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Error-with-Redshift-Timestamp/m-p/2204636#M5442</link>
      <description>Upon further exploration, the equivalent of CURRENT_TIMESTAMP is SYSDATE. That also works.&lt;BR /&gt;What doesn't work are the AWS Data Pipeline scripts to go from mysql to redshift.</description>
      <pubDate>Fri, 03 Feb 2017 10:36:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Error-with-Redshift-Timestamp/m-p/2204636#M5442</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2017-02-03T10:36:10Z</dc:date>
    </item>
  </channel>
</rss>

