elyzer | Stop worrying about Elasticsearch analyzers | Natural Language Processing library

by o19s Python Version: 1.2.2 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | elyzer Summary

elyzer is a Python library typically used in Artificial Intelligence, Natural Language Processing applications. elyzer has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install elyzer' or download it from GitHub, PyPI.

See step-by-step how Elasticsearch custom analyzers decompose your text into tokens. My therapist said this would be a good idea...

Support

Quality

Security

License

Reuse

Support

elyzer has a low active ecosystem.

It has 136 star(s) with 15 fork(s). There are 12 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 7 have been closed. On average issues are closed in 98 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of elyzer is 1.2.2

Quality

elyzer has 0 bugs and 16 code smells.

Security

elyzer has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

elyzer code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

elyzer is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

elyzer releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

elyzer saves you 64 person hours of effort in developing the same functionality from scratch.

It has 168 lines of code, 9 functions and 5 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed elyzer and discovered the below as its top functions. This is intended to give you an instant insight into elyzer implemented functionality, and help decide if they suit your requirements.

Analyze a single index
Prints tokens to stdout
Retrieve an analyzer from the index
Convert str to list
Normalize analyzer
Parse command line arguments

Get all kandi verified functions for this library.

elyzer Key Features

No Key Features are available at this moment for elyzer.

elyzer Examples and Code Snippets

No Code Snippets are available at this moment for elyzer.

Community Discussions

Trending Discussions on elyzer

Can we apply a char_filter to a custom tokenizer in elasticsearch?

QUESTION

Can we apply a char_filter to a custom tokenizer in elasticsearch?

Asked 2019-Mar-06 at 14:34

I have set up a custom analyser in Elasticsearch that uses an edge-ngram tokeniser and I'm experimenting with filters and char_filters to refine the search experience.

I've been pointed to the excellent tool elyser which enables you to test the affect your custom analyser has on a specific term but this is throwing errors when I combine a custom analyser with a char_filter, specifically html_strip.

The error I get from elyser is:

illegal_argument_exception', 'reason': 'Custom normalizer may not use char filter [html_strip]'

I would like to know whether this is a legitimate error message or whether it represents a bug in the tool.

I've referred to the main documentation and even their custom analyser example throws an error in elyser:

...

ANSWER

Answered 2019-Mar-06 at 14:24

This bug is in elyzer. In order to show the state of the tokens at each step of the analysis process, elyzer performs an analyze query for each stage: first char filters, then tokenizer, and finally token filters.

The problem is that on ES side, the analysis process has changed since they introduced normalizers (in a non-backward compatible way). They assume that if there is no normalizer, no analyzer and no tokenizer in the request but either a token filter or a char_filter, then the analyze request should behave like a normalizer.

In your case, elyzer will first perform a request for the html_strip character filter and ES will think it is about a normalizer, hence the error you're getting since html_strip is not a valid char_filter for normalizers.

Since I know Elyzer's developer pretty well (Doug Turnbull), so I've filed a bug already. We'll see what unfolds.

Source https://stackoverflow.com/questions/55023508

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install elyzer

(ES 2.x & 5.x).

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: