Which version of the neo4j plugin should I be using with grails?
The official grails site claims that version 2.0.0-M02 is the latest, but the associated documentation is from version 1.x. Is there later documentation? Has much changed?
I'm interested in particular in how the node structure has been changed to represent the domain model. Is it now the case that labels are being used instead of SUBREFERENCE nodes now?
Related
I am having an application build on grails 2.2.4. I need to update it to grails 4.0.8 Can i upgrade directly. As i checked from various sources, i need to jump first from 2.2.4 to 3.x then thereafter 3.x to 4.x. Please suggest me optimum way to do this upgrade.
Similar to other question about Grails upgrades
Major version upgrades in Grails are rarely trivial. I'd suggest starting a new app in the target version, and migrating classes/functionalities.
In Grails framework, the effort required to update your application depends on multiple factors, such as:
The standard practices. For instance, the persistence stuff in the Grails services instead of controller or domains itself.
The underline plugins your application depends on. You would need to update to the latest version of the plugin, or in some case find an alternative approaches as the plugin may longer be maintained, or there maybe better ways of doing it. For instance, we had some custom plugin for multi-tenancy back when I started with Grails, But now, GORM has great support for multi-tenancy.
I personally think you should directly jump from Grails 2 to Grails 4 by creating a new application, and then move your source code. But, first you need to identify all the variables such as plugins or libraries.
I have an application which loads some external data based on gremlin.
I want to use it to load the data into a Neo4j database.
I saw that there was partial support for gremlin in previous versions but couldn't find any solution for latest version.
I'll be happy to hear if it is still possible and how can it be done.
At this point, TinkerPop expects to support 3.4.11 in its future 3.5.0 release (here) which is yet several months away. For TinkerPop to support 4.0 it would need a fresh release of the neo4j-tinkerpop-api-impl to be released with that version. It seems an issue has been created for that here.
Right now we are using Neo4j 1.9.9 version(embedded mode) with tinkerpop blueprints 2.4 API. We are planning to upgrade our Neo4j to 2.3. But I see that blueprints is not compatible with neo 2.3. Since our system is stable now we are trying to upgrade our neo4j without disturbing the crud layer much.
1.Can any one help me here to understand why blueprints is not compatible with 2.3?
2. If I plan to use spring-data from my understanding it is not for embedded mode.Can some one share if you faced this scenario and how you approached the problem?
I understand that was possible in previous versions, and I also understand that version 4.0.0 is a total redesign towards a server-first approach, but nowhere in the documentation it is said whether embedded mode is supported.
4.0.0.RELEASE is server only. Embedded support will be available in a future release.
I'm trying with the 2.5.0 release of Grails but I have had problems of compatibility with some plugins I've tried (for example searchable)
Which version of Grails you recommend to start a new project? I'd like to start with the version more compatible with the list of current Grails plugins https://grails.org/plugins/
I'm not interested with the newer version but with the most compatible/stable with the current plugins list.
Both 2.4.x and 2.5.x will work fine with the current plugins in general.
Without any details it's hard to know why the searchable plugin isn't working for you, but note that it only works with Hibernate 3 and the default in new Grails apps is to use Hibernate 4. But you can see that the Hibernate 3 configuration settings are commented out in BuildConfig.groovy and DataSource.groovy so you can easily change back to Hibernate 3.
Having said that, don't use searchable. The underlying Compass library is no longer maintained, and using the searchable plugin will cause scaling problems because it's very inconvenient to get it to use a shared index between servers. The author of Compass created Elasticsearch, and that's a much better option. There's also an actively maintained plugin for it.