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 2015/12/06 22:52:42 UTC
Next Malhar release (3.3.0)
There are 17 issues currently planned for 3.3.0:
https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
Downstream projects are interested in some of the changes.
Is there other work in progress that should go into this release?
Should we release in Dec?
Re: Next Malhar release (3.3.0)
Posted by Thomas Weise <th...@datatorrent.com>.
It's a completely new operator that should probably see some feedback and
go into next release.
On Tue, Jan 5, 2016 at 10:29 PM, Chinmay Kolhatkar <ch...@datatorrent.com>
wrote:
> Can this also be considered?
>
> https://issues.apache.org/jira/browse/APEXMALHAR-1963
>
> I've created a pull request for this.
>
>
> ~ Chinmay.
>
> On Wed, Jan 6, 2016 at 11:55 AM, Chandni Singh <ch...@datatorrent.com>
> wrote:
>
> > Can this go in as well? Will make the change by tonight.
> >
> > https://issues.apache.org/jira/browse/APEXMALHAR-1964
> >
> > On Tue, Jan 5, 2016 at 10:15 PM, Thomas Weise <th...@datatorrent.com>
> > wrote:
> >
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20APEXMALHAR%20AND%20fixVersion%20%3D%203.3.0%20ORDER%20BY%20status%20ASC
> > >
> > > APEXMALHAR-1904 should be done tomorrow
> > > APEXMALHAR-1892 will be looked at during the release process
> > > APEXMALHAR-1948 push to next release?
> > > APEXMALHAR-1950 rebase PR and merge
> > > APEXMALHAR-1936 push to next release
> > >
> > > Anything else that needs to be taken care of before cutting the RC?
> > >
> > >
> > > On Mon, Jan 4, 2016 at 11:46 PM, Thomas Weise <th...@datatorrent.com>
> > > wrote:
> > >
> > > > Most of the issues are resolved, the Kafka 0.9 support will make it
> > also.
> > > >
> > > > I would suggest that we move ahead and do the 3.3.0 release with Core
> > > > 3.2.0 as dependency, so that users can use the new features without
> > core
> > > > upgrade.
> > > >
> > > > Thoughts?
> > > >
> > > >
> > > > On Wed, Dec 9, 2015 at 2:36 AM, Tushar Gosavi <
> tushar@datatorrent.com>
> > > > wrote:
> > > >
> > > >> Hi Chandni,
> > > >>
> > > >> I have opened a pull request to change location of directory where
> > test
> > > >> files are kept.
> > > >> Now test do not create a directory under library.
> > > >>
> > > >> https://github.com/apache/incubator-apex-malhar/pull/121
> > > >>
> > > >> I could not reproduce the issue of test failure after running tests
> > > >> multiple times.
> > > >>
> > > >> - Tushar.
> > > >>
> > > >>
> > > >> On Tue, Dec 8, 2015 at 11:52 PM, Chandni Singh <
> > chandni@datatorrent.com
> > > >
> > > >> wrote:
> > > >>
> > > >> > https://malhar.atlassian.net/browse/MLHR-1901
> > > >> >
> > > >> > IMO this bug should be addressed before we release because right
> now
> > > >> > running the tests creates a folder right under library instead of
> > > >> target.
> > > >> > The test also fails in travis sometimes, so either we should mark
> it
> > > >> ignore
> > > >> > if it is not easy to fix.
> > > >> >
> > > >> > Thanks,
> > > >> > Chandni
> > > >> >
> > > >> > On Tue, Dec 8, 2015 at 10:09 AM, Siyuan Hua <
> siyuan@datatorrent.com
> > >
> > > >> > wrote:
> > > >> >
> > > >> > > There are 3 Kafka operator related work needs to be included in
> > the
> > > >> > release
> > > >> > > package
> > > >> > > https://malhar.atlassian.net/browse/MLHR-1928 is about
> > > >> fault-tolerant
> > > >> > > offset checkpointing
> > > >> > > https://malhar.atlassian.net/browse/MLHR-1925 is about safe
> > offset
> > > >> > storage
> > > >> > > for application restart
> > > >> > > and https://malhar.atlassian.net/browse/MLHR-1904 is about new
> > > >> operator
> > > >> > > with new Kafka API(assign API only) 0.9.0
> > > >> > >
> > > >> > > Thanks!
> > > >> > >
> > > >> > > On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <
> > > thomas@datatorrent.com>
> > > >> > > wrote:
> > > >> > >
> > > >> > > > There are 17 issues currently planned for 3.3.0:
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
> > > >> > > >
> > > >> > > > Downstream projects are interested in some of the changes.
> > > >> > > >
> > > >> > > > Is there other work in progress that should go into this
> > release?
> > > >> > > >
> > > >> > > > Should we release in Dec?
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
Re: Next Malhar release (3.3.0)
Posted by Chinmay Kolhatkar <ch...@datatorrent.com>.
Can this also be considered?
https://issues.apache.org/jira/browse/APEXMALHAR-1963
I've created a pull request for this.
~ Chinmay.
On Wed, Jan 6, 2016 at 11:55 AM, Chandni Singh <ch...@datatorrent.com>
wrote:
> Can this go in as well? Will make the change by tonight.
>
> https://issues.apache.org/jira/browse/APEXMALHAR-1964
>
> On Tue, Jan 5, 2016 at 10:15 PM, Thomas Weise <th...@datatorrent.com>
> wrote:
>
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20APEXMALHAR%20AND%20fixVersion%20%3D%203.3.0%20ORDER%20BY%20status%20ASC
> >
> > APEXMALHAR-1904 should be done tomorrow
> > APEXMALHAR-1892 will be looked at during the release process
> > APEXMALHAR-1948 push to next release?
> > APEXMALHAR-1950 rebase PR and merge
> > APEXMALHAR-1936 push to next release
> >
> > Anything else that needs to be taken care of before cutting the RC?
> >
> >
> > On Mon, Jan 4, 2016 at 11:46 PM, Thomas Weise <th...@datatorrent.com>
> > wrote:
> >
> > > Most of the issues are resolved, the Kafka 0.9 support will make it
> also.
> > >
> > > I would suggest that we move ahead and do the 3.3.0 release with Core
> > > 3.2.0 as dependency, so that users can use the new features without
> core
> > > upgrade.
> > >
> > > Thoughts?
> > >
> > >
> > > On Wed, Dec 9, 2015 at 2:36 AM, Tushar Gosavi <tu...@datatorrent.com>
> > > wrote:
> > >
> > >> Hi Chandni,
> > >>
> > >> I have opened a pull request to change location of directory where
> test
> > >> files are kept.
> > >> Now test do not create a directory under library.
> > >>
> > >> https://github.com/apache/incubator-apex-malhar/pull/121
> > >>
> > >> I could not reproduce the issue of test failure after running tests
> > >> multiple times.
> > >>
> > >> - Tushar.
> > >>
> > >>
> > >> On Tue, Dec 8, 2015 at 11:52 PM, Chandni Singh <
> chandni@datatorrent.com
> > >
> > >> wrote:
> > >>
> > >> > https://malhar.atlassian.net/browse/MLHR-1901
> > >> >
> > >> > IMO this bug should be addressed before we release because right now
> > >> > running the tests creates a folder right under library instead of
> > >> target.
> > >> > The test also fails in travis sometimes, so either we should mark it
> > >> ignore
> > >> > if it is not easy to fix.
> > >> >
> > >> > Thanks,
> > >> > Chandni
> > >> >
> > >> > On Tue, Dec 8, 2015 at 10:09 AM, Siyuan Hua <siyuan@datatorrent.com
> >
> > >> > wrote:
> > >> >
> > >> > > There are 3 Kafka operator related work needs to be included in
> the
> > >> > release
> > >> > > package
> > >> > > https://malhar.atlassian.net/browse/MLHR-1928 is about
> > >> fault-tolerant
> > >> > > offset checkpointing
> > >> > > https://malhar.atlassian.net/browse/MLHR-1925 is about safe
> offset
> > >> > storage
> > >> > > for application restart
> > >> > > and https://malhar.atlassian.net/browse/MLHR-1904 is about new
> > >> operator
> > >> > > with new Kafka API(assign API only) 0.9.0
> > >> > >
> > >> > > Thanks!
> > >> > >
> > >> > > On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <
> > thomas@datatorrent.com>
> > >> > > wrote:
> > >> > >
> > >> > > > There are 17 issues currently planned for 3.3.0:
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
> > >> > > >
> > >> > > > Downstream projects are interested in some of the changes.
> > >> > > >
> > >> > > > Is there other work in progress that should go into this
> release?
> > >> > > >
> > >> > > > Should we release in Dec?
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
Re: Next Malhar release (3.3.0)
Posted by Chandni Singh <ch...@datatorrent.com>.
Can this go in as well? Will make the change by tonight.
https://issues.apache.org/jira/browse/APEXMALHAR-1964
On Tue, Jan 5, 2016 at 10:15 PM, Thomas Weise <th...@datatorrent.com>
wrote:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20APEXMALHAR%20AND%20fixVersion%20%3D%203.3.0%20ORDER%20BY%20status%20ASC
>
> APEXMALHAR-1904 should be done tomorrow
> APEXMALHAR-1892 will be looked at during the release process
> APEXMALHAR-1948 push to next release?
> APEXMALHAR-1950 rebase PR and merge
> APEXMALHAR-1936 push to next release
>
> Anything else that needs to be taken care of before cutting the RC?
>
>
> On Mon, Jan 4, 2016 at 11:46 PM, Thomas Weise <th...@datatorrent.com>
> wrote:
>
> > Most of the issues are resolved, the Kafka 0.9 support will make it also.
> >
> > I would suggest that we move ahead and do the 3.3.0 release with Core
> > 3.2.0 as dependency, so that users can use the new features without core
> > upgrade.
> >
> > Thoughts?
> >
> >
> > On Wed, Dec 9, 2015 at 2:36 AM, Tushar Gosavi <tu...@datatorrent.com>
> > wrote:
> >
> >> Hi Chandni,
> >>
> >> I have opened a pull request to change location of directory where test
> >> files are kept.
> >> Now test do not create a directory under library.
> >>
> >> https://github.com/apache/incubator-apex-malhar/pull/121
> >>
> >> I could not reproduce the issue of test failure after running tests
> >> multiple times.
> >>
> >> - Tushar.
> >>
> >>
> >> On Tue, Dec 8, 2015 at 11:52 PM, Chandni Singh <chandni@datatorrent.com
> >
> >> wrote:
> >>
> >> > https://malhar.atlassian.net/browse/MLHR-1901
> >> >
> >> > IMO this bug should be addressed before we release because right now
> >> > running the tests creates a folder right under library instead of
> >> target.
> >> > The test also fails in travis sometimes, so either we should mark it
> >> ignore
> >> > if it is not easy to fix.
> >> >
> >> > Thanks,
> >> > Chandni
> >> >
> >> > On Tue, Dec 8, 2015 at 10:09 AM, Siyuan Hua <si...@datatorrent.com>
> >> > wrote:
> >> >
> >> > > There are 3 Kafka operator related work needs to be included in the
> >> > release
> >> > > package
> >> > > https://malhar.atlassian.net/browse/MLHR-1928 is about
> >> fault-tolerant
> >> > > offset checkpointing
> >> > > https://malhar.atlassian.net/browse/MLHR-1925 is about safe offset
> >> > storage
> >> > > for application restart
> >> > > and https://malhar.atlassian.net/browse/MLHR-1904 is about new
> >> operator
> >> > > with new Kafka API(assign API only) 0.9.0
> >> > >
> >> > > Thanks!
> >> > >
> >> > > On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <
> thomas@datatorrent.com>
> >> > > wrote:
> >> > >
> >> > > > There are 17 issues currently planned for 3.3.0:
> >> > > >
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
> >> > > >
> >> > > > Downstream projects are interested in some of the changes.
> >> > > >
> >> > > > Is there other work in progress that should go into this release?
> >> > > >
> >> > > > Should we release in Dec?
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: Next Malhar release (3.3.0)
Posted by Thomas Weise <th...@datatorrent.com>.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20APEXMALHAR%20AND%20fixVersion%20%3D%203.3.0%20ORDER%20BY%20status%20ASC
APEXMALHAR-1904 should be done tomorrow
APEXMALHAR-1892 will be looked at during the release process
APEXMALHAR-1948 push to next release?
APEXMALHAR-1950 rebase PR and merge
APEXMALHAR-1936 push to next release
Anything else that needs to be taken care of before cutting the RC?
On Mon, Jan 4, 2016 at 11:46 PM, Thomas Weise <th...@datatorrent.com>
wrote:
> Most of the issues are resolved, the Kafka 0.9 support will make it also.
>
> I would suggest that we move ahead and do the 3.3.0 release with Core
> 3.2.0 as dependency, so that users can use the new features without core
> upgrade.
>
> Thoughts?
>
>
> On Wed, Dec 9, 2015 at 2:36 AM, Tushar Gosavi <tu...@datatorrent.com>
> wrote:
>
>> Hi Chandni,
>>
>> I have opened a pull request to change location of directory where test
>> files are kept.
>> Now test do not create a directory under library.
>>
>> https://github.com/apache/incubator-apex-malhar/pull/121
>>
>> I could not reproduce the issue of test failure after running tests
>> multiple times.
>>
>> - Tushar.
>>
>>
>> On Tue, Dec 8, 2015 at 11:52 PM, Chandni Singh <ch...@datatorrent.com>
>> wrote:
>>
>> > https://malhar.atlassian.net/browse/MLHR-1901
>> >
>> > IMO this bug should be addressed before we release because right now
>> > running the tests creates a folder right under library instead of
>> target.
>> > The test also fails in travis sometimes, so either we should mark it
>> ignore
>> > if it is not easy to fix.
>> >
>> > Thanks,
>> > Chandni
>> >
>> > On Tue, Dec 8, 2015 at 10:09 AM, Siyuan Hua <si...@datatorrent.com>
>> > wrote:
>> >
>> > > There are 3 Kafka operator related work needs to be included in the
>> > release
>> > > package
>> > > https://malhar.atlassian.net/browse/MLHR-1928 is about
>> fault-tolerant
>> > > offset checkpointing
>> > > https://malhar.atlassian.net/browse/MLHR-1925 is about safe offset
>> > storage
>> > > for application restart
>> > > and https://malhar.atlassian.net/browse/MLHR-1904 is about new
>> operator
>> > > with new Kafka API(assign API only) 0.9.0
>> > >
>> > > Thanks!
>> > >
>> > > On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <th...@datatorrent.com>
>> > > wrote:
>> > >
>> > > > There are 17 issues currently planned for 3.3.0:
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
>> > > >
>> > > > Downstream projects are interested in some of the changes.
>> > > >
>> > > > Is there other work in progress that should go into this release?
>> > > >
>> > > > Should we release in Dec?
>> > > >
>> > >
>> >
>>
>
>
Re: Next Malhar release (3.3.0)
Posted by Thomas Weise <th...@datatorrent.com>.
Most of the issues are resolved, the Kafka 0.9 support will make it also.
I would suggest that we move ahead and do the 3.3.0 release with Core 3.2.0
as dependency, so that users can use the new features without core upgrade.
Thoughts?
On Wed, Dec 9, 2015 at 2:36 AM, Tushar Gosavi <tu...@datatorrent.com>
wrote:
> Hi Chandni,
>
> I have opened a pull request to change location of directory where test
> files are kept.
> Now test do not create a directory under library.
>
> https://github.com/apache/incubator-apex-malhar/pull/121
>
> I could not reproduce the issue of test failure after running tests
> multiple times.
>
> - Tushar.
>
>
> On Tue, Dec 8, 2015 at 11:52 PM, Chandni Singh <ch...@datatorrent.com>
> wrote:
>
> > https://malhar.atlassian.net/browse/MLHR-1901
> >
> > IMO this bug should be addressed before we release because right now
> > running the tests creates a folder right under library instead of target.
> > The test also fails in travis sometimes, so either we should mark it
> ignore
> > if it is not easy to fix.
> >
> > Thanks,
> > Chandni
> >
> > On Tue, Dec 8, 2015 at 10:09 AM, Siyuan Hua <si...@datatorrent.com>
> > wrote:
> >
> > > There are 3 Kafka operator related work needs to be included in the
> > release
> > > package
> > > https://malhar.atlassian.net/browse/MLHR-1928 is about fault-tolerant
> > > offset checkpointing
> > > https://malhar.atlassian.net/browse/MLHR-1925 is about safe offset
> > storage
> > > for application restart
> > > and https://malhar.atlassian.net/browse/MLHR-1904 is about new
> operator
> > > with new Kafka API(assign API only) 0.9.0
> > >
> > > Thanks!
> > >
> > > On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <th...@datatorrent.com>
> > > wrote:
> > >
> > > > There are 17 issues currently planned for 3.3.0:
> > > >
> > > >
> > > >
> > >
> >
> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
> > > >
> > > > Downstream projects are interested in some of the changes.
> > > >
> > > > Is there other work in progress that should go into this release?
> > > >
> > > > Should we release in Dec?
> > > >
> > >
> >
>
Re: Next Malhar release (3.3.0)
Posted by Tushar Gosavi <tu...@datatorrent.com>.
Hi Chandni,
I have opened a pull request to change location of directory where test
files are kept.
Now test do not create a directory under library.
https://github.com/apache/incubator-apex-malhar/pull/121
I could not reproduce the issue of test failure after running tests
multiple times.
- Tushar.
On Tue, Dec 8, 2015 at 11:52 PM, Chandni Singh <ch...@datatorrent.com>
wrote:
> https://malhar.atlassian.net/browse/MLHR-1901
>
> IMO this bug should be addressed before we release because right now
> running the tests creates a folder right under library instead of target.
> The test also fails in travis sometimes, so either we should mark it ignore
> if it is not easy to fix.
>
> Thanks,
> Chandni
>
> On Tue, Dec 8, 2015 at 10:09 AM, Siyuan Hua <si...@datatorrent.com>
> wrote:
>
> > There are 3 Kafka operator related work needs to be included in the
> release
> > package
> > https://malhar.atlassian.net/browse/MLHR-1928 is about fault-tolerant
> > offset checkpointing
> > https://malhar.atlassian.net/browse/MLHR-1925 is about safe offset
> storage
> > for application restart
> > and https://malhar.atlassian.net/browse/MLHR-1904 is about new operator
> > with new Kafka API(assign API only) 0.9.0
> >
> > Thanks!
> >
> > On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <th...@datatorrent.com>
> > wrote:
> >
> > > There are 17 issues currently planned for 3.3.0:
> > >
> > >
> > >
> >
> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
> > >
> > > Downstream projects are interested in some of the changes.
> > >
> > > Is there other work in progress that should go into this release?
> > >
> > > Should we release in Dec?
> > >
> >
>
Re: Next Malhar release (3.3.0)
Posted by Chandni Singh <ch...@datatorrent.com>.
https://malhar.atlassian.net/browse/MLHR-1901
IMO this bug should be addressed before we release because right now
running the tests creates a folder right under library instead of target.
The test also fails in travis sometimes, so either we should mark it ignore
if it is not easy to fix.
Thanks,
Chandni
On Tue, Dec 8, 2015 at 10:09 AM, Siyuan Hua <si...@datatorrent.com> wrote:
> There are 3 Kafka operator related work needs to be included in the release
> package
> https://malhar.atlassian.net/browse/MLHR-1928 is about fault-tolerant
> offset checkpointing
> https://malhar.atlassian.net/browse/MLHR-1925 is about safe offset storage
> for application restart
> and https://malhar.atlassian.net/browse/MLHR-1904 is about new operator
> with new Kafka API(assign API only) 0.9.0
>
> Thanks!
>
> On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <th...@datatorrent.com>
> wrote:
>
> > There are 17 issues currently planned for 3.3.0:
> >
> >
> >
> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
> >
> > Downstream projects are interested in some of the changes.
> >
> > Is there other work in progress that should go into this release?
> >
> > Should we release in Dec?
> >
>
Re: Next Malhar release (3.3.0)
Posted by Siyuan Hua <si...@datatorrent.com>.
There are 3 Kafka operator related work needs to be included in the release
package
https://malhar.atlassian.net/browse/MLHR-1928 is about fault-tolerant
offset checkpointing
https://malhar.atlassian.net/browse/MLHR-1925 is about safe offset storage
for application restart
and https://malhar.atlassian.net/browse/MLHR-1904 is about new operator
with new Kafka API(assign API only) 0.9.0
Thanks!
On Sun, Dec 6, 2015 at 1:52 PM, Thomas Weise <th...@datatorrent.com> wrote:
> There are 17 issues currently planned for 3.3.0:
>
>
> https://malhar.atlassian.net/issues/?jql=project%20%3D%20MLHR%20AND%20fixVersion%20%3D%203.3.0
>
> Downstream projects are interested in some of the changes.
>
> Is there other work in progress that should go into this release?
>
> Should we release in Dec?
>