Skip to content
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

Wildcard expansion on field names should not try to match on name #6494

Closed
jpountz opened this issue Jun 13, 2014 · 2 comments
Closed

Wildcard expansion on field names should not try to match on name #6494

jpountz opened this issue Jun 13, 2014 · 2 comments

Comments

@jpountz
Copy link
Contributor

jpountz commented Jun 13, 2014

If you have two fields bar and foo.bar, b* would match both since the regexp is applied to the index name, the full name and the name. And for foo.bar, these are:

  • index name: foo.bar
  • full name: foo.bar
  • name: bar

I don't think the regexp should try to match the name.

Related to: #4081

@clintongormley
Copy link
Contributor

I agree. If wildcards are used, then they should match the full path, not the short version. Additional thought: it would be nice to allow * to match just one step in the path, and ** to match across dots, so, given fields:

  • name.first
  • name.first.raw
  • name.last
  • name.last.raw

This pattern name.* would match only name.first and name.last, while name.** would match all four fields.

@clintongormley
Copy link
Contributor

Closing in favour of #8870

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants