Danny Cranmer created FLINK-29954:
-
Summary: Improve DynamoDB Connector Sample Code
Key: FLINK-29954
URL: https://issues.apache.org/jira/browse/FLINK-29954
Project: Flink
Issue Type:
Jingsong Lee created FLINK-29953:
Summary: Get rid of flink-connector-hive dependency in
flink-table-store-hive
Key: FLINK-29953
URL: https://issues.apache.org/jira/browse/FLINK-29953
Project: Flink
Hang HOU created FLINK-29952:
Summary: Using DROP TABLE XXX to drop a temporary table （or view）
in sql-client can get an exception with incomplete explaination.
Key: FLINK-29952
URL:
Xuannan Su created FLINK-29951:
--
Summary: Kafka SQL connector supports setting end offset/timestamp
Key: FLINK-29951
URL: https://issues.apache.org/jira/browse/FLINK-29951
Project: Flink
Issue
yuzelin created FLINK-29950:
---
Summary: Add 'contentType' and 'FieldFormat' to 'ResultSet' for
improvement
Key: FLINK-29950
URL: https://issues.apache.org/jira/browse/FLINK-29950
Project: Flink
yuzelin created FLINK-29949:
---
Summary: Implement 'RemoteExecutor' to perform the communication
with Gateway
Key: FLINK-29949
URL: https://issues.apache.org/jira/browse/FLINK-29949
Project: Flink
yuzelin created FLINK-29948:
---
Summary: Introduce ErrorResponse in Gateway RestEndpoint.
Key: FLINK-29948
URL: https://issues.apache.org/jira/browse/FLINK-29948
Project: Flink
Issue Type: Sub-task
yuzelin created FLINK-29947:
---
Summary: Support configuring session API in Gateway RestEndpoint
Key: FLINK-29947
URL: https://issues.apache.org/jira/browse/FLINK-29947
Project: Flink
Issue Type:
yuzelin created FLINK-29946:
---
Summary: Introduce ‘ErrorDetail’ in SQL Gateway Rest Endpoint for
error handling
Key: FLINK-29946
URL: https://issues.apache.org/jira/browse/FLINK-29946
Project: Flink
yuzelin created FLINK-29945:
---
Summary: Refactor ‘Executor’ interface to work with Gateway API
Key: FLINK-29945
URL: https://issues.apache.org/jira/browse/FLINK-29945
Project: Flink
Issue Type:
hk__lrzy created FLINK-29944:
Summary: Support accumaltor in source reader
Key: FLINK-29944
URL: https://issues.apache.org/jira/browse/FLINK-29944
Project: Flink
Issue Type: Improvement
Caizhi Weng created FLINK-29943:
---
Summary: Bump Table Store 0.2 Flink version to 1.15.2
Key: FLINK-29943
URL: https://issues.apache.org/jira/browse/FLINK-29943
Project: Flink
Issue Type:
Jark Wu created FLINK-29942:
---
Summary: Improve average performance for TPC-DS
Key: FLINK-29942
URL: https://issues.apache.org/jira/browse/FLINK-29942
Project: Flink
Issue Type: New Feature
Jark Wu created FLINK-29941:
---
Summary: Support SQL Client connects to SQL Gateway
Key: FLINK-29941
URL: https://issues.apache.org/jira/browse/FLINK-29941
Project: Flink
Issue Type: New Feature
Hi Roman,
Thanks for the proposal, this allows State Backend to make better use of
memory.
After reading the ticket, I'm curious about some points:
1. Is shared-memory only for the state backend? If both
"taskmanager.memory.managed.shared-fraction: >0" and
"state.backend.rocksdb.memory.managed:
Mingliang Liu created FLINK-29940:
-
Summary: ExecutionGraph logs job state change at ERROR level when
job fails
Key: FLINK-29940
URL: https://issues.apache.org/jira/browse/FLINK-29940
Project: Flink
Zhou Jiang created FLINK-29939:
--
Summary: Add metrics for Kubernetes Client Response 5xx count and
rate
Key: FLINK-29939
URL: https://issues.apache.org/jira/browse/FLINK-29939
Project: Flink
Danny Cranmer created FLINK-29938:
-
Summary: Add open() Method to AsyncSink ElementConverter
Key: FLINK-29938
URL: https://issues.apache.org/jira/browse/FLINK-29938
Project: Flink
Issue
Danny Cranmer created FLINK-29937:
-
Summary: Enhanced DynamoDB Element Converter
Key: FLINK-29937
URL: https://issues.apache.org/jira/browse/FLINK-29937
Project: Flink
Issue Type:
Hi everyone,
I'd like to discuss sharing RocksDB memory across slots as proposed in
FLINK-29928 [1].
Since 1.10 / FLINK-7289 [2], it is possible to:
- share these objects among RocksDB instances of the same slot
- bound the total memory usage by all RocksDB instances of a TM
However, the memory
Gyula Fora created FLINK-29936:
--
Summary: Make operator more robust to namespaces access errors
Key: FLINK-29936
URL: https://issues.apache.org/jira/browse/FLINK-29936
Project: Flink
Issue
Hi, Alexander
Happy to hear that you’re willing to contribute to Flink, the answer of these
specific tech design/functionality questions may need to dig the code.
I’m not familiar with FTS code base, but I’v CC my colleagues who are the core
maintainers of FTS and maybe they can give your some
Hi
Sorry for the late reply. I'm one of the core flink iceberg connector
maintainers at the early stage (flink 1.12, flink 1.13, flink 1.14). For
the later flink releases, I've had some adjustments in my work and had
less interactions with apache flink+iceberg, thanks Ryan, Steven, Kyle,
Taking a step back here: I think this needs to be handled in the
application mode in any case. Even if we had a better parser, it would
still treat # as a comment char. The application mode needs to be fixed to
come up with an escape scheme. YAML supports this via \# but that won't
work with our
Chesnay Schepler created FLINK-29935:
Summary: Setup CI runs against 1.16/1.17-SNAPSHOT
Key: FLINK-29935
URL: https://issues.apache.org/jira/browse/FLINK-29935
Project: Flink
Issue Type:
jackylau created FLINK-29934:
Summary: maven-assembly-plugin 2.4 make assemble plugin could find
xml in flink clients module
Key: FLINK-29934
URL: https://issues.apache.org/jira/browse/FLINK-29934
Jingsong Lee created FLINK-29933:
Summary: Bump Flink version to 1.16.0
Key: FLINK-29933
URL: https://issues.apache.org/jira/browse/FLINK-29933
Project: Flink
Issue Type: New Feature
Sergey Nuyanzin created FLINK-29932:
---
Summary: Upgrade Calcite version to 1.29.0
Key: FLINK-29932
URL: https://issues.apache.org/jira/browse/FLINK-29932
Project: Flink
Issue Type:
Chesnay Schepler created FLINK-29931:
Summary: Pin Flink binary URL and cache binary
Key: FLINK-29931
URL: https://issues.apache.org/jira/browse/FLINK-29931
Project: Flink
Issue Type:
Shammon created FLINK-29930:
---
Summary: ParquetFileStatsExtractorTest is unstable
Key: FLINK-29930
URL: https://issues.apache.org/jira/browse/FLINK-29930
Project: Flink
Issue Type: Bug
Yubin Li created FLINK-29929:
Summary: Correct conversions from ResolvedSchema to TableSchema
Key: FLINK-29929
URL: https://issues.apache.org/jira/browse/FLINK-29929
Project: Flink
Issue Type:
zentol commented on code in PR #1:
URL:
https://github.com/apache/flink-connector-shared-utils/pull/1#discussion_r1016492375
##
README.md:
##
@@ -1 +1,79 @@
-This repository contains utilities for [Apache
Flink](https://flink.apache.org/) connectors.
\ No newline at end of
>> # Horizontal scaling V.S. Vertical scaling
>
>True. We left out vertical scaling intentionally. For now we assume CPU /
memory is set up by the user. While definitely useful, vertical scaling
>adds another dimension to the scaling problem which we wanted to tackle
later. I'll update the FLIP to
Roman Khachatryan created FLINK-29928:
-
Summary: Allow sharing (RocksDB) memory between slots
Key: FLINK-29928
URL: https://issues.apache.org/jira/browse/FLINK-29928
Project: Flink
Issue
Hi everyone,
Please review and vote on the release candidate #1 for the version 16.1,
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],
I had 2 extra comments to Max's reply:
1. About pre-allocating resources:
This could be done through the operator when the standalone deployment mode
is used relatively easily as there we have better control of pods/resources.
2. Session jobs:
There is a FLIP (
@Yang
>Since the current auto-scaling needs to fully redeploy the application, it
may fail to start due to lack of resources.
Great suggestions. I agree that we will have to have to preallocate /
reserve resources to ensure the rescaling doesn't take longer as expected.
This is not only a
+1 (binding)
- Downloaded artifacts
- Checked hash and signature
- No binaries in source archive found
- Verified NOTICE files
- Build from source code
- Spinned up a Flink 1.16 cluster with Kafka and Elasticsearch7 and
used flink-sql-connector-elasticsearch7-3.0.0.jar to successfully sent data
Hi Max,
Thanks for bringing this up. I'm open to a re-evaluation of the Slack
usages.
In the initial discussion for creating the Slack workspace [1], leveraging
the ASF Slack was indeed brought up as an alternative by many folks. I
think we have chosen a dedicated Flink Slack over the ASF Slack
Gen Luo created FLINK-29927:
---
Summary: AkkaUtils#getAddress may cause memory leak
Key: FLINK-29927
URL: https://issues.apache.org/jira/browse/FLINK-29927
Project: Flink
Issue Type: Bug
If you click on the link from Beam via an incognito window/logged out of
Slack, you will be prompted to provide the workspace URL of the ASF. If you
do that, you're prompted for a login screen or you can create an account.
Creating an account prompts you to have an @apache.org email address. See
HI, @Paul Lam Thanks for the reply. I think it makes a lot of sense to
distinguish exceptions, but it might add complexity to the restart policy
maintenance, and some exceptions might be wrapped in the
FlinkRuntimeException or something else.
Maybe we can implement the first version based on the
Avinash created FLINK-29926:
---
Summary: File source continuous monitoring mode ignoring files
during savepoint upgrade mode
Key: FLINK-29926
URL: https://issues.apache.org/jira/browse/FLINK-29926
Project:
43 matches
Mail list logo
