Release Notes

Table of Contents

• Qorus 4.1
  • Release Overview
  • Important Upgrade and Backwards Compatibility Information
  • New Features
  • Bug Fixes in Qorus 4.1
  • Bug Fixes in Qore

Qorus Release Notes History

Latest version: Qorus 4.1

Qorus 4.1

Release Overview

This is a major release of Qorus with the following major changes:

• Data Provider API
  • The Data Provider API allows any system to be introspected and communicated with, through record-based or request/response APIs; it supports high-performance volume operations as well as efficient search, creation, update, upsert, and deletion of data.
  • The mapper infrastructure has been updated to fully support the Data Provider API as well as now supporting autonomous mode where data transformations are automatically performed on data retrieved from the input provider and stored in the output provider after data transformations. For data providers supporting bulk operations, this results in extremely high performance data integration flows based entirely on configuration.
  • The DataProvider module was added and many modules were updated to support its API
  • New system option: qorus.dataprovider-modules
• Qorus Interface Metadata in YAML Format
  Defining Qorus interface metadata in YAML format has been introduced to facilitate the creation, editing and management of Qorus interfaces in the new Qorus IDE (see Implementing Qorus Objects Using YAML format).
  The new IDE supports creating, editing, deleting, and packaging interface code along with their metadata as well as ensuring the alignment of code and metadata in interface objects.
• Java Updated to Java 11
  Qorus's Java support has been updated to OpenJDK 11; see Java Requirements for more information
• Enhanced Unicode Support
  All interface objects in Qorus can now be made up of any Unicode characters including those outside the Latin or European character sets (ex: "ワークフローの例" is a valid workflow name as of this release)
• Qorus Cluster Startup Improvements
  Qorus starts up faster and is more responsive during startup; enabled workflows, services, and jobs now start in parallel, additionally, excess serialization in accessing internal data structures during startup was removed.

Important Upgrade and Backwards Compatibility Information

• New Environment Variables
  Set "QORE_DATA_PROVIDERS=QorusDataProviders" in your system environment to Qorus data providers with the qdp program for command-line introspection and manipulation of data providers
• Qore Parser Fixes
  The Qore library has undergone the following parser fixes:
  • corrected the cast<> operator to no longer silently accept NOTHING; to get the old behavior, use the %broken-cast parse directive in individual code objects, or set qorus.compat-broken-cast in the System Options File.
  • the deprecated returns keyword is no longer accepted by default; to get the old behavior, use the %allow-returns parse directive in individual code objects, or set qorus.compat-allow-returns in the System Options File.
• Event Code Changes
  logger and appender event codes were reassigned to the correct range starting with 5200: see LOGGER_CREATED for new values
• Abstract Method Signature Change
  • AbstractDatasource::getDBEncoding() now has a return type of *string as it can return no value; in previous versions of Qore this method could return NOTHING despite the return type; this fix will break any classes derived from AbstractDatasource, so adjust your source code accordingly
• Metadata-Based Interface Objects oload will load YAML-metadata-based integration objects first and does not handle dependencies between old-style objects with embedded metadata and YAML-metadata-based objects. Errors will result if a YAML-metadata-based object created from the IDE depends on older code when oload loads the objects for the first time. It is recommended to migrate all objects to YAML-metadata-based objects and not to mix the two types of objects in the same release.

New Features

• Service Config Item Updates
  Services can now react actively to configuration item changes; see:
  • Qore: ServiceApi::setConfigItemChangeCallback()
  • Java: ServiceApi.setConfigItemChangeCallback()
  for more information
