I'm still apprehensive about it, but don't mind trying it out. It's not
like it can break something.
On 24.07.2017 18:52, Ufuk Celebi wrote:
What's the conclusion of last weeks discussion here?
Fabian and Chesnay raised concerns about the introductory text. Are
you still concerned?
On Wed, Ju
Hello Flink, Calcite, and Beam dev lists!
Linked below is the second document I promised way back in April regarding
a collaborative spec for streaming SQL in Beam/Calcite/Flink (& apologies
for the delay; I thought I was nearly done a while back and then temporal
joins expanded to something much
Hi,
I have two streams reading from kafka, one for data and other for control.
The data stream is split by type and there are around six types. Each type
has its own processing logic and finally everything has to be merged to get
the collective state per device. I was thinking I could connect mul
I think a combination of techniques would be effective:
- identifying focus areas for the next release (e.g. see Robert's thread
about 1.4)
- emphasizing design discussion in advance of a PR
- assigning reviewers and a steward in a structured way
- using a label or assignment field to 'pass the bat
@Eron Review timeliness would be great to improve.
Some observation from the past year:
There were periods where some components in Flink were making slow progress
because all committers knowledgeable in those components were busy handling
pull requests that were opened against those components, b
This seems like a good step in establishing a better PR process. I believe
the process could be improved to ensure timely and targeted review by
component experts and committers.
On Mon, Jul 17, 2017 at 9:36 AM, Stephan Ewen wrote:
> Hi all!
>
> I have reflected a bit on the pull requests and o
What's the conclusion of last weeks discussion here?
Fabian and Chesnay raised concerns about the introductory text. Are
you still concerned?
On Wed, Jul 19, 2017 at 10:04 AM, Stephan Ewen wrote:
> @Chesnay:
>
> Put text into template => contributor will have to read it
> Put link to text into t
Aside from the release management aspect, shall we discuss the major themes
of 1.4?
On Thu, Jun 1, 2017 at 8:26 AM, Robert Metzger wrote:
> Hi all,
>
> Flink 1.2 was released on February 2, Flink 1.3 on June 1, which means
> we've managed to release Flink 1.3 in almost exactly 4 months!
>
> For
Dear Flink community,
Please vote on releasing the following candidate as Apache Flink-shaded
version 1.0.
The commit to be voted in:
https://gitbox.apache.org/repos/asf/flink-shaded/commit/290526022bb99a276220afd73d0c5ffb0eb2cc59
Branch:
release-1.0-rc2
The release artifacts to be voted on
Ufuk Celebi created FLINK-7258:
--
Summary: IllegalArgumentException in Netty bootstrap with large
memory state segment size
Key: FLINK-7258
URL: https://issues.apache.org/jira/browse/FLINK-7258
Project: F
Chesnay Schepler created FLINK-7257:
---
Summary: Extend flink-runtime checkstyle coverage to tests
Key: FLINK-7257
URL: https://issues.apache.org/jira/browse/FLINK-7257
Project: Flink
Issue T
Chesnay Schepler created FLINK-7256:
---
Summary: End-to-end tests should only be run after successful
compilation
Key: FLINK-7256
URL: https://issues.apache.org/jira/browse/FLINK-7256
Project: Flink
Chesnay Schepler created FLINK-7255:
---
Summary: ListStateDescriptor example uses wrong constructor
Key: FLINK-7255
URL: https://issues.apache.org/jira/browse/FLINK-7255
Project: Flink
Issue
I just merged the fixes for FLINK-7137 and FLINK-7177. All blockers are
resolved from the Table & SQL API side.
Regards,
Timo
Am 24.07.17 um 11:14 schrieb Aljoscha Krettek:
@Greg: I merged that.
It seems like all blockers are now either resolved or determined not to be
blocking for this rele
Chesnay Schepler created FLINK-7254:
---
Summary: java8 module pom disables checkstyle
Key: FLINK-7254
URL: https://issues.apache.org/jira/browse/FLINK-7254
Project: Flink
Issue Type: Bug
I've opened a PR to adjust the artifact names:
https://github.com/apache/flink-shaded/pull/17
Under the new scheme the asm artifact would be named
"flink-shaded-asm-5.0.4-1.0"
By default maven concatenates the artifactId and version with a dash,
hence no underscore.
On 23.07.2017 21:37, St
@Greg: I merged that.
It seems like all blockers are now either resolved or determined not to be
blocking for this release. I will try and cut the first RC now.
Best,
Aljoscha
> On 21. Jul 2017, at 19:07, Greg Hogan wrote:
>
> FLINK-7211 is a trivial change for excluding the gelly examples ja
I'm canceling the RC to fix the artifact versioning.
Greg raises a good point, and the required changes are minimal.
I will create another RC later today.
On 24.07.2017 10:22, Stephan Ewen wrote:
There is no real pressure, true.
I was simply checking the mandatory constraints for the release.
Stephan Ewen created FLINK-7253:
---
Summary: Remove all 'assume Java 8' code in tests
Key: FLINK-7253
URL: https://issues.apache.org/jira/browse/FLINK-7253
Project: Flink
Issue Type: Sub-task
Stephan Ewen created FLINK-7251:
---
Summary: Merge the flink-java8 project into flink-core
Key: FLINK-7251
URL: https://issues.apache.org/jira/browse/FLINK-7251
Project: Flink
Issue Type: Sub-tas
Stephan Ewen created FLINK-7252:
---
Summary: Remove Flink Futures or back them by CompletableFutures
Key: FLINK-7252
URL: https://issues.apache.org/jira/browse/FLINK-7252
Project: Flink
Issue Typ
Stephan Ewen created FLINK-7249:
---
Summary: Bump Java version in build plugind
Key: FLINK-7249
URL: https://issues.apache.org/jira/browse/FLINK-7249
Project: Flink
Issue Type: Sub-task
Stephan Ewen created FLINK-7250:
---
Summary: Drop the jdk8 build profile
Key: FLINK-7250
URL: https://issues.apache.org/jira/browse/FLINK-7250
Project: Flink
Issue Type: Sub-task
Repo
Tzu-Li (Gordon) Tai created FLINK-7248:
--
Summary: Invalid checkRestoredNullCheckpointWhenFetcherNotReady
test in FlinkKafkaConsumerBaseTest
Key: FLINK-7248
URL: https://issues.apache.org/jira/browse/FLINK-724
Chesnay Schepler created FLINK-7247:
---
Summary: Replace travis java 7 profiles
Key: FLINK-7247
URL: https://issues.apache.org/jira/browse/FLINK-7247
Project: Flink
Issue Type: Sub-task
There is no real pressure, true.
I was simply checking the mandatory constraints for the release. and leave
it to Chesnay to make the call whether to release or adjust the naming
scheme of the artifacts.
The other two points raised in the "improvements mail" are not really
important in any way.
26 matches
Mail list logo
