Hi,
I think questions about Flink should be posted on the public mailing lists
instead of asking just a single expert.
There's many reasons for that:
* usually more than one person can answer the question (what if the expert
is not available?)
* non-committers can join the discussion and contribu
Dawid Wysakowicz created FLINK-10414:
Summary: Add skip to next strategy
Key: FLINK-10414
URL: https://issues.apache.org/jira/browse/FLINK-10414
Project: Flink
Issue Type: Improvement
Till Rohrmann created FLINK-10415:
-
Summary: RestClient does not react to lost connection
Key: FLINK-10415
URL: https://issues.apache.org/jira/browse/FLINK-10415
Project: Flink
Issue Type: Bu
Dawid Wysakowicz created FLINK-10416:
Summary: Add to rat excludes files generated by jepsen tests
Key: FLINK-10416
URL: https://issues.apache.org/jira/browse/FLINK-10416
Project: Flink
I
Dawid Wysakowicz created FLINK-10417:
Summary: Add option to throw exception on pattern variable miss
with SKIP_TO_FIRST/LAST
Key: FLINK-10417
URL: https://issues.apache.org/jira/browse/FLINK-10417
Hi all,
It seems that there are more and more users from user mailing list ask how
to do unit test with Flink
features like states or timer. And the community usually tends to suggest
them using
`AbstractStreamOperator` and provide an example from Flink github repo.
Here I sort out some
examples a
Aleksei Izmalkin created FLINK-10418:
Summary: Add COSH math function supported in Table API and SQL
Key: FLINK-10418
URL: https://issues.apache.org/jira/browse/FLINK-10418
Project: Flink
Nico Kruber created FLINK-10419:
---
Summary: ClassNotFoundException while deserializing user
exceptions from checkpointing
Key: FLINK-10419
URL: https://issues.apache.org/jira/browse/FLINK-10419
Project:
vinoyang created FLINK-10420:
Summary: Create and drop view in sql client should check the view
created based on the configuration.
Key: FLINK-10420
URL: https://issues.apache.org/jira/browse/FLINK-10420
Dawid Wysakowicz created FLINK-10421:
Summary: Shaded Hadoop S3A end-to-end test failed on Travis
Key: FLINK-10421
URL: https://issues.apache.org/jira/browse/FLINK-10421
Project: Flink
Is
Hi Fabian,
You convinced me. I miss the advantage we can take from mailing lists.
Now I am of the same opinion.
Best,
tison.
Fabian Hueske 于2018年9月25日周二 下午3:01写道：
> Hi,
>
> I think questions about Flink should be posted on the public mailing lists
> instead of asking just a single expert.
>
eugen yushin created FLINK-10422:
Summary: Follow AWS specs in Kinesis Consumer
Key: FLINK-10422
URL: https://issues.apache.org/jira/browse/FLINK-10422
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-10423:
Summary: Forward RocksDB memory metrics to Flink metrics reporter
Key: FLINK-10423
URL: https://issues.apache.org/jira/browse/FLINK-10423
Project: Flink
Iss
Dominik Wosiński created FLINK-10424:
Summary: Inconsistency between JsonSchemaConveerter and
FlinkTypeFactory
Key: FLINK-10424
URL: https://issues.apache.org/jira/browse/FLINK-10424
Project: Flin
I think that all discussion/coordination related to a contribution / PR
should be handled through the official project channel.
I would also prefer that there are no designated "owners" and "experts",
for the reasons Fabian mentioned.
Ideally there is no need to have "suggested reviewers" either,
Andrew Kowpak created FLINK-10425:
-
Summary: taskmaster.host is not respected
Key: FLINK-10425
URL: https://issues.apache.org/jira/browse/FLINK-10425
Project: Flink
Issue Type: Bug
tison created FLINK-10426:
-
Summary: Port TaskTest to new code base
Key: FLINK-10426
URL: https://issues.apache.org/jira/browse/FLINK-10426
Project: Flink
Issue Type: Sub-task
Components: T
There is no guarantee that a PR will be looked at nor is it possible to
provide this in any way on the project level.
As far as Apache is concerned all contributors/committers etc. work
voluntarily, and
as such assigning work (which includes ownership if it implies such) or
similar is simply n
Still, even with a group of volunteers coordinating well, it is possible to
do better than we currently do, which is the goal.
No hard guarantees, agreed, but reasonable estimates and rules-of-thumbs
can work well...
On Tue, Sep 25, 2018 at 5:21 PM Chesnay Schepler wrote:
> There is no guarantee
I agree with Chesnay that we don't guarantee (quick) review of a PR at the
project level. As ASF statement[1]:
> Please show some patience with the developers if your patch is not
applied as fast as you'd like or a developer asks you to make changes to
the patch. If you do not receive any feedback
Hi Tony,
I think this would be great - we’ve been building out tests using
AbstractStreamOperator, and the lack of documentation has made it challenging.
For example, there was this exchange I had with Piotr about a month ago:
> You made a small mistake when restoring from state using test harn
Great tool!
> On Sep 24, 2018, at 10:59 PM, Zhijiang(wangzhijiang999)
> wrote:
>
> Thanks @Piotr Nowojski and @Nico Kruber for the good job!
>
> I already benefit from this benchmark in the previous PRs. Wish the
> visualization tool becoming stronger to benefit more for the community!
>
>
It is a great tool. Thanks for the contribution.
On Tue, Sep 25, 2018 at 11:39 AM Jin Sun wrote:
> Great tool!
>
> > On Sep 24, 2018, at 10:59 PM, Zhijiang(wangzhijiang999) <
> wangzhijiang...@aliyun.com.INVALID> wrote:
> >
> > Thanks @Piotr Nowojski and @Nico Kruber for the good job!
> >
> > I
tison created FLINK-10427:
-
Summary: Port JobSubmitTest to new code base
Key: FLINK-10427
URL: https://issues.apache.org/jira/browse/FLINK-10427
Project: Flink
Issue Type: Sub-task
Componen
24 matches
Mail list logo
