Re: [DISCUSS] Update Roadmap

>>>> F: +61 2 9292 6444 >>>>> >>>>> W: quantium.com.au <http://www.quantium.com.au> >>>>> -- >>>>> >>>>> linkedin.com/company/quantium >>>>> <http://www.linkedin.com/compa

Re: [DISCUSS] Update Roadmap

g attachments, may be confidential >>> information. If you are not the intended recipient, any use, disclosure or >>> copying of the information is unauthorised. If you have received this email >>> in error, we would be grateful if you would notify us immediately by email

Re: [DISCUSS] Update Roadmap

mail >> in error, we would be grateful if you would notify us immediately by email >> reply, phone (+ 61 2 9292 6400) or fax (+ 61 2 9292 6444) and delete the >> message from your system. >> >> >> >> *From:* Nikolay Voronchikhin [mailto:nvoronchik...@gmail.com] >> *Sent:* Tues

RE: [DISCUSS] Update Roadmap

44) and delete the > message from your system. > > > > *From:* Nikolay Voronchikhin [mailto:nvoronchik...@gmail.com] > *Sent:* Tuesday, 22 March 2016 11:39 AM > *To:* users@zeppelin.incubator.apache.org > *Subject:* Re: [DISCUSS] Update Roadmap > > > > Hi Zeppeli

RE: [DISCUSS] Update Roadmap

, 22 March 2016 11:39 AM To: users@zeppelin.incubator.apache.org Subject: Re: [DISCUSS] Update Roadmap Hi Zeppelin Users and Developers, Do you know if MapR will be adding Zeppelin to its roadmap for the next version after MapR 5.1? We see in Hue 3.9 that it provides notebooks for R Shell, Python Shell

Re: [DISCUSS] Update Roadmap

Hi Zeppelin Users and Developers, Do you know if MapR will be adding Zeppelin to its roadmap for the next version after MapR 5.1? We see in Hue 3.9 that it provides notebooks for R Shell, Python Shell, PySpark, SparkR, Hive SQL, Impala SQL, and Spark SQL, but no Drill SQL notebook. We are

Re: [DISCUSS] Update Roadmap

Shabeel, thanks for the feedback about rest api and custom id. that might help avoid multiple rest api calls. Thanks everyone for valuable feedback. Looks like all we're going to the same direction. I have updated wiki. https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap Please

Re: [DISCUSS] Update Roadmap

Also we need better rest api support for creating and fetching the notebooks and paragraphs. for example if I can set custom defined notebookid and paragraphid , we can avoid multiple rest api calls. http://localhost:8080/#/notebook/ /paragraph/?asIframe should return me error if notebook or

Re: [DISCUSS] Update Roadmap

+1 on @rick. quality is really important... I am still encountering bugs consistently On Tue, Mar 1, 2016 at 10:16 AM, TEJA SRIVASTAV wrote: > +1 on @rick > > On Tue, Mar 1, 2016 at 11:26 PM Benjamin Kim wrote: > >> I see in the Enterprise section

Re: [DISCUSS] Update Roadmap

+1 on @rick On Tue, Mar 1, 2016 at 11:26 PM Benjamin Kim wrote: > I see in the Enterprise section that multi-tenancy will be included, will > this have user impersonation too? In this way, the user executing will be > the user owning the process. > > On Mar 1, 2016, at 12:51

Re: [DISCUSS] Update Roadmap

I see in the Enterprise section that multi-tenancy will be included, will this have user impersonation too? In this way, the user executing will be the user owning the process. > On Mar 1, 2016, at 12:51 AM, Shabeel Syed wrote: > > +1 > > Hi Tamas, >Pluggable

Re: [DISCUSS] Update Roadmap

@Vinayak, @Eran, @Benjamin, @Guilherme, @Sourav, @Rick Now I can see a lot of demands around enterprise level job scheduling. Either external or built-in, I completely agree having enterprise level job scheduling support on the roadmap. ZEPPELIN-137

Re: [DISCUSS] Update Roadmap

Hi, For one, I know that there is rudimentary scheduling built into Zeppelin already (at least I fixed a bug in the test for a scheduling feature a few months ago). But another point is, that Zeppelin should also focus on quality, reproduceability and portability. Although this doesn't offer

