[Measures] added new measure (UsageCounts)
#214
Merged
claudio.atzori
merged 8 commits from eosc_dimitris
into beta
2 years ago
Loading…
Reference in New Issue
There is no content yet.
Delete Branch 'eosc_dimitris'
Deleting a branch is permanent. It CANNOT be undone. 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) 2 years ago@ -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.
a289c9eae2
into beta 2 years agoReviewers
a289c9eae2
.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.