The Score Records Command

TIBCO Patterns provides a score records command. Using this command, you can perform a query against a given set of records instead of a table. This command is similar to a search command with a few key differences:

•

Instead of passing the name of a table or set of tables to be searched a set of records is passed in.

•

Joined searches are not supported by the score records command. As tables are not involved, the concept of joined tables does not apply.

•

All records passed in are always scored and returned. This command is explicitly a request to calculate and return the match score for a set of records, and not a "search" request. Therefore, all records are always returned, even if the record is assigned the "reject" score.

•

Filtering predicates do not apply. All records given are always scored and returned and therefore, a filtering predicate is ignored.

•

Prefilters are never used, and therefore, all prefilter search options are ignored.

•

Cutoff options do not apply. Again, all records are always scored and returned, and therefore, cutoff options are ignored.

•

A query that has no query data is not considered an error when used with the score records command. In a search command, a query that has no query data is rejected as an error. With no data, the TIBCO Patterns server can make no reasonable selection among the records in the table. The score records command is not making a selection, it only provides scores, and therefore this restriction does not apply to the score records command.

The score records command ignores options that do not apply, it does not reject them with an error. This allows the same query and search options used with a search command to be used with a score records command. The output of the score records command uses the same format as the output of the search command, including ordering the records from the highest score to the lowest. The special reject score is considered the lowest possible score.

Some of the possible use cases for the score records commands are:

•

Scoring record pairs when training a Learn model.

•

Applications where a stream of records must be tested for a match to a particular query. Instead of loading the records into a temporary table, they can be tested directly.

•

Applications that need a two-phase search. The first phase is a rough search to see if there are any candidates. The second phase applies a more precise, but more expensive, search to refine or obtain additional score information on the records. The score records command can be used in the second phase to avoid searching the entire table twice.