I think, if there is clear use case, it makes sense to document that in Jira.
For 1), it sounds like it requires some "state" to be preserved between job runs, something which is not available directly. This theoretically can be done with elasticsearch input reading latest previous result of the job, and then spark-sql computing difference between old and new value. This requires either custom elasticsearch input, or implementation of GRIFFIN-214 <https://issues.apache.org/jira/browse/GRIFFIN-214> in upstream. For 2), are you talking about profiling publishing MIN/MAX, or something more sophisticated? On Thu, Mar 7, 2019 at 6:11 AM William Guo <[email protected]> wrote: > Hi all, > > I translate the original email into english as following. > > ===== > Whether the following requirements will be considered in the griffin later > versions: > > > 1. monitoring year-over-year/month-over-month growth for some columns > 2. monitoring column value change range > > > Thank you > ===== > > > > On Wed, Mar 6, 2019 at 3:41 PM [email protected] <[email protected]> wrote: > > > griffin后期版本迭代中是否会考虑以下需求： > > > > 同一个表某一列或者几列的值的同步/环比监控。 > > 列的值域监控 > > > > 谢谢~ > > > > > > > > [email protected] > > >
