Changes to indicators and funders definition #372
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
RDGraph
RSAC
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: D-Net/dnet-hadoop#372
Loading…
Reference in New Issue
No description provided.
Delete Branch "antonis.lempesis/dnet-hadoop:beta"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
b139de8286
to8b2cbb611e
Dear Dimitris, this PR mentions a few changes in the definition of one table and the addition of three indicators. I would assume these changes to be confined to the modules
However, I see two new submodules are included in the PR:
Were they intended to be included in this PR? If so, please describe them. I need to know
Thank you!
Regarding the 2 new wfs:
dhp-stats-monitor-irish
Builds the db for the Irish Monitor and is meant to run after the stats-update one. They are separate wfs because we want to be able to run this on demand, more often than the main wf, at least while we actively develop the monitor and add more and more stuff.
The parameters it expects are (descripion and example value in parentheses):
dhp-stats-hist-snaps
Creates and updates a db of some historical snapshots from the graph. It should run after the stats-update and the dhp-stats-monitor-irish.
I have a few questions myself about the parameters, so I'll Dimitris and comment again. In an case, you can schedule the irish monitor one now (the params are pretty standard) and we'll come back about the historical one.
@antonis.lempesis although I'm still waiting for the clarification you mentioned above about the parameters for the workflow
dhp-stats-hist-snaps
, I integrated the PR in the beta codebase. While doing so, I noticed the changes include yet another submodule defining another oozie workflow that was not described yet:I can imagine this workflow implements the update of the monitor DBs, hence I take it as a refactoring of parts defined in the
dhp-stats-update
workflow. Can you confirm this the case?If so, please
Thanks!
ps. in the meantime I will prepare the automated deployment procedures for all the new oozie workflows.
Please ignore this wf. It's updating the beta institutional monitor db whenever we need to add a couple of more orgs in the monitor, and we run it manually between beta runs. I'll move it to a new project when we split the whole thing.