1) Plugins can only expose REST endpoints that are added to node, relationship
and graphdb URIs, return types are restricted to nodes, relationships, paths,
primitives and collections thereof.
2) Extensions can add arbitrary REST endpoints.
You could also write an Extension that sets up its own
I have no problem writing it :). So plugin can expose anything it
likes and it will bootstrapped by the server when starting/deploying ?
Regards,
Dima Gutzeit.
Sent from my iPhone
On 18 באפר 2011, at 13:10, Jim Webber wrote:
> Hi Dima,
>
>> Can it be not REST interface but some custom made Pro
Hi Dima,
> Can it be not REST interface but some custom made ProtoBuff interface instead
> ?
It can be, but we don't have such a binding at the moment. This will be
something you'd have to write for yourself, or (sadly) wait until a later
Neo4j release.
Jim
__
Can it be not REST interface but some custom made ProtoBuff interface instead ?
Regards,
Dima Gutzeit.
Sent from my iPhone
On 18 באפר 2011, at 12:42, Michael Hunger
wrote:
> Dima,
>
> yes, you can write Server Plugins (and Extensions) and then just put those
> jars in your servers plugin dire
Dima,
yes, you can write Server Plugins (and Extensions) and then just put those jars
in your servers plugin directory.
They will be picked up and be available as REST endpoints for your client
applications to consume.
Those can also be implemented on top of your domain model, so that you don't
On Mon, Apr 18, 2011 at 11:40 AM, Mattias Persson wrote:
> 2011/4/17 Dima Gutzeit :
> > Tobias, thank you very much for your quick response.
> >
> Hi Dima,
>
> > Estimated number of relationships is ten times number of nodes, which
> makes
> > it 20 billion. Number of properties for each node is
2011/4/17 Dima Gutzeit :
> Tobias, thank you very much for your quick response.
>
Hi Dima,
> Estimated number of relationships is ten times number of nodes, which makes
> it 20 billion. Number of properties for each node is ~10 and for each
> relationship is ~5.
Currently neo4j supports 64 billio
Tobias, thank you very much for your quick response.
Estimated number of relationships is ten times number of nodes, which makes
it 20 billion. Number of properties for each node is ~10 and for each
relationship is ~5.
I have another question that troubles me, and its what the correct way to go
w
What is the required number of relationships?
I'll answer your questions inline below.
On Sun, Apr 17, 2011 at 7:27 PM, Dima Gutzeit
wrote:
> Oops, small correction. The required number of nodes is 2 billions and not
> 100 millions as originally stated.
>
> On Sun, Apr 17, 2011 at 8:16 PM, Dima
Oops, small correction. The required number of nodes is 2 billions and not
100 millions as originally stated.
On Sun, Apr 17, 2011 at 8:16 PM, Dima Gutzeit
wrote:
> Dear list members,
>
> I have a need for storage engine (graph based) for a server I am building.
>
> Here are the requirements:
>
>
Dear list members,
I have a need for storage engine (graph based) for a server I am building.
Here are the requirements:
1. Support for High Availability
2. Ability to store around 100 millions of nodes, estimated data size of
around 5 terabytes.
I've been reading about different options that N
11 matches
Mail list logo
