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

Mapper: Ability to disable storing the "source" field #66

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

Mapper: Ability to disable storing the "source" field #66

kimchy opened this issue Mar 17, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Mar 17, 2010

The source field is used to store the actual json that was indexed. Have the ability to disable storing it.

Disclaimer: Some features in elasticsearch might, in the future, require accessing the source field. When disabled, this features will simply not work. It is preferable to keep it on.

Disabling the source field can be done using the following mapping:

{
    person : {
        dateFormats : ["yyyy-MM-dd", "dd-MM-yyyy"],
        sourceField : {enabled : false}
    }
}

It can be disabled for all dynamic mappings created using the shared dynamic mapping definition.

@kimchy
Copy link
Member Author

kimchy commented Mar 17, 2010

Mapper: Ability to disable storing the "source" field, closed by 3a55998.

rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Closes elastic#66.
(cherry picked from commit fb3b288)
maabernethy pushed a commit to maabernethy/elasticsearch that referenced this issue Mar 20, 2017
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
Small cosmetically fixes in the REAMDME
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
refactor command infrastructure
add internal command templating
improved serialization limiting 'garbage' copies
relates to elastic#66 elastic#85 elastic#81 elastic#69
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
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
…1 (pull request elastic#66)

support new behavior

* support new behavior

* add comment

* add count print

* check different tenant bug

* fix cr comments

* last fixes

* add header check

Approved-by: Gideon Avida
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
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