Flowpack
Custom analyzer will fail if using custom index name.
To avoid ambivalence I usually use a project specific index name for the CR index. So instead of typo3cr I would name the index myproject-cr. Due to the custom analyzer configuration this will fail hard as the analyzer will then be used (due to the nodetype) but doesn't a actually exist in "my" index as it is only configured for typo3cr index. IMHO we need to find a solution that doesn't depend on the index name.
See https://github.com/Flowpack/Flowpack.SearchPlugin/commit/872f3622dde5fb104302c00de76cace2ed6ae135#diff-d06e40a2a4877cacd0ccde3ab14e8588R23 for the cause
Hey @kitsunet, that is really bad. I noticed that myself some days ago. I also encountered another problem, it seemed that parts of the index configuration is only working for elastic 1.x which we used at that time... I plan to dedicate my time on the april sprint to the search packages, but it may be that I not find much time till then.
My suggestion would be to move this index configuration out into the documentation to fix it in the meantime.
For me the suggested configuration works with Elasticsearch 2.4, I cannot reproduce the compatibility issue mentioned.
#42 adds at the documentation to work around this.
