...
Parameter | ||||||
---|---|---|---|---|---|---|
|
Code Block | ||||
---|---|---|---|---|
| ||||
"patterns":"regex-provider:patterns" |
...
In the following example, "number" is in the dictionary as a regex for using "[0-9]+" and "[0-9]+\\.[0-9]+" :
Code Block | ||||
---|---|---|---|---|
| ||||
V--------------------------------------[What's your name 12 @#$ 25 63.3]---------------------------------------V ^-----[What's]-----V--[your]--V--[name]--V-----[12]-----V--[@#$]--V-----[25]-----V-----------[63.3]------------^ ^--[What]--V--[s]--^ ^--[{number}]--^ ^--[{number}]--^-----[63]-----V-----[3]------^ ^-----[what's]-----^ ^---------[{number}]----------^ ^--[what]--^ ^--[{number}]--^--[{number}]--^ |
Note |
---|
Notice that on the example for Regex Pattern Stage the "self-name" tag would have a potential match with "What's your name". However, the Simple Regex Stage does not lookup for matches beyond a single token (as the Regex Patter Stage does). |
Info |
---|
No vertices are created in this stage |
The regex pattern must have an "pattern dictionary" (a string to JSON map) which is a list of JSON records, indexed by entity ID. In addition, there may also be a pattern map and a token index.
...
Each JSON record represents an entity. The format is as follows:
Code Block | ||
---|---|---|
| ||
"_id" : "KGAAJGsBemSwA0nZTLXA", "tag" : "number", "pattern" : "[0-9]+\\.[0-9]+", "options" : { "caseInsensitive" : true, "literal" : false }, "confAdjust": 0.95 . . . additional fields as needed go here . . . |
...