-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Extra blank field in "Fields Selector" #663
Comments
This is fixed with the new mapping flattener. Thanks! |
w33ble
added a commit
to w33ble/kibana
that referenced
this issue
Sep 13, 2018
* chore: minor code refactor * feat: change the function separator use newlines before the pipes, instead of just keeping everything on 1 line * feat: naive argument formatting put arguments on new line when existing line is over 80 characters * test: fix the toExpression output check * chore: update element expressions match the new formatting rules so changing values from the sidebar is less jarring * fix: handle nested formatting differently * fix: don't wrap subexpression args * chore: typo fix * chore: attempt to make arg value formatting clearer break up the nested ternary, add comments
This was referenced Apr 7, 2021
This was referenced May 6, 2021
This was referenced Sep 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While attempting to limit the fields displayed in the Fields Selector of a Table by turning off ES dynamic mapping, an additional blank field shows up in the fields selector.
Using default-mapping.json in elastic search config directory:
{
"default":{
"dynamic":false,
"properties":{
"@timestamp":{"type":"date","format":"dateOptionalTime"},
"@Version":{"type":"string"},
"Message":{"type":"string"},
}
}
}
If I remove "dynamic":false, the blank field no longer exists. I am assuming the issue involves attemping to parse the dynamic parameter as an additional field.
The text was updated successfully, but these errors were encountered: