-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
out_es: new 'replace_dots' option (#708)
On Elasticsearch 2.0-2.3, key names with dots were not allowed for hence was required to replace every dot with an underscore. This requirement is not longer true on newer versions of Elasticsearch. The following patch introduce a new option called 'replace_dot' which is disabled by default. So now the plugin will only replace the dots if the flag is enabled for use cases where old versions of Elasticsearch are in use. Signed-off-by: Eduardo Silva <[email protected]>
- Loading branch information
Showing
3 changed files
with
26 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6764ac7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. It looks like it changed previous default behavior. Before commit dots was replaced. After commit (and WITHOUT new option in config) default will be FLB_FALSE, so dots will not replaced.
Maybe better keep previous behavior as a default?
Line 256: ctx->replace_dots = FLB_TRUE;
6764ac7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since Elasticsearch 2.3 is very old and this new feature will land in Fluent Bit v0.14, I prefer to keep it disabled as the default behavior to play nice with newer versions of Elastic. If someone have an older version of Elastic so they can enable the backward compatible option replace_dots. Of course I will make sure to document the change.