Tushar Gosavi created APEXCORE-709:
--
Summary: Refactor changes done through APEXCORE-575
Key: APEXCORE-709
URL: https://issues.apache.org/jira/browse/APEXCORE-709
Project: Apache Apex Core
I
Pramod Immaneni created APEXCORE-708:
Summary: Allow number of blocks when bp kicks in to be specified
Key: APEXCORE-708
URL: https://issues.apache.org/jira/browse/APEXCORE-708
Project: Apache Apex
Pramod Immaneni created APEXCORE-707:
Summary: Allow configurability on a per-stream basis using an
attribute
Key: APEXCORE-707
URL: https://issues.apache.org/jira/browse/APEXCORE-707
Project: Apa
[
https://issues.apache.org/jira/browse/APEXCORE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni reassigned APEXCORE-707:
Assignee: Pramod Immaneni
> Allow configurability on a per-stream basis using an
[
https://issues.apache.org/jira/browse/APEXCORE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni reassigned APEXCORE-706:
Assignee: Pramod Immaneni
> Drop blocks that have already been read so that the l
Pramod Immaneni created APEXCORE-706:
Summary: Drop blocks that have already been read so that the list
size does not keep growing
Key: APEXCORE-706
URL: https://issues.apache.org/jira/browse/APEXCORE-706
Pramod Immaneni created APEXCORE-705:
Summary: Prevent publisher from getting ahead of subscriber more
than max block count
Key: APEXCORE-705
URL: https://issues.apache.org/jira/browse/APEXCORE-705
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970454#comment-15970454
]
Vlad Rozov commented on APEXCORE-703:
-
I believe that the second test case is alread
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXCORE-703:
--
Fix Version/s: 3.6.0
> Window processing timeout for finished/undeployed container
> -
GitHub user vrozov opened a pull request:
https://github.com/apache/apex-core/pull/516
APEXCORE-703 Window processing timeout for finished/undeployed container.
During an operator shutdown, mark it as INACTIVE to exclude it from the
blocked operators check.
@tweise Please review
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970439#comment-15970439
]
ASF GitHub Bot commented on APEXCORE-703:
-
GitHub user vrozov opened a pull requ
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970436#comment-15970436
]
Thomas Weise commented on APEXCORE-703:
---
Perhaps a test that verifies that the ope
[
https://issues.apache.org/jira/browse/APEXCORE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXCORE-654:
--
Fix Version/s: 3.6.0
> Recovery window is not updated when Delay Operator is used along with
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970413#comment-15970413
]
Vlad Rozov commented on APEXCORE-703:
-
I'll open a PR. Do you have a suggestion for
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov reassigned APEXCORE-703:
---
Assignee: Vlad Rozov
> Window processing timeout for finished/undeployed container
> --
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970411#comment-15970411
]
Thomas Weise commented on APEXCORE-703:
---
I looked at it also and what you suggest
[
https://issues.apache.org/jira/browse/APEXCORE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970407#comment-15970407
]
Vlad Rozov commented on APEXCORE-703:
-
I don't see why INACTIVE operators can not be
[
https://issues.apache.org/jira/browse/APEXCORE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda resolved APEXCORE-678.
-
Resolution: Fixed
> Shutdown of application should start from input nodes
>
[
https://issues.apache.org/jira/browse/APEXCORE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970283#comment-15970283
]
ASF GitHub Bot commented on APEXCORE-678:
-
Github user asfgit closed the pull re
Github user asfgit closed the pull request at:
https://github.com/apache/apex-core/pull/509
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Since the release is an infrequent event and also not on a fixed schedule,
I think, it is good to give the community, enough time, to make their issue
preferences known and also have discussions on the merits and demerits of
including these in the release on an individual basis. From past
experienc
21 matches
Mail list logo