Safe Neo4j-Lucene Transactions
Reported by Andreas Ronge | February 8th, 2010 @ 08:44 PM
There is a problem with synchronization lucene and neo4j
transactions.
If neo4j crash just before the lucene index is commited the
indexing might never take place.
In version 0.4.0 the index is searchable after the transaction
commits.
Do we want to be able to search before the transaction commits
?
Maybe it should be configurable when indexing should be
performed:
1. In the transaction
2. Just after transaction
3. Sometime later - Polling some queue of nodes to be indexed.
Maybe use activemq or rabbitmq for option 3, or keep the queue as a linked list of nodes in neo4j ???
Comments and changes to this ticket
-
Andreas Ronge March 11th, 2010 @ 06:49 AM
- Milestone cleared.
-
Andreas Ronge November 4th, 2010 @ 09:33 PM
- State changed from “new” to “resolved”
Solved in neo4j 1.0.0, you can do both.
-
Andreas Ronge December 15th, 2011 @ 02:43 PM
(from [00150dd172e916d2334cdbe5bddd4033fa2f7557]) Formtastic support - allow assignment of has_n relationship with ids string integers closes #109 https://github.com/andreasronge/neo4j/commit/00150dd172e916d2334cdb...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Neo4j.rb is a graph database framework for JRuby.
It provides:
* Mapping of ruby objects to nodes in networks rather than in tables.
* Storage of ruby object to a file system.
* Fast traversal of relationships between nodes in a hugh node space.
* Transaction with rollbacks support.
* Indexing and quering of ruby objects.
* Integration with Rails
Andreas Ronge