Gentle ping to surface this up for more discussions.
Regards
Venkata krishnan
On Tue, Sep 26, 2023 at 4:59 PM Venkatakrishnan Sowrirajan
wrote:
> Hi Martijn,
>
> Agree with your point that closing a PR without any review feedback even
> after 'X' days is discouraging to a new contributor. I un
Chandra Prakash created FLINK-33180:
---
Summary: Implement support for processing subset of shards/traffic
Key: FLINK-33180
URL: https://issues.apache.org/jira/browse/FLINK-33180
Project: Flink
+1 for David's suggestion. We should get away from the current
approach with two abstractions and get to one rock solid one.
On Mon, Oct 2, 2023 at 11:13 PM David Morávek wrote:
>
> Hi Maomao,
>
> I wonder whether it would make sense to take a stab at consolidating the S3
> filesystems instead an
Hey all,
My understanding was that from the first message we were discussing
throwing an exception. Oracle was only shown as an example of a system
that have a flag for hints behaviour.
Let's get back to the discussion and agree on the behavior. My
suggestion is to introduce an enum instead o
Thanks everyone for the efforts!
Checked the following:
- Downloaded artifacts
- Built Flink from source
- Verified checksums/signatures
- Verified NOTICE, LICENSE files
- Deployed dummy SELECT job via SQL gateway on standalone cluster, things
seemed fine according to the log files
+1 (non-bind
Dawid Wysakowicz created FLINK-33179:
Summary: Improve reporting serialisation issues
Key: FLINK-33179
URL: https://issues.apache.org/jira/browse/FLINK-33179
Project: Flink
Issue Type: Su
Hi David,
Thx for your feedback.
First of all, for keeping some spare resources around, do you mean
'Redundant TaskManagers'[1]? If not, what is the difference between the
spare resources and redundant taskmanagers?
Secondly, IMHO the difference between min-reserved resource and spare
resources
Hi,
I agree this is a standardising, simplifying change for read, simplifying
programmatically authoring the config file as well. As you know the mapping
for the old config form to the new form, could we write a migration tool, that
would convert the old config files to the new format, with er
Hello,
I notice:
*the web UI listens on port 8081,
* The default port for that Flink listens on for rest calls is 8081.
* Specifying rest.port in the configuration changes the port for both
listeners.
We would like the 2 ports to be different so they can be secured differently,
Emre Kartoglu created FLINK-33178:
-
Summary: Highly parallel apps suffer from bottleneck in NativePRNG
Key: FLINK-33178
URL: https://issues.apache.org/jira/browse/FLINK-33178
Project: Flink
It is a unfortunate that we'll need a separate config file but the FLIP
does a good job justifying it.
Personally I'd just name it "config.yaml"; I never quite understood why
there was a flink prefix to begin with, and the current proposal
("flink-configuration.yaml") seems unnecessarily long.
11 matches
Mail list logo
