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

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

Yes, the backslashes are generated by UI, the code is around here: 
[https://github.com/apache/incubator-griffin/blob/griffin-0.2.0-incubating/ui/angular/src/app/measure/create-measure/pr/pr.component.ts#L291|https://github.com/apache/incubator-griffin/blob/griffin-0.2.0-incubating/ui/angular/src/app/measure/create-measure/pr/pr.component.ts#L291,]

But we've tested about this, it works well in our docker container.

I noticed that your livy version is 0.3.0 too, it should perform the same as 
ours.

If you want to fix this, you can have a try to fix it, you can ignore this 
step: 
[https://github.com/apache/incubator-griffin/blob/griffin-0.2.0-incubating/service/src/main/java/org/apache/griffin/core/job/SparkSubmitJob.java#L181|https://github.com/apache/incubator-griffin/blob/griffin-0.2.0-incubating/service/src/main/java/org/apache/griffin/core/job/SparkSubmitJob.java#L181,]
 * If this works, maybe our livy works in different way, or they're in 
different version.
 * If this brings error in livy's log, you can just remove all the backslashes 
in UI code around above link.

> 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