# Elasticsearch 6 to 7 scoring change **URL:** \ **Category:** Elasticsearch\ **Tags:** migration\ **Created:** [September 19, 2022, 3:40pm UTC](https://discuss.elastic.co/t/elasticsearch-6-to-7-scoring-change/314709 "2022-09-19T15:40:47Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mask](https://avatars.discourse-cdn.com/v4/letter/m/67e7ee/32.png) [@mask](https://discuss.elastic.co/u/mask)\ **Post date:** [September 19, 2022, 3:40pm UTC](https://discuss.elastic.co/t/elasticsearch-6-to-7-scoring-change/314709/1 "2022-09-19T15:40:47Z")
My service which run with Elasticsearch 6.4 has a function score query with boost and weight to find the most match document for user. After migrate to Elasticsearch 7.10 (same mapping, number of shards, data count) I found that the same function score query had different sequence of results. I have observed through explain api and the scoring logic seems to have changed. I wonder if there has any way to make the query result consistent as Elasticsearch 6? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 19, 2022, 3:40pm UTC](https://discuss.elastic.co/t/elasticsearch-6-to-7-scoring-change/314709/2 "2022-09-19T15:40:47Z")
Elasticsearch 7.10 is [EOL](https://www.elastic.co/support/eol) and no longer supported. Please upgrade ASAP. (This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: ) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 17, 2022, 3:41pm UTC](https://discuss.elastic.co/t/elasticsearch-6-to-7-scoring-change/314709/3 "2022-10-17T15:41:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.