Re: Merging the experimental API Framework

2016-11-29 Thread Alex Van Boxel
Although I haven't had the time to dive deep into API (sorry Bolke) I do want to be part of the discussion. I hope to have a look at it soon. On Tue, Nov 29, 2016 at 10:43 AM Bolke de Bruin wrote: > Flask App Builder looks great at a first glance and experience counts > obviously, though I have

Re: Merging the experimental API Framework

2016-11-29 Thread Bolke de Bruin
Flask App Builder looks great at a first glance and experience counts obviously, though I have several concerns: Authentication - The Hadoop ecosystem, especially the on premise installs, is dependent for its security integration on Kerberos. FAB out of the box does not support this. - In addit

Re: Merging the experimental API Framework

2016-11-28 Thread Maxime Beauchemin
It works very well. For Superset (aka Caravel) we're mostly in the React / async world while using FAB as an async REST backend, and still leveraging the CRUD interface where it makes sense. It's nice to be able to define roles as collection of perms that affect both the REST api and the UI consist

Re: Merging the experimental API Framework

2016-11-28 Thread Li Xuan Ji
Max, How well does FAB support building pages that use XHR to consume a REST api, instead of doing templating on the backend? We already have some ad-hoc XHR in airflow, and backend templating is the reason large DAG graph/tree views don't render (and probably other things I missed). It might be

Re: Merging the experimental API Framework

2016-11-28 Thread Maxime Beauchemin
Glad to see this! On my side I've been playing around trying to use Flask App Builder (just obtained committer status on the project) which covers some out of the box CRUD REST API for models and a authentication/role/permission framework that would allow for a multi-tenant UI / API with arbitrary

Re: Merging the experimental API Framework

2016-11-28 Thread Andrew Phillips
Just wanted to say this is very exciting, thank you Bolke :). Big +1 to that. Thanks, Bolke! ap

Re: Merging the experimental API Framework

2016-11-28 Thread Bolke de Bruin
There is some work on the wiki. However, I found out that it needs quite a lot of experimenting to found out the right way to approach things. Hence marking this as experimental. I think it needs a bit more experimenting, before we get to a stabilized API design doc. I’m also asking the communit

Re: Merging the experimental API Framework

2016-11-28 Thread siddharth anand
Bolke, Thanks for kicking this off. Is there already a design document for this? If not, can you create one? It makes sense to have a design document for this to connect multiple PRs. You can also add the information above to the same wiki -- The mailing list is not always super friendly for histo

Re: Merging the experimental API Framework

2016-11-28 Thread Dan Davydov
Just wanted to say this is very exciting, thank you Bolke :). On Mon, Nov 28, 2016 at 10:50 AM, Bolke de Bruin wrote: > All, > > After a few weeks of work I have finalized the implementation of a Rest > API Framework. Out of the box it supports Kerberos authentication, which is > now fully end t