- Need to optimize Neo4j 2.2 configuration to fix query cache problem
- Migrate neo4j2.2 Data to latest version. (Do we need to change all queries in application once we migrated?
I imagine that I'd do #2 first, by leaving the production db online, and upgrade a copy to work out any issues.
On the upgraded db copy test each of the queries.
If the upgrade is certain, then I'm pretty sure I would do the upgrade first before working on #1, unless it is a critical issue that can't wait.
Are you planning to upgrade to 3.5.x or 4.x?