We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In all our fields.yml files we use int to define integers. It seems the correct mapping type in elasticsearch is integer: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html We should rename all int to integer and regenerate our templates.
fields.yml
int
integer
Note: This had not affect so far as we didn't generate the templates for int.
Example here: https://github.com/elastic/beats/pull/1155/files/e5b256f2376efd752f23bec8c60dfff46eb2ba42#diff-8034c25c820cd3bb48fe68e5a463a9b3R100
The text was updated successfully, but these errors were encountered:
"type":"int" does not work on ES 1.7, 2.x and 5.0. We must change this for all beats.
Sorry, something went wrong.
No branches or pull requests
In all our
fields.yml
files we useint
to define integers. It seems the correct mapping type in elasticsearch isinteger
: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html We should rename allint
tointeger
and regenerate our templates.Note: This had not affect so far as we didn't generate the templates for
int
.Example here:
https://github.com/elastic/beats/pull/1155/files/e5b256f2376efd752f23bec8c60dfff46eb2ba42#diff-8034c25c820cd3bb48fe68e5a463a9b3R100
The text was updated successfully, but these errors were encountered: