-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
License expiring #110
Comments
This seems to be related to @orangejulius where's best to disable |
The X-Pack extensions to Elasticsearch are proprietary addons for additional functionality, none of which is needed by Pelias. In the past, we've made due with disabling some of them by environment variable, however that still leaves them present to emit scary warnings about licenses. These warnings probably are ok to ignore, again since Pelias does not use any X-Pack features. However, its best to avoid scary warnings where possible, so this change removes the X-Pack plugin completely. Fixes #110
Hi @sweco-sefild thanks for reporting this, we totally hadn't noticed. I have no idea if there would actually be any impact to Pelias users come June 27th (mine showed June 10th), but it's not worth waiting to find out. I just opened #111 to remove the X-Pack extension from our docker images completely. |
The X-Pack extensions to Elasticsearch are proprietary addons for additional functionality, none of which is needed by Pelias. In the past, we've made due with disabling some of them by environment variable, however that still leaves them present to emit scary warnings about licenses. These warnings probably are ok to ignore, again since Pelias does not use any X-Pack features. However, its best to avoid scary warnings where possible, so this change removes the X-Pack plugin completely. Fixes pelias#110
Started my elastic-container, running pelias/elasticsearch:5.6.12, and got the following in the log:
(I deleted #'s before each row to calm markdown a bit)
I don't think I've seen it before - is this anything one should be worried about?
The text was updated successfully, but these errors were encountered: