tonychan created FLINK-20527:
Summary: how to add a side output for flink sql watermaker?
Key: FLINK-20527
URL: https://issues.apache.org/jira/browse/FLINK-20527
Project: Flink
Issue Type: Bug
Huang Xingbo created FLINK-20528:
Summary: Add Python building blocks to make sure the basic
functionality of Stream Group Table Aggregation could work
Key: FLINK-20528
URL: https://issues.apache.org/jira/browse/
Dian Fu created FLINK-20529:
---
Summary: Publish Dockerfiles for release 1.12.0
Key: FLINK-20529
URL: https://issues.apache.org/jira/browse/FLINK-20529
Project: Flink
Issue Type: Task
Compo
xiaozilong created FLINK-20530:
--
Summary: Invalid metric named `lastCheckpointExternalPath`
Key: FLINK-20530
URL: https://issues.apache.org/jira/browse/FLINK-20530
Project: Flink
Issue Type: Bu
Robert Metzger created FLINK-20531:
--
Summary: Flink docs are not building anymore due to builder change
Key: FLINK-20531
URL: https://issues.apache.org/jira/browse/FLINK-20531
Project: Flink
Hi devs,
There has been a bit more delay but we finally get all bockers resolved.
I'm creating the RC right now (commit id:
47c2d97499ed95a33c071e916eb8bde7b179e879).
This could take some time given that I'm doing this for the first time and
accessing to Apache Nexus Repository from my place is s
Robert Metzger created FLINK-20532:
--
Summary: generate-stackbrew-library.sh in flink-docker doesn't
properly prune the java11 tag
Key: FLINK-20532
URL: https://issues.apache.org/jira/browse/FLINK-20532
Chesnay Schepler created FLINK-20533:
Summary: Add histogram support to Datadog reporter
Key: FLINK-20533
URL: https://issues.apache.org/jira/browse/FLINK-20533
Project: Flink
Issue Type:
Hi all,
Currently, the most convenient way of programmatically submitting a job to a
running session cluster is using Flink’s RestClusterClient.
Unfortunately, it is only supported, as of now, to submit a job graph.[1] To
construct a job graph from a jar file, additional Flink dependencies are
Dian Fu created FLINK-20534:
---
Summary: Add Flink 1.12 MigrationVersion
Key: FLINK-20534
URL: https://issues.apache.org/jira/browse/FLINK-20534
Project: Flink
Issue Type: Task
Components:
richt richt created FLINK-20535:
---
Summary: "GROUPING SETS" query result cannot upsert to table
Key: FLINK-20535
URL: https://issues.apache.org/jira/browse/FLINK-20535
Project: Flink
Issue Type
Dian Fu created FLINK-20536:
---
Summary: Update migration tests in master to cover migration from
release-1.12
Key: FLINK-20536
URL: https://issues.apache.org/jira/browse/FLINK-20536
Project: Flink
Thanks a lot for driving this release Xintong! Looking forward to the
1.11.3 release :-)
Cheers,
Till
On Tue, Dec 8, 2020 at 11:27 AM Xintong Song wrote:
> Hi devs,
>
> There has been a bit more delay but we finally get all bockers resolved.
>
> I'm creating the RC right now (commit id:
> 47c2d
Hi Fabian,
thanks for starting this discussion. In general I would be a bit hesitant
to build upon Flink's web UI submission because it suffers from a couple of
drawbacks.
1) The web UI submission only supports single job applications.
2) The JobGraph is generated from within the web UI Netty thr
Rui Li created FLINK-20537:
--
Summary: Failed to call Hive UDF with string literal arguments
Key: FLINK-20537
URL: https://issues.apache.org/jira/browse/FLINK-20537
Project: Flink
Issue Type: Bug
zhuxiaoshang created FLINK-20538:
Summary: sink.rolling-policy.file-size does not work in filesystem
connector
Key: FLINK-20538
URL: https://issues.apache.org/jira/browse/FLINK-20538
Project: Flink
I'm surprised that this is not possible currently. Seems like a glaring
missing feature to me.
I'd assume the best way would be to extend the REST API to /jar/:jarId/run
with an option to overwrite configuration values. I'm not sure how to map
json well to the yaml structure of the config, but I g
Timo Walther created FLINK-20539:
Summary: Type mismatch when using ROW in computed column
Key: FLINK-20539
URL: https://issues.apache.org/jira/browse/FLINK-20539
Project: Flink
Issue Type: S
Hi Everyone,
I've been spending a lot of time recently working on the SQL documentation
and I'm finding it very difficult to explain semantics as the two table
planners continue to diverge. As Blink has been the default planner for
some time, and 1.12 now offers bounded data stream support, how do
Hi Seth,
this is a very good idea. We might not be able to remove the legacy
planner immediately but at least we can make the docs easier for current
and future users of the Blink planner.
Making the SQL docs Blink-only with a dedicated legacy planner page
sounds good to me.
Regards,
Timo
I agree -- I think separating out the legacy planner info should make
things clearer for everyone, and then some day we can simply drop it. Plus,
doing it now will make it easier to make improvements to the docs going
forward.
David
On Tue, Dec 8, 2020 at 4:38 PM Timo Walther wrote:
> Hi Seth,
+1
Yes, please!
On 08.12.20 16:52, David Anderson wrote:
I agree -- I think separating out the legacy planner info should make
things clearer for everyone, and then some day we can simply drop it. Plus,
doing it now will make it easier to make improvements to the docs going
forward.
David
On
+1, this is confusing (esp. for new users) and also creates more and more
"annotation clutter" as new features are added.
On Tue, Dec 8, 2020 at 5:30 PM Aljoscha Krettek wrote:
> +1
>
> Yes, please!
>
> On 08.12.20 16:52, David Anderson wrote:
> > I agree -- I think separating out the legacy pla
+1, add a small info box about legacy planner and point to 1.11 doc
(nothing should have changed)
Ideally, "legacy" and "blink" does not appear anywhere in the doc (except
for that info box)
On Tue, Dec 8, 2020 at 6:35 PM Marta Paes Moreira
wrote:
> +1, this is confusing (esp. for new users) an
zhangzhao created FLINK-20540:
-
Summary: Failed connecting to
jdbc:postgresql://flink-postgres.cdn-flink:5432flink via JDBC
Key: FLINK-20540
URL: https://issues.apache.org/jira/browse/FLINK-20540
Project:
+1
Very good proposal, blink planner has been the default planner since Flink
1.11.0, and many new features are not supported in legacy planner.
Best,
Leonard
> 在 2020年12月9日，05:15，Arvid Heise 写道：
>
> +1, add a small info box about legacy planner and point to 1.11 doc
> (nothing should have
lixiaobao created FLINK-20541:
-
Summary: ClusterID is not used in the method!
Key: FLINK-20541
URL: https://issues.apache.org/jira/browse/FLINK-20541
Project: Flink
Issue Type: Improvement
+1
This is a very good proposal.In release-1.12, many newly added features are
only supported on the blink planner. For example, the newly added features
of PyFlnk in FLIP-137[1] and FLIP-139[2] are only available on the blink
planner.
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-13
谢波 created FLINK-20542:
--
Summary: flink-1.11.2 - stream join stream savepoint fail
Key: FLINK-20542
URL: https://issues.apache.org/jira/browse/FLINK-20542
Project: Flink
Issue Type: Bug
Environ
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.11.3,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
+1
This is a very good idea.
Best,
Jark
On Wed, 9 Dec 2020 at 10:43, Xingbo Huang wrote:
> +1
>
> This is a very good proposal.In release-1.12, many newly added features are
> only supported on the blink planner. For example, the newly added features
> of PyFlnk in FLIP-137[1] and FLIP-139[2]
xiaozilong created FLINK-20543:
--
Summary: Fix typo in upsert kafka docs
Key: FLINK-20543
URL: https://issues.apache.org/jira/browse/FLINK-20543
Project: Flink
Issue Type: Bug
Component
zhuxiaoshang created FLINK-20544:
Summary: ConcurrentModificationException when writing to hive and
fail over happened
Key: FLINK-20544
URL: https://issues.apache.org/jira/browse/FLINK-20544
Project:
Echo Lee created FLINK-20545:
Summary: SQLClientSchemaRegistryITCase compilation failed
Key: FLINK-20545
URL: https://issues.apache.org/jira/browse/FLINK-20545
Project: Flink
Issue Type: Bug
34 matches
Mail list logo
