Re: UI roadmap questions

2018-09-13 Thread Lionel Liu
Hi Nick,

For profiling results rendering on UI, we're showing it in a table, because
it's not easy to put the profiling metrics with timestamp in one chart.
Maybe we could change our mind, to show it in a customized page or
something like that.

The other two requirements are not supported on UI now, it would be really
nice to have the features.

Looking forward to your contribution.

Thanks,
Lionel



On Fri, Sep 14, 2018 at 8:14 AM William Guo  wrote:

> hi Nick Sokolov,
>
> For the UI part, currently, it supports typical use cases.
> We are focus on backend features for now, but you are always welcome to
> contribute for UI to enable all backend features.
>
> It is apache way , just create the ticket and send us your PR and we will
> review and merge it.
>
> http://griffin.apache.org/docs/contribute.html
>
>
> Thanks,
> William
>
>
> On Fri, Sep 14, 2018 at 1:58 AM Nick Sokolov  wrote:
>
> > Hi all,
> >
> > We are considering to use Griffin in our project, and while there are not
> > major questions with the backend, looks like UI is missing some features
> we
> > are going to need for our use cases:
> > - showing profiling results in DQ metrics
> > - ability to create spark-sql measures
> > - possibly, the same for completeness measures
> > I'm fine to implement those on our side, however would like to
> doublecheck:
> > is anyone working/planning to work on those? Will these changes be
> welcome
> > by the community, or it's against current vision of project? In the end
> of
> > the day, it would be good for us to avoid reinventing the wheel or being
> > stuck in our fork incompatible with upstream.
> >
> > Thanks in advance!
> >
>


Re: UI roadmap questions

2018-09-13 Thread William Guo
hi Nick Sokolov,

For the UI part, currently, it supports typical use cases.
We are focus on backend features for now, but you are always welcome to
contribute for UI to enable all backend features.

It is apache way , just create the ticket and send us your PR and we will
review and merge it.

http://griffin.apache.org/docs/contribute.html


Thanks,
William


On Fri, Sep 14, 2018 at 1:58 AM Nick Sokolov  wrote:

> Hi all,
>
> We are considering to use Griffin in our project, and while there are not
> major questions with the backend, looks like UI is missing some features we
> are going to need for our use cases:
> - showing profiling results in DQ metrics
> - ability to create spark-sql measures
> - possibly, the same for completeness measures
> I'm fine to implement those on our side, however would like to doublecheck:
> is anyone working/planning to work on those? Will these changes be welcome
> by the community, or it's against current vision of project? In the end of
> the day, it would be good for us to avoid reinventing the wheel or being
> stuck in our fork incompatible with upstream.
>
> Thanks in advance!
>


UI roadmap questions

2018-09-13 Thread Nick Sokolov
Hi all,

We are considering to use Griffin in our project, and while there are not
major questions with the backend, looks like UI is missing some features we
are going to need for our use cases:
- showing profiling results in DQ metrics
- ability to create spark-sql measures
- possibly, the same for completeness measures
I'm fine to implement those on our side, however would like to doublecheck:
is anyone working/planning to work on those? Will these changes be welcome
by the community, or it's against current vision of project? In the end of
the day, it would be good for us to avoid reinventing the wheel or being
stuck in our fork incompatible with upstream.

Thanks in advance!