Issue 31043: Elastic Search interferes with the default sort order of products (changing newest first to oldest first)

[rogerdz]

Description (*)

Add sorting condition by product id desc

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Elastic Search interferes with the default sort order of products (changing newest first to oldest first) #31043

Manual testing scenarios (*)

1. ...
2. ...

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @rogerdz. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[rogerdz]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[rogerdz]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[rogerdz]

@magento give me test instance

[magento-deployment-service]

Hi @rogerdz. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @rogerdz, here is your Magento Instance: https://a961f7d4071fdb23cce8cdfa12c1651a.instances.magento-community.engineering
Admin access: https://a961f7d4071fdb23cce8cdfa12c1651a.instances.magento-community.engineering/admin_bb93
Login: b2a75abc
Password: d5ee90711a13

[rogerdz]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[TuVanDev]

@magento give me test instance

[magento-deployment-service]

Hi @Viper9x. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @Viper9x, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[TuVanDev]

@magento give me test instance

[magento-deployment-service]

Hi @Viper9x. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @Viper9x, here is your Magento Instance: https://a961f7d4071fdb23cce8cdfa12c1651a.instances.magento-community.engineering
Admin access: https://a961f7d4071fdb23cce8cdfa12c1651a.instances.magento-community.engineering/admin_9821
Login: de7e84f9
Password: c38f57fc7b93

[TuVanDev]

I confirmed this PR resolved issue #31043. Special thanks to @rogerdz for providing the fix.

[rogerdz]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[rogerdz]

@magento run Functional Tests B2B, Functional Tests CE , Functional Tests EE

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[rogerdz]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[Den4ik]

@rogerdz Could you please resolve conflict?

[engcom-Hotel]

Hello @rogerdz,

We request you to please resolve the conflicts on this PR, so that we can proceed further with this. Meanwhile moving this PR On Hold.

Thanks

[rogerdz]

@magento run all tests

[engcom-Hotel]

@magento run all tests

[Copilot]

Pull Request Overview

The pull request updates the default fallback sort order in the product fulltext collection to use descending product IDs.

• Changed the default entity_id sort from ascending to descending.
• Ensures newer products appear first when no other sort is specified.

Comments suppressed due to low confidence (2)

app/code/Magento/CatalogSearch/Model/ResourceModel/Fulltext/Collection.php:584

• No tests appear to cover the updated fallback sort order. Consider adding or updating unit/integration tests to validate that products are sorted by entity_id descending when using this collection.

$this->setOrder('entity_id', Select::SQL_DESC);

app/code/Magento/CatalogSearch/Model/ResourceModel/Fulltext/Collection.php:581

• The doc block above the sort change should mention that the fallback order is now set to entity_id descending to reflect the new behavior.

* NOTE: this does not replace existing orders but ADDs one more

[engcom-Hotel]

Hello @rogerdz,

The changes seems good to us, but please refer to the below review comments:

• It seems some automated tests are failing due to the changes
• Consider making the default sort order configurable if different deployments require different behaviors.
• Add/modify an integration test to assert search results default to descending order by entity_id.
• Update the comment above the line to specify "newest first" for clarity.