IBM Support

JR60858: IMPLEMENT MERGE STATEMENTS IN SNOWFLAKE CONNECTOR TO EXECUTE UPDATE, DELETE AND DUAL MODE QUERIES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Currently Update, Delete and the dual mode queries execute
    through the snowflake JDBC driver. An option to execute these
    write mode operations using Merge statements is provided
    

Local fix

  • No Fix - Implementing functionality that was not available
    before
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Snowflake connector users
    ****************************************************************
    PROBLEM DESCRIPTION:
    Using snowflake jdbc driver implementation of Updates and
    deletes is having an effect on the performance.
    ****************************************************************
    RECOMMENDATION:
    Apply patch JR60858 on engine tier
    ****************************************************************
    

Problem conclusion

  • Update, Delete, Insert then Update and Delete then Insert
    operations can now be performed  using the Merge statement in
    Snowflake which offers a better performance. In order that
    these write modes use Merge statement the property "Use merge
    statements" should be set to 'Yes? and values for the
    corresponding required properties which will get enabled should
    be provided.
    
      The APAR fixes the below issues too -
      1.  User can choose between using Merge statements or driver
    supported updates/deletes.
      2.  The staging files are created in job specific directories
    in the staging area. This would be useful in reusing the same
    staging area across different jobs.
      3.  User is given the choice to retain or purge the files in
    the staging area. If the property "Purge files after loading" is
    set to 'Yes' when write mode is set to "Load from file" then
    after the COPY command is executed the files in the staging area
    are removed.
      4.  When creating the staging area, the user can provide file
    format options based on the nature of the input data. For
    example , if the input column has comma in data then the user
    can select pipe as the field delimiter.
      5.  For an existing staging area , the user can provide file
    format options which the COPY  command will use in loading the
    files to the table.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR60858

  • Reported component name

    INFO SRVR PLATF

  • Reported component ID

    5724Q3612

  • Reported release

    B70

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-24

  • Closed date

    2019-05-02

  • Last modified date

    2019-05-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    INFO SRVR PLATF

  • Fixed component ID

    5724Q3612

Applicable component levels

  • RB70 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"InfoSphere Information Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.7","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 October 2021