xingHu created FLINK-6790:
-
Summary: Flink Kafka Consumer Cannot Round Robin Fetch Records
Key: FLINK-6790
URL: https://issues.apache.org/jira/browse/FLINK-6790
Project: Flink
Issue Type: Bug
Hello all,
I am very interesting in Flink framework, especially development. Since I
joined a new company below, I have been fallen into OSS. I haven't taken a
chance to contribute to OSS, but I am happy if I would take an opportunity
to be a developer for Flicker.
I read "How to contribute" sect
Chesnay Schepler created FLINK-6789:
---
Summary: Remove duplicated test utility reducer in optimizer
Key: FLINK-6789
URL: https://issues.apache.org/jira/browse/FLINK-6789
Project: Flink
Issue
Chesnay Schepler created FLINK-6788:
---
Summary: Remove unused GenericFlatTypePostPass/AbstractSchema class
Key: FLINK-6788
URL: https://issues.apache.org/jira/browse/FLINK-6788
Project: Flink
Chesnay Schepler created FLINK-6787:
---
Summary: Job-/StoppableException should extend FlinkException
Key: FLINK-6787
URL: https://issues.apache.org/jira/browse/FLINK-6787
Project: Flink
Issu
What do you think about waiting with the release announcement for Flink
1.3.1 until next week.
IMHO the documentation is not in a good shape for a release annoucement
right now anyway.
Most of the new features of the Table API are not documented. Docs for
other features are missing as well o
Hi Stefano,
I implemented the overlap according to Calcite's implementation. Maybe
they changed the behavior in the mean time. I agree we should try to
stay in sync with Calcite. What do other DB vendors do? Feel free to
open an issue about this.
Regards,
Timo
Am 30.05.17 um 14:24 schrieb
Chesnay Schepler created FLINK-6786:
---
Summary: Remove duplicate QueryScopeInfoTest
Key: FLINK-6786
URL: https://issues.apache.org/jira/browse/FLINK-6786
Project: Flink
Issue Type: Improveme
Chesnay Schepler created FLINK-6785:
---
Summary: Ineffective checks in MetricRegistryTest
Key: FLINK-6785
URL: https://issues.apache.org/jira/browse/FLINK-6785
Project: Flink
Issue Type: Bug
Nico Kruber created FLINK-6784:
--
Summary: Add some notes about externalized checkpoints and the
difference to savepoints
Key: FLINK-6784
URL: https://issues.apache.org/jira/browse/FLINK-6784
Project: Fli
In several locations we have copied code from external projects, for
example
flink-scala-shell/src/main/java/org/apache/flink/api/java/JarHelper.java
links to the file from org.apache.xmlbeans/xmlbeans/2.4.0. We also have
copied from Apache's Calcite, Spark, and Hadoop.
None of these projects are
Yes, FLINK-6783 might even have been a release blocker…. It’s a new feature
that simply doesn’t work in most cases.
> On 31. May 2017, at 14:51, Timo Walther wrote:
>
> We should also include FLINK-6783. It seems that WindowedStream::aggregate is
> broken right now.
>
>
> Am 31.05.17 um 14:3
We should also include FLINK-6783. It seems that
WindowedStream::aggregate is broken right now.
Am 31.05.17 um 14:31 schrieb Timo Walther:
I merged all Table API related PRs.
I'm also fine with a 1.3.1 release this or next week.
Am 31.05.17 um 14:08 schrieb Till Rohrmann:
I would be ok to
Dawid Wysakowicz created FLINK-6783:
---
Summary: Wrongly extracted TypeInformations for
WindowedStream::aggregate
Key: FLINK-6783
URL: https://issues.apache.org/jira/browse/FLINK-6783
Project: Flink
I merged all Table API related PRs.
I'm also fine with a 1.3.1 release this or next week.
Am 31.05.17 um 14:08 schrieb Till Rohrmann:
I would be ok to quickly release 1.3.1 once the the respective PRs have
been merged.
Just for your information, I'm not yet through with the testing of the typ
Thanks a lot for all your responses on the point Till raised.
It seems that we have an agreement to release this RC as Flink 1.3.0.
I'll include a note into the release announcement regarding the state
descriptor issue.
Thanks also for all the release testing and the votes.
+1 votes:
- Chesnay
-
I would be ok to quickly release 1.3.1 once the the respective PRs have
been merged.
Just for your information, I'm not yet through with the testing of the type
serializer upgrade feature, though.
Cheers,
Till
On Wed, May 31, 2017 at 12:14 PM, Stefan Richter <
s.rich...@data-artisans.com> wrote:
+1 for releasing now and providing a 1.3.1 release soon.
> Am 31.05.2017 um 11:02 schrieb Gyula Fóra :
>
> Hi All,
>
> I also lean towards getting the release out as soon as possible given that
> it had been delayed quite a bit and there is no major issue without a
> straightforward workaround (
Hi All,
I also lean towards getting the release out as soon as possible given that
it had been delayed quite a bit and there is no major issue without a
straightforward workaround (agreeing with Nico and Kostas). I am sure once
people will start using the new features we will see more issues that
Hi all,
I also tend to agree with the argument that says a release should be out
as soon as possible, given that 1) it improves usability/functionality and
2) at a minimum, it does not include new known bugs. The arguments are
more or less aligned with Nico’s response on the matter.
Focusing on
Nico Kruber created FLINK-6782:
--
Summary: Update savepoint documentation
Key: FLINK-6782
URL: https://issues.apache.org/jira/browse/FLINK-6782
Project: Flink
Issue Type: Sub-task
Compo
I agree with Robert that this could be fixed in a bugfix release, but
I really don't like immediately starting a new 1.3.1 vote a day after
the 1.3.0 vote ends. I think it potentially gives a bad/sloppy
impression to our users.
Therefore, I lean towards cancelling this RC and creating a new one
wi
IMHO, any release that improves things and does not break anything is worth
releasing and should not be blocked on bugs that it did not cause.
There will always be a next (minor/major) release that may fix this at a later
time, given that the time between releases is not too high.
Consider someo
Maximilian Bode created FLINK-6781:
--
Summary: Make fetch size configurable in JDBCInputFormat
Key: FLINK-6781
URL: https://issues.apache.org/jira/browse/FLINK-6781
Project: Flink
Issue Type:
Moreover it looks to me as if FLINK-6780 can be fixed without touching the
API, i.e., it can be fixed in 1.3.1.
Haohui, do you think that's correct?
Thanks, Fabian
2017-05-31 8:56 GMT+02:00 Timo Walther :
> I don't think that FLINK-6780 is a blocker, because the Table API is still
> a new feat
25 matches
Mail list logo
