AMBARI-22750. Add custom input / mapper descriptor to config api #79
Conversation
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
kasakrisz
reviewed
Jan 10, 2018
|
|
||
| String getMapperClassName(); | ||
|
|
||
| void setClassName(String className); |
There was a problem hiding this comment.
This can be setMapperClassName
oleewere
force-pushed
the
logfeeder-shipper
branch
from
588171b
to
1800b88
Compare
kasakrisz
reviewed
Jan 10, 2018
| @ShipperConfigElementDescription( | ||
| path = "/filter/[]/post_map_values/{field_name}/[]/map_custom/class_name", | ||
| type = "string", | ||
| description = "Custom class which implements an mapper type", |
kasakrisz
approved these changes
Jan 10, 2018
oleewere
force-pushed
the
logfeeder-shipper
branch
from
1800b88
to
97b274a
Compare
zeroflag
approved these changes
Jan 10, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
New custom input and mapper blocks for the logsearch config api:
{ inputs : [ "source":"custom" "class": "..." "properties": { "k1": "v1", "k2": "v2"} ] #... and same for mappers inside filtersHow was this patch tested?
With docker based environment, logfeeder still behave as the same way.
The more detailed testing will be added after logfeeder will be pluggable
@kasakrisz @swagle @zeroflag