Re: [Neo4j] Using AStar Algorithm with neo4j REST API

> I love the fact that I am able to use Astar for my search when running with > org.neo4j.kernel.EmbeddedGraphDatabase in-memory. Could you please explain how you came to these conclusions? It would be interesting for us where to update docs and information so that people don't run into this reas

Re: [Neo4j] Using AStar Algorithm with neo4j REST API

It's not exposed in the standard REST API, but you could easily write an a plugin which does, see http://docs.neo4j.org/chunked/stable/server-plugins.html 2011/12/9 Israel Ekpo > Hi Jim, > > I was just wondering how I can query the REST API for the shortest path b/w > 2 nodes using Astar instead

Re: [Neo4j] Using AStar Algorithm with neo4j REST API

Hi Jim, I was just wondering how I can query the REST API for the shortest path b/w 2 nodes using Astar instead of Dijkstra ___ NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please register and consider posting at https://groups.google.

Re: [Neo4j] Using AStar Algorithm with neo4j REST API

Hi Israel, Neo4j doesn't have an "in-memory" mode as you allude to - it's the same database whether you run it remotely or in your app (or container). Is your reasoning because the app itself has a large footprint such that it contends with Neo4j within the same process? Jim

[Neo4j] Using AStar Algorithm with neo4j REST API

Hi All, I am new to neo4j and I really like it. I love the fact that I am able to use Astar for my search when running with org.neo4j.kernel.EmbeddedGraphDatabase in-memory. With A-star, I am able to use dynamic values in the computation of the shortest path at run time. The in-memory version i

Re: [Neo4j] REST API - always batch?

