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

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

I need to double confirm about this: {color:#14892c}some of the jobs are 
completing successfully now with metric files, but some of the rules still 
fail. {color:#333333}You mean all jobs of some rules like the null-count always 
failed? Or only some jobs of the null-count rule failed while some 
succeeded?{color}{color}

{color:#14892c}{color:#333333}If the former one, all the null-count rule jobs 
failed, we need to check the dq.json.{color}{color}

{color:#14892c}{color:#333333}If the latter one, that might be caused by the 
data difference among different partitions, like the data of 11:00 performs 
different from the data of 12:00, which may lead the failure of calculation, 
then we have to check the data.{color}{color}

> 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
>         Attachments: PLDataLineageLoad061818.csv
>
>
> 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