Re: Nested documents vs. flattening document structure?
Thank you Erick. That was my instinct as well. On Tue, Mar 6, 2018 at 10:05 AM, Erick Ericksonwrote: > Flattening the nested documents is usually preferred if at all > possible. Nested documents to, indeed, have a series of restrictions > that often make them harder to work with than flattened docs. > > Best, > Erick > > On Tue, Mar 6, 2018 at 6:48 AM, Dc Tech wrote: > > We are evaluating using nested documents vs. simply flattening the > document. > > > > Looking through the documentation, it is not very clear to me if the > nested > > documents are fully mature, and support the full richness of SOLR > > (streaming, mature faceting) etc... > > > > Any opinions or guidance on that? > > > > > > For *flattening*, we are thinking of setting up three groups of fields: > > 1. Fields for search - 3-4 groups of fields that glom together the > document > > fields in order of boosting priority (e.g. f1 has just the title , f2 has > > title+authors) > > 2. Fields for faceting if needed > > 3. and Fields for display (or the original document fields) e.g. > > author_name|author_unique_id... >
Re: Nested documents vs. flattening document structure?
Flattening the nested documents is usually preferred if at all possible. Nested documents to, indeed, have a series of restrictions that often make them harder to work with than flattened docs. Best, Erick On Tue, Mar 6, 2018 at 6:48 AM, Dc Techwrote: > We are evaluating using nested documents vs. simply flattening the document. > > Looking through the documentation, it is not very clear to me if the nested > documents are fully mature, and support the full richness of SOLR > (streaming, mature faceting) etc... > > Any opinions or guidance on that? > > > For *flattening*, we are thinking of setting up three groups of fields: > 1. Fields for search - 3-4 groups of fields that glom together the document > fields in order of boosting priority (e.g. f1 has just the title , f2 has > title+authors) > 2. Fields for faceting if needed > 3. and Fields for display (or the original document fields) e.g. > author_name|author_unique_id...
Nested documents vs. flattening document structure?
We are evaluating using nested documents vs. simply flattening the document. Looking through the documentation, it is not very clear to me if the nested documents are fully mature, and support the full richness of SOLR (streaming, mature faceting) etc... Any opinions or guidance on that? For *flattening*, we are thinking of setting up three groups of fields: 1. Fields for search - 3-4 groups of fields that glom together the document fields in order of boosting priority (e.g. f1 has just the title , f2 has title+authors) 2. Fields for faceting if needed 3. and Fields for display (or the original document fields) e.g. author_name|author_unique_id...