Zheng Hu created FLINK-14446:
Summary: Design a Java end to end test framework for supporting
more external system
Key: FLINK-14446
URL: https://issues.apache.org/jira/browse/FLINK-14446
Project: Flink
Another perspective is that a stable, carefully-designed interface with
clear semantic
could be safer to customize.
Following the discussion in FLINK-10333 our JobGraphStore is actually
required
performing write operation only with leadership, which is a basic
requirement
for coordination rather
+1 to start a vote.
Good to see that it is backward compatibility, as python UDFs will also be
affected.
BTW, do we target this Flip to release-1.10?
Best, Hequn
On Wed, Oct 16, 2019 at 6:19 PM Timo Walther wrote:
> Hi everyone,
>
> thanks for the comments in the doc. The feedback so far was
Yun Tang created FLINK-14445:
Summary: Python module build failed when making sdist
Key: FLINK-14445
URL: https://issues.apache.org/jira/browse/FLINK-14445
Project: Flink
Issue Type: Bug
Thanks Chesnay! Great job!
Best,
Vino
Jark Wu 于2019年10月18日周五 上午9:51写道：
> Thanks Chesnay! This is really a great job!
>
> Best,
> Jark
>
> > 在 2019年10月17日，22:03，未来阳光 <2217232...@qq.com> 写道：
> >
> > Thanks for this improvement Chesnay !
> >
> >
> >
> >
> > ---Original---
> > From: "Chesnay Schepl
Cool! Thanks a lot for the improvement, Chesnay!
On Fri, Oct 18, 2019 at 9:51 AM Jark Wu wrote:
> Thanks Chesnay! This is really a great job!
>
> Best,
> Jark
>
> > 在 2019年10月17日，22:03，未来阳光 <2217232...@qq.com> 写道：
> >
> > Thanks for this improvement Chesnay !
> >
> >
> >
> >
> > ---Original---
>
Thanks Chesnay! This is really a great job!
Best,
Jark
> 在 2019年10月17日，22:03，未来阳光 <2217232...@qq.com> 写道：
>
> Thanks for this improvement Chesnay !
>
>
>
>
> ---Original---
> From: "Chesnay Schepler" Date: Thu, Oct 17, 2019 21:37 PM
> To: "dev@flink.apache.org" Subject: [NOTICE] Binary licen
Michael Holler created FLINK-1:
--
Summary: Publish BOMs for Flink
Key: FLINK-1
URL: https://issues.apache.org/jira/browse/FLINK-1
Project: Flink
Issue Type: Improvement
None none created FLINK-14443:
-
Summary: Enable checkpointing for JDBC sink/output
Key: FLINK-14443
URL: https://issues.apache.org/jira/browse/FLINK-14443
Project: Flink
Issue Type: Improvement
None none created FLINK-14442:
-
Summary: Add time based interval execution to JDBC connectors.
Key: FLINK-14442
URL: https://issues.apache.org/jira/browse/FLINK-14442
Project: Flink
Issue Type: I
Hi Yijie,
I also agree with Jark on separating the Catalog part into another FLIP.
With FLIP-27[1] also in the air, it is also probably great to split and
unblock the sink implementation contribution.
I would suggest either putting in a detail implementation plan section in
the doc, or (maybe too
Thanks for pointing them out, Dawid. I've went over the overall doc again
and corrected the above typos.
- ModuleManager#listFunctions() returns Set
- ModuleManager holds a LinkedHashMap to keep loaded
modules in order
- ModuleFactory#createModule(Map) and returns Module
On Thu, Oct 17, 2019 at
+1 (binding)
- Verified signatures and checksums
- Source archive does not contain any new binaries
- Successfully built Flink from sources for Hadoop 2.7.5 and Scala 2.12
- Verified that no new dependencies have been added
- Verified that the last release-1.9 cron job passed. The cron job being
e
hailong wang created FLINK-14441:
Summary: Fix ValueLiteralExpression#getValueAs when valueClass is
Period.class
Key: FLINK-14441
URL: https://issues.apache.org/jira/browse/FLINK-14441
Project: Flink
Zhu Zhu created FLINK-14440:
---
Summary: Enable BatchFineGrainedRecoveryITCase to pass with
scheduler NG
Key: FLINK-14440
URL: https://issues.apache.org/jira/browse/FLINK-14440
Project: Flink
Issue
Zhu Zhu created FLINK-14439:
---
Summary: RestartPipelinedRegionStrategy leverage tracked partition
availability for better failover experience in DefaultScheduler
Key: FLINK-14439
URL: https://issues.apache.org/jira/brow
Thanks for this improvement Chesnay !
---Original---
From: "Chesnay Schepler"https://cwiki.apache.org/confluence/display/FLINK/Licensing>; accordingly.
Thanks for this improvement Chesnay ;-)
Best,
tison.
Chesnay Schepler 于2019年10月17日周四 下午9:37写道：
> Hello,
>
> I just merged FLINK-14008 to 1.8, 1.9 and 1.10, which means that from
> now on the tricky part of the binary licensing (NOTICE-binary,
> licenses-binary) is automatically generated durin
Hello,
I just merged FLINK-14008 to 1.8, 1.9 and 1.10, which means that from
now on the tricky part of the binary licensing (NOTICE-binary,
licenses-binary) is automatically generated during the release process.
As such these files have been removed from the root directory of the
project (th
Thanks for creating this FLIP and starting the VOTE for it.
+1 (binding)
Cheers,
Till
On Thu, Oct 17, 2019 at 5:08 AM Yun Gao
wrote:
> Hi Chesnay,
>
> +1 (non-binding).
>
> Very thanks for driving this.
>
> Best,
> Yun
>
>
>
Timo Walther created FLINK-14438:
Summary: Fix RowTypeInfo.equals()
Key: FLINK-14438
URL: https://issues.apache.org/jira/browse/FLINK-14438
Project: Flink
Issue Type: Improvement
Co
Timo Walther created FLINK-14437:
Summary: Drop the legacy planner
Key: FLINK-14437
URL: https://issues.apache.org/jira/browse/FLINK-14437
Project: Flink
Issue Type: Sub-task
Compon
A challenge is how we ensure the support for customized implementation. When
we introduce JobGraphStore#releaseJobGraph we actually change quite a bit
codepath
in Dispatcher. While we are unable to test arbitrarily customized
implementation our
compatibility promise is actually no more than compila
Hi devs,
Recently the community excludes customize support on new restart strategies[1],
which reminds
me to think of which kind of customized support a framework like Flink
should provides.
The key idea is pluggable is not customizable.
We might handle a series of implementation of restart stra
Kevin Zhang created FLINK-14436:
---
Summary: Add getter for ContextEnvironment instance in
StreamContextEnvironment
Key: FLINK-14436
URL: https://issues.apache.org/jira/browse/FLINK-14436
Project: Flink
lining created FLINK-14435:
--
Summary: Add TaskManagerResourceInfo in TaskManagerDetailsInfo to
show TaskManager Resource
Key: FLINK-14435
URL: https://issues.apache.org/jira/browse/FLINK-14435
Project: Flink
Zili Chen created FLINK-14434:
-
Summary: Dispatcher#createJobManagerRunner should returns on
creation succeed, not after startJobManagerRunner
Key: FLINK-14434
URL: https://issues.apache.org/jira/browse/FLINK-14434
Congxian Qiu(klion26) created FLINK-14433:
-
Summary: Move generated Jaas conf file from /tmp directory to Job
specific directory
Key: FLINK-14433
URL: https://issues.apache.org/jira/browse/FLINK-14433
Canbin Zheng created FLINK-14432:
Summary: Add 'SHOW SYSTEM FUNCTIONS' support in SQL CLI
Key: FLINK-14432
URL: https://issues.apache.org/jira/browse/FLINK-14432
Project: Flink
Issue Type: Im
lining created FLINK-14431:
--
Summary: Update TaskManager's memory information to match its
memory composition
Key: FLINK-14431
URL: https://issues.apache.org/jira/browse/FLINK-14431
Project: Flink
Hi all,
Generally I'm fine with the design. Before I cast my +1 I wanted to
clarify one thing. Is the module name in ModuleFactory#createModule
necessary? Can't it be just?:
interface ModuleFactory extends TableFactory {
Module createModule(Map properties);
}
The name under which the module w
Jark Wu created FLINK-14430:
---
Summary: BaseArraySerializerTest.testDuplicate fails on travis
Key: FLINK-14430
URL: https://issues.apache.org/jira/browse/FLINK-14430
Project: Flink
Issue Type: Bug
liupengcheng created FLINK-14429:
Summary: Wrong app final status when running yarn-cluster in
non-detached mode
Key: FLINK-14429
URL: https://issues.apache.org/jira/browse/FLINK-14429
Project: Flink
vinoyang created FLINK-14428:
Summary: Non-consistency key access in KeyedProcessFunction when
use keyed state in both processElement and onTimer method
Key: FLINK-14428
URL: https://issues.apache.org/jira/browse/FLIN
qinkaixin created FLINK-14427:
-
Summary: 批流融合
Key: FLINK-14427
URL: https://issues.apache.org/jira/browse/FLINK-14427
Project: Flink
Issue Type: Improvement
Environment: 批流融合
Sounds good to me.
Thanks,
Timo
On 17.10.19 09:30, Kostas Kloudas wrote:
Hi Timo,
I agree that distinguishing between "executor" and "execution" when
scanning through a configuration file can be difficult. These names
were mainly influenced by the fact that FLIP-73 introduced the
"Executor".
Hi Timo,
I agree that distinguishing between "executor" and "execution" when
scanning through a configuration file can be difficult. These names
were mainly influenced by the fact that FLIP-73 introduced the
"Executor".
In addition, I agree that "deployment" or "deploy" sound good
alternatives. Be
37 matches
Mail list logo
