[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz updated FLINK-5717:
Fix Version/s: (was: 1.12.3)
(was: 1.11.4)
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Assignee: Kezhu Wang
>Priority: Major
> Labels: easyfix, pull-request-available, starter
> Fix For: 1.13.0
>
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz updated FLINK-5717:
Fix Version/s: 1.12.3
1.13.0
1.11.4
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Assignee: Kezhu Wang
>Priority: Major
> Labels: easyfix, pull-request-available, starter
> Fix For: 1.11.4, 1.13.0, 1.12.3
>
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-5717:
--
Labels: easyfix pull-request-available starter (was: easyfix starter)
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Assignee: Lijie Wang
>Priority: Major
> Labels: easyfix, pull-request-available, starter
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek updated FLINK-5717:
Labels: easyfix starter (was: easyfix pull-request-available starter)
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Assignee: Lijie Wang
>Priority: Major
> Labels: easyfix, starter
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-5717:
--
Labels: easyfix pull-request-available starter (was: easyfix starter)
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Assignee: Lijie Wang
>Priority: Major
> Labels: easyfix, pull-request-available, starter
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek updated FLINK-5717:
Labels: easyfix starter (was: easyfix pull-request-available starter)
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Assignee: Lijie Wang
>Priority: Major
> Labels: easyfix, starter
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek updated FLINK-5717:
Labels: easyfix pull-request-available starter (was:
pull-request-available)
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Assignee: Lijie Wang
>Priority: Major
> Labels: easyfix, pull-request-available, starter
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-5717:
--
Labels: pull-request-available (was: )
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
>Affects Versions: 1.1.4, 1.2.0
>Reporter: Oriol Orellana
>Priority: Major
> Labels: pull-request-available
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek updated FLINK-5717:
Affects Version/s: (was: 2.0.0)
1.2.0
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
>Affects Versions: 1.2.0, 1.1.4
>Reporter: Oriol Orellana
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
> org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
> at
> org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
> at
> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
> at
> org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *how to reproduce ?*
> use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger
> in SessionWindowing example.
> *what's the cause ?*
> When two session windows are being merged, the states of the two
> ContinuousProcessingTimeTrigger are merged as well and the new namespace is
> the merged window. Later when the context tries to delete Timer from the old
> trigger and looks up the timestamp by the old namespace, null value is
> returned.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oriol Orellana updated FLINK-5717:
--
Description:
The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
ContinuousProcessingTimeTrigger. I copied the description from that same issue.
*what's the error?*
The following NPE error is thrown when SessionWindows with
ContinuousProcessingTimeTrigger is used.
{code:borderStyle=solid}
Caused by: java.lang.NullPointerException
at
org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
at
org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
at
org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
at java.lang.Thread.run(Thread.java:745)
{code}
*how to reproduce ?*
use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger in
SessionWindowing example.
*what's the cause ?*
When two session windows are being merged, the states of the two
ContinuousProcessingTimeTrigger are merged as well and the new namespace is the
merged window. Later when the context tries to delete Timer from the old
trigger and looks up the timestamp by the old namespace, null value is returned.
was:
The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
ContinuousProcessingTimeTrigger. I copied the description from that same issue.
*what's the error?*
The following NPE error is thrown when SessionWindows with
ContinuousProcessingTimeTrigger is used.
{code:borderStyle=solid}
Caused by: java.lang.NullPointerException
at
org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
at
org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
at
org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
at java.lang.Thread.run(Thread.java:745)
{code}
*how to reproduce ?*
use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger in
SessionWindowing example.
*what's the cause ?*
When two session windows are being merged, the states of the two
ContinuousEventTimeTrigger are merged as well and the new namespace is the
merged window. Later when the context tries to delete Timer from the old
trigger and looks up the timestamp by the old namespace, null value is returned.
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
>Affects Versions: 2.0.0, 1.1.4
>Reporter: Oriol Orellana
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
>
[jira] [Updated] (FLINK-5717) NPE on SessionWindows with ContinuousProcessingTimeTrigger
[
https://issues.apache.org/jira/browse/FLINK-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oriol Orellana updated FLINK-5717:
--
Description:
The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
ContinuousProcessingTimeTrigger. I copied the description from that same issue.
*what's the error?*
The following NPE error is thrown when SessionWindows with
ContinuousProcessingTimeTrigger is used.
{code:borderStyle=solid}
Caused by: java.lang.NullPointerException
at
org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
at
org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
at
org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
at java.lang.Thread.run(Thread.java:745)
{code}
*how to reproduce ?*
use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger in
SessionWindowing example.
*what's the cause ?*
When two session windows are being merged, the states of the two
ContinuousEventTimeTrigger are merged as well and the new namespace is the
merged window. Later when the context tries to delete Timer from the old
trigger and looks up the timestamp by the old namespace, null value is returned.
was:
The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
ContinuousProcessingTimeTrigger. I copied the description from that same issue.
*what's the error?*
The following NPE error is thrown when SessionWindows with
ContinuousProcessingTimeTrigger is used.
{code:borderStyle=solid}
Caused by: java.lang.NullPointerException
at
org.apache.flink.streaming.api.windowing.triggers.ContinuousProcessingTimeTrigger.clear(ContinuousProcessingTimeTrigger.java:91)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$Context.clear(WindowOperator.java:768)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:310)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator$2.merge(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.operators.windowing.MergingWindowSet.addWindow(MergingWindowSet.java:196)
at
org.apache.flink.streaming.runtime.operators.windowing.WindowOperator.processElement(WindowOperator.java:297)
at
org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:183)
at
org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:66)
at
org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:271)
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:609)
at java.lang.Thread.run(Thread.java:745)
{code:borderStyle=solid}
*how to reproduce ?*
use ContinuousProcessingTimeTrigger instead of the default EventTimeTrigger in
SessionWindowing example.
*what's the cause ?*
When two session windows are being merged, the states of the two
ContinuousEventTimeTrigger are merged as well and the new namespace is the
merged window. Later when the context tries to delete Timer from the old
trigger and looks up the timestamp by the old namespace, null value is returned.
> NPE on SessionWindows with ContinuousProcessingTimeTrigger
> --
>
> Key: FLINK-5717
> URL: https://issues.apache.org/jira/browse/FLINK-5717
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
>Affects Versions: 2.0.0, 1.1.4
>Reporter: Oriol Orellana
>
> The same bug as https://issues.apache.org/jira/browse/FLINK-4862, but for
> ContinuousProcessingTimeTrigger. I copied the description from that same
> issue.
> *what's the error?*
> The following NPE error is thrown when SessionWindows with
> ContinuousProcessingTimeTrigger is used.
> {code:borderStyle=solid}
> Caused by: java.lang.NullPointerException
> at
>
