You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by Thomas Weise <th...@datatorrent.com> on 2016/02/13 02:50:24 UTC
Malhar 3.3.1 patch release
There are a few critical fixes to the Kafka operators and idempotency
support that might be good to provide as patch release? Perhaps there are
other fixes in master that should go into it, too?
Thomas
Re: Malhar 3.3.1 patch release
Posted by Thomas Weise <th...@datatorrent.com>.
Here are some more:
https://issues.apache.org/jira/browse/APEXMALHAR-1973
https://issues.apache.org/jira/browse/APEXMALHAR-1970
https://issues.apache.org/jira/browse/APEXMALHAR-1984
https://issues.apache.org/jira/browse/APEXMALHAR-1983
On Mon, Feb 15, 2016 at 8:37 AM, Vlad Rozov <v....@datatorrent.com> wrote:
> It will be good to send list of candidate JIRAs to be included into 3.3.1
> release for the community to vote on. Currently I see
>
> 1. APEXMALHAR-1993 Committed offsets are not present in offset manager
> storage for kafka input operator
> <https://issues.apache.org/jira/browse/APEXMALHAR-1993>
>
> 1. APEXMALHAR-1990 Occasional concurrent modification exceptions from
> IdempotentStorageManager
> <https://issues.apache.org/jira/browse/APEXMALHAR-1990>
>
>
> Is this a full list? Any other candidates?
>
> Vlad
>
>
> On 2/15/16 00:15, Yogi Devendra wrote:
>
>> I assume that this is backed by some user who need these fixes and not
>> ready to upgrade to apex core 3.3.0.
>>
>> +1 if above assumption is true.
>>
>> ~ Yogi
>>
>> On 14 February 2016 at 05:11, Thomas Weise <th...@datatorrent.com>
>> wrote:
>>
>> That's correct, patch releases cannot upgrade dependencies to newer minor
>>> or major version.
>>>
>>> Also, these fixes should not force users to upgrade the Apex install.
>>>
>>> Thomas
>>>
>>> On Fri, Feb 12, 2016 at 8:04 PM, Yogi Devendra <yo...@apache.org>
>>> wrote:
>>>
>>> Instead of patch release should we have next minor release which would
>>>>
>>> also
>>>
>>>> have dependency change to depend on apex-core-3.3.0?
>>>>
>>>> I guess dependency change can't go in the patch release. Is that
>>>> correct?
>>>>
>>>> ~ Yogi
>>>>
>>>> On 13 February 2016 at 08:04, Pramod Immaneni <pr...@datatorrent.com>
>>>> wrote:
>>>>
>>>> +1 for 3.3.1
>>>>>
>>>>> On Fri, Feb 12, 2016 at 5:50 PM, Thomas Weise <th...@datatorrent.com>
>>>>> wrote:
>>>>>
>>>>> There are a few critical fixes to the Kafka operators and idempotency
>>>>>> support that might be good to provide as patch release? Perhaps there
>>>>>>
>>>>> are
>>>>
>>>>> other fixes in master that should go into it, too?
>>>>>>
>>>>>> Thomas
>>>>>>
>>>>>>
>
Re: Malhar 3.3.1 patch release
Posted by Vlad Rozov <v....@datatorrent.com>.
It will be good to send list of candidate JIRAs to be included into
3.3.1 release for the community to vote on. Currently I see
1. APEXMALHAR-1993 Committed offsets are not present in offset manager
storage for kafka input operator
<https://issues.apache.org/jira/browse/APEXMALHAR-1993>
1. APEXMALHAR-1990 Occasional concurrent modification exceptions from
IdempotentStorageManager
<https://issues.apache.org/jira/browse/APEXMALHAR-1990>
Is this a full list? Any other candidates?
Vlad
On 2/15/16 00:15, Yogi Devendra wrote:
> I assume that this is backed by some user who need these fixes and not
> ready to upgrade to apex core 3.3.0.
>
> +1 if above assumption is true.
>
> ~ Yogi
>
> On 14 February 2016 at 05:11, Thomas Weise <th...@datatorrent.com> wrote:
>
>> That's correct, patch releases cannot upgrade dependencies to newer minor
>> or major version.
>>
>> Also, these fixes should not force users to upgrade the Apex install.
>>
>> Thomas
>>
>> On Fri, Feb 12, 2016 at 8:04 PM, Yogi Devendra <yo...@apache.org>
>> wrote:
>>
>>> Instead of patch release should we have next minor release which would
>> also
>>> have dependency change to depend on apex-core-3.3.0?
>>>
>>> I guess dependency change can't go in the patch release. Is that correct?
>>>
>>> ~ Yogi
>>>
>>> On 13 February 2016 at 08:04, Pramod Immaneni <pr...@datatorrent.com>
>>> wrote:
>>>
>>>> +1 for 3.3.1
>>>>
>>>> On Fri, Feb 12, 2016 at 5:50 PM, Thomas Weise <th...@datatorrent.com>
>>>> wrote:
>>>>
>>>>> There are a few critical fixes to the Kafka operators and idempotency
>>>>> support that might be good to provide as patch release? Perhaps there
>>> are
>>>>> other fixes in master that should go into it, too?
>>>>>
>>>>> Thomas
>>>>>
Re: Malhar 3.3.1 patch release
Posted by Yogi Devendra <yo...@apache.org>.
I assume that this is backed by some user who need these fixes and not
ready to upgrade to apex core 3.3.0.
+1 if above assumption is true.
~ Yogi
On 14 February 2016 at 05:11, Thomas Weise <th...@datatorrent.com> wrote:
> That's correct, patch releases cannot upgrade dependencies to newer minor
> or major version.
>
> Also, these fixes should not force users to upgrade the Apex install.
>
> Thomas
>
> On Fri, Feb 12, 2016 at 8:04 PM, Yogi Devendra <yo...@apache.org>
> wrote:
>
> > Instead of patch release should we have next minor release which would
> also
> > have dependency change to depend on apex-core-3.3.0?
> >
> > I guess dependency change can't go in the patch release. Is that correct?
> >
> > ~ Yogi
> >
> > On 13 February 2016 at 08:04, Pramod Immaneni <pr...@datatorrent.com>
> > wrote:
> >
> > > +1 for 3.3.1
> > >
> > > On Fri, Feb 12, 2016 at 5:50 PM, Thomas Weise <th...@datatorrent.com>
> > > wrote:
> > >
> > > > There are a few critical fixes to the Kafka operators and idempotency
> > > > support that might be good to provide as patch release? Perhaps there
> > are
> > > > other fixes in master that should go into it, too?
> > > >
> > > > Thomas
> > > >
> > >
> >
>
Re: Malhar 3.3.1 patch release
Posted by Thomas Weise <th...@datatorrent.com>.
That's correct, patch releases cannot upgrade dependencies to newer minor
or major version.
Also, these fixes should not force users to upgrade the Apex install.
Thomas
On Fri, Feb 12, 2016 at 8:04 PM, Yogi Devendra <yo...@apache.org>
wrote:
> Instead of patch release should we have next minor release which would also
> have dependency change to depend on apex-core-3.3.0?
>
> I guess dependency change can't go in the patch release. Is that correct?
>
> ~ Yogi
>
> On 13 February 2016 at 08:04, Pramod Immaneni <pr...@datatorrent.com>
> wrote:
>
> > +1 for 3.3.1
> >
> > On Fri, Feb 12, 2016 at 5:50 PM, Thomas Weise <th...@datatorrent.com>
> > wrote:
> >
> > > There are a few critical fixes to the Kafka operators and idempotency
> > > support that might be good to provide as patch release? Perhaps there
> are
> > > other fixes in master that should go into it, too?
> > >
> > > Thomas
> > >
> >
>
Re: Malhar 3.3.1 patch release
Posted by Yogi Devendra <yo...@apache.org>.
Instead of patch release should we have next minor release which would also
have dependency change to depend on apex-core-3.3.0?
I guess dependency change can't go in the patch release. Is that correct?
~ Yogi
On 13 February 2016 at 08:04, Pramod Immaneni <pr...@datatorrent.com>
wrote:
> +1 for 3.3.1
>
> On Fri, Feb 12, 2016 at 5:50 PM, Thomas Weise <th...@datatorrent.com>
> wrote:
>
> > There are a few critical fixes to the Kafka operators and idempotency
> > support that might be good to provide as patch release? Perhaps there are
> > other fixes in master that should go into it, too?
> >
> > Thomas
> >
>
Re: Malhar 3.3.1 patch release
Posted by Pramod Immaneni <pr...@datatorrent.com>.
+1 for 3.3.1
On Fri, Feb 12, 2016 at 5:50 PM, Thomas Weise <th...@datatorrent.com>
wrote:
> There are a few critical fixes to the Kafka operators and idempotency
> support that might be good to provide as patch release? Perhaps there are
> other fixes in master that should go into it, too?
>
> Thomas
>