[jira] [Commented] (APEXMALHAR-2289) Managed State benchmark improvement

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15638263#comment-15638263
 ] 

ASF GitHub Bot commented on APEXMALHAR-2289:


Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/473


>  Managed State benchmark improvement
> 
>
> Key: APEXMALHAR-2289
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2289
> Project: Apache Apex Malhar
>  Issue Type: Improvement
>Reporter: bright chen
>Assignee: bright chen
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> It seems the State Manager will slow down after run a while. Add following 
> feature to the Managed State benchmark for monitoring
> 1. monitor the system resource.
> 2. monitor the garbage collection 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-malhar pull request #473: APEXMALHAR-2289 #resolve #comment Add resourc...

[brightchen]

Github user brightchen closed the pull request at:

https://github.com/apache/apex-malhar/pull/473


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-core pull request #416: *Review only* APEXCORE-426 Reuse the running co...

[sandeshh]

GitHub user sandeshh opened a pull request:

https://github.com/apache/apex-core/pull/416

*Review only* APEXCORE-426 Reuse the running container, when the Stram 
restarts.

@tweise & @vrozov  please review

If you guys are fine with the approach, I will work on unit tests.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sandeshh/apex-core APEXCORE-426

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/416.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #416






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (APEXCORE-572) Remove dependency on hadoop-common test.jar

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15637900#comment-15637900
 ] 

ASF GitHub Bot commented on APEXCORE-572:
-

GitHub user vrozov opened a pull request:

https://github.com/apache/apex-core/pull/415

APEXCORE-572 - Remove dependency on hadoop-common test.jar

@PramodSSImmaneni, @tweise Please review

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vrozov/apex-core APEXCORE-572

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/415.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #415


commit fff38f3d9cca9776e65e1d8ae9489eaa6f541cb0
Author: Vlad Rozov 
Date:   2016-11-04T22:01:08Z

APEXCORE-572 - Remove dependency on hadoop-common test.jar




> Remove dependency on hadoop-common test.jar
> ---
>
> Key: APEXCORE-572
> URL: https://issues.apache.org/jira/browse/APEXCORE-572
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-core pull request #415: APEXCORE-572 - Remove dependency on hadoop-comm...

[vrozov]

GitHub user vrozov opened a pull request:

https://github.com/apache/apex-core/pull/415

APEXCORE-572 - Remove dependency on hadoop-common test.jar

@PramodSSImmaneni, @tweise Please review

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vrozov/apex-core APEXCORE-572

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/415.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #415


commit fff38f3d9cca9776e65e1d8ae9489eaa6f541cb0
Author: Vlad Rozov 
Date:   2016-11-04T22:01:08Z

APEXCORE-572 - Remove dependency on hadoop-common test.jar




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (APEXCORE-571) References to ApplicationFactory should be removed in the docs

[Sanjay M Pujare (JIRA)]

Sanjay M Pujare created APEXCORE-571:


 Summary: References to ApplicationFactory should be removed in the 
docs
 Key: APEXCORE-571
 URL: https://issues.apache.org/jira/browse/APEXCORE-571
 Project: Apache Apex Core
  Issue Type: Bug
  Components: Documentation
Affects Versions: 3.5.0
Reporter: Sanjay M Pujare
Priority: Minor


There are references to ApplicationFactory in the docs 
(apex-core/docs/application_development.md for example) that need to be removed 
since the class doesn't exist any more .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2022) S3 Output Module for file copy

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15636249#comment-15636249
 ] 

ASF GitHub Bot commented on APEXMALHAR-2022:


GitHub user chaithu14 opened a pull request:

https://github.com/apache/apex-malhar/pull/483

APEXMALHAR-2022 Developed S3 Output Module



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chaithu14/incubator-apex-malhar 
APEXMALHAR-2022-S3Output-multiPart

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/483.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #483


commit 24fb5638ecb6f0e45edb5d5f640b220ad9372fcc
Author: chaitanya 
Date:   2016-11-04T12:48:21Z

APEXMALHAR-2022 Developed S3 Output Module




> S3 Output Module for file copy
> --
>
> Key: APEXMALHAR-2022
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2022
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Chaitanya
>Assignee: Hitesh Kapoor
>
> Primary functionality of this module is copy files into S3 bucket using 
> block-by-block approach.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] apex-malhar pull request #483: APEXMALHAR-2022 Developed S3 Output Module

[chaithu14]

GitHub user chaithu14 opened a pull request:

https://github.com/apache/apex-malhar/pull/483

APEXMALHAR-2022 Developed S3 Output Module



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chaithu14/incubator-apex-malhar 
APEXMALHAR-2022-S3Output-multiPart

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/483.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #483


commit 24fb5638ecb6f0e45edb5d5f640b220ad9372fcc
Author: chaitanya 
Date:   2016-11-04T12:48:21Z

APEXMALHAR-2022 Developed S3 Output Module




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---