You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Sreenath Somarajapuram (JIRA)" <ji...@apache.org> on 2015/12/16 10:49:46 UTC
[jira] [Updated] (TEZ-2985) Tez UI: Create loader and entity
classes
[ https://issues.apache.org/jira/browse/TEZ-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sreenath Somarajapuram updated TEZ-2985:
----------------------------------------
Description:
Entity:
- An entity would contain a model and defines it's complex relationship with other models
- Differing from a model entities gets satisfied only when all the required data is loaded
- Entity must ensure REST API backward compatibility
Loader
- Loaders are supposed to load an entity(s), like stores fetch model(s)
- Loaders must take case of caching
- In pages like 'All DAGs' without a limit. If tables do client side filtering after loading, we might end-up with lower number of records than loaded. Tables must be able to inform loader to load more more records.
was:
Entity:
- An entity would contain a model and defines it's complex relationship with other models
- Differing from a model entities gets satisfied only when all the required data is loaded
- Entity must ensure REST backward compatibility
Loader
- Loaders are supposed to load an entity(s), like stores fetch model(s)
- Loaders must take case of caching
> Tez UI: Create loader and entity classes
> ----------------------------------------
>
> Key: TEZ-2985
> URL: https://issues.apache.org/jira/browse/TEZ-2985
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Sreenath Somarajapuram
>
> Entity:
> - An entity would contain a model and defines it's complex relationship with other models
> - Differing from a model entities gets satisfied only when all the required data is loaded
> - Entity must ensure REST API backward compatibility
> Loader
> - Loaders are supposed to load an entity(s), like stores fetch model(s)
> - Loaders must take case of caching
> - In pages like 'All DAGs' without a limit. If tables do client side filtering after loading, we might end-up with lower number of records than loaded. Tables must be able to inform loader to load more more records.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)