Add filter-on ability to accept blank action as wildcard

[heifner]

• Update mongo_db_plugin mongodb-filter-on & mongodb-filter-out with ability to wildcard action & receiver.
  -- Now receiver, action, and actor can be wildcarded.
• This updates mongo_db_plugin with latest filter capability of history plugin
  -- See Add filter-out history config option #4739
• Includes changes from fix mongo_db_plugin filter deficiency to allow any combination of receiver,action,actor #5691. Thanks go to @venediktov for implementation.

[wanderingbort]

is my read of the code wrong or does this not also allow reciever:0:actor which is not covered in the output?

[heifner]

How about:

"Mongodb: Track actions which match receiver:action:actor. Action and/or Actor may be blank to include all. Action and Actor both blank allows all from Receiver. Receiver may not be blank."

[wanderingbort]

I'll buy it

[venediktov]

Hi @wanderingbort , @heifner , this implementation does not allow "0:action:actor" code proposed by me in PR #5691 as it was handling all permutations , including ability to leave receiver blank.

if( filter_on_star  ) {
      include = true;
   } else {
      for( const auto& a : action_trace.act.authorization ) {
           auto itr = std::find_if(filter_on.begin(), filter_on.end(), [&action_trace,&a](auto && filter) {
              bool is_found{true};
              if(filter.receiver) {
                  is_found &= action_trace.receipt.receiver == filter.receiver;
              }
              if(filter.action) {
                  is_found &= action_trace.act.name == filter.action;
              }
              if(filter.actor) {
                  is_found &= a.actor == filter.action;
              }
              return is_found;
           });
           if(itr != filter_on.end()) {
               include = true;
               break;
           }
      }
   }

The rationale for "0:action:0" in our project we don't know upfront what coin will be running on the MainNet , so we listen for "0:issue:0 , "0:transfer:0" actions and record them in DB. To work with old solution would require restarting API node , this is not desirable for services we provide as syncing node takes quite some time.

[venediktov]

@heifner , match function is great , it eliminates verbosity , you also took care of mongodb-filter-out looks good !

[venediktov]

Hi @wanderingbort , @heifner , this implementation does not allow "0:action:actor" code proposed by me in PR #5691 as it was handling all permutations , including ability to leave receiver blank.

if( filter_on_star  ) {
      include = true;
   } else {
      for( const auto& a : action_trace.act.authorization ) {
           auto itr = std::find_if(filter_on.begin(), filter_on.end(), [&action_trace,&a](auto && filter) {
              bool is_found{true};
              if(filter.receiver) {
                  is_found &= action_trace.receipt.receiver == filter.receiver;
              }
              if(filter.action) {
                  is_found &= action_trace.act.name == filter.action;
              }
              if(filter.actor) {
                  is_found &= a.actor == filter.action;
              }
              return is_found;
           });
           if(itr != filter_on.end()) {
               include = true;
               break;
           }
      }
   }

The rationale for "0:action:0" in our project we don't know upfront what coin will be running on the MainNet , so we listen for "0:issue:0 , "0:transfer:0" actions and record them in DB. To work with old solution would require restarting API node , this is not desirable for services we provide as syncing node takes quite some time.