New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardise wildcard matching #11334
Comments
Highlighting has an issue about excluding fields from * that this applies to. I don't have the number handy. |
If we used Regex would that prevent us from hand crafting the parsing? How much of performance hit is that going to be? We could execute regex only when we detect the presence of regex. |
You'd have to have some marker to indicate that it is a regex, otherwise |
Discussing this some more: changing the index pattern matching would be problematic, eg you'd have to escape the . in |
Won't fix |
With the new
path_filter
parameter (#10980) we support wildcards with*
matching a single "segment" of the path and**
matching multiple segments.Currently we use slightly different simple wildcards in a number of other places, such as when looking up field names. Index wildcards also support a leading
-
to exclude matches.I'd like to propose that we standardise the syntax across all APIs that use wildcard matching, as follows:
*
matches zero or more characters up to but not including a period.
**
matches all zero or more characters including a period,
+
to include matches (the default if not specified) or a-
to exclude matches*
,+
,-
,,
,\
with a preceding\
Relates to #11294
The text was updated successfully, but these errors were encountered: