You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, we often think 1.0 == 100%. Shouldn't it use ">" instead of ">="?
(By doing that, we won't be able to use min=1 as absolute number but it doesn't have any effect anyway)
In any case, adding document on this threshold would help.
The text was updated successfully, but these errors were encountered:
According to document, max/min values can be specified as absolute number or percentage.
And according to this https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/index/fielddata/plain/AbstractIndexOrdinalsFieldData.java#L118
, if a number is >= 1.0, it's considered as absolute number.
However, we often think 1.0 == 100%. Shouldn't it use ">" instead of ">="?
(By doing that, we won't be able to use min=1 as absolute number but it doesn't have any effect anyway)
In any case, adding document on this threshold would help.
The text was updated successfully, but these errors were encountered: