Hi Flavio,
shouldn't be a problem to include these issues in the release.
Cheers, Fabian
2016-05-25 17:42 GMT+02:00 Flavio Pompermaier :
> If it's ok for you I'd need also to merge FLINK-3901[1] and FLINK-3908[2]
>
> [1] https://github.com/apache/flink/pull/1989
> [2] https://github.com/apache/
If it's ok for you I'd need also to merge FLINK-3901[1] and FLINK-3908[2]
[1] https://github.com/apache/flink/pull/1989
[2] https://github.com/apache/flink/pull/2007
Best,
Flavio
On Wed, May 25, 2016 at 5:04 PM, Fabian Hueske wrote:
> Hi everybody,
>
> thanks for the feedback so far.
>
> I jus
Hi everybody,
thanks for the feedback so far.
I just went over JIRA and increased the priority of some of the issues I
listed (the TOP 6, out of which 1 is fixed, + FLINK-3723) to CRITICAL to
distinguish them from the rest.
I found two more critical issue that should be fixed:
- FLINK-3971: Inco
Hey all,
@Fabian: thanks for compiling the list of issues and trying out TPC-H I
think it would be nice to include the first 5 from your list in 1.1.0. What
about FLINK-3656 (re-working the tests)? Do we want to do this before the
release as well?
Great to see Timo willing to coordinate and Yijie
On Fri, May 20, 2016 at 3:32 PM, Timo Walther wrote:
> What are the plans for 1.1.0 release so far?
Hey Timo,
following the 3 months release schedule, a release would be due soon
(June 8th). My personal opinion is that exact date is probably a
little optimistic, but June sounds about right.
We
Hi Fabian,
thank you for summarizing the most important issues. I already worked on
FLINK-3152 / FLINK-3580 but stopped in favor of FLINK-3859. I will open
a PR for FLINK-3859 very soon, just need to rebase it onto the latest
validation layer and do some testing. Unfortunately I'm on vacation
Hi Fabian,
The priority seems reasonable to me. I skimmed through your TPCH branch and
find data type and related functions would be quite important to enable
most of TPC-H queries.
I would try out your TPC-H branch and pick up some issues you filed these
two days for the 1.1.0 release.
Hope thi
Hi everybody,
I'd like to start a discussion about blocking issues and outstanding
features of the Table API and SQL for the 1.1.0 release. As you probably
know, the Table API was completely reworked and ported to Apache Calcite.
Moreover, we added initial support for SQL on batch and streaming ta
