[Broker] Allow to configure the calculation of individual topic types #75

Closed
opened 2020-12-11 16:14:48 +01:00 by claudio.atzori · 2 comments

As the data relative to newer topic types needs to be validated by end-users before we put them in production, the workflow responsible for the creation of the events should allow to configure which topics types must be taken into account by the procedure.

So, in beta ALL the event types should be included, while in production we should activate all, except for

  • ENRICH/MISSING/DATASET/IS_SUPPLEMENTED_BY
  • ENRICH/MISSING/PUBLICATION/IS_RELATED_TO
As the data relative to newer topic types needs to be validated by end-users before we put them in production, the workflow responsible for the creation of the events should allow to configure which topics types must be taken into account by the procedure. So, in beta ALL the event types should be included, while in production we should activate all, except for * ENRICH/MISSING/DATASET/IS_SUPPLEMENTED_BY * ENRICH/MISSING/PUBLICATION/IS_RELATED_TO
michele.artini was assigned by claudio.atzori 2020-12-11 16:14:48 +01:00
claudio.atzori added the
enhancement
label 2020-12-11 17:02:19 +01:00
Member

Committed in the broker branch.

I added the following wf property to generate only the events of a set of topics:

topicWhitelist = ENRICH/MORE/PID,ENRICH/MISSING/ABSTRACT,ENRICH/MORE/PROJECT

for all topics:

topicWhitelist = *

Committed in the broker branch. I added the following wf property to generate only the events of a set of topics: `topicWhitelist = ENRICH/MORE/PID,ENRICH/MISSING/ABSTRACT,ENRICH/MORE/PROJECT` for all topics: `topicWhitelist = *`
Author
Owner

Integrated in PR !78

Integrated in PR !78
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: D-Net/dnet-hadoop#75
No description provided.