TOLERANT Match Release 6.0

Notices

• The correct file-name and line-number should be written in log file, if a read-error occurred in the input file.
• The GUI should acquire logging information only when starting-up. A popup message is shown in case of an access violation.
• The Administration GUI should write the changed xml-Elements and not the complete configuration file. (Only relevant for products with an Administration GUI)
• The installer will now summarize all configured URLs for service and configured GUIs (if available) at the end of the installation.
• In case of an (unlikely) OutOfMemoryError the product will now crash and create dump files.
• Following project parameters will be ignored during the check for configuration compatibility in Tolerant Match cluster: saveInterval, saveSchedule, fullSavepointSchedule, nrFullSavepoints and protectedFullSavepoints.
• The Administration GUI provides information about cluster status for each of the configured projects.
• The new administration command state database project-Id can be used to check the state of the project’s databases. If the project-Id was not entered, all databases will be checked.
• The getByKey-Operation for the Match Service no longer returns the type and the partitionId for the returned results.
• Usage of a normalizer section name starting with a minus (-) is no longer allowed. Please replace the minus with another character.
• The validity of the synonym file will now be check before writing synonym file.
• The product ships with a newer embedded web server jetty 9.3.11.

New Product Features

Configuration and Administration GUI

• The GUI should acquire logging information only when starting-up. A popup message is shown in case of an access violation.
• The Administration GUI should write the changed xml-Elements and not the complete configuration file. (Only relevant for products with an Administration GUI)
• The Batch process dialog in the Administration GUI was extended to show the log-file and rejected-files.
• The Administration GUI provides information about cluster status for each of the configured projects.
• The validity of the synonym file will now be check before writing synonym file.

Client GUI

• It is now possible to control behaviour of Client GUI for empty optional service fields (send empty value or discard from request)
• The Administration GUI provides information about cluster status for each of the configured projects.

Batch

• The correct file-name and line-number should be written in log file, if a read-error occurred in the input file.

Service

• In case of service errors, the triggering request will be logged as error in the logfile in addition to the normal request logging to the trace file.
• New admin command can be used to list all available metrics list metric. The value of the single metrics can be aquired using the admin command get metric.
• The installer will now summarize all configured URLs for service and configured GUIs (if available) at the end of the installation.
• All steps within the internal processing now report the size of the incoming queue as performance value in JMX.
• Following project parameters will be ignored during the check for configuration compatibility in Tolerant Match cluster: saveInterval, saveSchedule, fullSavepointSchedule, nrFullSavepoints and protectedFullSavepoints.
• The getByKey-Operation for the Match Service no longer returns the type and the partitionId for the returned results.
• In a service it is now possible to define an output field as of type JSON (‚J‘). This is currently only useful for Tolerant NAME in conjunction with using the PERL script interface. A PERL script could thus return a JSON response, that is delivered as a field within the response of the service.
• Improved storage of Match data in database, format has changed. This requires re-build of index by new initial load or export/import of data.

General

• In case of an (unlikely) OutOfMemoryError the product will now crash and create dump files.
• Unified behaviour (help, usage, result codes, …) of Commandline Tools
• The new administration command state database project-Id can be used to check the state of the project’s databases. If the project-Id was not entered, all databases will be checked.
• The usage of the character minus (-) at the beginning of a normalizer section name is no longer allowed.
• The product ships with a newer embedded web server (jetty 9.3.11). The cyphersuite can be configured using TLCONFIG/jetty-config/tweak-ssl.xml.

Fixed Bugs

Configuration and Administration GUI

• TPR-1576: If a configuration file was changed manually, so that it was syntactically wrong, the administration GUI might have reported an „project ID error“ when trying to change a project.
• TPR-3531: The check for errors in synonym file does not validate entries, that have no list-name.
• TPR-3563: Not all possible input streams are activated for the SELF method in the Administration GUI.
• TPR-3566: The Administration GUI should use the configured host name when starting the client GUI.
• TPR-3658: Renaming transliteration nodes does not update their references.
• TPR-3806: Phonetic factor was renamed as Weighting factor.
• TPR-3860: Uninformative error message is shown, if the performed action requires rights that are missing for the current logged in user.
• TPR-3904: The Navigation bar is not reset correctly after login.

