Package org.apache.hadoop.yarn.server.timelineservice.storage.apptoflow

Class AppToFlowTable

java.lang.Object
org.apache.hadoop.yarn.server.timelineservice.storage.common.BaseTable<AppToFlowTable>
org.apache.hadoop.yarn.server.timelineservice.storage.apptoflow.AppToFlowTable
public final class AppToFlowTable extends BaseTable<AppToFlowTable>
The app_flow table as column families mapping. Mapping stores appId to flowName and flowRunId mapping information Example app_flow table record: 
 |--------------------------------------|
 |  Row       | Column Family           |
 |  key       | mapping                 |
 |--------------------------------------|
 | appId      | flow_name!cluster1:     |
 |            | foo@daily_hive_report   |
 |            |                         |
 |            | flow_run_id!cluster1:   |
 |            | 1452828720457           |
 |            |                         |
 |            | user_id!cluster1:       |
 |            | admin                   |
 |            |                         |
 |            | flow_name!cluster2:     |
 |            | bar@ad_hoc_query        |
 |            |                         |
 |            | flow_run_id!cluster2:   |
 |            | 1452828498752           |
 |            |                         |
 |            | user_id!cluster2:       |
 |            | joe                     |
 |            |                         |
 |--------------------------------------|
It is possible (although unlikely) in a multi-cluster environment that there may be more than one applications for a given app id. Different clusters are recorded as different sets of columns.

  • Constructor Details

    • AppToFlowTable

      public AppToFlowTable()