It took quite a bit of figuring out but we succeeded registering a rootMapper and using the ParseContext, thanks.
We don't have any plans for implementing SPARQL on top of ElasticSearch. Siren can do joins which perform better than blockjoins, especially for deep nesting, but it still is a different paradigm. On the other hand, we are always interested in new use cases. We've done work on indexing richly structured documents with lots of structure and lots of text content too and querying where you need to combine querying structure and text. Maybe that is something relevant to library catalog indexing? In any case, I'd be happy to hear more if you want to reply offline. Jakub On Friday, May 23, 2014 8:00:51 PM UTC+1, Jörg Prante wrote: > > Do you plan to implement SPARQL endpoint on Elasticsearch? > > That would be one wonderful asset missing in my portfolio for supporting > library catalog indexing and search, all I do with RDF and Elasticsearch is > based on JSON-LD. > > Jörg > > > On Fri, May 23, 2014 at 8:17 PM, Jakub Kotowski > <[email protected]<javascript:> > > wrote: > >> Great, the ParseContext looks promising. >> >> We'll try it and report back, thanks! >> >> Jakub >> >> BTW, just to answer your previous implicit question - SIREn allows for >> advanced structured document search, more at http://sirendb.com/ >> >> >> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e4168857-a854-4119-abae-58d4cbbbaf1a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
