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

Improve Elastic Search tokenizer/analyzer #129

Open
mihaidma opened this issue Jun 24, 2016 · 0 comments
Open

Improve Elastic Search tokenizer/analyzer #129

mihaidma opened this issue Jun 24, 2016 · 0 comments
Assignees

Comments

@mihaidma
Copy link
Contributor

If I load in the system the seneca and seneca-postgres-store plugins metadata:

  • searching for senec doesn't match anything,
  • searching for seneca matches both module names,
  • searching for seneca-postgres matches both module names. It actually searches for all modules containing seneca and postgres,
  • searching for seneca-postg finds both plugins (they are found by the seneca search term). Searching only postg finds nothing. Doing seneca-postg search on the live site finds:

Prerequisite for: #123

To have an autocomplete/search-as-you-type search it can be enhanced with an autocomplete analyzer at index time and a standard analyzer at search time, 2-8 letters Edge ngram for terms.

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

No branches or pull requests

1 participant