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: Set different boost for indices when searching across indices #23

Closed
kimchy opened this issue Feb 17, 2010 · 2 comments
Closed

Comments

@kimchy
Copy link
Member

kimchy commented Feb 17, 2010

Have the ability to set different boost values per index when searching across indices. This comes in handy for example, when each twitter user has an index, and his friends count more than the rest of the indices.

The parameter is a url parameter called indicesBoost, and for example: indicesBoost=indexName1:2,indexName2:3.1

@kimchy
Copy link
Member Author

kimchy commented Feb 17, 2010

Search API: Set different boost for indices when searching across indices, closed by 8a5a44c.

kimchy added a commit that referenced this issue Jun 5, 2015
Update S3Gateway to add us-west-2
johtani added a commit that referenced this issue Jun 5, 2015
dadoonet added a commit that referenced this issue Jun 5, 2015
Closes #23.
(cherry picked from commit 64a1d9c)
dadoonet added a commit that referenced this issue Jun 5, 2015
Some tools have changed on GCE platform.
We need to update the documentation.

Closes #23.
dadoonet added a commit that referenced this issue Jun 5, 2015
Closes #23.

(cherry picked from commit 5662016)
dadoonet added a commit that referenced this issue Jun 5, 2015
As for elastic/elasticsearch-cloud-aws#86, we should raise a `SnapshotMissingException`.

Closes #23.

(cherry picked from commit 61ddb60)
brwe added a commit that referenced this issue Jun 9, 2015
Due to a change in elasticsearch 1.4.0, we need to apply a similar patch here.

See #6864
See #7819

Closes #23.
(cherry picked from commit 5e5c373)
dadoonet added a commit that referenced this issue Jun 9, 2015
…Service`

This [PR](#8062) broke ScriptEngineService by adding a new method `scriptRemoved(CompiledScript)`.

Closes #23.
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Curl recreation:

        curl -X DELETE "localhost:9200/test"

        curl -X PUT "localhost:9200/test" -d '{
          "settings" : { "index" : { "number_of_shards" : 1, "number_of_replicas" : 0 }}
        }'

        curl -X GET "localhost:9200/_cluster/health?wait_for_status=green&pretty=1&timeout=5s"

        curl -X PUT "localhost:9200/test/attachment/_mapping" -d '{
          "attachment" : {
            "properties" : {
              "file" : {
                "type" : "attachment"
              }
            }
          }
        }'

        curl -X PUT "localhost:9200/test/attachment/1" -d '{
            "file" : {
                "_content_type" : "application/pdf",
                "_name" : "resource/name/of/my.pdf"
            }
        }
        '

Produces a:

        {"error":"NullPointerException[null]","status":500}

And in ES logs:

      [2013-02-20 12:49:04,445][DEBUG][action.index             ] [Drake, Frank] [test][0], node[LI6crwNKQmu1ue1u7mlqGA], [P], s[STARTED]: Failed to execute [index {[test][attachment][1], source[{
          "file" : {
              "_content_type" : "application/pdf",
              "_name" : "resource/name/of/my.pdf"
          }
      }
      ]}]
      java.lang.NullPointerException
      	at org.elasticsearch.common.io.FastByteArrayInputStream.<init>(FastByteArrayInputStream.java:90)
      	at org.elasticsearch.index.mapper.attachment.AttachmentMapper.parse(AttachmentMapper.java:309)
      	at org.elasticsearch.index.mapper.object.ObjectMapper.serializeObject(ObjectMapper.java:507)
      	at org.elasticsearch.index.mapper.object.ObjectMapper.parse(ObjectMapper.java:449)
      	at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:486)
      	at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:430)
      	at org.elasticsearch.index.shard.service.InternalIndexShard.prepareIndex(InternalIndexShard.java:318)
      	at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:203)
      	at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:531)
      	at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:429)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      	at java.lang.Thread.run(Thread.java:680)

Closes elastic#23
@thiagolocatelli
Copy link

Which of the available query builders provide this capability? I cant find a way to add indices_boost to my query.

ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Apr 24, 2018
Previously, the assertion in onPossibleCommitFailure() would fail if there's an already-committed node, which was marked as SUCCEEDED.

Additionally, previously we didn't take into account that any already-committed nodes won't be voting for this publication, so if one of the other voting nodes fails then we might not have failed the leader straight away.

This fixes that.
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, night_rally uses Kibana for visualizing nightly and
release benchmark results. We also add an administration tool e.g. for
adding annotations.

While we add support for these new visualizations now, we are in a
transitory phase and will still populate and use the current charts for
the time being. After a grace period, we will then switch to using
Kibana exclusively.

Relates elastic#23
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we embed Kibana dashboards for nightly and release
benchmarks. As we want to gather further feedback we did not yet remove
the old functionality based on dygraphs (this will happen in elastic#33).

Closes elastic#23
Closes elastic#9
Closes elastic#11
Closes elastic#12
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