-
Notifications
You must be signed in to change notification settings - Fork 4
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
index aanmaken met mapping werkt niet op amazon #72
Comments
😢 |
So even though code has been added to I've solved this for now by creating the indices in This problem needs a better solution |
Create indices before indexing documents
Actually, we now have this index creation in two places (here and |
I think this duplicate index creation is what is causing errors on AWS now
|
I think this is affecting me too. Is solving this a question of removing it in one or the other place? |
no, it is a complicated race condition that is not easily fixed without changing how the API/IO/redis work. In the past we used the default-mapping file (described somewhere in the installation manual) that you place in the ES config directory. On AWS this is not possible so we changed the software to create the index. The |
ok, yeah, I saw that Graphmalizer was still proceeding. Maybe a false alarm On Mon, Nov 23, 2015 at 2:28 PM, Jelle Herold notifications@github.com
|
exactly, it’s probably a false alarm :^) sorry for the confusion |
Is this still an issue or is it resolved? |
Still an issue. |
We are running our own instance of ES, so the problem of the default mapping is not applicable anymore. As far as I can see there is no problem in creating the indexes |
@bertspaan NOOIT ERRORS OPETEN
fix:
https://gist.github.com/wires/6aa3615cc99f47693fd5#file-default-mapping-js-L35
lowercase analyser was unknown..
The text was updated successfully, but these errors were encountered: