_query_rewrite_staging collection. It also uses reviewed documents from that collection to improve the accuracy of the job. You can review, edit, deploy, or delete output from this job using the Query Rewriting UI.
Fusion ships with the OpenNLP Maxent model already loaded in the blob store.
This job’s output, and output from the Token and Phrase Spell Correction job, can be used as input for the Synonym and Similar Queries Detection job.
Minimum configuration
For most use cases, the minimum configuration for this job consists of these fields:id/Spark Job ID Give this job an arbitrary ID string.trainingCollection/Training Collection Specify the input collection.fieldToVectorize/Field to Vectorize Specify the field in the input collection where phrases can be found.outputCollection/Output Collection Specify the collection in which the output documents should be indexed.
Output documents
By default, the job only outputs the phrases found from the original document. In each row of the phrases output, these fields are most useful:- The phrase itself is in the
phrases_sfield, which can be used for faceting. - The
likelihood_dfield gives the likelihood that the phrase is legitimate, from 0 to infinity.
Low-probability phrases are automatically trimmed from the results. - When a phrase’s likelihood value is ambiguous, the
reviewfield is set to “true” to indicate that the phrase should be reviewed. - A
phrase_countfield indicates the number of instances of the phrase in the input collection.
Output fields
If the
attachPhrases/Extract Key Phrases from Input Text parameter is set to “true”, then the job also outputs the original documents from the input collection with an appended field, phrases_extracted_tt, that lists the extracted phrases from this document.
The way to distinguish the phrases output from the original document output is by the field doc_type_s, with one of these values:
key_phrasesdenotes phrases output.original_doc_with_phrasesdenotes the original documents.