Re: [Neo4j] Size limits for REST Server?
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 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 kind of docs about this? > > Yes, and I just noticed Peter responded with those links :-) > > > And lastly (I just realized I only asked more questions so far... ) is > the > > REST-Server somehow prepared > > for these extensions? I mean, could I use the 'skeleton' of the Server > and > > only change some parts in order > > to get all this? > > With the managed and unmanaged extensions, you add your code into the > server through APIs. The managed API gives you a very graph-centric view and > manages creation of JSON and HTML representations on your behalf. The > unmanaged API gives you a JAX-RS API plus direct access to the underlying > database. > > Jim > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Pablo Pareja Tobes My site http://about.me/pablopareja LinkedInhttp://www.linkedin.com/in/pabloparejatobes Twitter http://www.twitter.com/pablopareja Creator of Bio4j --> http://www.bio4j.com http://www.ohnosequences.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Size limits for REST Server?
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 kind of docs about this? Yes, and I just noticed Peter responded with those links :-) > And lastly (I just realized I only asked more questions so far... ) is the > REST-Server somehow prepared > for these extensions? I mean, could I use the 'skeleton' of the Server and > only change some parts in order > to get all this? With the managed and unmanaged extensions, you add your code into the server through APIs. The managed API gives you a very graph-centric view and manages creation of JSON and HTML representations on your behalf. The unmanaged API gives you a JAX-RS API plus direct access to the underlying database. Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Size limits for REST Server?
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 GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Thu, Oct 13, 2011 at 5:04 PM, Pablo Pareja wrote: > 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 somehow prepared > for these extensions? I mean, could I use the 'skeleton' of the Server and > only change some parts in order > to get all this? > > Thanks! > > Pablo > > On Thu, Oct 13, 2011 at 4:32 PM, Jim Webber wrote: > >> 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 >> ___ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user >> > > > > -- > Pablo Pareja Tobes > > My site http://about.me/pablopareja > LinkedIn http://www.linkedin.com/in/pabloparejatobes > Twitter http://www.twitter.com/pablopareja > > Creator of Bio4j --> http://www.bio4j.com > > http://www.ohnosequences.com > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Size limits for REST Server?
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 somehow prepared for these extensions? I mean, could I use the 'skeleton' of the Server and only change some parts in order to get all this? Thanks! Pablo On Thu, Oct 13, 2011 at 4:32 PM, Jim Webber wrote: > 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 > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Pablo Pareja Tobes My site http://about.me/pablopareja LinkedInhttp://www.linkedin.com/in/pabloparejatobes Twitter http://www.twitter.com/pablopareja Creator of Bio4j --> http://www.bio4j.com http://www.ohnosequences.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Size limits for REST Server?
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 ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
[Neo4j] Size limits for REST Server?
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 functionality so that fetching methods for specific kind of nodes/rels/situations can be overwritten ? Cheers, Pablo -- Pablo Pareja Tobes My site http://about.me/pablopareja LinkedInhttp://www.linkedin.com/in/pabloparejatobes Twitter http://www.twitter.com/pablopareja Creator of Bio4j --> http://www.bio4j.com http://www.ohnosequences.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
