We need to provide a better way to get the system properties from the WorkflowToken.
Following approaches tried so far:
1. In the "onFinish" method of the MapReduce program, user can add the counters to the WorkflowToken as required.
Disadvantages: User will explicitly require to add the MapReduce counters, which will involve the fair amount of coding on the user's part.
2. CDAP can provide the MapReduce counters implicitly with some prefix such as "mr.counters".
Advantages: User can focus on map and reduce functionality and will get access to the counters from token out of the box.
Disadvantages: User will need to remember the prefix "mr.counters", which can be prone to error.
Another way to solve the problem is by having SCOPE.