> > 1. There are limits to how large the results can be from a batch API call. Just curious, what those limits are and what happens if you hit it? > 2. ... We have lots of ideas for how we > can improve the current REST API (add full transactional support, massively > improve throughput and lat

Re: [Neo4j] REST API - always batch?

UID (Create Read Update Index > Delete) > to describe Neo4j operations? My other attempt was "ICRUD" but that sounds > like the stuff you rub out of your eyes when you wake up in the morning. > > -- > View this message in context: > http://neo4j-community-discussions.43852

Re: [Neo4j] REST API - always batch?

: http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-API-always-batch-tp3550568p3551739.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user

Re: [Neo4j] REST API - always batch?

On Thu, Dec 1, 2011 at 9:03 AM, Dmytrii Nagirniak wrote: > Thanks Peter. > > I was asking because of the request to support batching in neography: > https://github.com/maxdemarzi/neography/issues/16 > > I sounds like the "normal" API is obsolete then :) > > It encourages non-transactional operati

Re: [Neo4j] REST API - always batch?

I think especially for atomic create operations that will be solved by a GEOFF import plugin in the future. which allows for updates/insertions of subgraphs. https://github.com/nigelsmall/py2neo/wiki/GEOFF Michael Am 01.12.2011 um 09:03 schrieb Dmytrii Nagirniak: > Thanks Peter. > > I was as

Re: [Neo4j] REST API - always batch?

Thanks Peter. I was asking because of the request to support batching in neography: https://github.com/maxdemarzi/neography/issues/16 I sounds like the "normal" API is obsolete then :) It encourages non-transactional operations. I think the batch-ing should be promoted a little bit more. Check

Re: [Neo4j] REST API - always batch?

Dmytri, sounds like an interesting plan! I don't think there is anything directly that I can see, except a bug, https://github.com/neo4j/community/issues/113 with "\\" which you might watch our for, reported by Josh Adell. Let us know how it works out! Cheers, /peter neubauer GTalk:      neubau

[Neo4j] REST API - always batch?

Hi, I wonder what the disadvantages would be if every request to the server would always be a batch (even for simple GETs)? This would make it easier to use the API from the application. How bad is this idea? Cheers, Dima http://www.ApproachE.com ___

Re: [Neo4j] REST api get list of all relationship properties (unique)

Hi Peter, thanks a lot for your answer! Our alternative will be to keep a copy of the properties in memcached. Another option would have been to create a second graph, which is used only to store the properties in nodes/relationships, but from my view this has the disadvantage of different semanti

Re: [Neo4j] REST api get list of all relationship properties (unique)

Jure, for this, I think there is no explicit support in Neo4j. I guess you will have to iterate and build up an in-memory list of the unique RelTypes as you go. Anyone having a better idea? Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 L

Re: [Neo4j] REST api get list of all relationship properties (unique)

Hi, it's the question, how to get the unique set of relationship properties in the graph, without querying/traversing all of the properties. Since I can only index nodes/relationships, the index API does not seem to be an option. Example: 1M relationships, each of them having one of 10 properties

Re: [Neo4j] REST api get list of all relationship properties (unique)

So, are you talking about the performance on a supernode, or on an arbitrary set of 1M relationships from e.g. a variable length Cypher query? Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 LinkedIn   http://www.linkedin.com/in/neubauer T

Re: [Neo4j] REST api get list of all relationship properties (unique)

Hi Peter, sounds good, I'll check how to contribute.. Meanwhile I was working on the original question of the thread - getting a list of unique properties used in the relationships. Since the lucene indexer in neo4j always uses nodes or relationships, I don't see a way to extract a list of relati

Re: [Neo4j] REST api get list of all relationship properties (unique)

Jure, you could just write a testcase that does exactly this - send g.getRawGraph() to the plugin and check what is happening (GremlinPluginFunctionalTest) in the debugger. Let's connect next week if you can't sort it out? Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.ne

Re: [Neo4j] REST api get list of all relationship properties (unique)

Hi I tried the .toString() and it throws the same error. Which is strange, since in the RepresentationConverter, the string should be returned fine if no other representation is found. Could the error be somewhere else? I also forked the Gremlin plugin, but need to get familiar with it (first tim

Re: [Neo4j] REST api get list of all relationship properties (unique)

Or, if we are not explicitely catching and converting the representations, at the end of this switch we could hand it over to the server REST subsystem in order to convert things. I will raised https://github.com/neo4j/gremlin-plugin/issues/2 Cheers, /peter neubauer GTalk:      neubauer.peter Sk

Re: [Neo4j] REST api get list of all relationship properties (unique)

Shouldn't it be enough to call toString() on your results if they are not valid representations, which are for a plugin: * Primitives * Node * Relationship * Path * Iterables or Collections thereof * probably also Map but I'm not sure. please try: >> {"script":"neo4j = g.getRawGraph().toString(

Re: [Neo4j] REST api get list of all relationship properties (unique)

Jure, if the primitives in the response are not recognized (like a normal Groovy Object), then the toString() of the result is returned. If you want, you can fork and add to the representations, see https://github.com/neo4j/gremlin-plugin/blob/master/src/main/java/org/neo4j/server/plugin/gremlin/Gr

Re: [Neo4j] REST api get list of all relationship properties (unique)

Hi Peter and Community, I played a bit with passing a groovy script to neo4j. However the response seems to be not JSON encoded, did I overlook something? I'm using 1.5M02 and did the following request (from tcpmon) http request: POST /db/data/ext/GremlinPlugin/graphdb/execute_script HTTP/1.1 Co

Re: [Neo4j] REST api get list of all relationship properties (unique)

Hello Peter, many thanks for the quick reply, this will help! Regards Jure -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/REST-api-get-list-of-all-relationship-properties-unique-tp3458852p3458999.html Sent from the Neo4j Community Discussions mailing li

Re: [Neo4j] REST api get list of all relationship properties (unique)

Jure, if you know the Lucene query in Java, you could write a Groovy/Java script directly accessing the IndexAPI and thus do your own Lucene magic, see http://docs.neo4j.org/chunked/snapshot/gremlin-plugin.html#rest-api-send-an-arbitrary-groovy-script---lucene-sorting for an example with custom so

[Neo4j] REST api get list of all relationship properties (unique)

Dear All, I would like to extract a list of unique properties used for all relationships using the REST API. I created a relationship index and indexed all properties. When I query for * using the REST API for the lucene query, I receive lots of relationships, so it's difficult to get a unique set

Re: [Neo4j] REST API Base URI

On Tue, Sep 27, 2011 at 11:29 PM, Nuo Yan wrote: > Hi Jake, > > Thanks for your reply. > > Sorry if my previous email was misleading, but I don't absolutely need > key-based authentication; that just turned out to be the what I first > thought of. I was trying to figure out what authentication me

Re: [Neo4j] REST API Base URI

Hi Jake, Thanks for your reply. Sorry if my previous email was misleading, but I don't absolutely need key-based authentication; that just turned out to be the what I first thought of. I was trying to figure out what authentication methods were supported so that I can evaluate. HTTPS + basic auth

Re: [Neo4j] REST API Base URI

As far as I know, the auth plugin currently only supports HTTP BASIC authentication. But it would be interesting to expand it to allow other authentication methods, for instance by allowing pluggable authentication providers. So if I understand your question correctly, yes, it does support authent

Re: [Neo4j] REST API Base URI

Limiting access to certain URIs or IPs is great, but ideally at this moment I also need something like a key-based authentication so I can send a private key in the headers from my restclient and neo4j would authenticate and only take authenticated requests. Does the authentication extension suppor

Re: [Neo4j] REST API Base URI

you can see the usage with an embedded Neo4j Server instance in the test at https://github.com/neo4j/authentication-extension/blob/master/src/test/java/org/neo4j/server/extension/auth/TestAuthentification.java HTH Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Ph

Re: [Neo4j] REST API Base URI

Nuo, Thomas Baum has been working on an authentication extension for Neo4j Server, see https://github.com/neo4j/authentication-extension. He could help you set it up and test it - it's used in hosting scenarios and should do what you want in terms of limiting access to certain URIs if that is what

Re: [Neo4j] REST API Base URI

For my scenario, I currently only use the LB for request authentication, so that not everyone on the network can access the neo4j server. In my use case, I think making the base uri configurable (including the protocol, e.g. https://foobar.com/) is enough. There are a couple other approaches that

Re: [Neo4j] REST API Base URI

Nuo, right now the server is discovering its own IP upon startup. However, it sounds reasonable to return configurable base URL. I am just wondering if that really is enough to support a LB scenario? Do you need more stuff there? Cheers, /peter neubauer GTalk:      neubauer.peter Skype       pet

[Neo4j] REST API Base URI

I access my neo4j server through the REST API. For security purpose, I put the neo4j server behind a nginx lb. I'm wondering if there is config entry somewhere that I can set the neo4j server to return a customized base uri that I can set to my LB's uri. For example, currently creating a node by P

Re: [Neo4j] REST API: errors should always be JSON, not HTML

Pushed and fixed. Nite. 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

Re: [Neo4j] REST API: errors should always be JSON, not HTML

Thanks! 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://startup

Re: [Neo4j] REST API: errors should always be JSON, not HTML

https://github.com/neo4j/community/issues/13 Cheers, Aseem On Wed, Sep 7, 2011 at 11:57 AM, Aseem Kishore wrote: > Sure, Peter. Sorry I haven't done this yet for other issues I've reported! > > Aseem > > > On Wed, Sep 7, 2011 at 11:42 AM, Peter Neubauer < > peter.neuba...@neotechnology.com> wrot

Re: [Neo4j] REST API: errors should always be JSON, not HTML

Sure, Peter. Sorry I haven't done this yet for other issues I've reported! Aseem On Wed, Sep 7, 2011 at 11:42 AM, Peter Neubauer < peter.neuba...@neotechnology.com> wrote: > Aseem, > > do you care to raise an issue at > > https://github.com/neo4j/community/issues?sort=created&direction=desc&stat

Re: [Neo4j] REST API: errors should always be JSON, not HTML

Aseem, do you care to raise an issue at https://github.com/neo4j/community/issues?sort=created&direction=desc&state=openfor this? I understand - this sounds valid. Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.link

Re: [Neo4j] REST API: errors should always be JSON, not HTML

Hey Peter, sorry for not being totally clear. It should indeed be an *HTTP* error, e.g. 400 or whatever. The problem is that the *body* is HTML when it should be JSON. That is, you should see a bunch of HTML tags in the body, instead of a simple {error: ..., stacktrace: ...} object. Cheers, Aseem

Re: [Neo4j] REST API: errors should always be JSON, not HTML

Aseem, is this still relevant? I get the HTTP error with POST /db/data/ext/CypherPlugin/graphdb/execute_query {"query": "START n=(0) RETURN n.foobar"} Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/n

Re: [Neo4j] REST API: output respresentation and performance

Oleg, for an example of this, see http://docs.neo4j.org/chunked/snapshot/gremlin-plugin.html#rest-api-send-a-gremlin-script---json-encoded-with-table-resultswhere the returned table does not contain nodes or relationships, but only properties, this resulting in _MUCH_ smaller return values, doing m

[Neo4j] REST API: errors should always be JSON, not HTML

Hey, Just ran into an HTML error response which broke our error handling code since it was expecting the body to be JSON. It seems to only happen with the Cypher plugin. Here's a simple repro -- just paste this into the HTTP console in the web admin: POST /db/data/ext/CypherPlugin/graphdb/execute

Re: [Neo4j] REST API: output respresentation and performance

Hi, > - Data transfer bottleneck. Returning a large set of nodes/relationships > from a Gremlin query with Json might result in excesive result size. We > transfer from hundreds to 100.000 entities. In our case, we only need to > obtain a single property value (or just a few properties) for each >

[Neo4j] REST API: output respresentation and performance

Hi guys, We are developing an analytics server on top of Neo4j REST API. We use Neo4j 1.4.1. Our general experience is good, you are doing a great job! In our project we make a number of Gremlin/Cypher queries and some traversal calls via REST API. However, we have experienced some data

Re: [Neo4j] REST API paging: specify sorting? and for index results?

Thanks Michael. On Thu, Jul 14, 2011 at 2:21 AM, Michael Hunger < michael.hun...@neotechnology.com> wrote: > They will in 1.5 > > and using lucene query syntax you can probably sort them. > > Michael > > mobile mail please excuse brevity and typos > > Am 14.07.2011 um 07:49 schrieb Aseem Kishore

Re: [Neo4j] REST API paging: specify sorting? and for index results?

They will in 1.5 and using lucene query syntax you can probably sort them. Michael mobile mail please excuse brevity and typos Am 14.07.2011 um 07:49 schrieb Aseem Kishore : > Okay, thanks for explaining. > > Would still love an answer to whether index results will support paging or > not. =)

Re: [Neo4j] REST API paging: specify sorting? and for index results?

Okay, thanks for explaining. Would still love an answer to whether index results will support paging or not. =) Thanks! Aseem On Thu, Jul 14, 2011 at 1:23 AM, Jim Webber wrote: > Hi Aseem, > > I think in that case it's non-deterministic - which means you page until > you have enough results. >

Re: [Neo4j] REST API paging: specify sorting? and for index results?

Hi Aseem, I think in that case it's non-deterministic - which means you page until you have enough results. Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user

Re: [Neo4j] REST API paging: specify sorting? and for index results?

Sorry for not being clear -- I meant when the sorting isn't constrained by the algorithm or traverse parameters. A simple example is a social network, and you want to get a person's friends. This would be a breadth-first search of depth 1 for one relationship type (FOLLOWS/FRIEND/whatever). How wi

Re: [Neo4j] REST API paging: specify sorting? and for index results?

Hi Aseem, [snip] > What's the default sorting based on, then? Is it unspecified? I think it > would be helpful to at least know, to help is in design. At the most basic level, it can be down to whether you're doing a depth- or breadth-first search. It will be influenced by the relationship type

Re: [Neo4j] REST API paging: specify sorting? and for index results?

Hey, that totally makes sense. No worries about disappointing. =) What's the default sorting based on, then? Is it unspecified? I think it would be helpful to at least know, to help is in design. Cheers, Aseem On Wed, Jul 13, 2011 at 7:06 PM, Jim Webber wrote: > Hi Aseem, > > The paged travers

Re: [Neo4j] REST API paging: specify sorting? and for index results?

Hi Aseem, The paged traversers in the REST API don't support sorting, and probably never will do. Here's why: In order to sort, we need a set of results to sort. If we're going to have a completely sorted result set, we need a complete set of results which may be large. The irony is, even as

[Neo4j] REST API paging: specify sorting? and for index results?

It's great to hear that traverse results over the REST API will now support paging in Neo4j 1.4. But we were wondering: will you be able to specify the sorting to determine which results are returned first? E.g. suppose I have a node for "me", and I "follow" a bunch of other people. To get a list

Re: [Neo4j] REST API & LuceneTimeline

> > "fields" : [ > > >{ > > > "key" : "key1" > > > "value" : 12345 > > >}, > > >{ > > > "key" : "key2" > > > &qu

Re: [Neo4j] REST API & LuceneTimeline

ot; > > "value" : "ABC" > >}, > >{ > > "key" : "key3" > > "value" : [ "Dogs", "Cats", "Sheep" ] > >} > > ] > > } > &

