I used the following definition:
- Code: Select all
<auxiliaryField name="router" regexGroup="1" toLowercase="true">
I expected URLs matching any of the 3 regexes would have the "router" field added. However, what actually happened is that only URLs matching the first regex worked. Others silently failed. Replacing the above definition with 3 separate auxiliaryField elements, each with a single regex, worked OK.
Is this expected? If only a single child is allowed, why doesn't the above configuration produce an error?
I also would like to know what the "store" and "tokenize" attributes to auxiliaryField do? They are used in the sample CrawlerConfiguration.xml, but not documented in the online help.