Dian Fu created FLINK-31532:
---
Summary: Support StreamExecutionEnvironment.socketTextStream in
Python DataStream API
Key: FLINK-31532
URL: https://issues.apache.org/jira/browse/FLINK-31532
Project: Flink
+1 (non-binding)
1. Built from the source code
2. Verified the signature and checksum
3. Ran both streaming/batch jobs on yarn
4. Checked website PR
Best regards,
Weijie
Yun Tang 于2023年3月21日周二 14:07写道：
> +1 (non-binding)
>
>
> * Verified the signature of source.tgz and jar packages.
luoyuxia created FLINK-31533:
Summary: CREATE TABLE AS SELECT should support to define partition
Key: FLINK-31533
URL: https://issues.apache.org/jira/browse/FLINK-31533
Project: Flink
Issue Type:
luoyuxia created FLINK-31534:
Summary: CREATE TABLE AS SELECT should support to define primary
key
Key: FLINK-31534
URL: https://issues.apache.org/jira/browse/FLINK-31534
Project: Flink
Issue Ty
We've approved the release.
Votes:
+1 Etienne
+1 Danny (binding)
+1 Martijn (binding)
+1 Gordon (binding)
+1 Mason
On 15/03/2023 16:40, Chesnay Schepler wrote:
Hi everyone,
Please review and vote on the release candidate, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the releas
Hi Panagiotis,
Thanks for the proposal.
It's useful to enrich the information so that users can be more
clear why the job is failing, especially platform developers who
need to provide the information to their end users.
And for the very FLIP, I'd prefer the naming `FailureEnricher`
proposed by D
Hi, Hongshun,
Thank you for starting this discussion. I have some problems about the
field `firstDiscoveryDone`.
In the FLIP, why we need firstDiscoveryDone is as follows.
> Why do we need firstDiscoveryDone? Only relying on the
unAssignedInitialPartitons attribute cannot distinguish between the
Hi all,
- I read the release notes: I'd suggest if possible that we group the
subtasks by main task and show the main tasks to give better
understanding to the reader.
- tested RC3 on a standalone cluster with this user code:
https://github.com/echauchot/tpcds-benchmark-flink
+1 (not-bindi
+1 (non-binding)
- downloaded, checked hashes
- verified signatures
- built from sources
- checked LICENSE and NOTICE files
- ran simple jobs
On Tue, Mar 21, 2023, 11:16 Etienne Chauchot wrote:
> Hi all,
>
> - I read the release notes: I'd suggest if possible that we group the
> subtasks by mai
Hi all:
I am happy to announce that FLIP-296: Extend watermark-related features for
SQL [1] has been accepted.
There are 6 binding votes and 2 non-binding votes:
- Yun Tang (binding)
- Jark Wu (binding)
- Jingsong Li (binding)
- Jing Ge (binding)
- Yuxia (binding)
- Leonard Xu (binding)
- Jun He
Hi,
It would be nice to have the custom error handler, but at the same time I'm
not sure if we really have to bundle those two things together in the same
FLIP. We can always make sure that the interface introduced here, in
FLIP-304, can be expanded in the future.
Re @David and @Leonard.
> The m
Hi, Hang,
Thanks for your advice.
When the second case will occur? Currently, there are three ways to specify
partitions in Kafka: by topic, by partition, and by matching the topic with
a regular expression. Currently, if the initial partition number is 0, an
error will occur for the first two me
Yuan Kui created FLINK-31535:
Summary: Extend watermark-related features for SQL
Key: FLINK-31535
URL: https://issues.apache.org/jira/browse/FLINK-31535
Project: Flink
Issue Type: New Feature
Yuan Kui created FLINK-31536:
Summary: Support to set watermark emit strategy with table options
or 'OPTIONS' hint
Key: FLINK-31536
URL: https://issues.apache.org/jira/browse/FLINK-31536
Project: Flink
Weihua Hu created FLINK-31537:
-
Summary: Derive a new TaskManagerTrackerConfiguration from the
SlotManagerConfiguration.
Key: FLINK-31537
URL: https://issues.apache.org/jira/browse/FLINK-31537
Project: Fl
Fang Yong created FLINK-31538:
-
Summary: Supports parse catalog/database and properties for uri
Key: FLINK-31538
URL: https://issues.apache.org/jira/browse/FLINK-31538
Project: Flink
Issue Type:
Yuan Kui created FLINK-31539:
Summary: Support to configure watermark alignment in sql layer
Key: FLINK-31539
URL: https://issues.apache.org/jira/browse/FLINK-31539
Project: Flink
Issue Type: Sub
Yuan Kui created FLINK-31540:
Summary: Support to set source idle-timeout options in sql layer
Key: FLINK-31540
URL: https://issues.apache.org/jira/browse/FLINK-31540
Project: Flink
Issue Type: S
Hi devs,
I'd like to start a discussion on FLIP-292: Support configuring state TTL
at operator level for Table API & SQL programs [1].
Currently, we only support job-level state TTL configuration via
'table.exec.state.ttl'. However, users may expect a fine-grained state TTL
control to optimize st
Hi Panagiotis,
Thanks for the proposal. This is a very valuable feature and will be a good
add-on for Flink.
I also think that it will be great if we can consider how to make it
possible for users to customize the failure handling in this FLIP. It's
highly related to the problem we want to addres
+1 (binding)
- verify signatures and checksums
- verify python wheel package contents
- pip install apache-flink-libraries and apache-flink wheel packages
- run example flink/flink-python/pyflink/examples/table/basic_operations.py
with Python 3.10
- reviewed release note PR
Best,
Xingbo
Sergey N
Hi Piotr,
It's fine to me to have a separate FLIP to extend this `FailureListener`
to support custom restart strategy.
What I was a bit concerned is that if we just treat the `FailureListener`
as an error classifier which is not crucial to Flink framework process,
we may design it to run asynchro
tanjialiang created FLINK-31541:
---
Summary: Get metrics in Flink WEB UI error
Key: FLINK-31541
URL: https://issues.apache.org/jira/browse/FLINK-31541
Project: Flink
Issue Type: Bug
Com
Samuel Siebenmann created FLINK-31542:
-
Summary: FatalExceptionClassifier#isFatal returns false if the
exception is fatal
Key: FLINK-31542
URL: https://issues.apache.org/jira/browse/FLINK-31542
Pr
+1 (binding)
+ Started Flink locally with the changelog statebackend + rocksdb against
minio
+ used the maven artifacts to develop a little, large-state sample job to
test with the changelog statebackend
+ Opened this PR https://github.com/apache/flink/pull/22232
+ Manually eyeballed the diff for
*@Piotr*
> I was thinking about actually defining the order of the
> classifiers/handlers and not allowing them to be asynchronous.
> Asynchronousity would create some problems: when to actually return the
> error to the user? After all async responses will get back? Before, but
> without classif
Fang Yong created FLINK-31543:
-
Summary: Introduce FlinkStatement for jdbc driver
Key: FLINK-31543
URL: https://issues.apache.org/jira/browse/FLINK-31543
Project: Flink
Issue Type: Sub-task
Fang Yong created FLINK-31544:
-
Summary: Introduce FlinkDatabaseMetaData for jdbc driver
Key: FLINK-31544
URL: https://issues.apache.org/jira/browse/FLINK-31544
Project: Flink
Issue Type: Sub-tas
Fang Yong created FLINK-31545:
-
Summary: FlinkConnection creates and manages statements
Key: FLINK-31545
URL: https://issues.apache.org/jira/browse/FLINK-31545
Project: Flink
Issue Type: Sub-task
Fang Yong created FLINK-31546:
-
Summary: Add column info and management for sql jdbc
Key: FLINK-31546
URL: https://issues.apache.org/jira/browse/FLINK-31546
Project: Flink
Issue Type: Sub-task
Fang Yong created FLINK-31547:
-
Summary: Introduce FlinkResultSetMetaData for jdbc driver
Key: FLINK-31547
URL: https://issues.apache.org/jira/browse/FLINK-31547
Project: Flink
Issue Type: Sub-ta
Fang Yong created FLINK-31548:
-
Summary: Introduce FlinkDataSource for jdbc driver
Key: FLINK-31548
URL: https://issues.apache.org/jira/browse/FLINK-31548
Project: Flink
Issue Type: Sub-task
Fang Yong created FLINK-31549:
-
Summary: Add doc for jdbc driver
Key: FLINK-31549
URL: https://issues.apache.org/jira/browse/FLINK-31549
Project: Flink
Issue Type: Sub-task
Components:
Thanks for the proposal, Panagiotis. A lot of good points have been already
shared. I just want to add my view on some of the items:
- independent execution vs ordered execution: I prefer the listeners being
processed independently from each other because it adds less complexity
code-wise. The use
Jark Wu created FLINK-31550:
---
Summary: Replace deprecated TableSchema with Schema in
OperationConverterUtils
Key: FLINK-31550
URL: https://issues.apache.org/jira/browse/FLINK-31550
Project: Flink
Marios Trivyzas created FLINK-31551:
---
Summary: Support CrateDB in JDBC Connector
Key: FLINK-31551
URL: https://issues.apache.org/jira/browse/FLINK-31551
Project: Flink
Issue Type: New Featu
Marios Trivyzas created FLINK-31552:
---
Summary: Cannot use schema other than public with TableEnvironment
Key: FLINK-31552
URL: https://issues.apache.org/jira/browse/FLINK-31552
Project: Flink
Marios Trivyzas created FLINK-31553:
---
Summary: Choose Catalog, non-url based
Key: FLINK-31553
URL: https://issues.apache.org/jira/browse/FLINK-31553
Project: Flink
Issue Type: Improvement
Hi,
Thanks Panagiotis for this FLIP and thanks for all valuable discussions.
I'd like to share my two cents:
- FailureListenerContext#addTag and FailureListenerContext#getTags. It
seems that we have to call getTags() and then do remove activities if we
want to delete any tags (according to the ja
Fang Yong created FLINK-31554:
-
Summary: Translate "Overview" page of "sql-gateway" into Chinese
Key: FLINK-31554
URL: https://issues.apache.org/jira/browse/FLINK-31554
Project: Flink
Issue Type:
Fang Yong created FLINK-31555:
-
Summary: Translate "hiveserver2" page of "sql-gateway" into Chinese
Key: FLINK-31555
URL: https://issues.apache.org/jira/browse/FLINK-31555
Project: Flink
Issue Ty
Fang Yong created FLINK-31556:
-
Summary: Translate "rest" page of "sql-gateway" into Chinese
Key: FLINK-31556
URL: https://issues.apache.org/jira/browse/FLINK-31556
Project: Flink
Issue Type: Sub
+1 (no-binding)
+ verify signatures and checksums
+ build Flink from source (from the src archive)
+ run simple job flink on k8s application mode and session cluster
Robert Metzger 于2023年3月21日周二 20:36写道：
> +1 (binding)
>
> + Started Flink locally with the changelog statebackend + rocksdb again
LiuZeshan created FLINK-31557:
-
Summary: Metric viewUpdater and reporter task in a
SingleThreadScheduledExecutor lead to inaccurate PerSecond related metrics
Key: FLINK-31557
URL: https://issues.apache.org/jira/browse
44 matches
Mail list logo
