Yes, we have some code running, currently with the two pluggable storage providers being Neo native & file system, with Amazon S3 under construction. We haven't done anything for replication yet, though. The model is fairly simple, with a neo node maintaining two properties + one optional property. The two properties are storageProvider and storageKey. The storageProvider property is used to create a provider via a storage provider factory, and this provider (implementing IStorageProvider) handles store, retrieve, storeFromStream, retrieveAsStream, and remove methods. The neo node also has an optional property, mimeType, which is used to set the web response type when retrieving/streaming content.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Peter Neubauer Sent: Saturday, January 22, 2011 3:33 AM To: Neo4j user discussions Subject: Re: [Neo4j] Roadmap updated - Blob/document storage idea? Rick, Sounds like a perfect match! There are a number of other things around transactional datasources that want to integrate tightly with the e.g. Indexing frameworks, such as endogenous indexes in the graph. So, I think looking into wrapping eventually consistent datasources and graph based datasources would alsobe a good activity leading up to your scenario. Let's talk more about how this could look in practice. Got any example code running yet? /peter On Friday, January 21, 2011, Rick Bullotta <[email protected]> wrote: > Hi, all. > > Since it has been a frequent topic of conversation recently, I'd like to get > a roadmap dialog started on the topic of a companion blob/document store for > Neo. While there are plenty of ways to "roll our own", it requires a lot of > extra effort when we get into HA and load balanced scenarios. While it > might not make sense to use the existing storage model in Neo for big > strings/blobs, I am quite confident that it would be fairly easy to create a > file-system-based storage mechanism with eventually consistent replication > that is tightly integrated with Neo (which, of course, could be pluggable to > allow integrating stores such as Amazon S3, Mongo, Jackrabbit, etc.). > > It would be very easy to create a generic pattern for "blob" properties > which would internally maintain the logical storage system ID (as mentioned > in the previous sentence) and the unique key/ID in that store. Property > storage/retrieval could be transparently delegated to the the blob storage > provider, again, with file-system-based as the default/built-in. > Additionally, the replication and online backup infrastructure would be > aware of this and, in the case of the built-in file system store would take > care of the replication, and in the case of others, would simply replicate > the references or maybe even delegate to the storage provider > extension/plug-in to let it decide how to handle it. > > Rick > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Peter Neubauer > Sent: Friday, January 21, 2011 4:05 AM > To: Neo4j user discussions > Subject: Re: [Neo4j] Roadmap updated > > Oh, > btw, the roadmap document is at http://wiki.neo4j.org/content/Roadmap > > 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://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. > > > > On Fri, Jan 21, 2011 at 10:04 AM, Peter Neubauer > <[email protected]> wrote: >> Hi all, >> the roadmap document is now updated for 1.3.M1. We are struggling to >> get a better setup between trac.neo4j.org, the Neo Technology user >> stories and other issue tracking needs, so that the whole process is >> more transparent and open for more participation. Please bear with us >> while figuring out how to set this up. The roadmap are just the very >> high order bits, for details, for the commits, look at subscribing to >> https://lists.neo4j.org/mailman/listinfo/commits . >> >> 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://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. >> > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
