Samrat Deb created FLINK-30482:
--
Summary: Update catalog documentation
Key: FLINK-30482
URL: https://issues.apache.org/jira/browse/FLINK-30482
Project: Flink
Issue Type: Sub-task
Comp
Samrat Deb created FLINK-30481:
--
Summary: create base aws-glue catalog implementation in
flink-connector-aws
Key: FLINK-30481
URL: https://issues.apache.org/jira/browse/FLINK-30481
Project: Flink
Zhu Zhu created FLINK-30480:
---
Summary: Add benchmarks for adaptive batch scheduler
Key: FLINK-30480
URL: https://issues.apache.org/jira/browse/FLINK-30480
Project: Flink
Issue Type: Improvement
Hi Mingliang,
Thanks for bringing this up
>From one side, yes some engines use SHOW syntax and I would rather +0.5
here.
>From another side both SHOW and SET are very limited commands.
Maybe it would make sense to look at information_schema (mentioned in SQL
92[1])
and most databases already supp
Mingliang Liu created FLINK-30479:
-
Summary: Document flink-connector-files for local execution
Key: FLINK-30479
URL: https://issues.apache.org/jira/browse/FLINK-30479
Project: Flink
Issue Ty
Hello everyone,
Answering my own question, it turns out that Flink Table Store removes the
normalization node on read from an external log system only if
log.changelog-mode='all' and log.consistency = 'transactional' [1].
1.
https://github.com/apache/flink-table-store/blob/7e0d55ff3dc9fd48455b17d
The Apache Flink community is very happy to announce the release of Apache
flink-connector-rabbitmq 3.0.0
This release marks the first time we have released this connector
separately from the main Flink release.
Over time more connectors will be migrated to this release model.
This release is equ
The Apache Flink community is very happy to announce the release of Apache
flink-connector-jdbc 3.0.0
This release marks the first time we have released this connector
separately from the main Flink release.
Over time more connectors will be migrated to this release model.
This release is equival
The Apache Flink community is very happy to announce the release of Apache
flink-connector-pulsar 3.0.0
This release marks the first time we have released this connector
separately from the main Flink release.
Over time more connectors will be migrated to this release model.
This release is equiv
Hello,
I am using custom made connector to create Source table in this way:
create table Source (
ts TIMESTAMP(3),
instance STRING,
sservice STRING,
logdatetime STRING,
threadid STRING,
level STRING,
log_line STRING
) with (
Gunnar Morling created FLINK-30478:
--
Summary: Don't depend on IPAddressUtil
Key: FLINK-30478
URL: https://issues.apache.org/jira/browse/FLINK-30478
Project: Flink
Issue Type: Sub-task
I'm happy to announce that we have unanimously approved this release.
There are 7 approving votes, 3 of which are binding:
* Andrey
* Ahmed
* Martijn (binding)
* Sergey
* Maxillian (binding)
* Thomas (binding)
* Julian
There are no disapproving votes.
Thanks everyone!
--
Best Regards
Danny C
Hi everyone,
This vote is now closed, I will announce the results in a separate email.
Thanks all.
On Wed, Dec 21, 2022 at 3:51 AM Thomas Weise wrote:
> +1 (binding)
>
> * Checked hash and signature
> * Build from source and run tests
> * Checked licenses
>
>
>
> On Mon, Dec 19, 2022 at 1:50 P
Hi Martijn,
Agree that we need to detail the specific case in the release notes. I will
update the 'Release Note' related content of the three issues before the
release.
Also update the progress of the last issue FLINK-29849, which has been
merged to master.
If no one objects, FLINK-28988 and FLI
lincoln lee created FLINK-30477:
---
Summary: Not properly blocking retries when timeout occurs in
AsyncWaitOperator
Key: FLINK-30477
URL: https://issues.apache.org/jira/browse/FLINK-30477
Project: Flink
Denis created FLINK-30476:
-
Summary: TrackingFsDataInputStream batch tracking issue
Key: FLINK-30476
URL: https://issues.apache.org/jira/browse/FLINK-30476
Project: Flink
Issue Type: Bug
Co
Hi, all,
FLIP-275: Support Remote SQL Client Based on SQL Gateway[1] has been accepted.
There are 3 bindings, and 2 non-bindings as follows:
ShengKai Fang (binding),
Paul Lam (non-binding),
Hang Ruan (non-binding)
Godfrey He (binding)
Jark Wu (binding)
There are no votes against it.
Best,
Yu Z
HI, Mingliang.
Thanks for bringing this up. +1 to add this support.
I think use syntax "SET 'key'" to show a signle variable is weird, but use it
may be more convinent and more unified since we have used "SET" to show all
variable.
Considering many hive/spark users may be used to it, seems use
David Hrbacek created FLINK-30475:
-
Summary: Improved speed of RocksDBMapState clear() using
rocksDB.deleteRange
Key: FLINK-30475
URL: https://issues.apache.org/jira/browse/FLINK-30475
Project: Flink
Hi Mingliang,
Thanks for opening a discussion thread on this topic, much appreciated. If
there is no standard SQL for this, then we should have a discussion on this
topic indeed.
I'm not a fan of using "SET" to show a value. For me, "SET" implies that
you are setting a value. I prefer "SHOW" sinc
Matthias Pohl created FLINK-30474:
-
Summary: DefaultMultipleComponentLeaderElectionService triggers HA
backend change even if it's not the leader
Key: FLINK-30474
URL: https://issues.apache.org/jira/browse/FLINK-3
Hi all,
Currently in SQL Client we can use the "SET 'key'='value'" command to set a
value to a config property key for the session. We can also list all config
properties by just calling "SET". It would be convenient to show the value
of a specific config property given its key(s). Without this, u
Yuxin Tan created FLINK-30473:
-
Summary: Optimize the InputGate network memory management for
TaskManager
Key: FLINK-30473
URL: https://issues.apache.org/jira/browse/FLINK-30473
Project: Flink
I
Yuxin Tan created FLINK-30472:
-
Summary: Modify the default value of the max network memory config
option
Key: FLINK-30472
URL: https://issues.apache.org/jira/browse/FLINK-30472
Project: Flink
I
Yuxin Tan created FLINK-30471:
-
Summary: Optimize the enriching network memory process in
SsgNetworkMemoryCalculationUtils
Key: FLINK-30471
URL: https://issues.apache.org/jira/browse/FLINK-30471
Project:
+1 (binding)
Best,
Jark
On Wed, 21 Dec 2022 at 16:00, godfrey he wrote:
> +1 (binding)
>
> Best,
> Godfrey
>
> Hang Ruan 于2022年12月21日周三 15:21写道：
> >
> > +1 (non-binding)
> >
> > Best,
> > Hang
> >
> > Paul Lam 于2022年12月20日周二 17:36写道：
> >
> > > +1 (non-binding)
> > >
> > > Best,
> > > Paul Lam
Hi all,
I'm happy to announce that we have unanimously approved this release.
There are 4 approving votes, 3 of which are binding:
* Sergey Nuyanzin (non-binding)
* Dawid (binding)
* Martijn (binding)
* Danny (binding)
There are no disapproving votes.
Thanks everyone!
Best regards,
Martijn
O
Hi all,
I'm happy to announce that we have unanimously approved this release.
There are 3 approving votes, 3 of which are binding:
* Danny (binding)
* Dawid (binding)
* Martijn (binding)
There are no disapproving votes.
Thanks everyone!
Best regards,
Martijn
On Tue, Dec 20, 2022 at 2:31 PM Da
Hi all,
I'm happy to announce that we have unanimously approved this release.
There are 5 approving votes, 3 of which are binding:
* Yufan Sheng
* Dawid (binding)
* Danny (binding)
* Ahmed Hamdy
* Martijn (binding)
There are no disapproving votes.
Thanks everyone!
Best regards,
Martijn
On Tue
Hi Lincoln,
I'm +1 for also merging them back to 1.16.1. In the release notes we should
make it clear in which situations incompatibility issues will arise, so
that we inform the users correctly.
Best regards,
Martijn
On Wed, Dec 21, 2022 at 8:41 AM godfrey he wrote:
> Hi Martijn,
>
> Thank y
30 matches
Mail list logo
