Baubak Gandomi

It seems that we have a bug of when we set a value for the valueMap, we do not check if the header exists.

We have a bug where when the header (StdLogEntry.fetchHeaders) contains either key or frequence

move to streams. Replace direct access for fetchValueMap for updating values

We need to test the case of a log-parser used as a SDK. Thee seem to be some regressions there

It would make assertions easier if the log assertions could work with matchers `AssertLogData.assertLogMatches(String, ParseDefinitionEntry, Matcher)` And `AssertLogData.assertLogMatches(ParseDefinitionEntry, Matcher)`

One of the added values for log parsing is to calculate duration. Given two log data entries Start time | Action ---------- | ------- 11:59 | start 12:00 | finish...

Resolve and clarify difference between fetchHeaders and keyOrder

1

There is an ambiguity between the fetchHeaders and fetchKeyOrder. When is each used?

We are currently expecting exact values when performing search. We would like to be able to perform search with more advanced possibilities such as: * Hamcrest Matchers * Methods *...

In search I would like to pass a Matcher LogData.search("ParseDefinitionEntry1",Matchers.startsWith("value"))

We should be able to import logs from splunk. We should also be able to publish onto splunk