https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42835 --- Comment #77 from David Cook <dcook@prosentient.com.au> --- At the moment, I'm in the process of indexing tens/hundreds of millions of rows of non-Koha data into Elasticsearch, but it's a fairly straight forward de-normalised JSON document for each row, so not the same use case at all, but it'll be interesting from a performance perspective... -- Looking again at parent-join it says: "The only case where the join field makes sense is if your data contains a one-to-many relationship where one entity significantly outnumbers the other entity. An example of such case is a use case with products and offers for these products. In the case that offers significantly outnumbers the number of products then it makes sense to model the product as parent document and the offer as child document." Hmm tricky... that does seem to describe the biblio to item model... -- You are receiving this mail because: You are watching all bug changes.