David,
Yes. Document grouping (aka field collapsing) will help you here. It
should also allow you to create a better search experience on the front end
- it's often better to narrow down where in a large document a match is
than give users a large doc and say: we know the match is in here
somewhe
OK. Then the JSON returned would contain a lot of documents that are
really sections. This would work fine for the use-case I mentioned but I
also use the index for full-text search of the whole document. Therefore,
I would need to parse the result JSON in a way that combines the solr docs
return
Hi David,
A separate Solr document for each section is a good option if you also need
to handle phrases, case, special characters, etc. within the title field.
How do you map them to dynamic fields?
E.g.: "Appendix for cities", "APPENDIX 1: Cities"
Regards,
Aloke
On Wed, Oct 9, 2013 at 9:45 AM
I'd suggest that each of your source document sections would be a distinct
solr document. All of the sections could have a "source document ID" field
to tie them together.
Dynamic fields work best when used in moderation. Your use case seems like
an excessive use of dynamic fields.
-- Jack K