Query related to full text indexes - using custom analyzer

Neo4j Graph Platform
, , ,
1

:red_question_mark: Issue with Fulltext Index Not Coming Online After Migration

:wrench: Setup Summary:

  • Initial Neo4j version: 4.2.x
  • Intermediate version: 4.4.44
  • Target version: 5.26.7
  • Goal: Retain and activate fulltext indexes (with custom analyzer) after upgrade

:pushpin: What I Did

:white_check_mark: First Attempt (Success):

  1. I used scp to copy both:
  • /data/neo4j/data/databases/
  • /data/neo4j/data/transactions/
    from my Neo4j 4.2 instance to a Neo4j 4.4 setup.
  1. I pointed 4.4 to this copied data and started the database.
  2. From 4.4:
  • I ran neo4j-admin backup
  • Then restored and migrated that backup in Neo4j 5.26.7.
  1. After placing my custom analyzer JAR in the 5.26 plugins folder, all fulltext indexes came ONLINE successfully.

:cross_mark: Second Attempt (Issue):

  1. I again used the scp-copied data from 4.2.
  2. This time, I started 4.4, and then created a dump using neo4j-admin dump.
  3. I took that dump output, and restored it in 5.26 using neo4j-admin load.
  4. After adding the same custom analyzer JAR, the fulltext indexes remained in FAILED state.

:red_exclamation_mark: Question

Why does using neo4j-admin dump + load (in the second approach) cause fulltext indexes to fail to come online, while the first approach (using backup + restore) works perfectly?

  • Is neo4j-admin dump excluding some metadata related to custom analyzers or fulltext index internals?
  • Is there a recommended way to preserve fulltext index integrity when moving from 4.2 → 4.4 → 5.26?

Question : in 4.4 i created corresponding range indexes for btree indexes but when i migrate it gives error and suggest to use --force-btree-indexes-to-range @therese.magnusson