• New Common Interface APIs
  • Qore:
    • DbRemoteRawReceive class
    • QorusLocalRestHelper class
    • UserApi::checkObjectCache()
    • UserApi::clearObjectCache()
    • UserApi::clearObjectFromObjectCache()
    • UserApi::getContextUserName()
    • UserApi::getDataProvider()
    • UserApi::getObjectCacheSize()
    • UserApi::getThreadCallStack()
    • UserApi::logWithLevel()
    • UserApi::logWithLevelArgs()
    • UserApi::saveObjectInObjectCache()
    • UserApi::startCapturingObjectsFromJava()
    • UserApi::stopCapturingObjectsFromJava()
  • Java:
    • ConfigItemValueCallback class
    • QorusLocalRestHelper class
    • DbRemoteRawReceive class
    • UserApi.checkObjectCache()
    • UserApi.clearObjectCache()
    • UserApi.clearObjectFromObjectCache()
    • UserApi.getContextUserName()
    • UserApi.getDataProvider()
    • UserApi.getObjectCacheSize()
    • UserApi.saveObjectInObjectCache()
    • UserApi.startCapturingObjects()
    • UserApi.stopCapturingObjects()
• New Service APIs
  • Qore: ServiceApi::setConfigItemChangeCallback()
  • Java: ServiceApi.setConfigItemChangeCallback()
• New Class-Based Mapper API
  • Qore: MapperApi
  • Java: MapperApi
• New Template Substitution Type
  • parse-value: parses the given string argument as a Qore value after recursive template substitution
  • temp: retrieves or writes to workflow temporary data
  See Config Item / Building Block Template Substitution Strings for more information
• New Constants For New Permissions
  • DATA-PROVIDER-CONTROL
  • DATA-PROVIDER-CREATE
  • DATA-PROVIDER-READ
  • DATA-PROVIDER-UPDATE
  • DATA-PROVIDER-DELETE
  • DATA-PROVIDER-REQUEST
• REST API v4
  • /api/v4/...: the REST API has been extended and a new version is now available under this URI path prefix; see the previous link for changes in REST API v4
• Connection Socket Debugging
  • new REST APIs to enable and disable socket debugging; when enabled, connections will log all socket data transferred in the interface log file:
    • PUT /api/v4/remote/qorus/{name}?action=enableDebugData
    • PUT /api/v4/remote/qorus/{name}?action=disableDebugData
    • PUT /api/v4/remote/user/{name}?action=enableDebugData
    • PUT /api/v4/remote/user/{name}?action=disableDebugData
• New System Events
  • CONNECTION_DEBUG_DATA_CHANGE
    • Qore constant: OMQ::QEC_CONNECTION_DEBUG_DATA_CHANGE
    • Java constant: com.qoretechnologies.qorus.OMQ.QEC_CONNECTION_DEBUG_DATA_CHANGE
• Qorus Client Updates
  • QorusClientBase module added for faster initialization of common client code, furthermore connection initialization is only done on demand which provides much faster responses to client actions not requiring database access
  • QorusClient::addModuleOption(): allows for qorus module options to be updated in client or release scripts
  • QorusClient::configureInterfaces(): allows configuration item values to be set in client or release scripts
  • QorusClient::createGlobalError(): allows global workflow error configurations to be created in client or release scripts
  • QorusClient::createRole(): allows roles to be created in client or release scripts
  • QorusClient::createUser(): allows users to be created in client or release scripts
  • QorusClient::createUserConnection(): allows user connections to be created in client or release scripts
  • QorusClient::createOrUpdateWorkflowError(): allows workflow-specific error configurations to be created or updated in client or release scripts
• Qorus Test Updates
  • the QorusInterfaceTest class was enhanced to include support for starting and stopping Qorus in the base class
  • the QorusInterfaceTest module now includes the WorkflowLogHelper class to assist in outputting log messages while running workflow tests
• Interface Creation Updates
  • Added support for oload to load Qorus objects defined in YAML-format (feature 3102)
  • Added support for class-based workflows (feature 3274)
  • Added support for oload to load Qorus workflow error definitions in YAML-format (feature 3292)
  • Added support for library objects for steps in YAML-format (feature 3325)

Bug Fixes in Qorus 4.1

Issue ID	Severity	Description
3396	Normal	fixed bugs recovering processes after qorus-core and or qdsp-omq along with interface processes crash
3395	Normal	fixed a bug recovering qorus-master crashes with uninitalized processes in the cluster process table
3332	Normal	improved client library initialization time

Bug Fixes in Qore

See Bug Fixes in Qore