Alexander Dutton wrote: > Hi Glenn, > > On 06/03/12 09:57, Glenn Proctor wrote: >> On Tue, Mar 6, 2012 at 9:49 AM, Paolo Castagna wrote: >> >>> A completely different alternative would be to use something such as >>> Apache Solr or ElasticSearch along side your TDB store, they both >>> support facet searches (and they can be quite fast): […] >> Thanks Paulo - caching is indeed the next thing on the list to look at >> :) I hadn't considered the Solr approach, but will do so. > > This is the way we're going with our site, data.ox.ac.uk. After each > update to the triplestore we'll regenerate an ElasticSearch index from a > SPARQL query. It won't quite be real time, but should be good enough for > our purposes. From the small amount of playing around with ElasticSearch > I've done, it seems to 'Just Work'.
Hi Alex, interesting... How do you update your triplestore (SPARQL Update, Jena APIs via custom code, manually from command line, ...)? We (still) have two related JIRA 'issues': - LARQ needs to update the Lucene index when a SPARQL Update request is received https://issues.apache.org/jira/browse/JENA-164 - Refactor LARQ so that it becomes easy to plug in different indexes such as Solr or ElasticSearch instead of Lucene https://issues.apache.org/jira/browse/JENA-17 I am still unclear how to intercept all the possible update routes (i.e. SPARQL Update, APIs, bulk loaders, etc...). But, I think it would be useful to allow people to use Apache Solr and/or ElasticSearch indexes (and/or other custom indexes) and keep those up-to- date when changes come in. What do you store in ElasticSearch? Paolo > > I learnt about it from these people: > http://cottagelabs.com/indexing-elastic-search-workshop-from-dev8d/. > They've also got some JavaScript for faceted interfaces in > https://github.com/CottageLabs/edjo and > https://github.com/okfn/bibserver (the latter of which powers > http://bibsoup.net/kcoyle/publications_karen_coyle). I'm not sure how > repurposable it is… > > All the best, > > Alex
