Mark Roth wrote: > I'm still early on in my project, so this is not in response to a problem. > > I'm concerned about latency of response - when I add an entry to the > triplestore, I'd like the LARQ index to process it right away. However, I'd > like several indexers, each running on different machines, and so I need to > notify them of what changed. It would be convenient if they could just be > pinged and they would retrieve the new triples to index from the datastore, > but if I can leverage any existing infrastructure to do this then I don't > need to write such functionality myself.
Hi Mark, thanks for sharing your user needs, it's useful. Apache Jena does not have such functionality out-of-the-box for several indexers. May I ask you why you want several indexes running on different machines? While ago, building on LARQ design and approach and trying to explore possible ways to refactor LARQ's code to make it easier plug-in different indexing systems, I wrote SARQ (it uses Apache Solr) and EARQ (it uses ElasticSearch... and the code has been refactored), they are just prototypes but, you might find them useful, have a look and let me know: - https://github.com/castagna/SARQ - https://github.com/castagna/EARQ Apache Solr can be configured in master/slave mode and Solr Cloud is probably coming. ElasticSearch has been distributed since the beginning. Paolo > > - Mark
