[Measures] added new measure (UsageCounts) #214
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
RDGraph
RSAC
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: D-Net/dnet-hadoop#214
Loading…
Reference in New Issue
No description provided.
Delete Branch "eosc_dimitris"
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?
This PR introduces a new oozie workflow for the creation of a new action set that includes the usage counts (views and downloads) as a new measure on the result level.
It will have as provenaceaction.classid the value measure:usage_counts and as id for the measure the keywords downloads and views referring respectively to the attribute with the same names in the usage stats table, while the key for the unit will be count.
The values are calculated as the sum of the counts, aggregated for each record id.
The remaining part of the measure element is set exactly as for the bip!Finder integration.
[Measures] added new measure (usagecounts)to [Measures] added new measure (UsageCounts)@ -392,2 +392,4 @@
return null;
}
public static KeyValue newKeyValueInstance (String key, String value, DataInfo dataInfo){
Please compile before pushing. It seems the code formatting was not applied here.
@ -0,0 +33,4 @@
/**
* created the Atomic Action for each tipe of results
typo: tipe == type
@ -0,0 +65,4 @@
SparkConf conf = new SparkConf();
conf.set("hive.metastore.uris", parser.get("hive_metastore_uris"));
final String dbname = parser.get("statsdb");
Minor: I would name the parameter as
usagestatsdb
to avoid confusion with the other stats database. In this context there is no ambiguity, but from the workflow caller there might be.@ -0,0 +19,4 @@
},
{
"paramName": "sdb",
"paramLongName": "statsdb",
Minor: I would name the parameter as
usagestatsdb
to avoid confusion with the other stats database. In this context there is no ambiguity, but from the workflow caller there might be.@ -0,0 +5,4 @@
<description>the path where to store the actionset</description>
</property>
<property>
<name>statsdb</name>
Minor: I would name the parameter as
usagestatsdb
to avoid confusion with the other stats database. In this context there is no ambiguity, but from the workflow caller there might be.@ -0,0 +6,4 @@
</property>
<property>
<name>statsdb</name>
<description>the path where to store the actionset</description>
the description is wrong. Looks like a copy&paste
Overall looks ok, just minor changes. Please check the inline comments and remember to compile before issuing the commit&push so that the common formatting is applied.