Oh I see, will try again. Thanks Johan.
Jerry
On Fri, Jul 31, 2009 at 2:55 AM, Johan Svensson wrote:
> Hi Jerry,
>
> Looks like you have shutdown NeoService then try to make a backup.
> When using the online-backup component NeoService has to be running.
> For offline backups you can just copy t
Yeah absolutely, those can be used in more ways than "wrapping"
another iterable and maybe another name would be appropriate, but your
transformer is just one special case for that. So whatever name we
pick there will be uses of it that wont fit well with the name.
I think it's nice to see you use
Thanks for looking into it. I found another logical error in the code
segment and had to rework it anyway - I am not sure I will be able to
reproduce the situation to test the fix.
On Thu, Jul 30, 2009 at 9:06 PM, Johan Svensson wrote:
> Hi Rob,
>
> Your problem was caused by a bug in the batch i
Cool,
Thanks as ever Johan.
ATB
Neil
On 30 Jul 2009, at 20:03, Johan Svensson wrote:
> You are right, we should change that generic one to a specific runtime
> exception. Will look into that during our exception refactoring.
>
> -Johan
>
> On Thu, Jul 30, 2009 at 8:51 PM, Neil Ellis
> wrote:
>
Hi Rob,
Your problem was caused by a bug in the batch inserter. I just
committed a fix for it so a new b9-SNAPSHOT should be available soon.
-Johan
On Tue, Jul 28, 2009 at 11:25 AM, Rob Challen wrote:
> I'm using the batchinserter to build a graph. I'm not sure if what I am
> seeing here is some
You are right, we should change that generic one to a specific runtime
exception. Will look into that during our exception refactoring.
-Johan
On Thu, Jul 30, 2009 at 8:51 PM, Neil Ellis wrote:
> Hi Johan
>
> I meant the application is being shutdown (not neo.shutdown()) :-) -
> though I understa
Hi Jerry,
Looks like you have shutdown NeoService then try to make a backup.
When using the online-backup component NeoService has to be running.
For offline backups you can just copy the store directory.
Regards,
-Johan
On Wed, Jul 29, 2009 at 4:01 AM, Jerry Juanico wrote:
> Hi Emil
>
> I'm new
Hi Johan
I meant the application is being shutdown (not neo.shutdown()) :-) -
though I understand the confusion. So as part of our shutdown process
we will tell all active threads to stop by interrupting them. When
they've all stopped I'll shutdown Neo.
So the thread this code runs in is re
Hi Neil,
Yes, there are a lot of error messages that needs to be improved. On
the other hand the documentation should state that calling any Neo4j
API operation after (or concurrently with) NeoService.shutdown() is
not valid. Adding a flag to check if running is not an option because
of performanc
Clean shutdown should not result in recovery, if so it is a bug. Can
you reproduce a test case for this?
A bit simplified the recovery process can be divided into two parts:
o Put the store files in a consistent state by replaying the logical
log (this is fast).
o Rebuild the id generators (this
Thanks for the explanation. I've definitely gotten more insight into the
problem now, and
I understand your reasoning for naively loading relationships (even if it's not
especially scalable).
I'm now considering methods for restructuring the graph to improve the
performance.
Thanks Again,
Ik
11 matches
Mail list logo
