[GitHub] apex-malhar pull request #345: REVIEW ONLY (WindowedOperator): splitting Win...

Github user ilooner commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/345#discussion_r71473044 --- Diff: library/src/main/java/org/apache/apex/malhar/lib/window/impl/SpillableWindowedKeyedStorage.java --- @@ -0,0 +1,198 @@ +package org.apache.

[GitHub] apex-malhar pull request #347: APEXMALHAR-2156 changes

GitHub user sanjaypujare opened a pull request: https://github.com/apache/apex-malhar/pull/347 APEXMALHAR-2156 changes APEXMALHAR-2156 changes: @PramodSSImmaneni @amberarrow @ashwinchandrap pls review. You can merge this pull request into a Git repository by running: $ git p

[jira] [Commented] (APEXMALHAR-2156) JMS Input operator enhancements

[ https://issues.apache.org/jira/browse/APEXMALHAR-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385133#comment-15385133 ] ASF GitHub Bot commented on APEXMALHAR-2156: GitHub user sanjaypujare ope

[jira] [Created] (APEXCORE-495) Enhancing the configuration package to store apps

Sandesh created APEXCORE-495: Summary: Enhancing the configuration package to store apps Key: APEXCORE-495 URL: https://issues.apache.org/jira/browse/APEXCORE-495 Project: Apache Apex Core Issue

[jira] [Created] (APEXMALHAR-2162) Enable unit tests of 0.9.0 Kafka Output operator

Sandesh created APEXMALHAR-2162: --- Summary: Enable unit tests of 0.9.0 Kafka Output operator Key: APEXMALHAR-2162 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2162 Project: Apache Apex Malhar

[Proposal] Support storing apps in a Configuration Package

Hi All, Apex supports configuration package, separates application package from the actual configuration. (http://docs.datatorrent.com/configuration_packages/) We want to enhance the configuration package by adding support to "add Apps" (json format). UseCase: Multiple users sharing the same app

Powered by Apex

Recently a new Powered by Apex page has been added to the Apache Apex site. This page lists various organizations powered by or working with Apache Apex, as well as software which integrates with Apache Apex. http://apex.apache.org/powered-by-apex.htm

[GitHub] apex-site pull request #42: Added updating documentation to release process

Github user PramodSSImmaneni commented on a diff in the pull request: https://github.com/apache/apex-site/pull/42#discussion_r71422964 --- Diff: src/md/release.md --- @@ -150,6 +150,47 @@ mkdir svn-dist && cp *-source-* svn-dist/ svn import svn-dist https://dist.apache.org/rep

Powered by Apex

Recently a new Powered by Apex page has been added to the Apache Apex site. This page lists various organizations powered by or working with Apache Apex, as well as software which integrates with Apache Apex. http://apex.apache.org/powered-by-apex.htm

Re: Container & memory resource allocation

Thanks Chinmay & Ram. Troubleshooting page sounds the appropriate location. I shall raise PR with the given suggestions. --prad On Tue, Jul 19, 2016 at 5:49 AM, Munagala Ramanath wrote: > There is already a link to a troubleshooting page at bottom of > https://apex.apache.org/docs.html > That

[jira] [Updated] (APEXMALHAR-2135) Upgrade Kafka 0.8 input operator to support 0.8.2 client

[ https://issues.apache.org/jira/browse/APEXMALHAR-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2135: --- Fix Version/s: 3.5.0 > Upgrade Kafka 0.8 input operator to support 0.8.2 client > ---

Re: Container & memory resource allocation

There is already a link to a troubleshooting page at bottom of https://apex.apache.org/docs.html That page already has some discussion under the section entitled "Calculating Container Memory" so adding new content there seems like the right thing to do. Ram On Mon, Jul 18, 2016 at 11:27 PM, Chin

[jira] [Commented] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384006#comment-15384006 ] ASF GitHub Bot commented on APEXCORE-494: - GitHub user chaithu14 opened a pull r

[GitHub] apex-core pull request #359: APEXCORE-494 Fixed the dynamic partition issue ...

GitHub user chaithu14 opened a pull request: https://github.com/apache/apex-core/pull/359 APEXCORE-494 Fixed the dynamic partition issue in case of initial partition size is 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/chai

[jira] [Commented] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384004#comment-15384004 ] Chaitanya commented on APEXCORE-494: Observation: This was happening only when there

[jira] [Assigned] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya reassigned APEXCORE-494: -- Assignee: Chaitanya > Window id of downstream operator is not moving after dynamic partition

[jira] [Updated] (APEXMALHAR-2161) Add tests for AbstractThroughputFileInputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXMALHAR-2161: Summary: Add tests for AbstractThroughputFileInputOperator (was: Add tests fir

[jira] [Created] (APEXMALHAR-2161) Add tests fir AbstractThroughputFileInputOperator

Priyanka Gugale created APEXMALHAR-2161: --- Summary: Add tests fir AbstractThroughputFileInputOperator Key: APEXMALHAR-2161 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2161 Project: Apach

Re: Solving JIRA ISUUE : APEXMALHAR-2016.

Hi Harsh, This seems to be a backward incompatible change, so I would suggest let's wait to fix it till next major release when we can change the api. One option could be, deprecate current function and add new function with same name which accepts Set as parameter. But I am not sure how BeanUtil