Thanks, Eugeny! On Tuesday, June 28, 2016 at 4:59:58 PM UTC+5:30, [email protected] wrote: > > HI Aparna! > > *tl;dr:* Yes, ELASTIC_FIELD_MAPPINGS provide fine tuning capabilities - > you don't need to set them if you don't know what you're doing. > > Details: it is used in edx-search to specify ElasticSearch mapping for an > index > <https://github.com/edx/edx-search/blob/881e772aba8e92504acbcefab0b07d7531f845fc/search/elastic.py#L279-289> > > - it allows fine tuning the way ElasticSearch indexes the data. Default > mappings are less than ideal, but work. And unless you've got someone at > least roughly familiar with what ElasticSearch mappings are, you don't want > to change them as it might result in broken or malfunctioning search. > > Regards, > Eugeny > @Opencraft <http://opencraft.com> > > On Tuesday, June 14, 2016 at 8:20:23 AM UTC+3, Aparna P wrote: >> >> Hi all! >> >> For enabling course search, the documentation says to set >> ELASTIC_FIELD_MAPPINGS together with other fields like SEARCH_ENGINE and >> ENABLE_COURSEWARE_INDEX. >> >> But we found that even if ELASTIC_FIELD_MAPPINGS is not set, course >> search works just fine. So the question is : is ELASTIC_FIELD_MAPPINGS >> obsolete or does it provide some fine tuning to the search feature? >> >> Thanks, >> Aparna >> >>
-- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/beadbe9d-1b76-4c11-a3b8-d096056f8b2b%40googlegroups.com.
