Versions Compared

Version Old Version 124 New Version 125
Changes made by

Lakshmi Manda

Kalpana Malladi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
minLevel1
maxLevel1
include
outlinefalse
indent
exclude
typeflat
separatorbrackets
class
printablefalse

...

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#FFEBE6

Breaking Change

With the new support for LDAP authentication to HashiCorp Vaults, the Snaplex node configuration file secrets-config.json requires a new key, auth_method, with a value approle or ldap.

Action needed:

You must update each of your existing Snaplex node configuration files to include this key-value pair: "auth_method": "approle", as prescribed in the Step 1a-Approle, for the approle-based authentication to succeed.

...

  • Starting from version 433patches21482, the PGP Encrypt Snap does not support encryption with an expired key. To ensure continued support for encryption, we highly recommend that you renew your PGP key before it expires or extend the expiration date of your PGP key.

  • Starting from version 433patches22343, the Vertica-Bulk Load Snap displays no output in the output view when the Snap receives no input.

  • With the 433patches21307 version, the HTTP Client Snap evaluates the ‘Has next’ property before writing the output documentpagination evaluation occurs before sending the output to the output view. Therefore, if snap.out.totalCount is part of the ‘Has next’ expression, it must be used as snap.out.totalCount + 1, for example, "snap.out.totalCount + 1 < $entity.total" Has next or any other pagination properties, the Snap will not include the count in the output corresponding to the request that produced the output document.

Known Issues

  • For the Binary and Email Snap Packs, SFTP connections might experience connectivity issues because of the removal of some deprecated algorithms. To add these connections back, refer to Configuration Settings for Snaps for details.

  • If you use the PostgreSQL driver (org.postgresql.Driver) with the Redshift Snap Pack, it could result in errors if the data type provided to the Snap does not match the data type in the Redshift table schema. Either use the Redshift driver (com.amazon.redshift.jdbc42.Driver) or use the correct data type in the input document to resolve these errors.

  • The Send Email Snap might fail because of a 429 error response from the Graph API endpoint.

  • For Ultra Tasks using a continuous data flow design for polling with a Pipeline Execute Snap, the parent pipeline does not receive the document from the child pipeline, and the polling message is not generated for downstream Snaps.

  • The GeoJSON Parser and WKT Parser Snaps accept only application/zip or application/gml+xml; charset=utf-8 as a file input stream.
    However, the output content type from the File Reader Snap is binary/octet when the input file is read from SLDB.

    Workaround: To read an input file (ZIP or GML) from SLDB, use the Mapper Snap to change the content type from binary/octet to one of the following:

    • ZIP file: Change the content type to application/zip .

    • GML file: Change the content type to application/gml+xml; charset=utf-8.

...