BUG: filtering collection objects doesn't actually work for "added_after"

[oasis-open]

BUG: filtering collection objects doesn't actually work for "added_after"

[johntmyers]

Ok, so it appears you assume all objects in results have a modified key, for whatever reason, when testing with STAXX, they sometimes will add objects that do not have, such as a marking-definition.

So my results array had this:

{"created": "2018-08-18T08:38:43.559327Z", "definition": {"tlp": "green"}, "definition_type": "tlp", "id": "marking-definition--2496e5bf-137a-5dfa-bf89-8c47bc4bc277", "type": "marking-definition"}

The other objects in the collection reference this marking-definition. Bottom line, not all objects have a modified field, so this is a bad check to make to "assume" the list you are processing are manifest entries.

[clenk]

Thanks for filing an issue, @johntmyers! We'll take a look at this when we get a chance.

[rpiazza]

@johntmyers,

We just had a fix for a similar problem for the mongodb filter. If you are interested in creating a pull request asap - you can look in mongodb_filter.py for some hints. Otherwise, we will get to this as soon as we can.