Re: [Neo4j] Rest API in the future

http://docs.neo4j.org/chunked/snapshot/rest-api-batch-ops.html 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              

Re: [Neo4j] Rest API in the future

2011/6/19 Jim Webber > Hello Aniceto, > > > - EmbeddedGraphDatabase, which is good for tests, supports transactions > > and has quick communications. Not good for medium sized or HA apps > > because lacks separation between app and data > > The EmbeddedGraphDatabase is fine for production use - i

Re: [Neo4j] Rest API in the future

Hello Aniceto, > - EmbeddedGraphDatabase, which is good for tests, supports transactions > and has quick communications. Not good for medium sized or HA apps > because lacks separation between app and data The EmbeddedGraphDatabase is fine for production use - in fact it's the default choice!

[Neo4j] Rest API in the future

I have downloaded neo4-rest-graphdb, a rest wrapper for Java. README file says this interface does not support transactions. So we have: - EmbeddedGraphDatabase, which is good for tests, supports transactions and has quick communications. Not good for medium sized or HA apps because lacks separ

Re: [Neo4j] REST API & LuceneTimeline

t; "value" : 12345 >}, >{ > "key" : "key2" > "value" : "ABC" >}, >{ > "key" : "key3" > "value" : [ "Dogs", "Cats"

Re: [Neo4j] REST API & LuceneTimeline

s Lucene query syntax, you can >> use something like: >> >> timestamp : [1 to 2] >> >> You'd need to do the Date <-> UTC milliseconds conversion on the front end, >> I'd think. >> >> Rick >> >> ---

Re: [Neo4j] REST API & LuceneTimeline

illiseconds conversion on the front end, > I'd think. > > Rick > > -Original Message- > From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On > Behalf Of Matt Luongo > Sent: Wednesday, June 15, 2011 10:03 AM > To: Peter Neubauer

Re: [Neo4j] REST API & LuceneTimeline

, >> I'd think. >> >> Rick >> >> -Original Message- >> From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On >> Behalf Of Matt Luongo >> Sent: Wednesday, June 15, 2011 10:03 AM >> To: Peter Neubauer >> Cc: user@

Re: [Neo4j] REST API & LuceneTimeline

nds conversion on the front end, I'd think. Rick -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Matt Luongo Sent: Wednesday, June 15, 2011 10:03 AM To: Peter Neubauer Cc: user@lists.neo4j.org Subject: Re: [Neo4j] REST API &

Re: [Neo4j] REST API & LuceneTimeline

t;> On Wed, Jun 15, 2011 at 8:55 AM, Rick Bullotta >> wrote: >>> >>> You really don't need a timeline index to do a timeline index, if that >>> makes sense.  As mattias points out, it is just a convenient wrapper around >>> a plain lucene (neo) ind

Re: [Neo4j] REST API & LuceneTimeline

ly > > > On Wed, Jun 15, 2011 at 8:55 AM, Rick Bullotta > wrote: >> >> You really don't need a timeline index to do a timeline index, if that makes >> sense.  As mattias points out, it is just a convenient wrapper around a >> plain lucene (neo) index.  Just

Re: [Neo4j] REST API & LuceneTimeline

t need a timeline index to do a timeline index, if that makes >> sense.  As mattias points out, it is just a convenient wrapper around a >> plain lucene (neo) index.  Just index the timestamp as a numeric field. >> >> >> >> - Reply message - >> From: "

Re: [Neo4j] REST API & LuceneTimeline

sage - > From: "Matt Luongo" > Date: Wed, Jun 15, 2011 8:48 am > Subject: [Neo4j] REST API & LuceneTimeline > To: "Neo4j user discussions" > > Peter, > > I've done a bit more research, and you're right- it isn't. However, the REST >

Re: [Neo4j] REST API & LuceneTimeline

ta wrote: > > You really don't need a timeline index to do a timeline index, if that makes > sense.  As mattias points out, it is just a convenient wrapper around a plain > lucene (neo) index.  Just index the timestamp as a numeric field. > > > > - Reply mess

Re: [Neo4j] REST API & LuceneTimeline

Jun 15, 2011 8:48 am Subject: [Neo4j] REST API & LuceneTimeline To: "Neo4j user discussions" Peter, I've done a bit more research, and you're right- it isn't. However, the REST api let's me create an index of type 'timeline'. The first time I try to

Re: [Neo4j] REST API & LuceneTimeline

Peter, I've done a bit more research, and you're right- it isn't. However, the REST api let's me create an index of type 'timeline'. The first time I try to index a node, there's a 500 error (nullpointer) that stems from the index not being created. I'd be happy to file a bug report. Anyway, we'r

Re: [Neo4j] REST API & LuceneTimeline

Matt, what URL are you using to create the timeline? I don't recall that being exposed via REST ... Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 LinkedIn   http://www.linkedin.com/in/neubauer Twitter      http://twitter.com/peterneubaue

[Neo4j] REST API & LuceneTimeline

Forgive me if this is a foolish question. I'm really excited about using the LuceneTimeline in our product. I see that I can create it via "type":"timeline" in the REST interface. I'm not sure, though, how to add nodes to the timeline- it seems like you add things to a timeline by specifying just a

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

ay 11, 2011 at 8:01 AM, Rick Bullotta > > wrote: > > > >> I think you have to still do it over HTTP *in addition* to any other > >> transport, if for no other reason than the ubiquity of HTTP-capable > client > >> applications/platforms/languages. That said, I&#x

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

ot;time to live". >> >> -Original Message- >> From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] >> On Behalf Of Jacob Hansson >> Sent: Wednesday, May 11, 2011 10:58 AM >> To: Neo4j user discussions >> Subject: Re: [Neo

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

mailto:user-boun...@lists.neo4j.org] > On Behalf Of Jacob Hansson > Sent: Wednesday, May 11, 2011 10:58 AM > To: Neo4j user discussions > Subject: Re: [Neo4j] REST API (optimistic or transactional) concurrency? > > We started discussing how an implementation would look, but bumped into

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

me to live". -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Jacob Hansson Sent: Wednesday, May 11, 2011 10:58 AM To: Neo4j user discussions Subject: Re: [Neo4j] REST API (optimistic or transactional) concurrency? We started discussing how an

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

We started discussing how an implementation would look, but bumped into problems. The plan was to look at potentially adding a restful transaction API, something like "create a transaction context resource via a POST, and then work with the database "via" that context resource, commiting/aborting

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

Just wanted to ask: how'd the lab day go last Friday? Any updates on this? =) Cheers, Aseem On Thu, May 5, 2011 at 7:42 AM, Mattias Persson wrote: > 2011/5/5 Aseem Kishore > > > Yes, great points. > > > > I've worked a good deal with Microsoft's cloud NoSQL DB, Windows Azure > > Table > > Stora

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

2011/5/5 Aseem Kishore > Yes, great points. > > I've worked a good deal with Microsoft's cloud NoSQL DB, Windows Azure > Table > Storage, and for what it's worth, I thought they solved this problem very > elegantly. That API is entirely REST-based, and they use HTTP If-Match / > If-Modified-Since

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

Yes, great points. I've worked a good deal with Microsoft's cloud NoSQL DB, Windows Azure Table Storage, and for what it's worth, I thought they solved this problem very elegantly. That API is entirely REST-based, and they use HTTP If-Match / If-Modified-Since headers to achieve conditional reques

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

Assem, I agree. The problem is not the database API IMHO, but the mismatching semantics of HTTP REST and transactional DB APIs, and the balancing of shoving over work to the database server via server side processing scripting or plugins and client side operations via HTTP. Let's see if we can come

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

Thanks Peter. Looking forward to seeing what you guys come up with! Dima, thanks for the tip. It would be nice to not to have to write a custom plugin for what's arguably a pretty fundamental need from database APIs. =) Aseem On Wed, May 4, 2011 at 2:05 PM, Peter Neubauer < peter.neuba...@neotec

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

Guys, Friday is labday, so we there are tentative plans to sketch on some transactional semantics in the REST API and circle back to the list on that. Let's see how it goes! Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 LinkedIn   http:/

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

You should implement your own plugin/component on the standalone neo4j server and expose you own API that makes batch operations. Regards, Dima Gutzeit. Sent from my iPhone On 4 במאי 2011, at 21:56, Aseem Kishore wrote: > Re-sending in the hopes that someone has answers to or thoughts on this.

Re: [Neo4j] REST API (optimistic or transactional) concurrency?

Re-sending in the hopes that someone has answers to or thoughts on this. =) Aseem On Mon, May 2, 2011 at 4:16 PM, Aseem Kishore wrote: > Hi there, > > If we're using Neo4j purely over REST, do we have any means to protect > against concurrency? The REST API appears to expose neither transactions

