You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a simple note. When creating a custom_filter, the pattern_capture token filter does not throw an error with patterns missing. Instead, it must default to some behavior. I had mistakenly used "pattern" with a single string rather than "patterns" with an array.
If 'pattern_capture' tokenfilter is create / mapped without a 'patterns'
settings we now throw an exception since this is a misconfiguration and
likely due to the similar settings on related token filters.
Closes#3808
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
If 'pattern_capture' tokenfilter is create / mapped without a 'patterns'
settings we now throw an exception since this is a misconfiguration and
likely due to the similar settings on related token filters.
Closeselastic#3808
Just a simple note. When creating a custom_filter, the pattern_capture token filter does not throw an error with patterns missing. Instead, it must default to some behavior. I had mistakenly used "pattern" with a single string rather than "patterns" with an array.
https://gist.github.com/jtreher/6766911
{
"settings": {
"default" : {},
"analysis": {
"filter": {
"sample":{
"type":"pattern_capture",
"pattern":"(([a-z]+)(\d*))"
}
The text was updated successfully, but these errors were encountered: