Release Notes

• Includes RNI-RNT 7.47.0.c75.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.15.0

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled has been restored.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.46.0.c74.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.14.1.

• Added gender as a name property: You can now specify an explicit gender value when indexing, searching, or querying a name. Valid values are female, male, and nonbinary, (RLPNC-7445)

• Change to licensing when an overlay directory is specified: The license must be in the BT_ROOT directory, even if an overlay root is set. (RLPNC-7599).

• Bulk querying may experience performance degradation in multithreaded contexts when the system is under heavy load. (RLPNC-7560)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.45.0.73.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.12.2.

• An overlay root directory path can now be specified as a relative path to the RNI plugin installation directory. To do so, use the new bt.overlay.relative.root system property when starting Elasticsearch. (RLPNC-7377)

• Fixed a bug where stop word and override queries had inconsistent behavior. Now, for both stop words and overrides, queries with an entity type will return entries with that entity type and with no entity type; queries without an entity type will only return entries with no entity type. (RLPNC-7407)

• Fixed a bug where the pairwise match endpoint returns an empty response when the score is 0. Now the score is returned. (RLPNC-7213)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.46.0.c74.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.11.4.

• Added gender as a name property: You can now specify an explicit gender value when indexing, searching, or querying a name. Valid values are female, male, and nonbinary, (RLPNC-7445)

• Change to licensing when an overlay directory is specified: The license must be in the BT_ROOT directory, even if an overlay root is set. (RLPNC-7599).

• Bulk querying may experience performance degradation in multithreaded contexts when the system is under heavy load. (RLPNC-7560)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.44.0.c72.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.11.3.

• Overlay directory: Added support for specifying an overlay root directory location. This allows you to store the data components (models, parameters, config files, etc.) in a location other than the root directory within the plugin itself. To utilize this feature, specify the overlay location with the bt.overlay.root system property when starting the plugin. (RLPNC-7240)

• Control response format: The pairwise match endpoint now supports a new URL parameter, responseFormat, to control the format of the match response. If the parameter is unset or set to its default value, explainInfo, the response format of releases containing the RNI-RNT 7.43.0.c71.0 SDK is used. If the parameter is set to legacyExplainInfo , the response format of releases using older versions of the SDK is used. (RLPNC-7255)

• Dynamic configuration improvements: The type field can now be specified when adding token overrides using the dynamic configuration endpoints. (RLPNC-7256)

• Fixed a bug where the score field could not be omitted from dynamic token override requests. (RLPNC-7256)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.47.0.c75.0. Refer to the RNI-RNT release notes for a full description of new features.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled has been restored.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.44.0.c72.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.11.2.

• Overlay directory: Added support for specifying an overlay root directory location. This allows you to store the data components (models, parameters, config files, etc.) in a location other than the root directory within the plugin itself. To utilize this feature, specify the overlay location with the bt.overlay.root system property when starting the plugin. (RLPNC-7240)

• Control response format: The pairwise match endpoint now supports a new URL parameter, responseFormat, to control the format of the match response. If the parameter is unset or set to its default value, explainInfo, the response format of releases containing the RNI-RNT 7.43.0.c71.0 SDK is used. If the parameter is set to legacyExplainInfo , the response format of releases using older versions of the SDK is used. (RLPNC-7255)

• Dynamic configuration improvements: The type field can now be specified when adding token overrides using the dynamic configuration endpoints. (RLPNC-7256)

• Fixed a bug where the score field could not be omitted from dynamic token override requests. (RLPNC-7256)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.45.0.c73.0. Refer to the RNI-RNT release notes for a full description of new features.

• Overlay directory: Added support for specifying an overlay root directory location. This allows you to store the data components (models, parameters, config files, etc.) in a location other than the root directory within the plugin itself. To utilize this feature, specify the overlay location with the bt.overlay.root system property when starting the plugin. (RLPNC-7240)

• An overlay root directory path can now be specified as a relative path to the RNI plugin installation directory. To do so, use the new bt.overlay.relative.root system property when starting Elasticsearch. (RLPNC-7377)

