2.2.0 (Elasticsearch Component)

    Download
  • fixed

    Elasticsearch Metadata - "HTTP/REST" protocol should not be proposed in Metadata when Elasticsearch 2 version is selected as it is not supported with this Elasticsearch version


  • 2.1.0 (Elasticsearch Component)

    Download
  • added

    EMF compare utility - Component has been updated to support EMF Compare comparison utility


  • 2.0.5 (Elasticsearch Component)

    Download
  • fixed

    Elasticsearch - Defined HTTP password was not taken into account when performing an Elasticsearch Query operation on a secured Elasticsearch server


  • 2.0.4 (Elasticsearch Component)

    Download
  • added

    Elasticsearch 2 support is now kept as legacy and compatibility purposes, as this version is not supported anymore by Elasticsearch. Only maintenance and critical fixes will be performed on Elasticsearch 2.x.

  • added

    Support communicating with Elasticsearch through HTTP/REST protocol

  • added

    Templates updated - New Parameters 'Unlock Cdc Table' and 'Lock Cdc Table' to configure the behaviour of CDC tables locking

  • added

    Templates updated - New parameter 'Cdc Subscriber' on Templates on which it was not handled yet


  • 2.0.3 (Elasticsearch Component)

    Download
  • added

    Support Xpack Security

  • added

    When performing a search operation, it is now possible to limit the number of hits returned through a new parameter available on the corresponding template

  • fixed

    Elasticsearch default encoding used when performing operations should be UTF-8

  • fixed

    Search Guard properties were ignored, avoiding connecting to Search Guard secured Elasticsearch servers

  • fixed

    Search operation is throwing an error if returned data contains special characters

  • fixed

    Search operation was not handling properly some of the query parameters, such as includes, excludes, ... which were ignored

  • fixed

    The cluster-name specified in Metadata is ignored, which leads to connection errors when working with an elasticsearch server having a custom cluster-name