@jhalterman kinda hoped there was an existing module / class that could do all the yaml file parsing and exposing functions for calling the values etc.
Also for my project i want a kind of end-to-end persistence. so i was thinking of storing the original event in raft and then push it in the pipeline. only when its been sent out successfully then it gets removed out of raft.. this way if something messes up in the pipeline ( crash or whatever ) the original message can be replayed. what do you guys think of that?
i just left a comment on that github issue that has a more stripped down example of how to parse YAML to an object
my preference for internal config classes is to just have public fields and not even bother with getters/setters. if it's a config class that's part of a public API, then you probably want get/set methods.
well. at the moment logstash it self is a single isolated thing.. no concept of clustering or anything..Now they started their ‘clustering’ project which is a glorified storing of the config in ES so multiple nodes can read it
sort of config management replacement
which is stupid :-)
so i want to show them with some effort a real logstash cluster can be done with Raft.