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

_all field #63

Closed
kimchy opened this issue Mar 16, 2010 · 1 comment
Closed

_all field #63

kimchy opened this issue Mar 16, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Mar 16, 2010

Support _all field. The idea of an _all field is a field that includes the text of one or more other fields within the document indexed. It can come very handy especially for search request, where we want to execute a search query against the content of a document, without knowing which fields to search on. This comes at the expense of CPU cycles and index size.

The all fields can be completely disabled. Explicit field mapping and object mapping can be excluded / included in the all field. By default, all field is enabled and all fields are included in it for ease of use.

One of the nice features of the all field is that it takes into account specific fields boost levels. Meaning that if a title field is boosted more than content, the title (part) in the _all field will mean more than the content part in the all field.

With the _all field, certain APIs that require fields to be set can be simplified. They include:

  • The queryString query defaultField now defaults to the _all field.
  • The terms API fields now default to the _all field and not required.
  • More Like This query fields now default to _all if not set.

Here is a sample mapping:

{
    person : {
        allField : {enabled : true},
        properties : {
            name : {
                type : "object",
                dynamic : false,
                properties : {
                    first : {type : "string", store : "yes", includeInAll : false},
                    last : {type : "string", index : "not_analyzed"}
                }
            },
            address : {
                type : "object",
                includeInAll : false,
                properties : {
                    first : {
                        properties : {
                            location : {type : "string", store : "yes", indexName : "firstLocation"}
                        }
                    },
                    last : {
                        properties : {
                            location : {type : "string"}
                        }
                    }
                }
            },
            simple1 : {type : "long", includeInAll : true},
            simple2 : {type : "long", includeInAll : false}
        }
    }
}

The allField mapping can also be associated with an analyzer (index/search), a termVector, and the ability to store it (the concatenated text).

@kimchy
Copy link
Member Author

kimchy commented Mar 16, 2010

_all field, closed by 1dd5997.

IanvsPoplicola pushed a commit to IanvsPoplicola/elasticsearch that referenced this issue Mar 21, 2017
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Jun 4, 2018
Rethrowing a FailedToCommitClusterStateException is the wrong thing to do - it
should be passed to the listener for further processing.
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Jun 4, 2018
A consequence of elastic#63 is that a FailedToCommitClusterStateException is no longer
thrown by ZenDiscovery#publish(), it is just passed to the listener, so tests
that relied on catching it can no longer work.
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Jun 4, 2018
A consequence of elastic#63 is that a FailedToCommitClusterStateException is no longer
thrown by ZenDiscovery#publish(), it is just passed to the listener, so tests
that relied on catching it can no longer work.
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we expose the track parameter `bulk_size` for the challenge
`index-logs-fixed-daily-volume`. This also eliminates the need for the
challenges `bulk-size-evaluation`, `bulk-size-evaluation-mini` and
`bulk-size-concurrency-evaluation` as they can be simulated using the track
parameters `bulk_size` and `bulk_indexing_clients`.
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…quest elastic#63)

* Initial commit for engageli-media-server build and deploy scripts

Added "ems" type to build.py to build media server AMI.

New provisioning scripts for nodejs (to reuse) and EMS.

Terraform script to optionally deploy EMS node, controlled by "num_ems"
variable. Set to 1 in tfvars file to deploy an EMS instance to the stack.

Added ALB rule for routing traffic to the EMS node

Added engageli-media-server to tag_all repo list and did minor refactor to remove some code dup. More can and will be done later.

Expanded git ignore pattern for packer generated manifests.

Approved-by: Alan Nuchnoi
Approved-by: Rich Nessel
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we remove the cluster health check for x-pack because
recent Rally versions only test for cluster health of indices that are
created during the benchmark instead of all indices (e.g. `.security`).
Thus, the cluster health check is also green when x-pack is enabled.

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