The map_metadata transform is basically fun(_)-> !grab_from_ref It only needs to fire when the stream first starts, which it does. Indeed it does look like there may be a mutable state bug somewhere in the underlying ML. Sorry I don't have a really tight minimal repro test case... maybe could try to generate one.
-ken -- --------- On Fri, Oct 10, 2014 at 01:56:33PM +0200, David Baelde wrote: > Hi Ken, > > I'm glad you got to something that works for you. What you did with > definition names here is along the lines of the short advice I > proposed in my previous mail. However, I would not have suspected the > need for drop_metadata(). I find it weird: if you drop metadata, > there's nothing to transform next using map_metadata... or is your > map_metadata() supposed to *insert* rather than modify stuff? (i.e. > you would be using insert_missing) > > The reason why I'm asking is that there is possibly a bug lying here. > It seems surprising for basic stuff like this, but on the other we're > using a mutable data structure for metadata and may have forgotten to > copy in some places... > > Cheers, > > David > > On Thu, Oct 9, 2014 at 10:48 PM, Ken Restivo <k...@restivo.org> wrote: > > After some hours of struggle, I discovered that the above was the only way > > to decouple the two sources, was to drop_metadata() on the original source, > > i.e.: > > > > original_source = input.harbor(...) > > ignore(output.dummy(fallible=true, original_source) > > > > new_source_1 = map_metadata(some_transform, > > drop_metadata(original_source)) > > new_source_2 = map_metadata(some_other_transform, > > drop_metadata(original_source)) > > > > new_source_1 = output.icecast(...) > > new_source_2 = output.file(...) > > > > -ken > > -- > > --------- > > On Tue, Oct 07, 2014 at 09:46:00AM -0700, David Baelde wrote: > >> Hi Ken, > >> > >> You're almost there with the first attempt. Your problem there is that > >> you're redefining source1 on the first line and this new definition is > >> used when you define source2 next. > >> > >> Hope this helps, > >> > >> David > >> > > > > -- > David ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
