Finder type
|
Select Search Index.
|
Name
|
Select the appropriate index that was created using the Write to Search Index stage under the Advanced Matching deployed stages in
Enterprise Designer.
|
Starting record
|
Enter the record number on which search results should begin. The
default is 1.
|
Maximum results
|
Enter the maximum number of results you want the search index to return. Default is 10.
Note: If the maximum results is arbitrarily large,
process those in batches, using the Fetch Batch
Size field.
|
Fetch Batch Size
|
If the Maximum results is arbitrarily
large, enter the size of batches in which you want the results
to be processed. This optimizes processing of large number of
records. Default is 10000.
The recommended Fetch Batch Size is a value lesser than
Maximum results and if the
Fetch Batch Size is greater than
Maximum results, the records are
processed in a single batch.
Note: This field is applicable only to cluster supported search engine and
not to the legacy search engine.
|
Return match count
|
Returns the total number of matches that were made. For example,
if you use the default of "10" for the Maximum results field
above, only 10 results will be returned. However, if you check
this box, the TotalMatchCount output field will tell you how
many matches were made during processing.
|
Index search type |
Determines the type of index search you want to
conduct. Select Simple search. |
Index Fields
|
Select the index field(s) you want to use for comparison in the
simple search.
|
Input field
|
Select the input field you want to use for comparison in the
simple search.
|
Input analyzer
|
Specify which analyzer to use to tokenize the input string. One
of these:
- Standard—Provides a grammar-based tokenizer that contains a
superset of the Whitespace and Stop Word analyzers.
Understands English punctuation for breaking down words,
knows words to ignore (via the Stop Word Analyzer), and
performs technically case-insensitive searching by
conducting lowercase comparisons. For example, the string
“Precisely Software” would be returned as two tokens:
“Precisely” and “Software”.
- Whitespace—Separates tokens with whitespace. Somewhat of a
subset of the Standard Analyzer in that it understands word
breaks in English text based on spaces and line breaks.
- StopWord—Removes articles such as "the," "and," and "a" to
shrink the index size and increase performance.
- Keyword—Creates a single token from a stream of data. For
example, the string “Precisely Software” would be
returned as just one token “Precisely Software”.
- Russian—Supports Russian-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "and," "I," and "you" to shrink the index size and
increase performance.
- German—Supports German-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Danish—Supports Danish-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "at" "and," and "a" to shrink the index size and
increase performance.
- Dutch—Supports Dutch-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Finnish—Supports Finnish-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "is" "and," and "of" to shrink the index size and
increase performance.
- French—Supports French-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Hungarian—Supports Hungarian-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Italian—Supports Italian-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Norwegian—Supports Norwegian-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Portuguese—Supports Portuguese-language indexes and
type-ahead services. Also supports many stop words and
removes articles such as "the" "and," and "a" to shrink the
index size and increase performance.
- Spanish—Supports Spanish-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Swedish—Supports Swedish-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "the" "and," and "a" to shrink the index size and
increase performance.
- Hindi—Supports Hindi-language indexes and type-ahead
services. Also supports many stop words and removes articles
such as "by" "and," and "a" to shrink the index size and
increase performance.
|
Output Fields tab
|
Check the Include box to select which
stored fields should be included in the output. Note: If the
input field is from an earlier stage in the dataflow and it
has the same name as the store field name from the search
index, the values from the input field will overwrite the
values in the output field.
|