<?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 Enhancements to S3 components in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Enhancements-to-S3-components/m-p/2509108#M148925</link>
    <description>&lt;P&gt;We have a support ticket (&lt;A href="https://customerportal.qlik.com/case/500R500000IakTUIAZ/aws-components-using-out-of-date-sdk?c__tab=details" target="_blank"&gt;https://customerportal.qlik.com/case/500R500000IakTUIAZ/aws-components-using-out-of-date-sdk?c__tab=details&lt;/A&gt;) in progress which requests that the AWS components are updated to use Amazon's v2 SDK as the v1 SDK will soon be unsupported.&lt;/P&gt;
&lt;P&gt;Using the v2 SDK also makes additional functionality available and from our point of view it would be extremely desirable for this to be added to the components. Of most interest is the use of (pre-calculated) checksums to verify data integrity and the correctness of data transfer during S3 get, S3 put and S3 copy operations. See&amp;nbsp;&lt;A href="https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/s3-checksums.html" target="_blank"&gt;https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/s3-checksums.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;As we operate a long term archive, obtaining checksums of files is a key operation as data is transferred to the archive, so in general we will already have a checksum to supply during an initial put or copy operation so allowing the component to take a pre-calculated checksum as an additional input would also be key for us.&lt;/P&gt;
&lt;P&gt;Hope I've put this on the correct board&lt;/P&gt;</description>
    <pubDate>Fri, 02 Jan 2026 14:45:42 GMT</pubDate>
    <dc:creator>David_Underdown</dc:creator>
    <dc:date>2026-01-02T14:45:42Z</dc:date>
    <item>
      <title>Enhancements to S3 components</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Enhancements-to-S3-components/m-p/2509108#M148925</link>
      <description>&lt;P&gt;We have a support ticket (&lt;A href="https://customerportal.qlik.com/case/500R500000IakTUIAZ/aws-components-using-out-of-date-sdk?c__tab=details" target="_blank"&gt;https://customerportal.qlik.com/case/500R500000IakTUIAZ/aws-components-using-out-of-date-sdk?c__tab=details&lt;/A&gt;) in progress which requests that the AWS components are updated to use Amazon's v2 SDK as the v1 SDK will soon be unsupported.&lt;/P&gt;
&lt;P&gt;Using the v2 SDK also makes additional functionality available and from our point of view it would be extremely desirable for this to be added to the components. Of most interest is the use of (pre-calculated) checksums to verify data integrity and the correctness of data transfer during S3 get, S3 put and S3 copy operations. See&amp;nbsp;&lt;A href="https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/s3-checksums.html" target="_blank"&gt;https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/s3-checksums.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;As we operate a long term archive, obtaining checksums of files is a key operation as data is transferred to the archive, so in general we will already have a checksum to supply during an initial put or copy operation so allowing the component to take a pre-calculated checksum as an additional input would also be key for us.&lt;/P&gt;
&lt;P&gt;Hope I've put this on the correct board&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2026 14:45:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Enhancements-to-S3-components/m-p/2509108#M148925</guid>
      <dc:creator>David_Underdown</dc:creator>
      <dc:date>2026-01-02T14:45:42Z</dc:date>
    </item>
  </channel>
</rss>

