-
Notifications
You must be signed in to change notification settings - Fork 30
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
Errors during indexing-process #1
Comments
thanks for this. I just installed the plugin but I still get the same error. But I also get the error on plaintext content such as txt files..... |
Even after a restart of the elasticsearch servlet and the ./occ fullnextsearch:reset ? |
thanks.....after a complet reboot of the server and fullnextsearch:reset it seems to work now as expected. I now have to wait until the process is finished..... |
Is there a possibility to limit the indexing-process of files to certain file-types such as docx, etc ...? No a lot of unwanted files seems to be indexed too and I got this error at a specific file: [Elasticsearch\Common\Exceptions\BadRequest400Exception] |
Yes, there will be more settings/options in a future version. Can you provide more information regarding this file (format, size, ...) ? Is the index stuck on that file ? |
I am not sure what I am doing wrong Clean NC 13 beta But when i run index command i also get: [Elasticsearch\Common\Exceptions\BadRequest400Exception] **Edit: I give this a second try: sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment a reset and a restart Now it does work!** |
Yes, next release will first check that the plugin is installed. |
If I activate this app, I get a lot of the following errors during the indexing-process:
. Indexing: servername/foldername/problematic-file
[Elasticsearch\Common\Exceptions\BadRequest400Exception]
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline with id [attachment] does not exist"}],"type":"illegal_argument_exception","reason":"pipeline with id [attachment] does not exist"}
,"status":400}
If this error occures, the indexing-process is stopped immediately. After the problematic-file has been deleted, the process does not stop until the next problematic-file is going to be indexed....
The text was updated successfully, but these errors were encountered: