Felix Wollschläger created FLINK-12782:
--
Summary: Show formatted timestamp in Watermark Tab of JM Web UI
Key: FLINK-12782
URL: https://issues.apache.org/jira/browse/FLINK-12782
Project: Flink
Steven Zhen Wu created FLINK-12781:
--
Summary: run job REST api doesn't return complete stack trace for
start job failure
Key: FLINK-12781
URL: https://issues.apache.org/jira/browse/FLINK-12781
Projec
Bowen Li created FLINK-12780:
Summary: use LogicalTypeRoot for type comparison
Key: FLINK-12780
URL: https://issues.apache.org/jira/browse/FLINK-12780
Project: Flink
Issue Type: Sub-task
Hequn Cheng created FLINK-12779:
---
Summary: Avoid field conflicts when generate field names for
non-composite Typeinformation
Key: FLINK-12779
URL: https://issues.apache.org/jira/browse/FLINK-12779
Proje
Hi Georgi, Thanks for your feedback. And glad to hear you are using queryable
state. I agree that implementation of option 1 is easier than others. However,
when we design the new architecture we need to consider more aspects .e.g.
scalability. So it seems option 3 is more suitable. Actually, so
Hequn Cheng created FLINK-12778:
---
Summary: Fix deriveTableAggRowType bug for non-composite types
Key: FLINK-12778
URL: https://issues.apache.org/jira/browse/FLINK-12778
Project: Flink
Issue Typ
Just wanted to give an update on this.
Our ops team and myself independently came to the same conclusion that our
ZooKeeper quorum was having syncing issues.
After a bit more research, they have updated the initLimit and syncLimit in the
quorum configs to:
initLimit=10
syncLimit=5
After this c
Hi,
Thanks for your explanation.
I've added "Benchmarks" and renamed "Runtime / Operators".
On Mon, May 20, 2019 at 10:59 AM Piotr Nowojski wrote:
> Hi,
>
> > Concrete operator implementations will then go into the "API /
> DataStream"?
> > (or "API / DataSet" or Table)
> > Afaik, there were som
Piotr Nowojski created FLINK-12777:
--
Summary: Support CheckpointBarrierHandler in
StreamTwoInputSelectableProcessor
Key: FLINK-12777
URL: https://issues.apache.org/jira/browse/FLINK-12777
Project: Fl
Hi Vino,
I was investigating the current architecture and AFAIK the first proposal will
be a lot easier to implement, cause currently JM has the information about the
states (where, which etc thanks to KvStateLocationRegistry. Correct me if I’m
wrong)
We are using the feature and it’s indeed no
+ 1 for this feature which is great helpful in product situations and look
forward to see it as soon as possible.
> 在 2019年6月6日,下午4:58,qianjin Xu 写道:
>
>>
>> hi
>
> +1 nice work
>
> best
>
> forwardxu
Chesnay Schepler created FLINK-12776:
Summary: Ambiguous content in flink-dist NOTICE file
Key: FLINK-12776
URL: https://issues.apache.org/jira/browse/FLINK-12776
Project: Flink
Issue Typ
Chesnay Schepler created FLINK-12775:
Summary: Bump flink-shaded version to 7.0
Key: FLINK-12775
URL: https://issues.apache.org/jira/browse/FLINK-12775
Project: Flink
Issue Type: Improvem
Chesnay Schepler created FLINK-12774:
Summary: Pin version of build-helper-maven plugin
Key: FLINK-12774
URL: https://issues.apache.org/jira/browse/FLINK-12774
Project: Flink
Issue Type:
14 matches
Mail list logo