[Neo4j] REST API (optimistic or transactional) concurrency?

Hi there, If we're using Neo4j purely over REST, do we have any means to protect against concurrency? The REST API appears to expose neither transactions nor optimistic concurrency. Here's a simple example: we have nodes representing users, and users have a "username" property that we index. When

Re: [Neo4j] REST API thoughts/questions/feedback

On Tue, Apr 19, 2011 at 10:48 AM, Jacob Hansson wrote: > Hey Michael, big thanks again for taking the time to write down your > experiences working with the REST API. > > See inline response. Thanks for the follow up. That's quite helpful and let's me know I'm not doing the unique-key-implementa

Re: [Neo4j] REST API thoughts/questions/feedback

Hey Michael, big thanks again for taking the time to write down your experiences working with the REST API. See inline response. On Mon, Apr 18, 2011 at 4:10 PM, Michael DeHaan wrote: > Hi all. > > I've been working recently on writing a Perl binding for the Neo4j > REST AP

[Neo4j] REST API thoughts/questions/feedback

Hi all. I've been working recently on writing a Perl binding for the Neo4j REST API and thought I'd share some observations, and hopefully can get a few suggestions on some things. You can see some of the Perl work in progress here -- https://github.com/mpdehaan/Elevator (search fo

Re: [Neo4j] Neo4j REST API and JAXB

