issue. Is there any internal instrumentation on Neo memory usage that
>> could be used to help tune/tweak the settings? If not, would it make sense
>> to add a couple of MBeans for this type of information?
>>
>> Rick
>>
>> -Original Message-
>>
I just got this same problem, and was able to defeat by upping heap
size. It was very strange - does Transaction#finish do some
non-blocking work?
Disclaimer: I'm using trunk neo-kernel from 2/10.
Thanks,
Adam
On Mon, Jun 1, 2009 at 1:31 PM, Johan Svensson wrote:
> Great that it seems to work.
Congratulations! Fantastic product.
On Tue, Feb 16, 2010 at 12:55 PM, Dmitri Livotov wrote:
> Our congratulations as well !
> Hope we'll also join into the graph users for both production and
> opensource contribution this graph year !
>
> Best,
> Dmitri
>
> Johan Svensson wrote:
>> Friends,
>>
AM, Johan Svensson wrote:
> Hi Adam,
>
> On Wed, Dec 9, 2009 at 4:37 PM, Adam Rabung wrote:
> > 1. This iterator will just prevent duplicates from being returned from
> > the iterator? If there's a condition (bug in my code) that causes
> > shutdown w/ open transac
Hi,
I was wondering if there are any guarantees about the order of relationships
that come out of Node.getRelationships? In my test case (attached) it seems
they come out in "creation date, ascending" order, until you close and
re-open the database. After the database is reopened, it seems like t
fixed... the iterable
> from getNodes() now runs through a filter (lazily before each next())
> so your problem should go away.
>
> 2009/12/8 Adam Rabung :
>> Hi,
>> I've recently run into problems with indexes becoming corrupt after
>> unclean shutdowns. Basica
Hi,
I've recently run into problems with indexes becoming corrupt after
unclean shutdowns. Basically:
1. Transaction 1 writes some data
2. Transaction 2 reads some data, and is left open
3. The database is shut down, with warnings about an open transaction
4. The database is opened. Recovery execu
Hi, I was wondering where lifecycle events fall on the roadmap? I'm
thinking along the lines of Hibernate Interceptors:
https://www.hibernate.org/hib_docs/v3/api/org/hibernate/Interceptor.html
Thanks,
Adam
On Thu, Sep 3, 2009 at 11:38 AM, Rob Challen wrote:
> I moved over to the b10 snapshot and
things as well.
>
> Again note that these things (nodes added/deleted in the tx) are
> handled... see the implementation which uses an in-memory lucene index
> per tx to be able to handle it. I just ran this example locally and it
> worked just fine (after a minor commit I jus
approaches, I don't see how you can avoid implementing these
same comparisons in-memory so that you can ensure you consider tx
deleted/added/modified nodes in the search. Now let me strongly
restate I think I must be using IndexService incorrectly :)
On Sun, Jul 5, 2009 at 6:45 PM, Mattia
I can't answer your questions, but regarding the formatting we use an
>>> Eclipse code formatter which you can download from this page:
>>> http://wiki.neo4j.org/content/Coding_Standard
>>>
>>> This page could be of some interest as well:
>>> http://wi
Hello,
First - I am new to Neo, but very interested. After years of solving
problems w/ a relational model, neo is a breath of fresh air. So far, the
API has been a breeze.
I recently ran into a problem where traversals were simply stopping sooner
than I expected. Being a "neophyte", I suspecte
12 matches
Mail list logo