Re: [DISCUSS] Update Roadmap

I do agree with Vinayak. It need not be coupled with Oozie. Rather one should be able to call it from any scheduler typically used in enterprise level. May be support for BPML. I believe the existing ability to call/execute a Zeppelin Notebook or a specific paragraph within a notebook using REST

Re: [DISCUSS] Update Roadmap

@Eran Witkon, Thanks for the suggestion Eran. I concur with your thought. If Zepplin can be integrated with oozie, that would be wonderful. Users will also be able to leverage their Oozie skills. This would be promising for now. However, in the future Hadoop might not necessarily be installed in

Re: [DISCUSS] Update Roadmap

I agree. Jobs schedulling should be a core feature. Em 29 de fev de 2016 12:15, "Benjamin Kim" escreveu: > I concur with this suggestion. In the enterprise, management would like to > see scheduled runs to be tracked, monitored, and given SLA constraints for > the mission

Re: [DISCUSS] Update Roadmap

This is a great list. In the enterprise ready section, what do you think about adding "High Availability and Disaster Recovery"? We can start with updating the documentation with best practices and scripts for a cold standby solution and work towards active-active

Re: [DISCUSS] Update Roadmap

I concur with this suggestion. In the enterprise, management would like to see scheduled runs to be tracked, monitored, and given SLA constraints for the mission critical. Alerts and notifications are crucial for DevOps to respond with error clarification within it. If the Zeppelin notebooks

Re: [DISCUSS] Update Roadmap

@Vinayak Agrawal I would suggest adding the ability to connect zeppelin to existing scheduling tools\workflow tools such as https://oozie.apache.org/. this requires betters hooks and status reporting but doesn't make zeppeling and ETL\scheduler tool by itself/ On Mon, Feb 29, 2016 at 10:21 AM

Re: [DISCUSS] Update Roadmap

Moon, The new roadmap looks very promising. I am very happy to see security in the list. I have some suggestions regarding Enterprise Ready features: 1. Job Scheduler - Can this be improved? Currently the scheduler can be used with Cron expression or a pre-set time. But in an enterprise solution,

Re: [DISCUSS] Update Roadmap

Zhong Wang, Right, Folder support would be quite useful. Thanks for the opinion. Hope i can finish the work pr-190 . Sourav, Regarding concurrent running, Zeppelin doesn't have limitation of run paragraph/query concurrently. Interpreter can

Re: [DISCUSS] Update Roadmap

nal message > From: moon soo Lee <m...@apache.org> > Date: 02/27/2016 3:48 PM (GMT-05:00) > To: users@zeppelin.incubator.apache.org, d...@zeppelin.incubator.apache.org > Subject: [DISCUSS] Update Roadmap > > Hi Zeppelin users and developers, > > The roadmap we

Re: [DISCUSS] Update Roadmap

Sourav: I think this newly merged PR can help you https://github.com/apache/incubator-zeppelin/pull/703#issuecomment-185582537 On Sat, Feb 27, 2016 at 1:46 PM, Sourav Mazumder < sourav.mazumde...@gmail.com> wrote: > Hi Moon, > > This looks great. > > My only suggestion would be to include a

Re: [DISCUSS] Update Roadmap

This is awesome! Really glad to see that the roadmap is adjusted based on the community's needs. One feature I hope to see in 0.6.0 is folder support, which can benefit both "UX improvement" and "Multi-tenacy". Zhong On Sat, Feb 27, 2016 at 1:46 PM, Sourav Mazumder < sourav.mazumde...@gmail.com>

Re: [DISCUSS] Update Roadmap

Hi Moon, This looks great. My only suggestion would be to include a PR/feature - Support for Running Concurrent paragraphs/queries in Zeppelin. Right now if more than one user tries to run paragraphs in multiple notebooks concurrently through a single Zeppelin instance (and single interpreter

[DISCUSS] Update Roadmap

Hi Zeppelin users and developers, The roadmap we have published at https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap is almost 9 month old, and it doesn't reflect where the community goes anymore. It's time to update. Based on mailing list, jira issues, pullrequests,