[
https://issues.apache.org/jira/browse/GRIFFIN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Yao closed GRIFFIN-78.
----------------------------
Resolution: Fixed
Fix Version/s: 0.2.0-incubating
Solved.
> Manage job basic info by griffin rather than quartz
> ---------------------------------------------------
>
> Key: GRIFFIN-78
> URL: https://issues.apache.org/jira/browse/GRIFFIN-78
> Project: Griffin (Incubating)
> Issue Type: Improvement
> Components: accuracy-batch
> Affects Versions: 0.2.0-incubating
> Reporter: Kevin Yao
> Fix For: 0.2.0-incubating
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> In griffin now,jobs info is completely managed by quartz.Sometimes it is
> inconvenient for us to get basic job info and delete job,because the
> structure for quartz table is relatively complex.Therefore,We decide to
> create a simple table in griffin to manage job basic info for different job
> type.
> Our solution:
> 1.we create a base table called job.
> 2.Different job type can inherit the base table.They will be mapped in
> a single table.
> 3.This approach makes polymorphic queries very efficient and provides
> the best performance.But it also has some drawbacks. The attributes of all
> entities are mapped to the same database table. Each record uses only a
> subset of the available columns and sets the rest of them to null. You can,
> therefore, not use not null constraints on any column that isn’t mapped to
> all entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