Cool, will rebase my fork and check it out as soon as I am not officially on parental leave anymore ;) Cheers, /peter neubauer GTalk:      neubauer.peter Skype       peter.neubauer Phone       +46 704 106975 LinkedIn   http://www.linkedin.com/in/neubauer Twitter      http://twitter.com/peterneub

Re: [Neo4j] Neo4j REST API and JAXB

I see ... You can use val anyRef = "/index/node".GET[AnyRef] in this case anyRef.toString returns: {index2={template= http://localhost:7474/db/data/index/node/index2/{key}/{value}, provider=lucene, type=fulltext}, my_nodes={template= http://localhost:7474/db/data/index/node/my_nodes/{key}/{valu

Re: [Neo4j] Neo4j REST API and JAXB

Yeah, that sounds good. However, in the Index listing case, there is no top-level key to pass into the class, sine alrady the root-level index names are unpredictable. Is that possible to cover, too? In the extensions case, there is at least the "extensions" handle to pass in, even if we don't know

Re: [Neo4j] Neo4j REST API and JAXB

Same as GET http://localhost:7474/db/data/ where I can not predict the extensions parameter. I used the simple data binding (see here). Means that the parameter is of type Any case class GetRoot( . . . @BeanProperty var extensions:Any) { . . . } Jac

Re: [Neo4j] Neo4j REST API and JAXB

Christopher, my problem is with the names of the index representations being able to contain whatever, so the Scala case class can't assume a parameter name. look at the result of an index creation and listing: curl -X POST -H Accept:application/json -HContent-Type:application/jon -d '{"name":"in

Re: [Neo4j] Neo4j REST API and JAXB

Happy new year Peter, I did that already in my repo and added as well an example to use polymorphic "*node classes"* (using Scala's case classes, see here ). Christopher On Sat, Jan 1, 201

Re: [Neo4j] Neo4j REST API and JAXB

Christopher, Happy New Year! I tried to fork and adapt the code to reflect the updated REST API, but the variable index listing under /db/data/index/node is too hard for my Scala skillz ... Feel free to pull, diff and correct :) /Peter On Wednesday, December 29, 2010, Christopher Schmidt wrote:

  1   2   >