Hi all,
Publish the PyFlink into PyPI is very important for our user, Please vote
on the following proposal:
1. Create PyPI Project for Apache Flink Python API, named: "apache-flink"
2. Release one binary with the default Scala version same with flink
default config.
3. Create an account, named "
Rui Li created FLINK-13526:
--
Summary: Switching to a non existing database crashes sql-client
Key: FLINK-13526
URL: https://issues.apache.org/jira/browse/FLINK-13526
Project: Flink
Issue Type: Bug
Thanks for your confirm Till !
Publish the PyFlink into PyPI is very important for our user, I
have initiated a voting thread.
Best,
Jincheng
Till Rohrmann 于2019年7月29日周一 下午3:01写道：
> Sounds good to me. Thanks for driving this discussion.
>
> Cheers,
> Till
>
> On Mon, Jul 29, 2019 at 9:24 AM ji
Hi Jincheng,
Thanks a lot for driving this.
+1 (non-binding).
Regards,
Dian
> 在 2019年8月1日，下午3:24，jincheng sun 写道：
>
> Hi all,
>
> Publish the PyFlink into PyPI is very important for our user, Please vote
> on the following proposal:
>
> 1. Create PyPI Project for Apache Flink Python API, nam
Yun Tang created FLINK-13527:
Summary: Instable KafkaProducerExactlyOnceITCase due to
CheckpointFailureManager
Key: FLINK-13527
URL: https://issues.apache.org/jira/browse/FLINK-13527
Project: Flink
Chesnay Schepler created FLINK-13528:
Summary: Kafka 0.10/0.11 E2E test fail on Java 11
Key: FLINK-13528
URL: https://issues.apache.org/jira/browse/FLINK-13528
Project: Flink
Issue Type:
+1 (binding)
On Thu, Aug 1, 2019 at 9:52 AM Dian Fu wrote:
> Hi Jincheng,
>
> Thanks a lot for driving this.
> +1 (non-binding).
>
> Regards,
> Dian
>
> > 在 2019年8月1日，下午3:24，jincheng sun 写道：
> >
> > Hi all,
> >
> > Publish the PyFlink into PyPI is very important for our user, Please vote
> > on
+1 （non-binding）
Stephan Ewen 于2019年8月1日周四 下午4:29写道：
> +1 (binding)
>
> On Thu, Aug 1, 2019 at 9:52 AM Dian Fu wrote:
>
> > Hi Jincheng,
> >
> > Thanks a lot for driving this.
> > +1 (non-binding).
> >
> > Regards,
> > Dian
> >
> > > 在 2019年8月1日，下午3:24，jincheng sun 写道：
> > >
> > > Hi all,
> >
Please open a JIRA with INFRA and ask whether OpenLab/Drone are
supported by INFRA.
On 01/08/2019 04:16, Xiyuan Wang wrote:
Thanks for your reply.
We are now keeping investigating and debugging Flink on ARM. It's hard for
us to say How many kinds of test are enough for ARM support at this mom
+1 （non-binding）
Jeff Zhang 于2019年8月1日周四 下午4:33写道：
> +1 （non-binding）
>
> Stephan Ewen 于2019年8月1日周四 下午4:29写道：
>
> > +1 (binding)
> >
> > On Thu, Aug 1, 2019 at 9:52 AM Dian Fu wrote:
> >
> > > Hi Jincheng,
> > >
> > > Thanks a lot for driving this.
> > > +1 (non-binding).
> > >
> > > Regards,
Asking INFRA to add support means filing a JIRA ticket.
That works the same way as filing a FLINK Jira ticket, but selecting INFRA
as the project to file the ticket for.
On Thu, Aug 1, 2019 at 4:17 AM Xiyuan Wang wrote:
> Thanks for your reply.
>
> We are now keeping investigating and debugging
Jing Zhang created FLINK-13529:
--
Summary: Verify and correct agg function's semantic for Blink
planner
Key: FLINK-13529
URL: https://issues.apache.org/jira/browse/FLINK-13529
Project: Flink
Iss
Hi all!
I would like to backport a minor chance from 'master' to 'release-1.9'.
It is a very minor change
I am checking here because this is not technically a bug fix, but a way of
exposing the raw keyed state stream in tasks a bit different. It would
unblock some work in a project that tries to
Thanks for checking. No concerns on my side. +1 to back port. Fixing fault
tolerance of streaming iterations sounds like a very valuable thing to
unblock with this release.
– Ufuk
On Thu, Aug 1, 2019 at 11:02 AM Stephan Ewen wrote:
> Hi all!
>
> I would like to backport a minor chance from 'ma
Hi David,
thanks for starting this discussion. I like the idea of improving insights
into Flink's execution and I believe that a flame graph could be helpful.
I quickly glanced over your changes and I think they go in a good
direction. One idea could be to share the `StackTraceSample` produced by
Thanks for the pointer. I'll take a look later today.
Cheers,
Till
On Thu, Aug 1, 2019 at 8:00 AM David Morávek
wrote:
> Hi Till, the PR should be ready ;) Can you please do the final check?
>
> Best,
> D.
>
> On Tue, Jul 23, 2019 at 3:01 PM Till Rohrmann
> wrote:
>
> > I've assigned the issue
+1
Cheers,
Till
On Thu, Aug 1, 2019 at 10:39 AM vino yang wrote:
> +1 （non-binding）
>
> Jeff Zhang 于2019年8月1日周四 下午4:33写道：
>
> > +1 （non-binding）
> >
> > Stephan Ewen 于2019年8月1日周四 下午4:29写道：
> >
> > > +1 (binding)
> > >
> > > On Thu, Aug 1, 2019 at 9:52 AM Dian Fu wrote:
> > >
> > > > Hi Jinch
Chesnay Schepler created FLINK-13530:
Summary: AbstractServerTest failed on Travis
Key: FLINK-13530
URL: https://issues.apache.org/jira/browse/FLINK-13530
Project: Flink
Issue Type: Bug
I've quickly glanced over the changes and I would be ok with backporting it
if it helps fixing fault tolerance of streaming iterations. Hence +1 from
my side.
Cheers,
Till
On Thu, Aug 1, 2019 at 11:20 AM Ufuk Celebi wrote:
> Thanks for checking. No concerns on my side. +1 to back port. Fixing f
+1 as well. If this affects the fault tolerance of streaming iteration, I'd
consider this as a bug fix.
On Thu, Aug 1, 2019 at 11:44 AM Till Rohrmann wrote:
> I've quickly glanced over the changes and I would be ok with backporting it
> if it helps fixing fault tolerance of streaming iterations.
+1 (non-binding)
Thanks for driving this!
Best Regards,
Yu
On Thu, 1 Aug 2019 at 11:41, Till Rohrmann wrote:
> +1
>
> Cheers,
> Till
>
> On Thu, Aug 1, 2019 at 10:39 AM vino yang wrote:
>
> > +1 （non-binding）
> >
> > Jeff Zhang 于2019年8月1日周四 下午4:33写道：
> >
> > > +1 （non-binding）
> > >
> > > S
For clarification: It does not fix the loop fault tolerance in the existing
API. There, the concepts are a bit messy and this needs a bigger overhaul.
It is a building block for building fault tolerant loops in downstream
projects.
On Thu, Aug 1, 2019 at 11:45 AM Becket Qin wrote:
> +1 as well.
Yun Gao created FLINK-13531:
---
Summary: Do not print log and call release if no requests should
be evicted in slot sharing
Key: FLINK-13531
URL: https://issues.apache.org/jira/browse/FLINK-13531
Project: Fli
Chesnay Schepler created FLINK-13532:
Summary: Broken links in documentation
Key: FLINK-13532
URL: https://issues.apache.org/jira/browse/FLINK-13532
Project: Flink
Issue Type: Bug
Chesnay Schepler created FLINK-13533:
Summary: CassandraConnectorITCase fails on Java 11
Key: FLINK-13533
URL: https://issues.apache.org/jira/browse/FLINK-13533
Project: Flink
Issue Type:
Hi Bekir
I'll first comb through all the information here, and try to find out the
reason with you, maybe need you to share some more information :)
Best,
Congxian
Bekir Oguz 于2019年8月1日周四 下午5:00写道：
> Hi Fabian,
> Thanks for sharing this with us, but we’re already on version 1.8.1.
>
> What I
Rui Li created FLINK-13534:
--
Summary: Unable to query Hive table with decimal column
Key: FLINK-13534
URL: https://issues.apache.org/jira/browse/FLINK-13534
Project: Flink
Issue Type: Bug
Hi all,
As you probably already noticed, Stephan has triggered a discussion thread
about code style guide for Flink [1]. Recently we were discussing
internally some smaller concerns and I would like start separate threads
for them.
This thread is about creating collections always with initial cap
Nico Kruber created FLINK-13535:
---
Summary: Do not abort transactions twice during KafkaProducer
startup
Key: FLINK-13535
URL: https://issues.apache.org/jira/browse/FLINK-13535
Project: Flink
I
+1 on setting initial capacity only when have good expectation on the
collection size.
Thank you~
Xintong Song
On Thu, Aug 1, 2019 at 2:32 PM Andrey Zagrebin wrote:
> Hi all,
>
> As you probably already noticed, Stephan has triggered a discussion thread
> about code style guide for Flink [1]
+1 (non-binding)
Cheers,
Jark
On Thu, 1 Aug 2019 at 17:45, Yu Li wrote:
> +1 (non-binding)
>
> Thanks for driving this!
>
> Best Regards,
> Yu
>
>
> On Thu, 1 Aug 2019 at 11:41, Till Rohrmann wrote:
>
> > +1
> >
> > Cheers,
> > Till
> >
> > On Thu, Aug 1, 2019 at 10:39 AM vino yang wrote:
> >
Hi Flink devs,
RC1 for Apache Flink 1.9.0 has been created. Just as RC0, this is still
a preview-only RC to drive the current testing efforts. This has all the
artifacts that we would typically have for a release, except for a source
code tag and a PR for the release announcement.
RC1 contains th
Update: RC1 for 1.9.0 has been created. Please see [1] for the preview
source / binary releases and Maven artifacts.
Best,
Kurt
[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PREVIEW-Apache-Flink-1-9-0-release-candidate-1-td31233.html
On Tue, Jul 30, 2019 at 2:36 PM Tzu-Li (
François Lacombe created FLINK-13536:
Summary: Improve nullability handling in Types
Key: FLINK-13536
URL: https://issues.apache.org/jira/browse/FLINK-13536
Project: Flink
Issue Type: Imp
Nico Kruber created FLINK-13537:
---
Summary: Changing Kafka producer pool size and scaling out may
create overlapping transaction IDs
Key: FLINK-13537
URL: https://issues.apache.org/jira/browse/FLINK-13537
François Lacombe created FLINK-13538:
Summary: Give field names in deserializers thrown exceptions
Key: FLINK-13538
URL: https://issues.apache.org/jira/browse/FLINK-13538
Project: Flink
I
Hi everybody,
I think I'm in the same issue above described in
https://issues.apache.org/jira/browse/FLINK-6291 . Flink1-6.4
I have had this savepoint with a timer service belonging to a process
function. When I restore a new job w/o the former process function ti fails
in the following way.
What i
Thanks Jincheng for working on this.
+1 (non-binding)
Thanks,
Biao /'bɪ.aʊ/
On Thu, Aug 1, 2019 at 8:55 PM Jark Wu wrote:
> +1 (non-binding)
>
> Cheers,
> Jark
>
> On Thu, 1 Aug 2019 at 17:45, Yu Li wrote:
>
> > +1 (non-binding)
> >
> > Thanks for driving this!
> >
> > Best Regards,
> > Yu
Hi all,
This is the next follow up discussion about suggestions for the recent
thread about code style guide in Flink [1].
In general, one could argue that any variable, which is nullable, can be
replaced by wrapping it with Optional to explicitly show that it can be
null. Examples are:
- ret
Hi,
> - a bit more code, increases maintenance burden.
I think there is even more to that. It’s almost like a code duplication, albeit
expressed in very different way, with all of the drawbacks of duplicated code:
initial capacity can drift out of sync, causing confusion. Also it’s not “a bit
Hi all,
This is one more small suggestion for the recent thread about code style
guide in Flink [1].
We already have a note about using a new line for each chained call in
Scala, e.g. either:
*values**.stream()**.map(...)**,collect(...);*
or
*values*
*.stream()*
*.map(*...*)*
*.col
+1 (non-binding)
Thanks a lot for driving this! @jincheng sun
Best, Hequn
On Thu, Aug 1, 2019 at 11:00 PM Biao Liu wrote:
> Thanks Jincheng for working on this.
>
> +1 (non-binding)
>
> Thanks,
> Biao /'bɪ.aʊ/
>
>
>
> On Thu, Aug 1, 2019 at 8:55 PM Jark Wu wrote:
>
> > +1 (non-binding)
> >
>
Jingsong Lee created FLINK-13539:
Summary: DDL do not support CSV tableFactory because CSV require
format.fields
Key: FLINK-13539
URL: https://issues.apache.org/jira/browse/FLINK-13539
Project: Flink
Jingsong Lee created FLINK-13540:
Summary: DDL do not support key of properties contains number or
"-"
Key: FLINK-13540
URL: https://issues.apache.org/jira/browse/FLINK-13540
Project: Flink
EDIT: for Optional in public API vs performance concerns
Hi all,
This is the next follow up discussion about suggestions for the recent
thread about code style guide in Flink [1].
In general, one could argue that any variable, which is nullable, can be
replaced by wrapping it with Optional to ex
Hi Andrey,
I think that’s a good compromise easy to follow, so +1 from my side.
Piotrek
> On 1 Aug 2019, at 18:00, Andrey Zagrebin wrote:
>
> EDIT: for Optional in public API vs performance concerns
>
> Hi all,
>
> This is the next follow up discussion about suggestions for the recent
> thre
Seth Wiesman created FLINK-13541:
Summary: State Processor Api sets the wrong key selector when
writing savepoints
Key: FLINK-13541
URL: https://issues.apache.org/jira/browse/FLINK-13541
Project: Flin
Hi Till, thanks for the feedback! These endpoints are only called when the
vertex is selected in the UI, so there should be any heavy RPC load. For
back-pressure, we only sample top 3 calls of the stack (depth = 3). For the
flame-graph, we want to sample the whole stack trace and we need different
Mans Singh created FLINK-13542:
--
Summary: Flink Datadog metrics reporter sends empty series if
there is no metrics
Key: FLINK-13542
URL: https://issues.apache.org/jira/browse/FLINK-13542
Project: Flink
Hi:
I've created a JIRA issue
https://issues.apache.org/jira/browse/FLINK-13542?filter=-2 and have submitted
a pull request, but I am not able to assign it to myself. I believe I had the
privs earlier. Can you please let me know how I can assign the issue to myself.
Thanks
Mans
Hi Andrey,
Thanks for bringing this. Personally, I prefer to the following style which
(1) puts the right parenthese in the next line
(2) a new line for each exception if exceptions can not be put in the same
line
That way, parentheses are aligned in a similar way to braces and exceptions
can be
@Chesnay @ Stephan Thanks for the suggestion and help, and I open a JIRA
in [1].
Any other questions you could feel free to ping us.
[1] https://issues.apache.org/jira/browse/INFRA-18822
Regards,
Yikun
Jiang Yikun（Kero）
Mail: yikunk...@gmail.com
Steph
Hi Mans,
There has been an announcement by the community[1] which
apply a restrictive JIRA workflow. Briefly now it only
allow committers and PMC members to assign somebody to
a JIRA ticket. This is what you meet.
You could send a request for assigning you to the ticket
on dev list and hopefully
Jark Wu created FLINK-13543:
---
Summary: Enable reuse forks for integration tests in blink planner
Key: FLINK-13543
URL: https://issues.apache.org/jira/browse/FLINK-13543
Project: Flink
Issue Type: S
Jark Wu created FLINK-13544:
---
Summary: Set parallelism of table sink operator to input
transformation parallelism
Key: FLINK-13544
URL: https://issues.apache.org/jira/browse/FLINK-13544
Project: Flink
Agree that using Optional will improve code robustness. However we’re
hesitating to use Optional in data intensive operations.
For example, SingleInputGate is already creating Optional for every
BufferOrEvent in getNextBufferOrEvent(). How much performance gain would we get
if it’s replaced by
godfrey he created FLINK-13545:
--
Summary: JoinToMultiJoinRule should not match SEMI/ANTI LogicalJoin
Key: FLINK-13545
URL: https://issues.apache.org/jira/browse/FLINK-13545
Project: Flink
Issue
Jark Wu created FLINK-13546:
---
Summary: Run TPC-H E2E test on travis cron job
Key: FLINK-13546
URL: https://issues.apache.org/jira/browse/FLINK-13546
Project: Flink
Issue Type: Task
Compo
Hi Bekir
I’ll first summary the problem here(please correct me if I’m wrong)
1. The same program runs on 1.6 never encounter such problems
2. Some checkpoints completed too long (15+ min), but other normal
checkpoints complete less than 1 min
3. Some bad checkpoint will have a large sync time, asy
cc Bekir
Best,
Congxian
Congxian Qiu 于2019年8月2日周五 下午12:23写道：
> Hi Bekir
> I’ll first summary the problem here(please correct me if I’m wrong)
> 1. The same program runs on 1.6 never encounter such problems
> 2. Some checkpoints completed too long (15+ min), but other normal
> checkpoints compl
Hi devs,
I found that these two classes are quite similar except
SingleLeaderElectionService has a pre-config leader id.
However, I don't see use points of that leader id. Also
a random UUID would work as a DEFAULT_LEADER_ID(0).
I consider whether we could replace SingleLeaderElectionService
with
Hi Chesnay,
Can we assign Flink Committers the permission of flink-ci/flink repo?
Several times, when I pushed some new commits, the old build jobs are still
in pending and not canceled.
Before we fix that, we can manually cancel some old jobs to save build
resource.
Best,
Jark
On Wed, 10 Jul 2
Hi David,
The demo looks charming! I think it will definitely help a lot when
performance tuning.
A big +1 for this.
I cc-ed Yadong who's one of the main contributors of the new Web UI.
Maybe he can give some help on the front end.
Regards,
Jark
On Fri, 2 Aug 2019 at 04:26, David Morávek wrote
|
Hi,
I want to contribute to Apache Flink.
Would you please give methe contributor permission?
My JIRA ID iszhangyongchao
|
Hi Team,
We are facing frequent issues with the Flink job manager in one environment
when the processing happens.
CHAIN Join(Remap EDGES id: TO) -> Map (Key Extractor) -> Combine (Deduplicate
edges including bi-directional edges) (57/80)Timestamp: 2019-08-02, 4:13:25
Location: flink-taskmanager-
Hi sss,
The new JIRA workflow is in effect, and contributors don't have to go to dev
to apply for contributor permissions. If you are interested in JIRA, you can
reply directly to JIRA (of course, for complex issues, also to clarify the
implementation). Then there will be a committer/pmc assi
Zhenghua Gao created FLINK-13547:
Summary: Verify and correct string function's semantic for Blink
planner
Key: FLINK-13547
URL: https://issues.apache.org/jira/browse/FLINK-13547
Project: Flink
67 matches
Mail list logo
