Driven 1.3 Release Notes
version 1.3.8New in this Release
- Extended integration with Apache Hive and native MapReduce
-
Driven can monitor and display performance data for applications that are coded in Hive or in native MapReduce without setup of intermediate Cascading Java layers. The Driven Agent removes the dependency on HiveFlow for applications running with Hive queries, and also removes the dependency on Class MapReduceFlow for applications that are programmed in native MapReduce.
See link: Driven Agent 1.3 Installation Guide.
- Apache Tez support
-
Driven shows performance metrics of Cascading applications that use the Apache Tez framework. Version 0.6.2 of Apache Tez with Cascading 3.0.2+ is supported for Driven.
- Tap Field search parameter
-
With the Tap Field search parameter, you can search for applications that process the data stored in a particular field name. Matching results of the search list applications that have sourced or sinked Tap fields that match the string that you entered in the Search field. A use case for Tap Field searches in some environments is identifying which applications access sensitive or confidential data so that you can comply with security or auditing requirements.
See Tap Filters for more information.
- Email notifications
-
As a team leader, you can set up automatic messaging so that users who belong to the team receive an email message when applications reach a completed state. You can customize the message in the email or accept a default template.
See Enabling Automatic Email Notifications for more information.
- Shared views
-
You can share a view that you create so that other Driven users can easily access the same information. When you share the view, you can select whether to share only with other members of your teams or with anyone who is logged in to Driven.
See Sharing Saved Views for more information.
- Major enhancements to the Application View
-
The graphical and metric-reporting features of this view are refined to help you retrieve application performance data that is relevant to you and your runtime environment:
-
A timeline selector grid highlights the specific intervals that contain data for applications that match entered search criteria. The visual cues of the shaded grid enable one-click access to time intervals with relevant runtime data, instead of requiring the user to engage in a longer process of discovery.
-
Driven can calculate multiple types of statistics about particular time intervals and for aggregated application activity of the view’s time frame. These statistics pertain to various common benchmarks of application performance, and are displayed in context above a graph displaying metrics for the selected interval.
-
When State Transitions is turned on for the graph, the slopes of lines change to accurately reflect the duration of each status. Previously, the graphed lines did not bend slope in proportion to each status, which limited the ability to visualize and compare status durations for multiple instances of an application.
-
The graphical chart can be minimized or maximized with a single click on a button.
-
See Application Views for more information.
- Driven administrator can view information about all applications
-
Previously, the Driven administrator had to belong to a team to view status and runtime information for any applications that are associated with the team by virtue of the API key. Now the administrator can view application performance information for all applications that transmit data to the Driven deployment.
Fixed Bugs
-
1.3.7 Plugin side configurations such as driven.protocol.slice.suppress are no longer being ignored.
-
When the My Teams list was opened and exceeded the space that was available in the sidebar, there was no internal scrollbar to view teams that did not fit in the space. Now an internal scrollbar lets you navigate which teams are displayed in the My Teams list of the scrollbar.
-
In some cases the last flow of an application run without a cascade ended in PENDING status but the Driven Plugin marked the flow as SKIPPED.
-
The text of some pop-ups from the sidebar was cut off from view.
-
Source Taps that used the same URI as another source Tap did not always render properly in directed acyclic graphs (DAGs).
-
The icons for clearing search criteria were mangled when users ran Driven on the Firefox browser.
-
Excessive blank space appeared under DAGs when there were only a few flows or a single flow.