[ 
https://issues.apache.org/jira/browse/GRIFFIN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607886#comment-16607886
 ] 

Lionel Liu commented on GRIFFIN-190:
------------------------------------

Actually, in griffin-0.2.0-incubating, the parameters of "email" and "sms" are 
not supported in application, we didn't remove them from the code or in 
env.json, that leads some misunderstanding. You can just remove them from 
env.json, it will not make any difference.

We're using ElasticSearch as the default metric storage, thus users could 
leverage the alert function of ES for the notification, griffin will just focus 
on the DQ calculation.

In the latest version griffin-0.3.0-incubating, the "email" and "sms" 
parameters are removed. I think you can try that version, almost the same as 
0.2.0, with better config experience of spark job parameters for livy, and 
clearer job config structure. The latest version was released recently, the 
documents are not all updated yet, we're still working on it.

> Blank Health and DQ Metrics Screen
> ----------------------------------
>
>                 Key: GRIFFIN-190
>                 URL: https://issues.apache.org/jira/browse/GRIFFIN-190
>             Project: Griffin (Incubating)
>          Issue Type: Bug
>    Affects Versions: 0.2.0-incubating
>            Reporter: Cory Woytasik
>            Priority: Major
>
> Griffin is up and running.  We have both an accuracy measure and a profiling 
> measure that is set to run every minute via jobs.  When we click the chart 
> icon next to the job we receive a "no content" message.  When we click on the 
> Health link or DQ Metrics link they think for a second and then display a 
> blank screen.  We are thinking this might be ES related, but aren't 
> completely sure.  Need some help.  We assume it's a path or property setup 
> issue.  Here are the versions we are running:
> Hive - 3.1.0
> Elasticsearch - 5.3.1
> griffin - 0.2.0
> hadoop - 3.1.1
> livy - 0.3.0
> spark - 2.3.1
> Using postgres too



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to