Switch default cluster to ES7 #524
Conversation
Bug: T415664
tarrow
left a comment
tarrow
left a comment
There was a problem hiding this comment.
I know it's just a WIP but here's my thoughts:
- let's go ahead and remove all the ES6 stuff
- the actual ES6 deployment
- the special ES6 transport
- any ES6 related environment variables
- resolve any code that had special behaviour when those variables were set
- remove from the docs any references to ES6
dati18
changed the title
docker-compose.yml
Outdated
| - MW_WRITE_ONLY_ELASTICSEARCH_HOST=elasticsearch-7.svc | ||
| - MW_WRITE_ONLY_ELASTICSEARCH_PORT=9200 | ||
| - MW_WRITE_ONLY_ELASTICSEARCH_ES6=false | ||
| - MW_DEFAULT_ELASTICSEARCH_ES6=false |
There was a problem hiding this comment.
How come this line remains? I thought this PR was removing ES6.
There was a problem hiding this comment.
Yeah can you test it? Whenever I remove it, everything goes "kaputt"
There was a problem hiding this comment.
I just tried commenting out MW_DEFAULT_ELASTICSEARCH_ES6 and followed the instructions in https://github.com/wbstack/mediawiki/pull/525/changes. The first time didn't seem to work, but after throwing everything away (docker compose down --volumes) and trying again I was able to successfully create some items and do a case-insensitive search for them. The output at http://localhost:9200/mwdb_somedb1_content_first/_search also looked sensible.
Have you tried recreating your local set-up? What specifically is "kaputt"?
Bug: T415664