• Control response format: The pairwise match endpoint now supports a new URL parameter, responseFormat, to control the format of the match response. If the parameter is unset or set to its default value, explainInfo, the response format of releases containing the RNI-RNT 7.43.0.c71.0 SDK is used. If the parameter is set to legacyExplainInfo , the response format of releases using older versions of the SDK is used. (RLPNC-7255)

• Dynamic configuration improvements: The type field can now be specified when adding token overrides using the dynamic configuration endpoints. (RLPNC-7256)

• Fixed a bug where the score field could not be omitted from dynamic token override requests. (RLPNC-7256)

• Fixed a bug where stop word and override queries had inconsistent behavior. Now, for both stop words and overrides, queries with an entity type will return entries with that entity type and with no entity type; queries without an entity type will only return entries with no entity type. (RLPNC-7407)

• Fixed a bug where the pairwise match endpoint returns an empty response when the score is 0. Now the score is returned. (RLPNC-7213)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.43.0.c71.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.9.2

• Introduced JSON-formatted explain information blocks to provide improved explanations for pairwise matches (RLPNC-7153). The pairwise endpoint now only returns this explain information and the existing debug information is no longer available (RLPNC-7177).

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.42.0.c70. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.8.1 (RLPNC-7044)

• Matching now works properly with Java 19 and Java 20. (RLPNC-6969)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.43.0.c71.0. Refer to the RNI-RNT release notes for a full description of new features.

• Introduced JSON-formatted explain information blocks to provide improved explanations for pairwise matches (RLPNC-7153). The pairwise endpoint now only returns this explain information and the existing debug information is no longer available (RLPNC-7177).

• Matching now works properly with Java 19 and Java 20. (RLPNC-6969)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.41.0.c69.0. Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.6.2.

• Added support for selector values when using the dynamic override endpoints. (RLPNC-6673)

• Parameter universes can now be used in the query phase. To do so, specify the query name as a json string and include the universe in the body. (RLPNC-6672)

• Fixed a bug where queries using filter_out_scores_below could return improper document scores and/or exceptions. (RLPNC-6809)

• Fixed POST _parameter_universe endpoint so that it supports non-scalar parameter values. (RLPNC-6832)

• Fixed a bug where initially low-scoring results could still be processed in the rescoring phase (RLPNC-6829)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Bundled Java 19 JRE is not supported. Set ES_JAVA_HOME to a version of Java 17/18 to avoid score changes.

• Includes RNI-RNT 7.40.1.c68.0.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Bundled Java 19 JRE is not supported. Set ES_JAVA_HOME to a version of Java 17/18 to avoid score changes.

• Includes RNI-RNT 7.40.0.c68.0.

• Supports Elasticsearch 8.5.3.

• Fields of the type rni_name now support a new mapping parameter, testEntityType, to control whether a name’s entity type is required to match in the first pass. By default, this is set to true, meaning only names that match the entity type of the query will be returned. By setting it to false, names with any (or no) entity type will also be returned (RLPNC-6688)

• Fixed a bug where the pairwise match endpoint could fail to parse valid requests with non-RNI data types. (RLPNC-6631)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Bundled Java 19 JRE is not supported. Set ES_JAVA_HOME to a version of Java 17/18 to avoid score changes.

• Supports Elasticsearch 8.4.3 (RLPNC-6591)

• The real world id training suite (realWorldIDBuilder.zip) is now included as part of the RNI-ES release. (RLPNC-6588)

• We've improved stability and error handling in the jvm plugin. (RLPNC-6403, RLPNC-6593)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Supports Elasticsearch 8.4.2

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.47.0.c75.0. Refer to the RNI-RNT release notes for a full description of new features.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled has been restored.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.46.0.c74.0. Refer to the RNI-RNT release notes for a full description of new features.

• Added gender as a name property: You can now specify an explicit gender value when indexing, searching, or querying a name. Valid values are female, male, and nonbinary, (RLPNC-7445)

• Change to licensing when an overlay directory is specified: The license must be in the BT_ROOT directory, even if an overlay root is set. (RLPNC-7599).

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.45.0.c73.0. Refer to the RNI-RNT release notes for a full description of new features.

• An overlay root directory path can now be specified as a relative path to the RNI plugin installation directory. To do so, use the new bt.overlay.relative.root system property when starting Elasticsearch. (RLPNC-7377)

