You must be logged in to access this page

Semarchy xDI 2023.1.2 is available!

We have released today on semarchy.com Semarchy xDI 2023.1.2.


You can read the release notes (2023.1.2, Amazon, Snowflake, Google Platform, Greenplum, Kafka, Snowflake).



New Features

  • DI-6683: Connectors: The *Positional File Processing* property has been added to  the *Load file to Snowflake* template to support positional files.
  • DI-6824: Connectors: In Amazon S3 metadata, the *Secret Key* field is now encrypted and hidden like a password.
  • DI-7644: Runtime: In addition to the engineParameters.xml file, a standalone  file can also be used to define the external value resolver  configuration.


Bug Fixes

  • DI-7220: Analytics: Deliveries cannot be run from analytics when connecting to the runtime using the RMI protocol.
  • DI-7229: Analytics: Code has been improved to ensure that all exceptions thrown  by methods named `do*` are explicitly handled in servlet classes.
  • DI-7125: Analytics: At startup, Tomcat warns about missing externalization keys.
  • DI-6683: Connectors: The *Positional File Processing* property has been added to  the *Load file to Snowflake* template to support positional files.
  • DI-6824: Connectors: In Amazon S3 metadata, the *Secret Key* field is now encrypted and hidden like a password.
  • DI-7296: Connectors: The *AWS - S3* tool fails at the time of execution.
  • DI-6324: Connectors,Designer: When using Kafka structured as source, the *Load  Kafka Structure to RDBMS* template does not create the Load_Temporal  table and an insert error occurs at the integration step.
  • DI-7308: Connectors: Driver upgrade: PostgreSQL
  • DI-7268: Connectors: Third-party library upgrade: org.json
  • DI-7151: Connectors: When the Google storage delivery repository is set in the  `engineParameters`, the delivery name in the repository is incorrect.
  • DI-7282: Designer: When creating Google Sheets metadata, the reverse-engineering wizard and the query editor throw an error.
  • DI-7280: Designer: In a mapping, when one of the joins is conditionally  activated from the *Advanced* finger tab of the *Property* view, all the  other joins in the mapping are also activated using the same condition.
  • DI-7224: Designer: When building documentation from a mapping, the templates are  not displayed in the documentation and the files are not created in the  specified folder.
  • DI-7215: Designer: When creating a deserializer by the context menu, the input field is not mapped automatically.
  • DI-7214: Designer: When the alias of the deserializer is changed, it is not taken into account.
  • DI-7213: Designer: The copy-paste operation between mappings generates a copy  with the expression using the wrong datastore name.
  • DI-7644: Runtime: In addition to the engineParameters.xml file, a standalone file  can also be used to define the external value resolver configuration.
  • DI-7225: Runtime: Statistics are not displayed when the mapping name contains the _à_ character.
  • DI-7631: Runtime: Runtime commands returning session information fail with a `null` error message.
  • DI-7695: Runtime: It is not possible to define an empty configuration in an external value resolver.
  • DI-7650: Runtime: Runtime user roles no longer work.
Login to post a comment