Jun Zhang created FLINK-18479:
-
Summary: can not commit partition when set partition time
Key: FLINK-18479
URL: https://issues.apache.org/jira/browse/FLINK-18479
Project: Flink
Issue Type: Bug
+1 (binding)
Checks:
- built from sources
-verified signatures & no binaries in the source archive
- run all tests locally (mvn clean install)
here I had a couple of problems:
* https://issues.apache.org/jira/browse/FLINK-18476
*
+1
- verified hash of source release
- verified signature of source release
- source release compiles (with Scala 2.11)
- examples run without spurious log output (errors, exceptions)
I can confirm that log scrolling doesn't work on Firefox, though it
never has.
I would also feel better
Aljoscha Krettek created FLINK-18478:
Summary: AvroDeserializationSchema does not work with types
generated by avrohugger
Key: FLINK-18478
URL: https://issues.apache.org/jira/browse/FLINK-18478
Hi all,
As far as the issue that Chesnay mentioned that leads to a "Caused by:
org.apache.flink.api.common.InvalidProgramException:" for DataSet
examples with print() collect() or count() as sink, this was a
semi-intensional side-effect of the application mode. Before, in these
cases, the output
Dawid Wysakowicz created FLINK-18477:
Summary: ChangelogSocketExample does not work
Key: FLINK-18477
URL: https://issues.apache.org/jira/browse/FLINK-18477
Project: Flink
Issue Type: Bug
Dawid Wysakowicz created FLINK-18476:
Summary: PythonEnvUtilsTest#testStartPythonProcess fails locally
Key: FLINK-18476
URL: https://issues.apache.org/jira/browse/FLINK-18476
Project: Flink
+1
Aljoscha
On 01.07.20 15:14, Tzu-Li (Gordon) Tai wrote:
+1
On Wed, Jul 1, 2020, 8:57 PM Cranmer, Danny wrote:
Hi all,
I'd like to start a voting thread for FLIP-128 [1], which we've reached
consensus
in [2].
This voting will be open for minimum 3 days till 13:00 UTC, July 4th.
Wow, that is one thorough FLIP! I didn't fully go into all the technical
details but I think the general direction of this is good. If no one
objects I'd say we can proceed to voting and figure out the technical
details during implementation/review (if any remain unclear).
Best,
Aljoscha
On
+1 (binding)
Checks:
- source archive compiles
- checked artifacts in staging repo
- flink-azure-fs-hadoop-1.11.0.jar seems to have a correct NOTICE file
- versions in pom seem correct
- checked some other jars
- deployed Flink on YARN on Azure HDInsight (which uses Hadoop 3.1.1)
-
Dawid Wysakowicz created FLINK-18475:
Summary: Scrolling does not work in logs view
Key: FLINK-18475
URL: https://issues.apache.org/jira/browse/FLINK-18475
Project: Flink
Issue Type: Bug
Robert Metzger created FLINK-18474:
--
Summary: Flink on YARN produces WARN log statements about the
configuration
Key: FLINK-18474
URL: https://issues.apache.org/jira/browse/FLINK-18474
Project:
It is clear there are a lot of edge cases with temporal tables that need to
be carefully thought out. If we go at this problem from the perspective of
what a majority of users need to accomplish in production, I believe there
is a simpler version of this problem we can solve that can be expanded
Hi Zhijiang,
The performance degradation manifests in backpressure which leads to
growing backlog in the source. I switched a few times between 1.10 and 1.11
and the behavior is consistent.
The DAG is:
KinesisConsumer -> (Flat Map, Flat Map, Flat Map) forward
->
Hi everyone,
well, this got complicated :) Let me add my thoughts:
* Temporal Table Joins are already quite hard to understand for many users.
If need be, we should trade off for simplicity.
* The important case is the *event time *temporal join. In my understanding
processing time temporal
I've opened a PR for fixing the NOTICE file problems [1].
[1] https://github.com/apache/flink/pull/12811
Cheers,
Till
On Thu, Jul 2, 2020 at 6:23 PM Till Rohrmann wrote:
> - verified checksums and signature
> - built Flink from source release with Scala 2.12
> - Executed some example jobs
- verified checksums and signature
- built Flink from source release with Scala 2.12
- Executed some example jobs successfully
- verified license and notice files
I found the following issues with some NOTICE files:
* flink-connector-hive: org.apache.parquet:parquet-format:1.10.0 ->
fanrui created FLINK-18473:
--
Summary: Optimize RocksDB disk load balancing strategy
Key: FLINK-18473
URL: https://issues.apache.org/jira/browse/FLINK-18473
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-18472:
Summary: Local Installation Getting Started Guide
Key: FLINK-18472
URL: https://issues.apache.org/jira/browse/FLINK-18472
Project: Flink
Issue Type:
Listing more than we need to (especially if it is apache licensed) isn't
a big problem, since nothing changes from a users perspective in regards
to licensing.
On 02/07/2020 17:08, Robert Metzger wrote:
Issues found:
-
Issues found:
-
https://repository.apache.org/content/repositories/orgapacheflink-1377/org/apache/flink/flink-runtime_2.12/1.11.0/flink-runtime_2.12-1.11.0.jar
./META-INF/NOTICE lists "org.uncommons.maths:uncommons-maths:1.2.2a" as a
bundled dependency. However, it seems they are not bundled. I'm
Robert Metzger created FLINK-18471:
--
Summary: flink-runtime lists
"org.uncommons.maths:uncommons-maths:1.2.2a" as a bundled dependency, but it
isn't
Key: FLINK-18471
URL:
Dawid Wysakowicz created FLINK-18470:
Summary: Tests
RocksKeyGroupsRocksSingleStateIteratorTest#testMergeIteratorByte &
RocksKeyGroupsRocksSingleStateIteratorTest#testMergeIteratorShort fail locally
Key: FLINK-18470
Kostas Kloudas created FLINK-18469:
--
Summary: Add Application Mode to release notes.
Key: FLINK-18469
URL: https://issues.apache.org/jira/browse/FLINK-18469
Project: Flink
Issue Type:
+1
Re examples:
The examples failing is new in 1.1*1*, and was introduced in
https://issues.apache.org/jira/browse/FLINK-16655.
In prior versions, calls to print()/count()/etc. were were simply
treated as an execute(), whereas with 1.11 we outright fail the
submission because these do not
+1 (binding) from my side
- legal files (license, notice) looks correct
- no binaries in the release
- ran examples from command line
- ran some examples from web ui
- log files look sane
- RocksDB, incremental checkpoints, savepoints, moving savepoints
all works as expected.
There
Robert Metzger created FLINK-18468:
--
Summary:
TaskExecutorITCase.testJobReExecutionAfterTaskExecutorTermination fails with
Key: FLINK-18468
URL: https://issues.apache.org/jira/browse/FLINK-18468
Andrey Zagrebin created FLINK-18467:
---
Summary: Document what can be reconfigured for state with TTL
between job restarts
Key: FLINK-18467
URL: https://issues.apache.org/jira/browse/FLINK-18467
Jark Wu created FLINK-18466:
---
Summary: JDBC should fail-fast if the target table doesn't exist
Key: FLINK-18466
URL: https://issues.apache.org/jira/browse/FLINK-18466
Project: Flink
Issue Type:
Jark Wu created FLINK-18465:
---
Summary: Support to integrate FLIP-24 source interface with Table
API
Key: FLINK-18465
URL: https://issues.apache.org/jira/browse/FLINK-18465
Project: Flink
Issue
Roman Khachatryan created FLINK-18464:
-
Summary: ClassCastException during namespace serialization for
checkpoint (Heap)
Key: FLINK-18464
URL: https://issues.apache.org/jira/browse/FLINK-18464
Wei Zhong created FLINK-18463:
-
Summary: Make the "input_types" parameter of the Python udf
decorator optional
Key: FLINK-18463
URL: https://issues.apache.org/jira/browse/FLINK-18463
Project: Flink
I also agree with Till and Robert's proposals.
In general I think we should not block the release based on current estimation.
Otherwise we continuously postpone the release, it might probably occur new
bugs for blockers, then we might probably
get stuck in such cycle to not give a final
Jark Wu created FLINK-18462:
---
Summary: Improve the exception message when INSERT INTO mismatch
types for empty char
Key: FLINK-18462
URL: https://issues.apache.org/jira/browse/FLINK-18462
Project: Flink
I agree with Robert.
@Chesnay: The problem has probably already existed in Flink 1.10 and before
because we cannot run jobs with eager execution calls from the web ui. I
agree with Robert that we can/should improve our documentation in this
regard, though.
@Thomas:
1. I will update the release
Thanks a lot for the thorough testing Thomas! This is really helpful!
@Chesnay: I would not block the release on this. The web submission does
not seem to be the documented / preferred way of job submission. It is
unlikely to harm the beginner's experience (and they would anyways not read
the
Hi,
I'm very sorry but we just found a blocker issue FLINK-18461 [1] in the new
feature of changelog source (CDC).
This bug will result in queries on changelog source can’t be inserted into
upsert sink (e.g. ES, JDBC, HBase),
which is a common case in production. CDC is one of the important
37 matches
Mail list logo