• Fixed a bug where stop word and override queries had inconsistent behavior. Now, for both stop words and overrides, queries with an entity type will return entries with that entity type and with no entity type; queries without an entity type will only return entries with no entity type. (RLPNC-7407)

• Fixed a bug where the pairwise match endpoint returns an empty response when the score is 0. Now the score is returned. (RLPNC-7213)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.44.0.c72.0. Refer to the RNI-RNT release notes for a full description of new features.

• Overlay directory: Added support for specifying an overlay root directory location. This allows you to store the data components (models, parameters, config files, etc.) in a location other than the root directory within the plugin itself. To utilize this feature, specify the overlay location with the bt.overlay.root system property when starting the plugin. (RLPNC-7240)

• Control response format: The pairwise match endpoint now supports a new URL parameter, responseFormat, to control the format of the match response. If the parameter is unset or set to its default value, explainInfo, the response format of releases containing the RNI-RNT 7.43.0.c71.0 SDK is used. If the parameter is set to legacyExplainInfo , the response format of releases using older versions of the SDK is used. (RLPNC-7255)

• Dynamic configuration improvements: The type field can now be specified when adding token overrides using the dynamic configuration endpoints. (RLPNC-7256)

• Fixed a bug where the score field could not be omitted from dynamic token override requests. (RLPNC-7256)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.43.0.c71.0. Refer to the RNI-RNT release notes for a full description of new features.

• Introduced JSON-formatted explain information blocks to provide improved explanations for pairwise matches (RLPNC-7153). The pairwise endpoint now only returns this explain information and the existing debug information is no longer available (RLPNC-7177).

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.42.0.c70. Refer to the RNI-RNT release notes for a full description of new features.

• Matching now works properly with Java 19 and Java 20. (RLPNC-6969)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.41.0.c69.0. Refer to the RNI-RNT release notes for a full description of new features.

• Fixed a bug where queries using filter_out_scores_below could return improper document scores and/or exceptions. (RLPNC-6809)

• Fixed POST _parameter_universe endpoint so that it supports non-scalar parameter values. (RLPNC-6832)

• Fixed a bug where initially low-scoring results could still be processed in the rescoring phase (RLPNC-6829)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.40.1.c68.0.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.40.0.c68.0.

• Fields of the type rni_name now support a new mapping parameter, testEntityType, to control whether a name’s entity type is required to match in the first pass. By default, this is set to true, meaning only names that match the entity type of the query will be returned. By setting it to false, names with any (or no) entity type will also be returned (RLPNC-6688)

• We've improved stability and error handling in the jvm plugin. (RLPNC-6403, RLPNC-6593)

• Fixed a bug where the pairwise match endpoint could fail to parse valid requests with non-RNI data types. (RLPNC-6631)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.39.0.c67.0

• Supports Elasticsearch 8.4.1

• The Katakana-English neural model is now available in MacOS and Linux platforms. (RLPNC-6070)

• enablePromisingTermsFiltering: You can now set the value of the parameter enablePromisingTermsFiltering to true to improve throughput for most languages. There may be a slight decrease in accuracy. The default value of the parameter is false. (RLPNC-5491)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Fixed POST _parameter_universe endpoint so that it supports non-scalar parameter values. (RLPNC-6832)

• Fixed a bug where initially low-scoring results could still be processed in the rescoring phase. (RLPNC-6829)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.39.0.c67.0

• The Katakana-English neural model is now available in MacOS and Linux platforms. (RLPNC-6070)

• enablePromisingTermsFiltering: You can now set the value of the parameter enablePromisingTermsFiltering to true to improve throughput for most languages. There may be a slight decrease in accuracy. The default value of the parameter is false. (RLPNC-5491)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.38.0.c67.0

• Supports Elasticsearch 8.2.2

• The speed of pairwise matching is no longer impacted by the number of parameter universes created. (RLPNC-6353)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• Includes RNI-RNT 7.40.1.c68.0 Refer to the RNI-RNT release notes for a full description of new features.

• Supports Elasticsearch 8.1.1

• All 8.x.x.x features through January 2023 are included.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Supports Elasticsearch 7.17.9.

