Hello!
I had a few questions regarding Batch insert and normal insert in neo4j:
- All the properties of nodes need to be set initially while creating graph
db in batch insert mode.Can the values of a subset of the nodes be
updated/changed later on? Does this lead to any performance issues?
- Whi
Hi!
I've written about part of the recent Neo4j development taking place:
http://blog.neo4j.org/2010/06/neo4j-development-news.html
There's lots of links to this mailing list in it :-)
/anders
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.n
Hi,
I'm a beginner to neo4j. Recently set up the standalone rest server in linux
(started using neo4j-rest start). I was reviewing
http://wiki.neo4j.org/content/Configuration_Settings and was wondering how to
specify memory-mapped I/O settings & other backup-related settings to the REST
server
Hi Suruchi,
I'll answer each question inline below.
On Wed, Jun 30, 2010 at 6:27 PM, Suruchi Deodhar
wrote:
> Hello!
>
> I had a few questions regarding Batch insert and normal insert in neo4j:
>
> - All the properties of nodes need to be set initially while creating graph
> db in batch insert m
Hello!
I had a few questions regarding Batch insert and normal insert in neo4j:
- All the properties of nodes need to be set initially while creating graph
db in batch insert mode.Can the values of a subset of the nodes be
updated/changed later on? Does this lead to any performance issues?
- Whi
This problem has a simple solution:
Remove neo4j-commons-1.0 from your classpath, it conflicts with the commons
classes in 1.1-SNAPSHOT (that have now moved into kernel).
Cheers,
Tobias
On Wed, Jun 30, 2010 at 12:24 PM, Christian Morgner <
christian.morg...@udo.edu> wrote:
> Hi all,
>
> I encou
As the example states you must use the LuceneFulltextQueryIndexService (not
the LuceneFulltextIndexService)!
2010/6/30 Paddy
> I have been trying out the example at:
> http://wiki.neo4j.org/content/Indexing_with_IndexService
> I'm trying to implement LuceneFulltextIndexService searching
>
> I ma
Hi all,
I encountered a problem with the new TraversalDescription API in
1.1-SNAPSHOT (1.1-20100628.145423-131), using neo4j-commons-1.0.
The code
TraversalDescription descr = TraversalFactory.createTraversalDescription()
.breadthFirst()
.expand(TraversalFactory.expanderForType(RelTypes
Since write operations are confined in a transaction, data is only written
in tx.finish() så that's where neo4j does the invalidation of the searcher.
I.e. assuming multiple write operations are performed in each transaction
searchers need not be invalidated as often, and only when something is
act
Yes, but isn't that what you in practice have to do when using lucene
as an index for values in neo4j? Data could be written all the time,
and then you have to open a new reader every time you do a search, at
least when the index for the value you are searching for has changed.
How is that impleme
10 matches
Mail list logo