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

Search API: Indices Boost to apply a boost factor to each index #143

Closed
kimchy opened this issue Apr 19, 2010 · 2 comments
Closed

Search API: Indices Boost to apply a boost factor to each index #143

kimchy opened this issue Apr 19, 2010 · 2 comments

Comments

@kimchy
Copy link
Member

kimchy commented Apr 19, 2010

A boost factor is simply multiplying the score of the query by the boost factor to provide the final scoring of each document. This is more powerful then the way it works currently, by setting the boost on the top level query, since it makes little sense to do so... .

@kimchy
Copy link
Member Author

kimchy commented Apr 19, 2010

Search API: Indices Boost to apply a boost factor to each index, closed by 2fdc49c.

@clintongormley
Copy link

fixed++

dadoonet added a commit that referenced this issue Jun 5, 2015
…sion()

The AwsEc2UnicastHostsProvider creates DiscoveryNodes that are used as an initial seed for unicast based discovery. At the moment it uses Version.CURRENT (see [1]) for those DiscoveryNode object, which confuses the backwards compatibility layer to think this nodes are of the latest version. This causes new nodes to fail to join old nodes as the ping serialization goes wrong. Instead we should use version.minimumCompatibilityVersion(). See [2]

[1] https://github.com/elasticsearch/elasticsearch-cloud-aws/blob/es-1.x/src/main/java/org/elasticsearch/discovery/ec2/AwsEc2UnicastHostsProvider.java#L165
[2] https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/discovery/zen/ping/unicast/UnicastZenPing.java#L130

Ps. this was reported on the mailing list. See: https://groups.google.com/forum/#!msg/elasticsearch/8pUwFld88tI/7jRuG6hqtbAJ

Closes #143.
C-Bish pushed a commit to C-Bish/elasticsearch that referenced this issue Mar 23, 2017
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we change the annotation mapping to use the new field
`race-timestamp` instead of the previous field `trial-timestamp` so it
matches documents in `rally-results-*` again. We also remove any
incompatibilies for newer versions of Elasticsearch (`_all` field,
document type is `_doc` now).

Relates elastic#128
Relates elastic#143
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we remove all leftover references to trial timestamp
and replace it with the new name race timestamp.

Relates elastic#128
Relates elastic#143
Relates elastic#144
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants