[GitHub] metron issue #836: DO NOT MERGE METRON-1308: Fix Metron Documentation

2017-11-08 Thread JonZeolla
Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/836 I just took a stab at an update, @cestella can you take a look when you get a second ---

[GitHub] metron issue #836: DO NOT MERGE METRON-1308: Fix Metron Documentation

2017-11-08 Thread JonZeolla
Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/836 I think I'm more of a fan of being explicit than providing a key, given this only happens a few times through the whole doc. Also, like I mentioned, the \*s are being suppressed, so they're not

[GitHub] metron issue #836: DO NOT MERGE METRON-1308: Fix Metron Documentation

2017-11-08 Thread cestella
Github user cestella commented on the issue: https://github.com/apache/metron/pull/836 So, answering your questions en-masse we use the following similar to how they exist in regex: * `*` - `0` or `n` instances * `?` - `0` or `1` instance * `+` - `1` or `n` instances