Versions Compared

Key

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

Release date: April 24th, 2024

Easy Heading Free

Tech Stack

NoSQL DB provider supported

  • Elasticsearch versions 8.1012.12
  • Opensearch v. 1.1, 2.8

Java supported

  • OpenJDK 17

Python supported

  • Python version 3.11.49

Node.js (for development)

  • Node.js LTS v. 18.17.1.
New Features


Improvements

Framework

  • Saga logger. SUGGEST ANOTHER NAME!!

UI/UX

Processors and Recognizers

Improvements

Aspire Saga-Parser

  • : Ability to log into NoSQL DB (in addition to filesystem)

Docker/Kubernetes

  • Several improvements to docker file/image to make it easier to deploy and work Saga in Kubernetes.
    • Dynamic load configuration (env file, path, dynamic environment variables for Saga and Python Bridge)
    Improved to be easier to use with Kubernetes.

Recognizers/Processors

  • Entity Recognizer - New flags (TOTAL_MATCH and PARTIAL_MATCH). 
  • Python Model Recognizer - Added "Match Threshold" option.
  • Python Model Recognizer - inform Inform hostname error properly.
  • Python Classification Watcher/Mode Python Model Recognizers - improved Improved authentication process with Python Bridge
Server
  • Spellchecker stage using now the abstract indexer (it was connecting directly to Elasticsearch before.) Known issue on 1.3.3.

UI/UX

  • Deprecated warning added in Rules/Executors screen. Rules/Executors only work with old ESUI not GAIA.

Vulnerabilities

  • Vulnerabilities Fixed critical, high, and medium vulnerabilities found by security scans . SHOULD WE MENTION THEM???
Bug fixes
  • on both Saga Server and Python Bridge. Remaining some vulnerabilites related to CIO Docker Images out of our control. 

Bug fixes

Server

  • Better error message on start-up when connecting with NoSql provider (Elasticsearch/Opensearch).
  • Error message about Processing Units mapping during start-up when using Processing Units.
  • Multiple random ports opened by the Elasticsearch client library used by Saga.
  • Load Processing Units only after Resources have been loaded. 
  • State cannot be determined error when using SSO login.
  • Connection error messages not showing correctly for maximum retries. 
  • Fixed processing units mappings.  
  • Elasticsearch connections not being released. 

Evaluations Page

  • Statistics not being rendered after evaluating. Known issue on 1.3.3.

Framework/API

  • Stop endpoint path fixed. 

Pipelines

  • Spellchecker stage using now the abstract indexer. SOUND AS IMPROVEMENT???Dictionary process endpoint used by Aspire Saga Publisher is duplicating entries. 

Saga Parser

  • Using the Python Bridge with SSL or basic authentication was not connecting. Known issue on 1.3.3.
  • NPE error when enabling the Debug option. Known issue on 1.3.3.

Tags/Recognizers

  • PostalCode Recognizer - country selected was not working recognizing postal codes.
  • Intent/FAQ: Recognizers using the Python Bridge with authentication failing on the Recalculating vector option.
  • Python Classification Recognizer - Minor issues and improvements in the UI.
  • Check duplicate setting added to Entity and FAQ recognizer importers.
  • Fixed [object Object] message recalculating with no entries for the Intent Recognizer. 

UI/UX

  • Check Tag button in preview screen was not working. Known issue on 1.3.3.
  • Server Down popup message constantly appearing.
  • Missing user click results in Kibana.

Vulnerabilties

  • . Known issue on 1.3.3.
  • Refresh issue having multiple character splitters. 
  • Export for Data Science - null error trying to export - dataset with special characters (&).
  • Universal Importer - CSV for Intent Recognizer not loading dictionary. Fixed guava-31.1-jre library vulnerabilities in pac4j-oidc and google-api-client. IMPROVEMENT SECTION???


Note: you can find all the details in Jira here.

Known Issues

  • Spell checker only works with Elasticsearch.
  • Saga-Parser using recognizers that need Python Bridge, cannot connect to a Python Bridge set up with HTTPS, only HTTP.
  • Debug setting in Saga-parser causes a NPE during crawl. This setting needs to be disabled.
  • Statistics screen is not rendering correctly after an Evaluation with a dataset is performed.
  • Check Tag button in preview screen is not working properly.
  • Depending on connection quality a false "Server Down" message could appear in the UI

    .