[ 
https://bro-tracker.atlassian.net/browse/BIT-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robin Sommer updated BIT-1039:
------------------------------

    Status: Open  (was: Merge Request)
    
> Merge request for Bloom filters
> -------------------------------
>
>                 Key: BIT-1039
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1039
>             Project: Bro Issue Tracker
>          Issue Type: New Feature
>          Components: Bro
>            Reporter: Matthias Vallentin
>            Priority: Medium
>             Fix For: 2.2
>
>
> The Bloom filter implementation in `topic/matthias/bloom-filter` is ready to 
> merge into master. Have a look at the very end of `bro.bif` for the 
> script-land interface.
> Internally, we have a new `BloomFilterVal`, which is serializable and 
> mergeable and thus ready for cluster use. This `Val` contains a polymorphic 
> Bloom filter instance, which hides the concrete Bloom filter type (currently 
> only basic and counting). Moreover, this branch introduces the notion of 
> ''hashers'', which are parameterizable (i.e., seedable) structures for 
> hashing values ''k'' times. I recall that Bernhard waits for this feature. 
> See `Hasher.h` for the documented interface.
> In the future, we need to rethink how to construct hash functions which only 
> depend on a seed given at script land. This will be important when sharing 
> Bloom filters across organizational boundaries. At this point, the 
> implementation relies on `CompHash` (at least for composite values, such as 
> records) which itself depends on the initial Bro seed generated at startup 
> time or when the user specifies the environment variable `$BRO_SEED`.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://bro-tracker.atlassian.net/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Reply via email to