ScoreSort sort by Doc field
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
Research direction
Open java-client/src/main/java/co/elastic/clients/elasticsearch/_types/ScoreSort.java at the referenced line and inspect _sortOptionsKind(). Compare its returned kind with the issue's proposed Score value. Done means the method reports the correct score sort kind; the payload does not mention a test file to run.
Written by the indexing model from the issue text.
Description
Java API client version
7.17
Java version
jdk8
Elasticsearch Version
7.17
Problem description
Seems like ScoreSort sort by doc field - see https://github.com/elastic/elasticsearch-java/blob/7.17/java-client/src/main/java/co/elastic/clients/elasticsearch/_types/ScoreSort.java#L69
Probably it should be
public SortOptions.Kind _sortOptionsKind() {
return SortOptions.Kind.Score;
}
- Dominant language
- Java
- Stars
- 524
- Forks
- 299
- Avg merge
- 16m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from elastic/elasticsearch-java
-
Delete By Query deserialization will not account for search failuresPossibly taken @l-trotta claimed this 3 days ago. Open
elastic/elasticsearch-java#1349 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Nested index settings that do not end up deserialized in otherSettings leads to requiring properties on parent JSON nodesPossibly taken @l-trotta claimed this 3 days ago. OpenArea: Specification Category: Bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
elastic/elasticsearch-java#1347 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
RestClientTransport sends bulk bodies as one HTTP chunk / TLS record / syscall per NDJSON buffer, burning ~45x the reactor CPU of the HLRCPossibly taken @l-trotta claimed this 19 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
elastic/elasticsearch-java#1339 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
elastic/elasticsearch-java#1212 · 8 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
elastic/elasticsearch-java#1165 · 5 comments ·
Maintainers usually reply within 1 day
All issues in elastic/elasticsearch-java
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/skywalking#14120 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
HMCL-dev/HMCL#6943 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
micronaut-projects/micronaut-core#13677 ·
Maintainers usually reply within 1 day
-
new feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/rocketmq-dashboard#5594 ·
Maintainers usually reply within 3 days