Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abnormal sorting of query results when using numerical keywords #927

Open
Joe-rise opened this issue Oct 8, 2023 · 1 comment
Open

Abnormal sorting of query results when using numerical keywords #927

Joe-rise opened this issue Oct 8, 2023 · 1 comment

Comments

@Joe-rise
Copy link

Joe-rise commented Oct 8, 2023

Description:
I have noticed an issue with the sorting of query results when using numerical keywords, such as "123". The results are not ordered based on their relevance and do not appear at the top of the list as expected.

To reproduce the issue, follow these steps:

Enter a query with a numerical keyword, for example, "123".
Observe the order of the search results.
Compare the order with the expected result based on relevance.
Expected behavior:
When searching with numerical keywords, the query results should be sorted with the most relevant matches appearing at the top. This way, users can easily find the most relevant information related to their search.

Actual behavior:
Currently, the sorting of query results is not consistent with the expected behavior. The results may appear in a random order or do not prioritize the most relevant matches.

Environment:

Operating System: [linux centos 7]

Application version:
Version 0.4.8
CommitHash d17cd5d
BuildDate 2023-08-22T14:28:45Z
Additional information:
postman screenshot
f0418dde86608c66a2ec4bcc9a6b3b3
The results for the same data and query parameters in Elasticsearch (ES) are as follows:
a4cdaf9080d01f6bf108b1c99f12979

@hengfeiyang
Copy link
Contributor

That is different data, if you create a record like the es response, it also should be first.

The reason is, default it calculate score based on all columns, you can see multiple fields value contains 1234

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants