[Lognorm] PR for field-type 'float' and field-types for parsing suffixed-values('suffixed' and 'named_suffixed')

[Chris Schafer]

Valgrind will need additional modifications for Travis to fire.
On Fri, Feb 27, 2015 at 6:48 AM singh.janmejay <singh.janmejay at gmail.com>
wrote:

> Let me reach out to teams in my org to see if we can share log-samples
> (some privacy stuff may be involved). I want to do this, but somehow
> never got to it. Will start the conversation asap.
>
> On Fri, Feb 27, 2015 at 8:04 PM, Rainer Gerhards
> <rgerhards at hq.adiscon.com> wrote:
> > 2015-02-27 14:57 GMT+01:00 singh.janmejay <singh.janmejay at gmail.com>:
> >>
> >> Sounds good.
> >>
> >> Also, noticed we don't enable test-bench and valgrind on travis. It'll
> >> be very useful to have them enabled for travis. Also, we should
> >> probably enable regex too on travis(infact all optional things should
> >> be enabled to exercise as many tests as possible).
> >>
> >> Shall I do this in current PR?
> >>
> >
> > yes, please do!
> >
> > Side-note: do you have some logs to share for the tests and research I am
> > currently working on?
> >
> > Rainer
> >>
> >> On Fri, Feb 27, 2015 at 6:55 PM, Rainer Gerhards
> >> <rgerhards at hq.adiscon.com> wrote:
> >> > 2015-02-27 14:05 GMT+01:00 singh.janmejay <singh.janmejay at gmail.com>:
> >> >>
> >> >> - Implemented float (a type that parses real numbers in form of
> >> >> nnn.nnn) (note that this doesn't handle n.nnne^nn or any other
> >> >> scientific notation, but then those are not all that common in logs)
> >> >>
> >> >> - Implemented suffixed and named_suffixed field types that allow
> >> >> parsing of fields that have one of many potential suffixes (like a
> >> >> disk-space value which may have suffix kb, mb, gb etc). Field
> >> >> named_suffixed does exactly the same thing as suffixed, but allows
> >> >> user to name the parsed-value and suffix field unlike suffixed, which
> >> >> provides default names "value" and "suffix".
> >> >>
> >> >> - Tokenized wasn't working with lognorm special characters ('%' and
> >> >> ':') because it wasn't unescaping token-string, which is now fixed.
> >> >>
> >> >>
> >> >
> >> > This sounds really good. Given the fact that I was about to release
> the
> >> > current version, I think it would make sense to postpone  that for a
> few
> >> > days to permit releasing the new things in that same release.
> >> >
> >> > Any concerns?
> >> > Rainer
> >> >>
> >> >>
> >> >> --
> >> >> Regards,
> >> >> Janmejay
> >> >> http://codehunk.wordpress.com
> >> >> _______________________________________________
> >> >> Lognorm mailing list
> >> >> Lognorm at lists.adiscon.com
> >> >> http://lists.adiscon.net/mailman/listinfo/lognorm
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Lognorm mailing list
> >> > Lognorm at lists.adiscon.com
> >> > http://lists.adiscon.net/mailman/listinfo/lognorm
> >> >
> >>
> >>
> >>
> >> --
> >> Regards,
> >> Janmejay
> >> http://codehunk.wordpress.com
> >> _______________________________________________
> >> Lognorm mailing list
> >> Lognorm at lists.adiscon.com
> >> http://lists.adiscon.net/mailman/listinfo/lognorm
> >
> >
> >
> > _______________________________________________
> > Lognorm mailing list
> > Lognorm at lists.adiscon.com
> > http://lists.adiscon.net/mailman/listinfo/lognorm
> >
>
>
>
> --
> Regards,
> Janmejay
> http://codehunk.wordpress.com
> _______________________________________________
> Lognorm mailing list
> Lognorm at lists.adiscon.com
> http://lists.adiscon.net/mailman/listinfo/lognorm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.adiscon.net/pipermail/lognorm/attachments/20150227/37ea2544/attachment.html>