Till Rohrmann created FLINK-12323:
-
Summary: Remove legacy ActorGateway implementations
Key: FLINK-12323
URL: https://issues.apache.org/jira/browse/FLINK-12323
Project: Flink
Issue Type:
Hi Stephan,
This is excited! Thanks for sharing. The inter-process communication
code looks like the most natural choice as a common ground. To go
further, there are indeed some challenges to solve.
=> Biggest question is whether the language-independent DAG is expressive
enough to capture
Hi,
I gave you the permission.
On Mon, Apr 22, 2019 at 12:57 PM Armstrong wrote:
> Hi,
>
> I want to contribute to Apache Flink.
> Would you please give me the contributor permission?
> My JIRA ID is Armstrongya.
>
Hi,
I gave you the permission.
On Mon, Apr 22, 2019 at 12:45 PM 张军 wrote:
> Hi,
> I want to contribute to Apache Flink.
> Would you please give me the contributor permission?
> My JIRA ID is zhangjun
> Thanks.
Hi,
I gave you the permissions.
On Thu, Apr 18, 2019 at 5:05 PM peng2251 wrote:
> Hi,
>
>
> I want to contribute to Apache Flink.
> Would you please give me the contributor permission?
> My JIRA ID is TonySu.
> Thanks.
Hi,
I gave you the permission.
On Sat, Apr 20, 2019 at 12:24 PM Dillon Zhang wrote:
> Hi,
>
> I've been interested in flink for a long time and have worked on a few
> internal features mainly in flink-runtime.
>
> I'd like to apply for contributor permission so that I could join feature
>
godfrey he created FLINK-12321:
--
Summary: Supports sub-plan reuse
Key: FLINK-12321
URL: https://issues.apache.org/jira/browse/FLINK-12321
Project: Flink
Issue Type: Bug
Components:
Till Rohrmann created FLINK-12322:
-
Summary: Remove legacy ActorTaskManagerGateway
Key: FLINK-12322
URL: https://issues.apache.org/jira/browse/FLINK-12322
Project: Flink
Issue Type: Sub-task
Hi,
Welcome to the Flink community. I gave you the permissions.
On Wed, Apr 24, 2019 at 2:28 PM Sean Mao wrote:
> Hi,
> I want to contribute to Apache Flink.
> Would you please give me the contributor permission?
> My JIRA ID is seancxmao (
>
Hi,
I gave you the permission.
On Wed, Apr 24, 2019 at 12:42 PM cc c wrote:
> Hi,
>
> I want to contribute to Apache Flink.
> Would you please give me the contributor permission?
> My JIRA ID is chauncy
>
Till Rohrmann created FLINK-12324:
-
Summary: Remove ActorGateway interface
Key: FLINK-12324
URL: https://issues.apache.org/jira/browse/FLINK-12324
Project: Flink
Issue Type: Sub-task
Hey all,
quick update on this project: The frontend and backend code have been put
together into this repository: https://github.com/sorahn/flink-ecosystem
We also just agreed on an API specification, and will now work on finishing
the backend.
It will probably take a few more weeks for this to
Hi,
I gave you the permission.
On Wed, Apr 17, 2019 at 2:58 PM QingA Li wrote:
> Hi,
>
> I want to contribute to Apache Flink.
> Would you please give me the contributor permission?
> My JIRA ID is moqi.
>
Hi,
I gave you the permissions.
On Wed, Apr 17, 2019 at 3:18 PM DONG, Weike wrote:
> Hi,
>
> I want to contribute to Apache Flink.
> Would you please give me the contributor permission?
>
> My JIRA ID is kyledong
>
> Thanks : )
>
Thanks for the meeting summary, Stephan. Sound like you covered a lot of
ground. Some more comments below, adding onto what Max has said.
On Wed, Apr 24, 2019 at 3:20 PM Maximilian Michels wrote:
>
> Hi Stephan,
>
> This is excited! Thanks for sharing. The inter-process communication
> code
Richard Deurwaarder created FLINK-12325:
---
Summary: Statsd reporter gives wrong metrics when using negative
numbers
Key: FLINK-12325
URL: https://issues.apache.org/jira/browse/FLINK-12325
sunjincheng created FLINK-12327:
---
Summary: Add simplicity support for submitting Python Table API
job in CliFrontend, i.e. `flink run -py wordcount.py` can be work(with simple
test).
Key: FLINK-12327
URL:
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is zm12397.
I would like to thank you for your generous help in this matter.
sunjincheng created FLINK-12326:
---
Summary: Add a basic test framework, just like the existing Java
TableAPI, abstract some TestBase.
Key: FLINK-12326
URL: https://issues.apache.org/jira/browse/FLINK-12326
chauncy created FLINK-12328:
---
Summary: Invalid Express
Key: FLINK-12328
URL: https://issues.apache.org/jira/browse/FLINK-12328
Project: Flink
Issue Type: Improvement
Affects Versions: 1.8.0
Thanks everyone for the discussion here.
Regarding to the Java/Scala UDF and the built-in UDF to execute in the current
Flink way (directly in JVM, not via RPC), I share the same thoughts with Max
and Robert and I think it will not be a big problem. From the design doc, I
guess the main
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is quan
Best regards
Hi Robert,
In addition to the questions described by Dian, I also want to know what
difficult problems Py4j's solution will encounter in add UDF support, which
you mentioned as follows:
Using something like Py4j is an easy way to get up an running, especially
> for a very faithful API, but the
Yingjie Cao created FLINK-12329:
---
Summary: Netty thread deadlock bug of the SpilledSubpartitionView
Key: FLINK-12329
URL: https://issues.apache.org/jira/browse/FLINK-12329
Project: Flink
Issue
Thanks for the update, Robert. Looking forward to the website. If there is
already a list of software we need to run the website, we can ask Apache
infra team to prepare the VM for us, as that may also take some time.
On Wed, Apr 24, 2019 at 11:57 PM Robert Metzger wrote:
> Hey all,
>
> quick
Hi Gary,
+ 1 to remove it for now. Actually some users are not aware of that it’s still
experimental, and ask quite a lot about the problem it causes.
Best,
Paul Lam
> 在 2019年4月24日，14:49，Stephan Ewen 写道：
>
> Sounds reasonable to me. If it is a broken feature, then there is not much
> value
sunjincheng created FLINK-12311:
---
Summary: Add base python framework and Add Scan, Projection, and
Filter operator support
Key: FLINK-12311
URL: https://issues.apache.org/jira/browse/FLINK-12311
Hi Till,
IMHO, allow adding hooks involves 2 steps.
1. Provide hook interface, and call these hook in flink (ClusterClient) at
the right place. This should be done by framework (flink)
2. Implement new hook implementation and add/register them into
framework(flink)
What I am doing is step 1
FaxianZhao created FLINK-12309:
--
Summary: JDBCOoutputFormat and JDBCAppendTableSink float behavior
is not align
Key: FLINK-12309
URL: https://issues.apache.org/jira/browse/FLINK-12309
Project: Flink
Thank you so much for driving this, really great job!
About Flink internals: Agreed, that is not a good match. It needs to deep
technical understanding. Also, the benefit of having a technical writer
(make this easily understandable to less involved developers) is not as
helpful there.
Also
Hi Ken,
It’s a bad story for us: even for a small window we have a dozens of thousands
events per job with 10x in peaks or even more. And the number of jobs was known
to be high. So instead of N operations (our producer/consumer mechanism) with
shuffle/resorting (current flink realization) it
About auto-closing PRs from unassigned issues, consider the following case
that has happened quite a bit.
- a user reports a small bug and immediately wants to provide a fix for it
- it makes sense to not stall the user for a few days until a committer
assigned the issue
- not auto-closing
Ufuk Celebi created FLINK-12313:
---
Summary:
SynchronousCheckpointITCase.taskCachedThreadPoolAllowsForSynchronousCheckpoints
is unstable
Key: FLINK-12313
URL: https://issues.apache.org/jira/browse/FLINK-12313
YangFei created FLINK-12314:
---
Summary: Translate "Types Serializationn" into Chinese
Key: FLINK-12314
URL: https://issues.apache.org/jira/browse/FLINK-12314
Project: Flink
Issue Type: Sub-task
+1 for temporarily removing support for the modify command.
Eventually, we have to add it again in order to support auto scaling. The
next time we add it, we should address the known limitations.
Cheers,
Till
On Wed, Apr 24, 2019 at 9:06 AM Paul Lam wrote:
> Hi Gary,
>
> + 1 to remove it for
Hi Stephan，
Thanks for your summary, from the points of my view, we are on the same
page about the conclusion of the discussion!
I completely agree that we can divide the support of the Python Table API
into short-term and long-term goals, and the design of short-term goals
should be smoothly
also +1 for option 2.
I think auto-close a PR sometimes a bit impertinency.
The reasons just like Stephan mentioned.
Stephan Ewen 于2019年4月24日周三 下午4:08写道：
> About auto-closing PRs from unassigned issues, consider the following case
> that has happened quite a bit.
>
> - a user reports a small
Chesnay Schepler created FLINK-12315:
Summary: SynchronousCheckpointITCase deadlocks on Travis
Key: FLINK-12315
URL: https://issues.apache.org/jira/browse/FLINK-12315
Project: Flink
Chesnay Schepler created FLINK-12316:
Summary: JDBCFullTest fails on Java 9
Key: FLINK-12316
URL: https://issues.apache.org/jira/browse/FLINK-12316
Project: Flink
Issue Type: Sub-task
Chesnay Schepler created FLINK-12318:
Summary: TimestampITCase deadlocks on Java 9
Key: FLINK-12318
URL: https://issues.apache.org/jira/browse/FLINK-12318
Project: Flink
Issue Type:
Chesnay Schepler created FLINK-12317:
Summary: SynchronousCheckpointITCase fails on Java 9
Key: FLINK-12317
URL: https://issues.apache.org/jira/browse/FLINK-12317
Project: Flink
Issue
Will we only remove command support in client side or the code in job
master will also be removed?
Till Rohrmann 于2019年4月24日周三 下午4:12写道：
> +1 for temporarily removing support for the modify command.
>
> Eventually, we have to add it again in order to support auto scaling. The
> next time we add
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is chauncy
I think this sounds reasonable.
Let's keep the "reconfiguration without stopping the job" out of this,
because that would be a super big effort and if we approach that, then in
more generic way rather than specific to connector metrics.
I would suggest to look at the following things before
The idea is to also remove the rescaling code in the JobMaster. This will
make
it easier to remove the ExecutionGraph reference from the JobMaster which is
needed for the scheduling rework [1].
[1] https://issues.apache.org/jira/browse/FLINK-12231
On Wed, Apr 24, 2019 at 12:14 PM Shuai Xu
Hi Mikhail,
Thanks a lot for being interested in contributing! Connectors are crucial
to Flink ecosystem, the contribution is more than welcome.
Right now there are some ongoing changes to the way we manage Flink
connectors. The basic idea is to maintain the connectors separately from
the Flink
Bowen Li created FLINK-12310:
Summary: shade user facing common libraries in flink-connector-hive
Key: FLINK-12310
URL: https://issues.apache.org/jira/browse/FLINK-12310
Project: Flink
Issue
Gary Yao created FLINK-12312:
Summary: Remove CLI command for rescaling
Key: FLINK-12312
URL: https://issues.apache.org/jira/browse/FLINK-12312
Project: Flink
Issue Type: Sub-task
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is seancxmao (
https://issues.apache.org/jira/secure/ViewProfile.jspa?name=seancxmao)
Thanks,
Chenxiao Mao
Marco Pfatschbacher created FLINK-12319:
---
Summary: StackOverFlowError in cep.nfa.sharedbuffer.SharedBuffer
Key: FLINK-12319
URL: https://issues.apache.org/jira/browse/FLINK-12319
Project: Flink
shin chen created FLINK-12320:
-
Summary: Flink bucketing sink restart with save point cause data
loss when using SequenceFile.CompressionType.BLOCK
Key: FLINK-12320
URL:
51 matches
Mail list logo
