
reindexer fails to connect nodes to the IndexNode
Reported by Khaless | July 10th, 2009 @ 06:35 AM | in 0.3.1
I think I have identified a case where the reindexer extention does not connect nodes to the index node, and hence they cannot be found by calling Node.all
I belive the problem is in reindexer.rb on the definition of the class method on_neo_started.
The event handler for a new node is only registered if the index node is also created, however if the index node has been created, the step to register the on add event handler is skipped. If I put
Neo4j.event_handler.add(@index_node)
just before the "end" of the method everything seems to be fine.
Comments and changes to this ticket
-
Andreas Ronge July 14th, 2009 @ 08:14 AM
(from [b16862e812ff61038730c74d0f4184eb2bef8905]) Fixed reindexing bug. If neo4j was restarted it would not keep track of newly created nodes. Neo4j.update_index would not work after restart. [#53] http://github.com/andreasronge/neo4j/commit/b16862e812ff61038730c74...
-
Andreas Ronge July 14th, 2009 @ 08:52 AM
- Milestone set to 0.3.1
- State changed from new to resolved
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 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
People watching this ticket
Referenced by
-
53 reindexer fails to connect nodes to the IndexNode (from [b16862e812ff61038730c74d0f4184eb2bef8905]) Fixed r...