Solutions for when a sort field doesn't exist in the mapping


(Bryan Green) #1

Hiya,

When a field cannot be found in the mapping during the sort operation,
is there a way to have the system not throw an exception? It would be
nice if the field at fault is ignored from the sort fields.

Is the only other option to: pull the mappings for the item in the
particular index, see if the field exists or not, then tailor the
search statement?

Thank you for your time,
Bryan Green


(Bryan Green) #2

Sorry to reply to my own post...

I can turn down the log4j level from DEBUG to WARN as a "solution" but
I'd like to see if I can have this cleaned up via elasticsearch and
not have to make additional calls from my end.

Have a great weekend.
Bryan

On Dec 10, 12:41 pm, Bryan Green bryogr...@gmail.com wrote:

Hiya,

When a field cannot be found in the mapping during the sort operation,
is there a way to have the system not throw an exception? It would be
nice if the field at fault is ignored from the sort fields.

Is the only other option to: pull the mappings for the item in the
particular index, see if the field exists or not, then tailor the
search statement?

Thank you for your time,
Bryan Green


(Shay Banon) #3

Tuning the logging won't help, since it still won't search on those shards
/ indices where that field does not exists. It might be possible (might get
tricky when doing the "reduce" part of the search) to ignore fields that do
not exists, but open an issue, it might be possible.

On Sat, Dec 10, 2011 at 8:49 PM, Bryan Green bryogreen@gmail.com wrote:

Sorry to reply to my own post...

I can turn down the log4j level from DEBUG to WARN as a "solution" but
I'd like to see if I can have this cleaned up via elasticsearch and
not have to make additional calls from my end.

Have a great weekend.
Bryan

On Dec 10, 12:41 pm, Bryan Green bryogr...@gmail.com wrote:

Hiya,

When a field cannot be found in the mapping during the sort operation,
is there a way to have the system not throw an exception? It would be
nice if the field at fault is ignored from the sort fields.

Is the only other option to: pull the mappings for the item in the
particular index, see if the field exists or not, then tailor the
search statement?

Thank you for your time,
Bryan Green


(system) #4