On Saturday, September 4, 2010, Paddy <[email protected]> wrote: > Hi alex, > Some interesting suggestions, As far as I'm aware the Neo4j reference node > is needed to display graphs in neoclipse, That is the only reason i would > use a reference node.
I don't want tosound like arueing, but if that's the only reason, then it should definitely *not* be part of the API. > > The last test that was failing should work if you use the > LuceneFulltextQueryIndexService<http://components.neo4j.org/neo4j-index/apidocs/org/neo4j/index/lucene/LuceneFulltextQueryIndexService.html> > fulltextIndex = new LuceneFulltextQueryIndexService(gds); > This part is getting even more confusing now :(. There are 2 Lucene IndexServices in the neo4j 1.1 distro and there's an additional one in the components. Anyone could explain what each of them is offeringand if they can be combined? > ElasticSearch looks really good. How would you integrate ElasticSearch with > neo4j? > I'm a newbie to Neo4j so I'm not sure I know the right answer to this question. As far as I read, there're probably two ways to integrate the two: - using the same approach as the IndexService - use the Neo4j events framework for automatically index/update ElasticSearch (unfortunately I don't know much about the event framework to say if this would work or not though) Bests, :- alex > cheers > Paddy > > > > 2010/9/3 Alexandru Popescu ☀ <[email protected]> > >> On Friday, September 3, 2010, <[email protected]> >> wrote: >> > 1. They are "durable" but not "permanent", in the sense that if a node >> > is deleted, its ID will be re-used, unlike autoincremented keys in a >> > database, which are typically not re-used. Perhaps a poor choice of >> > words. >> > >> >> In fact if I'm reading this right, they are both durable and >> permanent: as long as the node exist it will always be associated with >> that ID. The only caveat is that IDs can be reused once their initial >> node was purged from the system. >> >> This is a very important aspect as I can imagine many systems that can >> use a small subset of the existing nodes as entry points. Basically by >> using the cached IDs you'll be able to get to these without the need >> of using indexing/traversals. >> > >> > 3. Third parameter = value of the K-V pair you're using to index the >> > node. >> > >> >> I figured that out myself, but I still believe that the new method >> I've suggested would be welcome. Real question is: how many time you >> store a set of properties in the node, but want to index it by a >> completely unrelated/not persistent value? I'd speculate that this >> scenario is very very rare. >> >> > >> > 4. The reference node is merely one approach to a graph structure. >> > You can have any number of standalone nodes. Reasonable to allow >> > deleting the default reference node, though it might be a good idea to >> > make this a configurable option on DB creation. >> > >> >> If the "reference node" is not mandatory then why creating it by >> default? If you take as a reference the most well known hierarchical >> model, the FS, there it makes a lot of sense to have a root node >> (which is undeletable). But as I read this and noticed from the tests, >> the Neo4j "reference node" serves no purpose at all. >> >> > >> > >> > 5/6. Haven't done much with Lucene yet, about to get started soon. >> > Please keep sharing your experiences. Considering whether or not to >> > use SOLR, also. >> > >> >> I want to keep things as simple as possible, so for my current >> experiments I'll not look beyond what is already available in Neo4j. >> This aside, if I'd be to look into using a 3rd party indexing tool, my >> first option would be ElasticSearch (disclaimer: I do know the lead >> developer of ElasticSearch and his experience in indexing tools). >> >> I hope others will jump in and comment/answer on my suggestions and >> questions. >> >> Thanks, >> >> :- alex >> >> > >> > >> > -------- Original Message -------- >> > Subject: [Neo4j] API Questions and a bit more >> > From: Alexandru_Popescu_â <[1][email protected]> >> > Date: Fri, September 03, 2010 4:53 am >> > To: [2][email protected] >> > Hi all, >> > Last night I had some time to play with Neo4j (1.1) API. I do have a >> > couple of questions and comments that I'd like to share with you: >> > 1. The documentation I've found mentions that `Node` IDs are not >> > "permanent". I'm wondering why are IDs exposed them? >> > 2. I was surprised to see a `Node`.delete() failing. The reason was it >> > had relationships. I think adding a method `Node`.delete(boolean >> > force) would >> > make code much easier. The method would automatically: >> > - remove all relationships >> > - clean up indexes >> > Note 1: I've been able to implement locally such a method in an >> > utility class and it seems to work without any problems. Anyways >> > another thing that I've found a bit weird was that I had to use >> > > _______________________________________________ >> Neo4j mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user >> > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
