Hi Karan,

First, we need to check has griffin successfully finished. What persist
types did you configure in env.json? "log", "hdfs", "http"?
- "log": print the metrics in application log.
- "hdfs": the metrics will be persisted in hdfs path you've set.
- "http": post the metrics to the "api" you've set, which should be the
elasticsearch endpoint by default.

You can choose multiple of them.
If "http" is not configured correctly, post metrics to ES fails.
If "hdfs" is configured, but you can not get any metric persisted in the
"path", maybe griffin has not finish the calculation correctly.
If "log" is configured, you can get the application log from yarn:
    yarn logs -applicationId <appId> > applog
Then read the applog, find if there's any output metric calculated.
If there's no metric persisted by any type of your persist configuration,
you need to read the applog, and find the error message. Then you can show
it to me, I'll help you find it.

Thanks,
Lionel


On Fri, May 4, 2018 at 2:00 PM, Karan Gupta <[email protected]> wrote:

> Hi Lionel,
>
>
>
> While the Spark Application gets finished, I do not see any Index getting
> created in the elastic search, hence I do not see the data quality metrics
> getting populated.
>
> Could you help me out with a possible solution?
>
>
>
>
>
> Thank you,
>
> Karan Gupta
> ------------------------------
> Any comments or statements made in this email are not necessarily those of
> Tavant Technologies. The information transmitted is intended only for the
> person or entity to which it is addressed and may contain confidential
> and/or privileged material. If you have received this in error, please
> contact the sender and delete the material from any computer. All emails
> sent from or to Tavant Technologies may be subject to our monitoring
> procedures.
>

Reply via email to