Hi Jim and Peter,
thanks for the info and the links, I'll have a look at them.
As always happy for the great support around here ;)
Pablo
On Thu, Oct 13, 2011 at 5:49 PM, Jim Webber wrote:
> Hi Pablo,
>
> > What do you exactly mean by discoverability ? Always getting all in/out
> rels
> > for
Hi Pablo,
> What do you exactly mean by discoverability ? Always getting all in/out rels
> for a node?
Yup, exactly. By default the REST server projects the graph (naively) onto the
Web (itself a graph).
> About writing an extension, has anyone already done this at some level?
> Is there any ki
Pablo,
find docs about unmanaged extensions here:
http://docs.neo4j.org/chunked/snapshot/server-unmanaged-extensions.html
and an example is the clean-db extension by Michael Hunger, see
https://github.com/jexp/neo4j-clean-remote-db-addon as an example.
Does that help?
Cheers,
/peter neubauer
G
Hi Jim,
What do you exactly mean by discoverability ? Always getting all in/out rels
for a node?
About writing an extension, has anyone already done this at some level?
Is there any kind of docs about this?
And lastly (I just realized I only asked more questions so far... ) is the
REST-Server s
Hi Pablo,
For the very specific use-cases I'd recommend writing an extension rather than
using the default representations. The default behaviour of the REST API
emphasises discoverability which in the case of supernodes isn't usually
desirable.
Jim
Hi,
I'd like to know which are the limits in terms of number of
nodes/relationships, topology *(e.g. supernodes*
*with millions of incoming/outgoing relationship in the same node)* for
Neo4j REST-Server?
Has it already been used for large DB / BigData ?
Otherwise, is there anyway to tune the core
6 matches
Mail list logo