Batch

• TPR-3561: Anonymizer-Tool should check whether configured length is valid. Length should be between 512 and 32000.
• TPR-3586: Batch process does not exist if the output file couldn’t be written.

Service

• TPR-1569: If Match service is configured, so that saveSchedule=0 and fullSavepointSchedule is not set, then save points will not be written.
• TPR-3533: STORONLY fields cannot be added to the disabledFields list.
• TPR-3594: Match Initial load does not exit on internal errors
• TPR-3636: Match service should output a more specific error message, if the configuration file is not compatible with the index structure of Match Kernel.
• TPR-3650: Handling of Match Kernel errors for searchByKey request should be revised.
• TPR-3668: Match search does not work properly with BITARRAY fields if resultMode=4 was used
• TPR-3687: The handling of network problems occurred during a database operation should be imporved.
• TPR-3724: The output of AdminCLI tools using json format is not JSON-conform.
• TPR-3731: Error when different phonetic types were found in project profiles
• TPR-3756: Unsufficient errorhandling in case of nonalphabetic requestIds for bulk-requests.
• TPR-3771: The field recordNumber containing the Id of single results within a bulk response is wrong.
• TPR-3805: Loading backlog files does not handle wildcard delete operations correctly
• TPR-3815: Backlog reader logged the fields values without anonymization

General

• TPR-7: Even if the logging for audit events was turned off, some initial logging messages appeared in the audit log.
• TPR-384: When upgrading an installation with https, the installer overwrites the keystore (only relevant for products with servicecomponent).
• TPR-484: The attribute „instances“ in the tag „configuration“ of the security.xml is no longer supported. All productinstance specific rights are now enabled, when „administration“ is enabled. The value of „instances“ will now be silently ignored.
• TPR-3518: Possible data loss due to race condition in Match kernel.
• TPR-3531: The check for errors in synonym file does not validate entries, that have no list-name.
• TPR-3555: The name of a Match field should not contain a special character.
• TPR-3569: All batch configuration templates coming with the product have now the same logginglevels:
  • Tracefiles: INFO
  • Logfiles: INFO
  • Console: INFO
• TPR-3591: When configuring https during the installation (for products with servicecomponent), the selfsignedcert.txt file was overwritten and therefore empty. Now the file will contain the details about the selfsigned certificate as intended.
• TPR-3620: A search using HOUSENUMBER field with emptyScore=100 returns no results
• TPR-3651: Potential data corruption due to race condition in Match Kernel
• TPR-3691: The counter metrics for the synonym substitution should be project-specific.
• TPR-3715: conditionValue must be a valid regular expression if conditionType is set to REGEXP.
• TPR-3734: Internal Error on Solaris when deleting all entries of PLAIN field
• TPR-3741: Wrong cardinality value when evaluting an input file containing chinese letters
• TPR-3742: Data corruption in PLAIN field if number of unique field values exceeds approx. 16.7 million values
• TPR-3796: If a script for a generatedField did not return a value (or a null value), the trace file will contain errors about NullPointerExceptions.
• TPR-3801: The element partitioningField can occur multiple times within the partitioningAggregation element
• TPR-3821: It is not possible to read and/or write in database tables if their schemas do not match the database username.
• TPR-3830: Save operation blocks PUT-operation in other project (occupied kernel threads).
• TPR-3837: Upgrade does not delete the Jetty-tmp directories if the hostname was used for JETTY_HOST (only relevant for products with servicecomponent)

Security

• TPR-3472: The security.xml reader now checks the version of the file.

Known Bugs

• TPR-3892: The new trimtypes M, RM, LM and A do not work for the following configuration-elements and tools:
  • serviceOutputField
  • csvOutputField
  • databaseOutputField
  • matchFiletest.sh/bat
  • postFiletest.sh/bat