ivan Qing created FLINK-29124:
-
Summary: Redundant checkNotNull in cli Package
Key: FLINK-29124
URL: https://issues.apache.org/jira/browse/FLINK-29124
Project: Flink
Issue Type: Improvement
Hi,
Thanks for feeback and descirption, Yang Wang.
I saw multiple Flink associated docker images on dockerhub and released
with X86 & ARM64. So we think that might be useful for community to setup
ARM CI relied on existing CICD system.
We are happy that we could help on that via donating ARM
Peter Vary created FLINK-29123:
--
Summary: Dynamic paramters are not pushed to working with
kubertenes
Key: FLINK-29123
URL: https://issues.apache.org/jira/browse/FLINK-29123
Project: Flink
Robert Metzger created FLINK-29122:
--
Summary: Improve robustness of FileUtils.expandDirectory()
Key: FLINK-29122
URL: https://issues.apache.org/jira/browse/FLINK-29122
Project: Flink
Issue
Jark Wu created FLINK-29121:
---
Summary:
SqlGatewayRestAPIStabilityTest.testSqlGatewayRestAPIStability is failed
Key: FLINK-29121
URL: https://issues.apache.org/jira/browse/FLINK-29121
Project: Flink
Thanks Bo for starting this discussion.
I think it is really useful to have the CI for ARM platform. But I am not
sure what is the current situation. TBH, I have not build an ARM image for
Flink.
Given that we have not finished the migration from azure pipelines to
github action, I believe we
HI Hong,
Maybe you forgot. I don’t know if the current FLIP still needs to be
modified. If not, we will start with the current plan. If you have
relevant ideas in the future, please continue to discuss. If not, we
will open voting at a later date.
Teoh, Hong 于2022年8月22日周一 16:02写道：
>
> Hi Zheng
Hi Chesnay ,
I have also considered the method you mentioned. If we deploy some
load balancing or intelligent scheduling in front of multiple
SessionClusters, this may cause the following problems
● Insufficient resource utilization. When we distribute these
resources on each cluster, the job
lincoln lee created FLINK-29120:
---
Summary: Unexpected join hint propagation into view
Key: FLINK-29120
URL: https://issues.apache.org/jira/browse/FLINK-29120
Project: Flink
Issue Type: Bug
lincoln lee created FLINK-29119:
---
Summary: Should clarify how join hints work with CTE
Key: FLINK-29119
URL: https://issues.apache.org/jira/browse/FLINK-29119
Project: Flink
Issue Type:
Shengkai Fang created FLINK-29118:
-
Summary: Remove default_catalog in the HiveServer2 Endpoint
Key: FLINK-29118
URL: https://issues.apache.org/jira/browse/FLINK-29118
Project: Flink
Issue
Hi Ran,
so if I understand it correctly, the problem here is not only backward
compatibility but also forward compatibility. You might run different
versions of your connector some of them offer a metadata key A and some
don't offer it yet. But the DDL should work for both connector
geonyeong kim created FLINK-29117:
-
Summary: Tried to associate with unreachable remote address
Key: FLINK-29117
URL: https://issues.apache.org/jira/browse/FLINK-29117
Project: Flink
Issue
geonyeong kim created FLINK-29116:
-
Summary: Tried to associate with unreachable remote address
Key: FLINK-29116
URL: https://issues.apache.org/jira/browse/FLINK-29116
Project: Flink
Issue
Yunfeng Zhou created FLINK-29115:
Summary: Improve the quickstart of Flink ML python API
Key: FLINK-29115
URL: https://issues.apache.org/jira/browse/FLINK-29115
Project: Flink
Issue Type:
Hi Ran,
If the metadata is from the message properties, then you can manually cast it
to your preferred types,
such as `my_dyanmic_meta AS CAST(properties['my-new-property’] AS TIMESTAMP)`.
If the metadata is not from the message properties, how does the connector know
which field to convert
Hi Sana,
I don't have much to offer. I haven't heard anyone doing any work directly
towards energy efficiency per se, but indirectly yes. I have seen companies
optimising performance of their workloads, with an ultimate goal of
assigning fewer resources to a cluster in order to save up on a
Sergey Nuyanzin created FLINK-29114:
---
Summary: TableSourceITCase#testTableHintWithLogicalTableScanReuse
sometimes fails with result mismatch
Key: FLINK-29114
URL:
Hi, TiMo. I think using one map column in the debezium format you
illustrated above can't cover the discussed scenario.
It's not the same thing.
Here is a debezium format example from flink docs: [1]
```
CREATE TABLE KafkaTable (
origin_ts TIMESTAMP(3) METADATA FROM 'value.ingestion-timestamp'
lincoln lee created FLINK-29113:
---
Summary: Join hint with invalid table name mixed with valid names
will not raise an error
Key: FLINK-29113
URL: https://issues.apache.org/jira/browse/FLINK-29113
lincoln lee created FLINK-29112:
---
Summary: Print the lookup join hint on the node `Correlate` in the
origin RelNode tree
Key: FLINK-29112
URL: https://issues.apache.org/jira/browse/FLINK-29112
Project:
lincoln lee created FLINK-29111:
---
Summary: deprecate 'lookup.async' and expose both async and sync
lookup capabilities to planner
Key: FLINK-29111
URL: https://issues.apache.org/jira/browse/FLINK-29111
22 matches
Mail list logo
