Elastic filter changes ordering












0















This query returns results well ordered:



GET <index>/_search
{
"query": {
"bool": {
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


How to add a filter to to remove entries outside of certain dates? Tried this:



GET <index>/_search
{
"query": {
"bool": {
"filter": [
{
"range": {
"date": {
"gte": "2008-01-01 00:00:00"
}
}
}
],
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


However the order is now ruined with worse matches up front. Even more, it seems valid entries are not here anymore?



Checks:




  • date is indeed indexed as a date

  • a post_filter returns the same result

  • adding the filter in the must returns the same result

  • the filter alone works correctly


What to do?










share|improve this question


















  • 1





    Could you add an example of a document that is filtered out and which should not? Plus the ordering in your query is based on the score and your filter will not change the score for matching documents. So the filter doesn't change the ordering it's just that it changes the ordered result set. Could you then explain to us what is a "well-ordered result set" for you? We need a concrete example to help you

    – Pierre Mallet
    Jan 18 at 16:11
















0















This query returns results well ordered:



GET <index>/_search
{
"query": {
"bool": {
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


How to add a filter to to remove entries outside of certain dates? Tried this:



GET <index>/_search
{
"query": {
"bool": {
"filter": [
{
"range": {
"date": {
"gte": "2008-01-01 00:00:00"
}
}
}
],
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


However the order is now ruined with worse matches up front. Even more, it seems valid entries are not here anymore?



Checks:




  • date is indeed indexed as a date

  • a post_filter returns the same result

  • adding the filter in the must returns the same result

  • the filter alone works correctly


What to do?










share|improve this question


















  • 1





    Could you add an example of a document that is filtered out and which should not? Plus the ordering in your query is based on the score and your filter will not change the score for matching documents. So the filter doesn't change the ordering it's just that it changes the ordered result set. Could you then explain to us what is a "well-ordered result set" for you? We need a concrete example to help you

    – Pierre Mallet
    Jan 18 at 16:11














0












0








0








This query returns results well ordered:



GET <index>/_search
{
"query": {
"bool": {
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


How to add a filter to to remove entries outside of certain dates? Tried this:



GET <index>/_search
{
"query": {
"bool": {
"filter": [
{
"range": {
"date": {
"gte": "2008-01-01 00:00:00"
}
}
}
],
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


However the order is now ruined with worse matches up front. Even more, it seems valid entries are not here anymore?



Checks:




  • date is indeed indexed as a date

  • a post_filter returns the same result

  • adding the filter in the must returns the same result

  • the filter alone works correctly


What to do?










share|improve this question














This query returns results well ordered:



GET <index>/_search
{
"query": {
"bool": {
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


How to add a filter to to remove entries outside of certain dates? Tried this:



GET <index>/_search
{
"query": {
"bool": {
"filter": [
{
"range": {
"date": {
"gte": "2008-01-01 00:00:00"
}
}
}
],
"must": [
{
"query_string": {
"fields": ["field1^7", "field2", "field3^4", "field4^6"],
"query": "query"
}
}
]
}
}
}


However the order is now ruined with worse matches up front. Even more, it seems valid entries are not here anymore?



Checks:




  • date is indeed indexed as a date

  • a post_filter returns the same result

  • adding the filter in the must returns the same result

  • the filter alone works correctly


What to do?







elasticsearch elasticsearch-dsl






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 18 at 13:59









DimebagDimebag

368518




368518








  • 1





    Could you add an example of a document that is filtered out and which should not? Plus the ordering in your query is based on the score and your filter will not change the score for matching documents. So the filter doesn't change the ordering it's just that it changes the ordered result set. Could you then explain to us what is a "well-ordered result set" for you? We need a concrete example to help you

    – Pierre Mallet
    Jan 18 at 16:11














  • 1





    Could you add an example of a document that is filtered out and which should not? Plus the ordering in your query is based on the score and your filter will not change the score for matching documents. So the filter doesn't change the ordering it's just that it changes the ordered result set. Could you then explain to us what is a "well-ordered result set" for you? We need a concrete example to help you

    – Pierre Mallet
    Jan 18 at 16:11








1




1





Could you add an example of a document that is filtered out and which should not? Plus the ordering in your query is based on the score and your filter will not change the score for matching documents. So the filter doesn't change the ordering it's just that it changes the ordered result set. Could you then explain to us what is a "well-ordered result set" for you? We need a concrete example to help you

– Pierre Mallet
Jan 18 at 16:11





Could you add an example of a document that is filtered out and which should not? Plus the ordering in your query is based on the score and your filter will not change the score for matching documents. So the filter doesn't change the ordering it's just that it changes the ordered result set. Could you then explain to us what is a "well-ordered result set" for you? We need a concrete example to help you

– Pierre Mallet
Jan 18 at 16:11












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54255533%2felastic-filter-changes-ordering%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54255533%2felastic-filter-changes-ordering%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Callistus III

Plistias Cous

Index Sanctorum