Thanks a lot @yuxia for your time. We will
try to back port https://issues.apache.org/jira/browse/FLINK-27450 and see
if that works. Also will keep watching for your fix for the Default Dialect
fix.
Regards
Ram
On Mon, Jul 17, 2023 at 8:08 AM yuxia wrote:
> Hi, Ram.
> Thanks for reaching
Zhenqiu Huang created FLINK-32597:
-
Summary: Drop Yarn specific get rest endpoints
Key: FLINK-32597
URL: https://issues.apache.org/jira/browse/FLINK-32597
Project: Flink
Issue Type:
Hi Matthias,
How's it going with the summary of existing 2.0.0 jira tickets?
I have gone through everything listed under FLINK-3957[1], and will
continue with other Jira tickets whose fix-version is 2.0.0.
Here are my 2-cents on the FLINK-3975 subtasks. Hope this helps on your
summary.
I'd
Thanks for creating this FLIP, Matthias. +1 from my side.
BTW, it's impressive how this FLIP clearly states the proposed API changes
and impacts on other classes / APIs, which makes it much easier for others
to evaluate the proposal. Nice work~!
Best,
Xintong
On Thu, Jul 13, 2023 at 9:11 PM
+1
Best,
Xintong
On Thu, Jul 13, 2023 at 9:34 PM Chesnay Schepler wrote:
> Hello,
>
> The request body for the jar run/plan REST endpoints accepts program
> arguments as a string (programArgs) or a list of strings
> (programArgsList). The latter was introduced as kept running into issues
>
+1
Best,
Xintong
On Thu, Jul 13, 2023 at 9:41 PM Chesnay Schepler wrote:
> Hello,
>
> The job cancellation REST endpoint has a terminationMode query
> parameter, which in the past could be set to either CANCEL or STOP, but
> nowadays the job stop endpoint has subsumed the STOP
+1
Best,
Xintong
On Thu, Jul 13, 2023 at 9:05 PM Chesnay Schepler wrote:
> Hello,
>
> Several REST responses contain a timestamp field of the current time
>
> There is no known use-case for said timestamp, it makes caching of
> responses technically sketchy (since the response differs on
Hi, Ram.
Thanks for reaching out.
1:
About Hive dialect issue, may be you're using JDK11?
There's a known issue in FLINK-27450[1]. The main reason that Hive dosen't
fully support JDK11. More specific to your case, it has been tracked in
HIVE-21584[2].
Flink has upgrade the Hive 2.x version
luoyuxia created FLINK-32596:
Summary: The partition key will be wrong when use Flink dialect to
create Hive table
Key: FLINK-32596
URL: https://issues.apache.org/jira/browse/FLINK-32596
Project: Flink
Hi Jiabao,
Thank you for your suggestions. I have added them to the "Going Beyond a
SQL Stream/Batch Processing Engine" and "Large-Scale State Jobs" sections.
Best,
Jark
On Thu, 13 Jul 2023 at 16:06, Jiabao Sun
wrote:
> Thanks Jark and Martijn for driving this.
>
> There are two suggestions
Yuxin Tan created FLINK-32595:
-
Summary: Kinesis connector doc show wrong deserialization schema
version
Key: FLINK-32595
URL: https://issues.apache.org/jira/browse/FLINK-32595
Project: Flink
@Yun,
I see your point that the ability queryable states trying to provide is
meaningful but the current implementation of the feature is problematic. So
what's your opinion on deprecating the current queryable state? Do you
think we need to wait until there is a new implementation of queryable
I'd propose to downgrade "Refactor the API modules" to TBD. The original
proposal was based on the condition that we are allowed to introduce
in-place API breaking changes in release 2.0. As the migration period is
introduced, and we are no longer planning to do in-place changes /
removal for
I agree that we could downgrade "Eager state declaration" to a nice-to-have
feature.
For the depreciation of "queryable state", can we just rename to deprecate
"current implementation of queryable state"? The feature to query the internal
state is actually very useful for debugging and could
+1 for the new look of website.
And for the content of FLIP, please do not paste the "Detailed designs" under
the scope of "Rejected Alternatives", you can just post the pictures in the
"Proposed Changes" part.
Best
Yun Tang
From: Mohan, Deepthi
Sent: Sunday,
@Chesnay
Thank you for your feedback.
An important takeaway from the previous discussion [1] and your feedback was to
keep the design and text/diagram changes separate as each change for text and
diagrams likely require deeper discussion. Therefore, as a first step I am
proposing only UX
16 matches
Mail list logo
