Hi Vishnu,
no, queryable state would not be part of the 1.1 release according to
Robert's proposal.
IMO, adding a major feature like queryable state shortly before a release
is not a good idea and likely to delay the release or cause problems later.
Major features need a bit of exposure in the master branch before including
them in a release.
The open PR for queryable state (#2051) should be merged after the release
branch was forked off.
Best, Fabian
2016-06-16 13:18 GMT+02:00 Vishnu Viswanath <vishnu.viswanat...@gmail.com>:
> Hi,
>
> Will queryable state available in 1.1.0?
>
> Thanks,
> Vishnu
>
> On Thursday, 16 June 2016, Aljoscha Krettek <aljos...@apache.org> wrote:
>
> > Hi,
> > +1 for releasing what we have now and making it rock solid.
> >
> > The support for merging windows (session windows) is also new, btw. :-)
> >
> > Cheers,
> > Aljoscha
> >
> > On Thu, 16 Jun 2016 at 11:12 Maximilian Michels <m...@apache.org
> > <javascript:;>> wrote:
> >
> > > Hi Robert, hi Henry,
> > >
> > > +1 for a 1.1.0 release soon! We have enough new features that justify
> > > a major release.
> > >
> > > @Henry We have plans to extend the ResourceManager to interact with
> > > the Scheduler which will be a prerequisite for dynamic scaling. I
> > > think this is out of scope for 1.1.0. The upcoming Mesos integration
> > > won't require additional refactoring of the ResourceManager. Instead,
> > > we will create a new "Dispatcher" component that takes care of
> > > bootstrapping the initial node with the JobManager/ResourceManager.
> > > From there on, everything will be handled by the Mesos
> > > ResourceManager. I recently discussed this with Eron (CC) who came up
> > > with this design and he plans to publish it to the mailing list soon.
> > >
> > > How about listing relevant JIRA issues here? "Half Merged" is kind of
> > > hard to get for people who are not involved in the different
> > > components.
> > >
> > > The Cassandra adapter seems like a pretty important thing to have for
> > > the next release. In addition, I would like to merge FLINK-3667 and
> > > FLINK-3937. Robert is doing a review at the moment :) Those are a)
> > > refactoring of the command-line and client classes b) adding
> > > capability to resume cluster programmatically.
> > >
> > > Then we should also have a look at any other critical/major bugs listed
> > in
> > > JIRA.
> > >
> > > Cheers,
> > > Max
> > >
> > > On Wed, Jun 15, 2016 at 10:50 PM, Henry Saputra <
> henry.sapu...@gmail.com
> > <javascript:;>>
> > > wrote:
> > > > Hi Robert,
> > > >
> > > > Thanks for staying the discussion.
> > > >
> > > > Do you know if there any open tasks for the Resource Manager left?
> > > >
> > > > That is probably needed for Mesos integration?
> > > >
> > > > - Henry
> > > >
> > > > On Wed, Jun 15, 2016 at 12:55 PM, Robert Metzger <
> rmetz...@apache.org
> > <javascript:;>>
> > > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Flink 1.0.0 was released early March, so three months have passed
> and
> > I
> > > >> think we should start discussing the scope of the next major release
> > > >> (1.1.0).
> > > >>
> > > >> From a high level point of view, we've added the following new
> > features:
> > > >> in master:
> > > >> - Table API Refactoring, SQL, StreamSQL
> > > >> - The metrics system
> > > >> - Kinesis Connector
> > > >> - Persistent file sources for streaming
> > > >>
> > > >> Half merged:
> > > >> - Resource manager refactoring
> > > >>
> > > >> Unmerged features:
> > > >> - Cassandra connector
> > > >> - Key groups ("rescaling from savepoints")
> > > >> - Queryable state
> > > >>
> > > >> I'm pretty sure I forgot many other features / pull requests, please
> > > post
> > > >> them to this thread. I'll collect them and create a Wiki page out of
> > it.
> > > >>
> > > >> Some immediate TODOs for us:
> > > >> - Which of the unmerged features are we going to add to the release?
> > > >> - Which blockers do we need to address before releasing?
> > > >> - Are there any volunteers for the release manager?
> > > >>
> > > >>
> > > >> Regards,
> > > >> Robert
> > > >>
> > >
> >
>
>
> --
> Thanks and Regards,
> Vishnu Viswanath,
> *www.vishnuviswanath.com <http://www.vishnuviswanath.com>*
>
