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

Query DSL: moreLikeThis & moreLikeThisField #43

Closed
kimchy opened this issue Feb 26, 2010 · 1 comment
Closed

Query DSL: moreLikeThis & moreLikeThisField #43

kimchy opened this issue Feb 26, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Feb 26, 2010

Add support for moreLikeThis (MLT) queries. More like this allows to find documents that "look" like the provided text when matches against one or more field.

The moreLikeThis query looks as follows:

{
    moreLikeThis : {
        fields : ["name.first", "name.last"],
        likeText : "something",
        minTermFrequency : 1,
        maxQueryTerms : 12
    }
}

The moreLikeThisField looks as follows:

{
    moreLikeThisField : {
        "name.first" : {
            likeText : "something",
            minTermFrequency : 1,
            maxQueryTerms : 12
        }
    }
}

There are much more parameters that are supported, will be documented in the ref docs for the next release. They basically follow the MLT support in Lucene.

The difference between moreLikeThisField and moreLikeThis is that in moreLikeThisField only a single field can be provided, and it will supported "typed" fields (will automatically filter based on the type).

@kimchy
Copy link
Member Author

kimchy commented Feb 26, 2010

Query DSL: moreLikeThis & moreLikeThisField, closed by 0ebb74d.

dadoonet added a commit that referenced this issue Jun 5, 2015
Based on issue #43, we want to support both notations:

* group name first
* group id if it does not work with group name

Closes #49.
johtani added a commit that referenced this issue Jun 5, 2015
dadoonet added a commit that referenced this issue Jun 5, 2015
Closes #43.

(cherry picked from commit 6e5efe6)
(cherry picked from commit 675a860)
dadoonet added a commit that referenced this issue Jun 5, 2015
Closes #43.
(cherry picked from commit b028910)
(cherry picked from commit fa3e157)
dadoonet added a commit that referenced this issue Jun 5, 2015
njlawton pushed a commit to njlawton/elasticsearch that referenced this issue Mar 15, 2017
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue May 24, 2018
Today, if a node detects it is lagging the master it falls back to CANDIDATE
but then receives a heartbeat from the master and goes back to FOLLOWER. If it
is lagging because it missed a cluster state update for some reason then it
will never recover, because there's no impetus to publish a further update.

This change fixes this, crudely, by causing nodes to consider themselves as
faulty while they are lagging, which eventually results in them being kicked
out of the cluster and, later, rejoining, which fixes the lag.

Fixes elastic#43, but will eventually be superseded by elastic#53.
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we remove the outdated #size() method from all
parameter sources.

Closes elastic#43
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we provide the necessary configuration to night-rally in order
to build x-pack from sources after the merge to the Elasticsearch repository.

We only make benchmarks with x-pack work again for source-based builds for now.
We assume that we only run source-based builds against master. We intentionally
do not cover distribution-based benchmarks with x-pack as this will be tackled
in a separate PR.

Relates elastic#43
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

1 participant