• Fields of the type rni_name now support a new mapping parameter, testEntityType, to control whether a name’s entity type is required to match in the first pass. By default, this is set to true, meaning only names that match the entity type of the query will be returned. By setting it to false, names with any (or no) entity type will also be returned. (RLPNC-6688)

• Fixed a bug where queries using filter_out_scores_below could return improper document scores and/or exceptions. (RLPNC-6809)

• Fixed a bug where the pairwise match endpoint could fail to parse valid requests with non-RNI data types. (RLPNC-6631)

• Fixed a bug where Elasticsearch would crash when indexing a document with an address. (RLPNC-6593).

• Improved stability and error handling of the JVM build to make it more robust. (RLPNC-6161)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.39.0.c67.0

• The Katakana-English neural model is now available in MacOS and Linux platforms. (RLPNC-6070)

• enablePromisingTermsFiltering: You can now set the value of the parameter enablePromisingTermsFiltering to true to improve throughput for most languages. There may be a slight decrease in accuracy. The default value of the parameter is false. (RLPNC-5491)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Supports Elasticsearch 7.17.5

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• No changes other than supporting Elasticsearch 7.17.5

• Includes RNI-RNT 7.38.0.c67.0

• Supports Elasticsearch 7.17.4. (RLPNC-6298)

• Supports Java 17. (RLPNC-6205)

• The parameter filter_out_scores_below has been added. This parameter filters out documents that do not rescore above the set threshold. (RLPNC-6170)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.40.0.c68.0

• The parameter filter_out_scores_below has been added. This parameter filters out documents that do not rescore above the set threshold. (RLPNC-6170)

• Fields of the type rni_name now support a new mapping parameter, testEntityType, to control whether a name’s entity type is required to match in the first pass. By default, this is set to true, meaning only names that match the entity type of the query will be returned. By setting it to false, names with any (or no) entity type will also be returned. (RLPNC-6688)

• This release requires Java 11 and supports Java 17.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on any platform.

• Supports Elasticsearch 7.17.3

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on any platform.

• No changes other than supporting Elasticsearch 7.17.3

• Multi-field mappings involving RNI types (rni_name, rni_address, rni_date) can now be successfully merged. (RLPNC-6264)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• No changes.

• Empty strings are now treated the same as null values for rni_name, rni_address, and rni_date types when the allowNullValue parameter is enabled. (RLPNC-6245)

• Multi-field mappings using types rni_name, rni_address, and rni_date no longer produce a mapping_parsing_exception. (RLPNC-6249)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• No changes.

• Includes RNI-RNT 7.37.0.c66.0

• Supports Elasticsearch 7.17.1

• Multi-token overrides are now applied correctly. Previously, when an override was delimited by spaces, only the first token would be considered. Now every token in overrides delimited by spaces are considered. (RLPNC-6189)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• No changes other than supporting Elasticsearch 7.17.1 and RNI-RNT 7.37.0.c66.0

• Includes RNI-RNT 7.37.0.c66.0

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting RNI-RNT 7.37.0.c66.0

• Supports Elasticsearch 7.16.3

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.16.3

• Fields of the type rni_name now support a new mapping parameter, testEntityType, to control whether a name’s entity type is required to match in the first pass. By default, this is set to true, meaning only names that match the entity type of the query will be returned. By setting it to false, names with any (or no) entity type will also be returned. (RLPNC-6688)

• Empty strings are now treated the same as null values for rni_name, rni_address, and rni_date types when the allowNullValue parameter is enabled. (RLPNC-6245)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes

• Includes RNI-RNT 7.36.1.c65.0. Refer to the RNI-RNT release notes for a full description of new features.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes

• Supports Elasticsearch 7.16.2

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.16.2

• Removed the vulnerable version of log4j from the package. (RLPNC-6071)

• The score_if_null option can now be used with nested fields. (RLPNC-5923)

• Updated the request syntax and improved the functionality of the dynamic parameter configuration endpoints. (RLPNC-5946)

• Supports Elasticsearch 7.15.2

• Fixed a bug where the pairwise match endpoint would not return results for certain inputs. (RLPNC-5959, RLPNC-6076)

• Fixed a bug where fielded names could not be used in rescore queries. (RLPNC-6055)

