Error while configuring settings
-
priyanka_kethireddyParticipant# 1 month ago
Hello Team,
While we are configuring solr in one of our sites we are getting below error{“error”:{“root_cause”:[{“type”:”illegal_argument_exception”,”reason”:”Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [type] in order to load field data by uninverting the inverted index. Note that this can use significant memory.”}],”type”:”search_phase_execution_exception”,”reason”:”all shards failed”,”phase”:”query”,”grouped”:true,”failed_shards”:[{“shard”:0,”index”:”sitename_live”,”node”:””,”reason”:{“type”:”illegal_argument_exception”,”reason”:”Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [type] in order to load field data by uninverting the inverted index. Note that this can use significant memory.”}}],”caused_by”:{“type”:”illegal_argument_exception”,”reason”:”Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [type] in order to load field data by uninverting the inverted index. Note that this can use significant memory.”,”caused_by”:{“type”:”illegal_argument_exception”,”reason”:”Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [type] in order to load field data by uninverting the inverted index. Note that this can use significant memory.”}}},”status”:400}
priyanka_kethireddyParticipant# 1 month agoIt was little bit confusing, because we are using same settings for all sites, those are working fine, only in one site we are getting this error.
You must be logged in to reply to this topic.