Jim Hughes created FLINK-35585:
--
Summary: Add documentation for distribution
Key: FLINK-35585
URL: https://issues.apache.org/jira/browse/FLINK-35585
Project: Flink
Issue Type: Sub-task
ableEnvironment.loadPlan`, it looks like the
compiled plan ought to be sufficient to run a job at a later time.
I think the FLIP should be clear on the backwards support strategy here.
The strategy for streaming is "forever". This may be the most interesting
part of the FLIP to discuss
HI all,
+1 (non-binding)
Cheers,
Jim
On Fri, Jun 7, 2024 at 4:03 AM Yuxin Tan wrote:
> Hi everyone,
>
> Thanks for all the feedback about the FLIP-459 Support Flink
> hybrid shuffle integration with Apache Celeborn[1].
> The discussion thread is here [2].
>
> I'd like to start a vote for it.
Hi Alexey,
After some thought, I have a question about deprecations:
3. Can we remove old versions of batch operators eventually? Or do we
need to keep them forever like we would for streaming operators?
Cheers,
Jim
On Thu, May 9, 2024 at 11:29 AM Jim Hughes wrote:
> Hi Ale
Hi Kanchi,
One can already directly query Kafka topics using Flink SQL. The Flink
Kafka connector allows one to use Kafka to back a Flink table.
As a concrete example, this blog post should explain things:
Hi Alexey,
Overall, the FLIP looks good and makes sense to me.
1. For the testing, I'd call the tests "execution" tests rather than
"restore" tests. For streaming execution, restore tests have the compiled
plan and intermediate state; the tests verify that those can work together
and continue
Hi Ferenc,
Looks like a good idea.
I'd prefer sticking to the SQL standard if possible. Would it be possible
/ sensible to allow for each syntax, perhaps managed by a config setting?
Cheers,
Jim
On Tue, Mar 26, 2024 at 6:59 AM Ferenc Csaky
wrote:
> Hello devs,
>
> I would like to start a
Hi Jeyhun,
I like the idea! Given FLIP-376[1], I wonder if it'd make sense to
generalize FLIP-434 to be about "pre-divided" data to cover "buckets" and
"partitions" (and maybe even situations where a data source is partitioned
and bucketed).
Separate from that, the page mentions TPC-H Q1 as an
Jim Hughes created FLINK-34173:
--
Summary: Implement CatalogTable.Builder
Key: FLINK-34173
URL: https://issues.apache.org/jira/browse/FLINK-34173
Project: Flink
Issue Type: Sub-task
Jim Hughes created FLINK-34172:
--
Summary: Add support for altering a distribution via ALTER TABLE
Key: FLINK-34172
URL: https://issues.apache.org/jira/browse/FLINK-34172
Project: Flink
Issue
Hi Jeyhun,
Generally, I like the idea of speeding up the optimizer in the case of
multiple queries!
I am new to the optimizer, but I have a few comments / questions.
1. StreamOptimizeContext may still be needed to pass the fact that we
are optimizing a streaming query. I don't think
Jim Hughes created FLINK-34067:
--
Summary: Fix javacc warnings in flink-sql-parser
Key: FLINK-34067
URL: https://issues.apache.org/jira/browse/FLINK-34067
Project: Flink
Issue Type: Improvement
Hi Alan,
+1 (non binding)
Cheers,
Jim
On Wed, Dec 20, 2023 at 2:41 PM Alan Sheinberg
wrote:
> Hi everyone,
>
> I'd like to start a vote on FLIP-400 [1]. It covers introducing a new UDF
> type, AsyncScalarFunction for completing invocations asynchronously. It
> has been discussed in this
Jim Hughes created FLINK-33918:
--
Summary: Fix AsyncSinkWriterThrottlingTest test failure
Key: FLINK-33918
URL: https://issues.apache.org/jira/browse/FLINK-33918
Project: Flink
Issue Type: Bug
Jim Hughes created FLINK-33805:
--
Summary: Implement restore tests for OverAggregate node
Key: FLINK-33805
URL: https://issues.apache.org/jira/browse/FLINK-33805
Project: Flink
Issue Type: Sub
ust mentioning that ahead
of time
Cheers,
Jim
>
> [1] https://issues.apache.org/jira/browse/FLINK-24204
>
>
>
>
>
>
> --
>
> Best！
> Xuyang
>
>
>
>
>
> At 2023-12-09 06:25:30, "Jim Hughes" wrote:
> >Hi Xuyang,
> &
Hi Xuyang,
As a clarification, since FLINK-24204 is finishing up work from
FLIP-145[1], do we need to discuss anything before you work out the details
of FLINK-24024 as a PR?
Relatedly, as that goes up for a PR, as part of FLINK-33421 [2], Bonnie and
I are working through migrating some of the
Jim Hughes created FLINK-33777:
--
Summary: ParquetTimestampITCase>FsStreamingSinkITCaseBase failing
in CI
Key: FLINK-33777
URL: https://issues.apache.org/jira/browse/FLINK-33777
Project: Fl
Hi Alan,
Nicely written and makes sense. The only feedback I have is around the
naming of the generalization, e.g. "Specifically, PythonCalcSplitRuleBase
will be generalized into RemoteCalcSplitRuleBase." This naming seems to
imply/suggest that all Async functions are remote. I wonder if we
Jim Hughes created FLINK-33767:
--
Summary: Implement restore tests for TemporalJoin node
Key: FLINK-33767
URL: https://issues.apache.org/jira/browse/FLINK-33767
Project: Flink
Issue Type: Sub
Jim Hughes created FLINK-33758:
--
Summary: Implement restore tests for TemporalSort node
Key: FLINK-33758
URL: https://issues.apache.org/jira/browse/FLINK-33758
Project: Flink
Issue Type: Sub
Jim Hughes created FLINK-33757:
--
Summary: Implement restore tests for Rank node
Key: FLINK-33757
URL: https://issues.apache.org/jira/browse/FLINK-33757
Project: Flink
Issue Type: Sub-task
Jim Hughes created FLINK-33756:
--
Summary: Missing record with CUMULATE/HOP windows using an
optimization
Key: FLINK-33756
URL: https://issues.apache.org/jira/browse/FLINK-33756
Project: Flink
Jim Hughes created FLINK-33676:
--
Summary: Implement restore tests for WindowAggregate node
Key: FLINK-33676
URL: https://issues.apache.org/jira/browse/FLINK-33676
Project: Flink
Issue Type: Sub
Jim Hughes created FLINK-33667:
--
Summary: Implement restore tests for MatchRecognize node
Key: FLINK-33667
URL: https://issues.apache.org/jira/browse/FLINK-33667
Project: Flink
Issue Type: Sub
+1 (non-binding)
Thanks, Dawid!
Jim
On Tue, Nov 21, 2023 at 7:20 AM Gyula Fóra wrote:
> +1 (binding)
>
> Gyula
>
> On Tue, 21 Nov 2023 at 13:11, xiangyu feng wrote:
>
> > +1 (non-binding)
> >
> > Thanks for driving this.
> >
> > Best,
> > Xiangyu Feng
> >
> >
> > Ferenc Csaky 于2023年11月21日周二
Jim Hughes created FLINK-33601:
--
Summary: Implement restore tests for Expand node
Key: FLINK-33601
URL: https://issues.apache.org/jira/browse/FLINK-33601
Project: Flink
Issue Type: Sub-task
Jim Hughes created FLINK-33521:
--
Summary: Implement restore tests for PythonCalc node
Key: FLINK-33521
URL: https://issues.apache.org/jira/browse/FLINK-33521
Project: Flink
Issue Type: Sub-task
Jim Hughes created FLINK-33488:
--
Summary: Implement restore tests for Deduplicate node
Key: FLINK-33488
URL: https://issues.apache.org/jira/browse/FLINK-33488
Project: Flink
Issue Type: Sub
Hi all,
+1 (non-binding)
Cheers,
Jim
On Mon, Nov 6, 2023 at 6:39 AM Timo Walther wrote:
> Hi everyone,
>
> I'd like to start a vote on FLIP-376: Add DISTRIBUTED BY clause[1] which
> has been discussed in this thread [2].
>
> The vote will be open for at least 72 hours unless there is an
Jim Hughes created FLINK-33470:
--
Summary: Implement restore tests for Join node
Key: FLINK-33470
URL: https://issues.apache.org/jira/browse/FLINK-33470
Project: Flink
Issue Type: Sub-task
Jim Hughes created FLINK-33469:
--
Summary: Implement restore tests for Limit node
Key: FLINK-33469
URL: https://issues.apache.org/jira/browse/FLINK-33469
Project: Flink
Issue Type: Sub-task
Hi Jing and Jark!
I can definitely appreciate the desire to have fewer configurations.
Do you have a suggested alternative for platform providers to limit or
restrict the hints that Bonnie is talking about?
As one possibility, maybe one configuration could be set to control all
hints.
Cheers,
Jim Hughes created FLINK-32691:
--
Summary: SELECT fcn does not work with an unset catalog or database
Key: FLINK-32691
URL: https://issues.apache.org/jira/browse/FLINK-32691
Project: Flink
Issue
Should this FLIP involve invalidating that information in some
manner? Or does truncating a source table for a query cause undefined
behavior on that query?
Basically, I'm trying to think through the implementations of a truncate
operation to streaming sources and queries.
Cheers,
Jim
> Best regar
Hi Yuxia,
Two questions:
1. Are you expecting all DynamicTableSinks to support Truncate? The FLIP
could use some explanation for what supporting and not supporting the
operation means.
2. How will truncate inoperate with streaming queries? That is, if I
truncate an input to a streaming
Hi all,
How do Flink formats relate to or interact with Paimon (formerly
Flink-Table-Store)? If the Flink format interface is used there, then it
may be useful to consider Arrow along with other columnar formats.
Separately, from previous experience, I've seen the Arrow format be useful
as an
Hi Yu,
Thanks for moving my comments to this thread! Also, thank you for
answering my questions; it is helping me understand the SQL Gateway
better.
5.
> Our idea is to introduce a new session option (like
'sql-client.result.fetch-interval') to control
the fetching requests sending frequency.
n my team about my design. My teammates
> > think it’s better to unify the local and remote mode, so I’ve
> investigated
> > and redesigned a new plan. I’ll inform you after the rewriting of FLIP
> > finished (will be soon) and Shengkai will help to your PR.
> > >
> &
PRs I see look pretty good. Are they going to be merged
soon? Anything else I can do to help?
Cheers,
Jim
On Mon, Nov 14, 2022 at 12:52 PM Jim Hughes wrote:
> Hi Yu,
>
> The PR looks good to me; the only thing I noticed is that the
> RemoveJarOperation may need to be added.
>
&g
ink/table/gateway/rest/handler/AbstractSqlGatewayRestHandler.java#L98
>
> Jim Hughes 于2022年11月12日周六 00:45写道：
>
> > Hi Shengkai,
> >
> > I think there is an additional case where a proxy is between the client
> and
> > gateway. In that case, being able to pass headers would
at 10:45 PM yu zelin wrote:
> Hi Jim,
>
> It would be nice if you can take a look on
> https://github.com/apache/flink/pull/21133 and give me some feedback.
>
> Best,
> Yu Zelin
>
> > 2022年11月12日 00:44，Jim Hughes 写道：
> >
> > Hi Shengkai,
> >
>
an join us to finish the feature. I think the
> modification about the SQL Gateway side is ready to review.
>
> Best,
> Shengkai
>
>
> Jim Hughes 于2022年11月11日周五 05:19写道：
>
> > Hi Yu Zelin,
> >
> > I have read through your draft and it looks good. I am n
Hi Yu Zelin,
I have read through your draft and it looks good. I am new to Flink, so I
haven't learned about everything which needs to be done yet.
One of the considerations that I'm interested in understanding is how to
pass additional headers when sending REST requests. From looking at the
44 matches
Mail list logo
