Hi Ivan,
(P.S.: I am one of the developer of the SIREn plugin)
it would be possible for SIREn to support such functionality (but it is not
yet implemented), as each element / node in the tree as a unique identifier
that is retrieved at search time. Therefore, one could use this identifier
to
Hi Brian,
Our apologies for the issues with the web site, we had some problems on our
web server yesterday.
What you have described is very close to the indexing model in SIREn. SIREn
provides an optimised Lucene's Codec for such data structure, and provide
query operators on top of this
Thanks for chiming in Renaud. Hopefully I will have a chance to test out
the plugin soon. My use case for nested documents is fairly simple.
--
Ivan
On Thu, Jul 24, 2014 at 4:00 AM, ren...@sindicetech.com wrote:
Hi Brian,
Our apologies for the issues with the web site, we had some problems
Has anyone else seen this plugin? http://siren.solutions/siren/overview/
There was some discussion between one of the developers and Jorg a while
back, so I guess this is the outcome. Have not tried it yet, but I will
give it a shot this weekend. I am hoping that it can fix a longstanding
issue
I noticed Siren has an example of 1000 library catalog records from British
Library prepared in JSON
https://github.com/sindicetech/siren/blob/master/siren-elasticsearch-demo/src/example/datasets/bnb/
From what it seems, Siren can index a tree (semi-structured data), using
positional nodes, then
Thanks for the link. Unfortunately, Chrome on Mac OS (latest versions of
each) causes this web page to blank and redisplay continually. Can't read
it; hope you can.
In a previous life, I created a search engine that handled parent/child
relationships with blindingly fast performance. One trick
