We are overriding the analyzer to be used for fulltext indexes to use the simple
analyzer. This works on a local single-node installation, but not on our cluster installation, as we can se that a query using English stop words does not yield any mathces.
I create the index with CALL db.index.fulltext.createNodeIndex("test",["Company"],["name"],{analyzer:"simple"})
CALL db.index.fulltext.listAvailableAnalyzers
lists the analyzer.
In the fulltext-index.properties
created, we see that the index uses the standard analyzer:
analyzer=standard
In the local installation, we get:
analyzer=simple
I've tried to re-create the index with several of the other available analyzers as well, but it always selects standard
according to the properties file.
We are running on enterprise version 3.5.3. We saw the same problem on 3.5.0 with a custom analyzer, but upgrading (including removing our custom analyzer as the simple
analyzer now is included OOTB) trying to recreate the index did not solve the problem.
The debug log does not contain any information about the analyzer:
2019-03-04 13:55:08.404+0000 INFO [o.n.k.i.a.i.IndexPopulationJob] Index population started: [NODE:Company(name) [provider: {key=fulltext, version=1.0}]]
2019-03-04 13:55:16.919+0000 INFO [o.n.k.i.a.i.IndexPopulationJob] Completed node store scan. Flushing all pending updates.
BatchingMultipleIndexPopulator{activeTasks=0, executor=java.util.concurrent.ThreadPoolExecutor@385bcd3a[Running, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1], batchedUpdates = [0 updates], queuedUpdates = 0}
2019-03-04 13:55:16.951+0000 INFO [o.n.k.i.a.i.IndexPopulationJob] Index creation finished. Index [NODE:Company(name) [provider: {key=fulltext, version=1.0}]] is ONLINE.
Could this be a bug when running in a cluster?