• Queries now filter by entity type. Note that indexed names without a specified entity type will only match query names that also don't specify an entity type. (RLPNC-5896)

  Example: Create an index with one document: “RIDGEWAY JOHN” as PERSON.  Query the index with “Ridgeway School” as ORGANIZATION.

  • Previously: Returns "RIDGEWAY JOHN"

  • Now: No results returned

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• Includes RNI-RNT 7.38.0.c67.0

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• ARM64 support: We now support ARM64 processors. (RLPNC-5912)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes

• Supports Elasticsearch 7.13.2

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.13.2

• Supports Elasticsearch 7.12.1

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.12.1

• Includes RNI-RNT 7.37.0.c66.0

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting RNI-RNT 7.37.0.c66.0

• Supports Elasticsearch 7.11.2

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.11.2

• Includes RNI-RNT 7.39.0.c67.0

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.38.1.c67.0

• enablePromisingTermsFiltering: You can now set the value of the parameter enablePromisingTermsFiltering to true to improve throughput for most languages. There may be a slight decrease in accuracy. The default value of the parameter is false. (RLPNC-5491)

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• When using the parameter filter_out_scores_below, the filter will always return at least one document, even if the highest scoring document is below the filter threshold value.

• Includes RNI-RNT 7.38.0.c67.0

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• Updated Graviton support: This version supports Graviton with glibc226.

• This release consumes a special release of the RNI-RNT SDK and supports glibc 2.26 for arm machines.  The corresponding BT_BUILD value is now aarch64-glibc226-gcc93, not aarch64-glibc231-gcc93.

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• No changes

• Includes RNI-RNT 7.37.0.c66.0

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• No changes other than supporting RNI-RNT 7.37.0.c66.0

• Includes RNI-RNT 7.36.1.c65.0. Refer to the RNI-RNT release notes for a full description of new features.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• No changes

• Removed the vulnerable version of log4j from the package. (RLPNC-6071)

• Fixed a bug where the pairwise match endpoint would not return results for certain address inputs. (RLPNC-6076)

• Fixed a bug where fielded names could not be used in rescore queries (RLPNC-6055)

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Fixed a bug where the pairwise match endpoint would not return results for certain inputs. (RLPNC-5969)

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported on Windows.

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• ARM64 processors are now supported. (RLPNC-5912)

• The score_if_null option can now be used with nested fields. (RLPNC-5923)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes

• Dynamically-specified parameters are now applied successfully and consistently. Previously, there was a bug where added parameters would not always be applied to a query. (RLPNC-5848, RLPNC-5878)

• RNI-ES now issues an error message when dynamically-specified parameters have invalid names or values. (RLPNC-5849)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes

• Includes RNI-RNT 7.34.0.c64.1. Refer to the RNI-RNT release notes for a full description of new features.

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes

• Supports Elasticsearch 7.10.2 and includes RNI-RNT 7.33.2.c63.0

• The pairwise match endpoint for address matching now provides detailed information on how the addresses were matched.

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.10.2

• Supports Elasticsearch 7.9.3

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.9.3

• Now including RNI-RNT 7.33.2.c63.0

• Indexing, querying and rescoring can now be performed between addresses structured with fields or as strings. RNI uses the jpostal library to internally parse address strings. (RLPNC-5523)

• Added support for window_size_allowance and score_to_rescore_resctriction parameters in address matching. (RLPNC-5537)

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting RNI-RNT 7.33.2.c63.0

• Supports Elasticsearch 7.9.2

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.9.2

• Supports Elasticsearch 7.8.1 and includes RNI 7.32.3.c62.2

Known Issues

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.

• No changes other than supporting Elasticsearch 7.8.1

• Now including RNI-RNT 7.32.3.c62.2

• Addresses are now supported in the pairwise matching endpoint. Matching can be performed between fielded addresses, unfielded addresses, or a combination of the two.

  • Example:

    curl -XPOST 'localhost:9200/rni_plugin/_pair_match?type=rni_address' -H "Content-Type: application/json" -d '
    {
      "dataPair": {
        "data1": {
          "houseNumber": "101",
          "road": "Main st",
          "city": "Cambridge",
          "state": "MA",
          "country": "USA"
        },
        "data2": "101 Main St, Cambridge, Massachusetts, United States of America"
      }
    }'

    {
      "score": 0.9,
      "type": "ORIGINAL"
    }

