[
https://issues.apache.org/jira/browse/APEXCORE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803771#comment-15803771
]
ASF GitHub Bot commented on APEXCORE-493:
-
GitHub user sandeshh opened a pull re
GitHub user sandeshh opened a pull request:
https://github.com/apache/apex-core/pull/443
APEXCORE-493 checkpoint purging from streaming container
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sandeshh/apex-core APEXCORE-493
Al
[
https://issues.apache.org/jira/browse/APEXMALHAR-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803677#comment-15803677
]
ASF GitHub Bot commented on APEXMALHAR-2343:
Github user asfgit closed th
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/517
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803664#comment-15803664
]
ASF GitHub Bot commented on APEXCORE-592:
-
Github user ajaygit158 closed the pul
Github user ajaygit158 closed the pull request at:
https://github.com/apache/apex-core/pull/435
---
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
About the following sentence:
➢ We continue to see increase in interest and adaption
Shouldn’t it be “adoption” ?
On 1/5/17, 7:47 PM, "Thomas Weise" wrote:
Below is the draft board report for feedback.
I'm planning to submit it on Monday.
Thanks,
Thomas
Below is the draft board report for feedback.
I'm planning to submit it on Monday.
Thanks,
Thomas
## Description:
Apache Apex is a distributed, large-scale, high throughput,
low-latency, fault tolerant, unified stream and batch processing
platform.
## Issues:
There are no issues that require
[
https://issues.apache.org/jira/browse/APEXCORE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-550:
-
Assignee: (was: Sandesh)
> User friendly error message when Java version mismatch happens
>
[
https://issues.apache.org/jira/browse/APEXCORE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-426:
-
Description:
On app master failure, the streaming containers should continue running.
As of 2.2, YARN
[
https://issues.apache.org/jira/browse/APEXCORE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-426:
-
Description:
On app master failure, the streaming containers should continue running.
As of 2.2, YARN
[
https://issues.apache.org/jira/browse/APEXCORE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-426:
-
Description:
On app master failure, the streaming containers should continue running.
As of 2.2, YARN
Agreed Thomas.
I was referring to the persona of the operator developer. The user of the
operator would not be doing anything related to the propagation of control
tuples. Actually, the behavior of the operator wrt. propagation of control
tuples would be part of the operator documentation.
Also, w
[
https://issues.apache.org/jira/browse/APEXCORE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXCORE-590.
--
Resolution: Fixed
> Failed to restart application on MapR
> --
[
https://issues.apache.org/jira/browse/APEXCORE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802155#comment-15802155
]
ASF GitHub Bot commented on APEXCORE-590:
-
Github user asfgit closed the pull re
Github user asfgit closed the pull request at:
https://github.com/apache/apex-core/pull/433
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved APEXCORE-595.
---
Resolution: Fixed
Fix Version/s: 3.6.0
> Master incorrectly updates committedWindowId
[
https://issues.apache.org/jira/browse/APEXCORE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801826#comment-15801826
]
ASF GitHub Bot commented on APEXCORE-595:
-
Github user asfgit closed the pull re
Github user asfgit closed the pull request at:
https://github.com/apache/apex-core/pull/439
---
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
I think it is important to be clear on the roles with regard to this
functionality. The user of the operator should not have to do anything to
get it to work. So while I suggested to consider attributes earlier, there
should not be any need for the user to set those. The operator needs to
work as i
Deepak Narkhede created APEXMALHAR-2381:
---
Summary: Change FSWindowManager for performance issues in Kinesis
Input Operator
Key: APEXMALHAR-2381
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2381
[
https://issues.apache.org/jira/browse/APEXCORE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800763#comment-15800763
]
ASF GitHub Bot commented on APEXCORE-596:
-
GitHub user francisf opened a pull re
GitHub user francisf opened a pull request:
https://github.com/apache/apex-core/pull/442
APEXCORE-596 Setting the thread for all oio nodes in the oio group
@tushargosavi please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.co
23 matches
Mail list logo
