Merge Python API
Locked
 
|
Hi,
The Python API pull request [1] has been open for quite some time now. I was wondering whether we are planning to merge it or not. I took a closer look at the Python API a few weeks ago and I think we should merge it to expose it to our users to collect feedback. I hope by merging it, we'll find additional contributors for it and we get more feedback. Since it will be located in the "flink-staging" module and we'll mark it as a beta component, there is not much risk that we break any existing code. Please give me some +1's if you want to merge the Python API PR. I'd like to merge it in the next 24 to 48 hours, depending on the feedback I'm getting in this thread here. [1] https://github.com/apache/flink/pull/202 |
|
|
I'm +1 for this
On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> wrote: > Hi, > > The Python API pull request [1] has been open for quite some time now. > > I was wondering whether we are planning to merge it or not. > I took a closer look at the Python API a few weeks ago and I think we > should merge it to expose it to our users to collect feedback. > I hope by merging it, we'll find additional contributors for it and we get > more feedback. > > Since it will be located in the "flink-staging" module and we'll mark it as > a beta component, there is not much risk that we break any existing code. > > Please give me some +1's if you want to merge the Python API PR. > I'd like to merge it in the next 24 to 48 hours, depending on the feedback > I'm getting in this thread here. > > > > > [1] https://github.com/apache/flink/pull/202 > |
|
|
+1 Let's merge it to flink-staging and get some people to use it.
On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> wrote: > I'm +1 for this > > On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> > wrote: > > > Hi, > > > > The Python API pull request [1] has been open for quite some time now. > > > > I was wondering whether we are planning to merge it or not. > > I took a closer look at the Python API a few weeks ago and I think we > > should merge it to expose it to our users to collect feedback. > > I hope by merging it, we'll find additional contributors for it and we > get > > more feedback. > > > > Since it will be located in the "flink-staging" module and we'll mark it > as > > a beta component, there is not much risk that we break any existing code. > > > > Please give me some +1's if you want to merge the Python API PR. > > I'd like to merge it in the next 24 to 48 hours, depending on the > feedback > > I'm getting in this thread here. > > > > > > > > > > [1] https://github.com/apache/flink/pull/202 > > > |
|
|
+1
2015-04-20 14:39 GMT+02:00 Maximilian Michels <[hidden email]>: > +1 Let's merge it to flink-staging and get some people to use it. > > On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> > wrote: > > > I'm +1 for this > > > > On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> > > wrote: > > > > > Hi, > > > > > > The Python API pull request [1] has been open for quite some time now. > > > > > > I was wondering whether we are planning to merge it or not. > > > I took a closer look at the Python API a few weeks ago and I think we > > > should merge it to expose it to our users to collect feedback. > > > I hope by merging it, we'll find additional contributors for it and we > > get > > > more feedback. > > > > > > Since it will be located in the "flink-staging" module and we'll mark > it > > as > > > a beta component, there is not much risk that we break any existing > code. > > > > > > Please give me some +1's if you want to merge the Python API PR. > > > I'd like to merge it in the next 24 to 48 hours, depending on the > > feedback > > > I'm getting in this thread here. > > > > > > > > > > > > > > > [1] https://github.com/apache/flink/pull/202 > > > > > > |
|
|
+1
On Mon, Apr 20, 2015 at 2:41 PM, Fabian Hueske <[hidden email]> wrote: > +1 > > 2015-04-20 14:39 GMT+02:00 Maximilian Michels <[hidden email]>: > > > +1 Let's merge it to flink-staging and get some people to use it. > > > > On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> > > wrote: > > > > > I'm +1 for this > > > > > > On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> > > > wrote: > > > > > > > Hi, > > > > > > > > The Python API pull request [1] has been open for quite some time > now. > > > > > > > > I was wondering whether we are planning to merge it or not. > > > > I took a closer look at the Python API a few weeks ago and I think we > > > > should merge it to expose it to our users to collect feedback. > > > > I hope by merging it, we'll find additional contributors for it and > we > > > get > > > > more feedback. > > > > > > > > Since it will be located in the "flink-staging" module and we'll mark > > it > > > as > > > > a beta component, there is not much risk that we break any existing > > code. > > > > > > > > Please give me some +1's if you want to merge the Python API PR. > > > > I'd like to merge it in the next 24 to 48 hours, depending on the > > > feedback > > > > I'm getting in this thread here. > > > > > > > > > > > > > > > > > > > > [1] https://github.com/apache/flink/pull/202 > > > > > > > > > > |
|
|
+1
On 20.04.2015 14:49, Gyula Fóra wrote: > +1 > > On Mon, Apr 20, 2015 at 2:41 PM, Fabian Hueske <[hidden email]> wrote: > >> +1 >> >> 2015-04-20 14:39 GMT+02:00 Maximilian Michels <[hidden email]>: >> >>> +1 Let's merge it to flink-staging and get some people to use it. >>> >>> On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> >>> wrote: >>> >>>> I'm +1 for this >>>> >>>> On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> The Python API pull request [1] has been open for quite some time >> now. >>>>> I was wondering whether we are planning to merge it or not. >>>>> I took a closer look at the Python API a few weeks ago and I think we >>>>> should merge it to expose it to our users to collect feedback. >>>>> I hope by merging it, we'll find additional contributors for it and >> we >>>> get >>>>> more feedback. >>>>> >>>>> Since it will be located in the "flink-staging" module and we'll mark >>> it >>>> as >>>>> a beta component, there is not much risk that we break any existing >>> code. >>>>> Please give me some +1's if you want to merge the Python API PR. >>>>> I'd like to merge it in the next 24 to 48 hours, depending on the >>>> feedback >>>>> I'm getting in this thread here. >>>>> >>>>> >>>>> >>>>> >>>>> [1] https://github.com/apache/flink/pull/202 >>>>> |
|
|
+1
On 20 April 2015 at 14:50, Timo Walther <[hidden email]> wrote: > +1 > > > On 20.04.2015 14:49, Gyula Fóra wrote: > >> +1 >> >> On Mon, Apr 20, 2015 at 2:41 PM, Fabian Hueske <[hidden email]> wrote: >> >> +1 >>> >>> 2015-04-20 14:39 GMT+02:00 Maximilian Michels <[hidden email]>: >>> >>> +1 Let's merge it to flink-staging and get some people to use it. >>>> >>>> On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> >>>> wrote: >>>> >>>> I'm +1 for this >>>>> >>>>> On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> >>>>> wrote: >>>>> >>>>> Hi, >>>>>> >>>>>> The Python API pull request [1] has been open for quite some time >>>>>> >>>>> now. >>> >>>> I was wondering whether we are planning to merge it or not. >>>>>> I took a closer look at the Python API a few weeks ago and I think we >>>>>> should merge it to expose it to our users to collect feedback. >>>>>> I hope by merging it, we'll find additional contributors for it and >>>>>> >>>>> we >>> >>>> get >>>>> >>>>>> more feedback. >>>>>> >>>>>> Since it will be located in the "flink-staging" module and we'll mark >>>>>> >>>>> it >>>> >>>>> as >>>>> >>>>>> a beta component, there is not much risk that we break any existing >>>>>> >>>>> code. >>>> >>>>> Please give me some +1's if you want to merge the Python API PR. >>>>>> I'd like to merge it in the next 24 to 48 hours, depending on the >>>>>> >>>>> feedback >>>>> >>>>>> I'm getting in this thread here. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> [1] https://github.com/apache/flink/pull/202 >>>>>> >>>>>> > |
|
|
In reply to this post by Gyula Fóra-2
+1 from me too, the presentation of the Python API seemed okay, plus that
having one more project in staging will not hurt. On Mon, Apr 20, 2015 at 2:49 PM, Gyula Fóra <[hidden email]> wrote: > +1 > > On Mon, Apr 20, 2015 at 2:41 PM, Fabian Hueske <[hidden email]> wrote: > > > +1 > > > > 2015-04-20 14:39 GMT+02:00 Maximilian Michels <[hidden email]>: > > > > > +1 Let's merge it to flink-staging and get some people to use it. > > > > > > On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> > > > wrote: > > > > > > > I'm +1 for this > > > > > > > > On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger < > [hidden email]> > > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > The Python API pull request [1] has been open for quite some time > > now. > > > > > > > > > > I was wondering whether we are planning to merge it or not. > > > > > I took a closer look at the Python API a few weeks ago and I think > we > > > > > should merge it to expose it to our users to collect feedback. > > > > > I hope by merging it, we'll find additional contributors for it and > > we > > > > get > > > > > more feedback. > > > > > > > > > > Since it will be located in the "flink-staging" module and we'll > mark > > > it > > > > as > > > > > a beta component, there is not much risk that we break any existing > > > code. > > > > > > > > > > Please give me some +1's if you want to merge the Python API PR. > > > > > I'd like to merge it in the next 24 to 48 hours, depending on the > > > > feedback > > > > > I'm getting in this thread here. > > > > > > > > > > > > > > > > > > > > > > > > > [1] https://github.com/apache/flink/pull/202 > > > > > > > > > > > > > > > |
|
In reply to this post by Timo Walther-2
+1
On Mon, Apr 20, 2015 at 2:50 PM, Timo Walther <[hidden email]> wrote: > +1 > > > On 20.04.2015 14:49, Gyula Fóra wrote: > >> +1 >> >> On Mon, Apr 20, 2015 at 2:41 PM, Fabian Hueske <[hidden email]> wrote: >> >> +1 >>> >>> 2015-04-20 14:39 GMT+02:00 Maximilian Michels <[hidden email]>: >>> >>> +1 Let's merge it to flink-staging and get some people to use it. >>>> >>>> On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> >>>> wrote: >>>> >>>> I'm +1 for this >>>>> >>>>> On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> >>>>> wrote: >>>>> >>>>> Hi, >>>>>> >>>>>> The Python API pull request [1] has been open for quite some time >>>>>> >>>>> now. >>> >>>> I was wondering whether we are planning to merge it or not. >>>>>> I took a closer look at the Python API a few weeks ago and I think we >>>>>> should merge it to expose it to our users to collect feedback. >>>>>> I hope by merging it, we'll find additional contributors for it and >>>>>> >>>>> we >>> >>>> get >>>>> >>>>>> more feedback. >>>>>> >>>>>> Since it will be located in the "flink-staging" module and we'll mark >>>>>> >>>>> it >>>> >>>>> as >>>>> >>>>>> a beta component, there is not much risk that we break any existing >>>>>> >>>>> code. >>>> >>>>> Please give me some +1's if you want to merge the Python API PR. >>>>>> I'd like to merge it in the next 24 to 48 hours, depending on the >>>>>> >>>>> feedback >>>>> >>>>>> I'm getting in this thread here. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> [1] https://github.com/apache/flink/pull/202 >>>>>> >>>>>> > |
|
|
+1, as I said on the Github PR
On Mon, Apr 20, 2015 at 3:00 PM, Till Rohrmann <[hidden email]> wrote: > +1 > > On Mon, Apr 20, 2015 at 2:50 PM, Timo Walther <[hidden email]> wrote: > >> +1 >> >> >> On 20.04.2015 14:49, Gyula Fóra wrote: >> >>> +1 >>> >>> On Mon, Apr 20, 2015 at 2:41 PM, Fabian Hueske <[hidden email]> wrote: >>> >>> +1 >>>> >>>> 2015-04-20 14:39 GMT+02:00 Maximilian Michels <[hidden email]>: >>>> >>>> +1 Let's merge it to flink-staging and get some people to use it. >>>>> >>>>> On Mon, Apr 20, 2015 at 2:21 PM, Kostas Tzoumas <[hidden email]> >>>>> wrote: >>>>> >>>>> I'm +1 for this >>>>>> >>>>>> On Mon, Apr 20, 2015 at 11:03 AM, Robert Metzger <[hidden email]> >>>>>> wrote: >>>>>> >>>>>> Hi, >>>>>>> >>>>>>> The Python API pull request [1] has been open for quite some time >>>>>>> >>>>>> now. >>>> >>>>> I was wondering whether we are planning to merge it or not. >>>>>>> I took a closer look at the Python API a few weeks ago and I think we >>>>>>> should merge it to expose it to our users to collect feedback. >>>>>>> I hope by merging it, we'll find additional contributors for it and >>>>>>> >>>>>> we >>>> >>>>> get >>>>>> >>>>>>> more feedback. >>>>>>> >>>>>>> Since it will be located in the "flink-staging" module and we'll mark >>>>>>> >>>>>> it >>>>> >>>>>> as >>>>>> >>>>>>> a beta component, there is not much risk that we break any existing >>>>>>> >>>>>> code. >>>>> >>>>>> Please give me some +1's if you want to merge the Python API PR. >>>>>>> I'd like to merge it in the next 24 to 48 hours, depending on the >>>>>>> >>>>>> feedback >>>>>> >>>>>>> I'm getting in this thread here. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> [1] https://github.com/apache/flink/pull/202 >>>>>>> >>>>>>> >> |
«
Return to (DEPRECATED) Apache Flink Mailing List archive.
|
1 view|%1 views
| Free forum by Nabble | Edit this page |