• Fixed a bug where nested queries could produce documents with the incorrect score with more complex mappings.

  • Previously: All documents could be incorrectly returned with a score of 0.0

  • Now: Documents are returned with the correct score

Known Issues

• The doc_score, name_score and date_score functions currently are not supported in percolator queries.

• Support Elasticsearch 7.7.1 and include RNI 7.31.1.c62.2 ^[4]

• Fixed a bug where nested queries using the rni_rescorer that did not specify the window_size parameter would cause a NullPointerException (RLPNC-5394)

• Fixed a bug where the windowSizeAllowance and scoreToRescoreRestriction parameters would not properly restrict the first-pass results being rescored in a nested query (RLPNC-5393)

• The doc_score, name_score and date_score functions currently are not supported in percolator queries.

• No changes other than supporting Elasticsearch 7.7.1 and RNI 7.31.1.c62.2

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported

• Fixed a bug where nested queries using the rni_rescorer that did not specify the window_size parameter would cause a NullPointerException (RLPNC-5394)

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported

• Fixed an issue where the enableDynamicConfigurationEndpoints parameter did not properly disable the appropriate endpoints when set to false (RLPNC-5373)

• Support Elasticsearch 7.6.1

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported

• Now including RNI-RNT 7.32.3.c62.2.

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• Now including RNI 7.32.1.c62.2.

• Fixed a bug where nested queries using the rni_rescorer that did not specify the window_size parameter would cause a NullPointerException (RLPNC-5394).

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported

• Fixed an issue where the enableDynamicConfigurationEndpoints parameter did not properly disable the appropriate endpoints when set to false (RLPNC-5373)

• Support Elasticsearch 7.5.2 and include RNI 7.30.5.c62.2

• Added a new rescore syntax which must be used when using the score_to_rescore_restriction or window_size_allowance parameters (RLPNC-5263)

• Added the parameter enableDynamicConfigurationEndpoints to enable endpoints for stopwords, token overrides and parameters (RLPNC-5225)

• It is necessary to add elasticsearch\plugins\rni\bt_root\rlp\bin\amd64-w64-msvc120\ to PATH when installing on Windows

• The doc_score, name_score and date_score functions currently are not supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported

• Fixed an issue where dynamic parameters were not loaded correctly in clusters with multiple nodes (RLPNC-5226)

• It is now possible to define parameters for multiple parameter universes in a single session (RLPNC-5261)

• Indexing, querying and rescoring can now be performed between addresses structured with fields or as strings. RNI uses the jpostal library to internally parse address strings.

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• Now including RNI-RNT 7.32.3.c62.2.

• The doc_score, name_score, and date_score functions currently are not supported in percolator queries.

• Addresses are now supported in the pairwise matching endpoint. Matching can be performed between fielded addresses, unfielded addresses, or a combination of the two.

  • Example:

    curl -XPOST 'localhost:9200/rni_plugin/_pair_match?type=rni_address' -H "Content-Type: application/json" -d '
    {
      "dataPair": {
        "data1": {
          "houseNumber": "101",
          "road": "Main st",
          "city": "Cambridge",
          "state": "MA",
          "country": "USA"
        },
        "data2": "101 Main St, Cambridge, Massachusetts, United States of America"
      }
    }'

    {
      "score": 0.9,
      "type": "ORIGINAL"
    }

• Fixed a bug where nested queries could produce documents with the incorrect score with more complex mappings.

  • Previously: All documents could be incorrectly returned with a score of 0.0

  • Now: Documents are returned with the correct score

Known Issues

• The doc_score, name_score and date_score functions currently are not supported in percolator queries.

• Fixed a bug where nested queries could produce documents with the incorrect score.

  • Previously: All documents could be incorrectly returned with a score of 0.0

  • Now: Documents are returned with the correct score

• The doc_score, name_score and date_score functions currently are not supported in percolator queries.

• Support Elasticsearch 7.4.2 and include RNI 7.30.5.c62.2

• The doc_score, name_score and date_score functions are not currently supported in percolator queries.

• Katakana-Latin name matching with the enableSeq2SeqTokenScorer parameter enabled is not currently supported.