String properties are stored in blocks so even if you have tiny string
values each property value will occupy a full block (30 or 60 bytes,
can someone correct me here?). That's what taking most of your space
IMHO
2010/6/3, Biren Gandhi biren.gan...@gmail.com:
Here is some content from
Hi Thomas,
From what I understand (someone correct me if I'm wrong please)
- Neo4j does reuse the holes.
- It will not reuse the holes you created in the current session, but will
reuse all holes created in previous sessions.
My problem is a bit of a strange use case as I'm trying to reduce the
Hi, Craig. Not crazy at all. We're doing something similar to flag
archived nodes. Instead of deleting context(since we want to
infrequently access the nodes/relationships, but only under certain
types of queries/traversals), instead we mark the nodes/relationships
with a boolean
Hi all,
Tim Anglade has started off a cool meetup series,
http://nosqlsummer.org with meetup places all over the world. The
Öresund gang is providing space and beer in Malmö, so if you are in
Sweden, Germany or Denmark just come along to discuss the Dynamo
Amazon paper and others!
Hey Peter,
What is the time frame for that?
Thanks,
Marko.
On Jun 3, 2010, at 5:19 AM, Peter Neubauer wrote:
Hi all,
Tim Anglade has started off a cool meetup series,
http://nosqlsummer.org with meetup places all over the world. The
Öresund gang is providing space and beer in Malmö, so if
We had an accidental shutdown of a running Neo instance, and there was no
automatic recovery on startup. We are getting a bunch of Block Not In
Use errors such as:
Block not inUse[0] blockId[179414]
Is there a way to recover from this? Is this a bug? If so, is there a fix
available?
The page in the link says 16th of June.
cheers,
-tobias
On Thu, Jun 3, 2010 at 5:05 PM, Marko Rodriguez okramma...@gmail.comwrote:
Hey Peter,
What is the time frame for that?
Thanks,
Marko.
On Jun 3, 2010, at 5:19 AM, Peter Neubauer wrote:
Hi all,
Tim Anglade has started off a cool
Some more information: This error is first occurring when trying to read a
String property on a node, and also happens when reading string properties
on other nodes.
-Original Message-
From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On
Behalf Of Rick Bullotta
Rick,
There is no ordinary way to NOT run recovery on startup if the system
crashes. The only way for that to happen is if something extraneous to
Neo4j has modified the filesystem in between runs. For example if the
logical files are removed after a crash, then starting up could lead
to no
Hi, Johan.
I might have missed the recovery attempt being logged, but here's the
basics:
- it was a non-clean shutdown but not a powerdown (task terminated).
- the nodes that seem to be exhibiting the odd behavior were not being
written to at the time, but that doesn't necessarily mean
Where do we sign up :-)
On Thu, Jun 3, 2010 at 1:19 PM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Hi all,
Tim Anglade has started off a cool meetup series,
http://nosqlsummer.org with meetup places all over the world. The
Öresund gang is providing space and beer in Malmö, so if
Hi, Johan.
I sent you the store as a zip file.
Nothing out of the ordinary other than the process terminating abnormally
(it was running in the context of an embedded Tomcat inside of Eclipse, and
the embedded instance got terminated by accident instead of shut down
normally).
Rick
No we do nothing like that so I do not think that is the problem. I
will have a look at your store to see if I can get any clues to what
the problem might be.
-Johan
On Thu, Jun 3, 2010 at 7:23 PM, Rick Bullotta
rick.bullo...@burningskysoftware.com wrote:
One possible hint?
Hi there Anders,
Thanks for spotting the bug! It appears that the Neo REST API (the HTTP URIs
the server expects) changed since the initial version I coded it for. All
fixed now.
I also included the set NULL to remove the property function.
New version on github.
Cheers
Al
I would like to store coordinates as nodes in neo4j to do simple querys
For example a list of 10,000 nodes:
Node[1] - lon=-74.007124, lat=40.714550
Node[2] - lon=-94.626824, lat=39.113380
Node[3] - lon=-105.937406, lat=35.691543
Node[4] - lon=-122.329439,
15 matches
Mail list logo