Re: Malhar release 3.6

The release is available already. For the announcement, would anyone want to provide some information that can go on the blog page, similar to what we had last time: https://blogs.apache.org/apex/entry/apache_apex_malhar_3_5 Thanks, Thomas On Tue, Nov 22, 2016 at 2:14 PM, Thomas Weise

[jira] [Commented] (APEXCORE-583) Buffer Server LogicalNode should not be reused by Subscribers

[ https://issues.apache.org/jira/browse/APEXCORE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717278#comment-15717278 ] ASF GitHub Bot commented on APEXCORE-583: - GitHub user vrozov opened a pull request:

[GitHub] apex-core pull request #428: APEXCORE-583 - Buffer Server LogicalNode should...

GitHub user vrozov opened a pull request: https://github.com/apache/apex-core/pull/428 APEXCORE-583 - Buffer Server LogicalNode should not be reused by Subscribers @PramodSSImmaneni, @tweise, @243826 Please review. You can merge this pull request into a Git repository by running:

[jira] [Commented] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717253#comment-15717253 ] Ajay Gupta commented on APEXCORE-561: - ContainerReport is already persisted in Yarn's timeline

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717143#comment-15717143 ] Munagala V. Ramanath commented on APEXCORE-526: --- I fixed it but the build is now failing

[jira] [Commented] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717118#comment-15717118 ] Munagala V. Ramanath commented on APEXCORE-558: --- True in theory but I think red is less of

[jira] [Assigned] (APEXCORE-586) Enhancement to persist logical and physical plan snapshots in HDFS

[ https://issues.apache.org/jira/browse/APEXCORE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay M Pujare reassigned APEXCORE-586: Assignee: Sanjay M Pujare > Enhancement to persist logical and physical plan

[jira] [Created] (APEXCORE-586) Enhancement to persist logical and physical plan snapshots in HDFS

Sanjay M Pujare created APEXCORE-586: Summary: Enhancement to persist logical and physical plan snapshots in HDFS Key: APEXCORE-586 URL: https://issues.apache.org/jira/browse/APEXCORE-586

[jira] [Commented] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716923#comment-15716923 ] David Yan commented on APEXCORE-558: We probably should not have any color at all since we should

[jira] [Commented] (APEXCORE-585) Latency should be calculated only after the first window has been complete

[ https://issues.apache.org/jira/browse/APEXCORE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716901#comment-15716901 ] ASF GitHub Bot commented on APEXCORE-585: - GitHub user davidyan74 opened a pull request:

[GitHub] apex-core pull request #427: APEXCORE-585 #resolve do not try to calculate l...

GitHub user davidyan74 opened a pull request: https://github.com/apache/apex-core/pull/427 APEXCORE-585 #resolve do not try to calculate latency if the first wi… …ndow has not complete @vrozov please review and merge You can merge this pull request into a Git

[jira] [Created] (APEXCORE-585) Latency should be calculated only after the first window has been complete

David Yan created APEXCORE-585: -- Summary: Latency should be calculated only after the first window has been complete Key: APEXCORE-585 URL: https://issues.apache.org/jira/browse/APEXCORE-585 Project:

[jira] [Updated] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay M Pujare updated APEXCORE-561: - Assignee: (was: Sanjay M Pujare) > Container info needs to be persisted even after

[jira] [Assigned] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay M Pujare reassigned APEXCORE-561: Assignee: Sanjay M Pujare (was: Priyanka Gugale) > Container info needs to be

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716805#comment-15716805 ] Thomas Weise commented on APEXCORE-526: --- Look for the Kafka 0.9 and SQL packages. > Publish

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716775#comment-15716775 ] Munagala V. Ramanath commented on APEXCORE-526: --- What's missing ? After adding that option

[jira] [Updated] (APEXMALHAR-2122) Upgrading elasticsearch java api from 1.1.2 to 2.3.3.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2122: - Fix Version/s: (was: 3.6.0) > Upgrading elasticsearch java api from 1.1.2 to

[jira] [Updated] (APEXMALHAR-2342) Fix null pointer exception in AbstractFileOutputOperator setup

[ https://issues.apache.org/jira/browse/APEXMALHAR-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2342: - Assignee: Darin Nee > Fix null pointer exception in AbstractFileOutputOperator setup

[jira] [Updated] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-526: -- Assignee: Munagala V. Ramanath > Publish javadoc for releases on ASF infrastructure >

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716260#comment-15716260 ] Thomas Weise commented on APEXCORE-526: --- There seems to be part of the documentation missing. Are

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716179#comment-15716179 ] Munagala V. Ramanath commented on APEXCORE-526: --- Yes, it can would take a bit more work.

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716174#comment-15716174 ] Munagala V. Ramanath commented on APEXCORE-526: --- Looks like the build was successful:

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716106#comment-15716106 ] Thomas Weise commented on APEXCORE-526: --- Can it be setup to build whenever there are commits

[jira] [Commented] (APEXCORE-581) Delivery of Custom Control Tuples

[ https://issues.apache.org/jira/browse/APEXCORE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716101#comment-15716101 ] Vlad Rozov commented on APEXCORE-581: - Agree, GenericNode needs to orchestrate tuples the same way

[jira] [Commented] (APEXCORE-526) Publish javadoc for releases on ASF infrastructure

[ https://issues.apache.org/jira/browse/APEXCORE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716088#comment-15716088 ] Munagala V. Ramanath commented on APEXCORE-526: --- Pushed changes to build a list of

[jira] [Commented] (APEXCORE-581) Delivery of Custom Control Tuples

[ https://issues.apache.org/jira/browse/APEXCORE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716077#comment-15716077 ] David Yan commented on APEXCORE-581: Yes, I think that makes sense. [~vrozov] thoughts? > Delivery

Re: [DISCUSSION] Custom Control Tuples

Bhupesh, Sandesh, Tushar: Thanks for volunteering. This task probably needs all three of you to work closely together. The subtasks so far are: https://issues.apache.org/jira/browse/APEXCORE-580 https://issues.apache.org/jira/browse/APEXCORE-581 Please first review the subtasks and see whether

[jira] [Commented] (APEXMALHAR-2339) Windowed Operator benchmarking

[ https://issues.apache.org/jira/browse/APEXMALHAR-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715934#comment-15715934 ] bright chen commented on APEXMALHAR-2339: - Suggest apply BloomFilter to bucket to reduce the

[jira] [Created] (APEXMALHAR-2366) Apply BloomFilter to Bucket

bright chen created APEXMALHAR-2366: --- Summary: Apply BloomFilter to Bucket Key: APEXMALHAR-2366 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2366 Project: Apache Apex Malhar Issue

[RESULT] [VOTE] Apache Apex Malhar Release 3.6.0 (RC1)

The vote is concluded and passes. Thanks for voting and verifying the release. binding +1 (3) Siyuan Hua David Yan Vlad Rozov non-binding +1 (4) Chinmay Kolhatkar Tushar Gosavi Bhupesh Chawda Chaitanya Chebolu No other votes. Will complete the release activities. Thanks, Thomas On Thu,

[jira] [Updated] (APEXMALHAR-2365) LogParser - Operator to parse byte array using log format and emit a POJO

[ https://issues.apache.org/jira/browse/APEXMALHAR-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2365: - Assignee: Shraddha > LogParser - Operator to parse byte array using log format and

Re: "ExcludeNodes" for an Apex application

Agree it should be via YARN; the poison pill would be the final barrier in the event all other mechanisms have failed -- sort of like an API call which documents that a parameter should be non-null but nevertheless checks it internally and throws an exception if it finds null. Additionally, it

[jira] [Commented] (APEXMALHAR-2365) LogParser - Operator to parse byte array using log format and emit a POJO

[ https://issues.apache.org/jira/browse/APEXMALHAR-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715437#comment-15715437 ] Munagala V. Ramanath commented on APEXMALHAR-2365: -- Couple of thoughts: 1. Some use

Re: "ExcludeNodes" for an Apex application

The OP is claiming (in the comment to the first response) that he actually tried the proposed solution and it did not work for him and shows the RM code fragment that is clobbering his preference. Ram On Fri, Dec 2, 2016 at 12:17 AM, Sandesh Hegde wrote: > Yarn allows

Re: "ExcludeNodes" for an Apex application

Stram exclude node should be via Yarn, poison pill is not a good way as it induces a terminate for wrong reasons. Thks Amol On Fri, Dec 2, 2016 at 7:13 AM, Munagala Ramanath wrote: > Could STRAM include a poison pill where it simply exits with diagnostic if > its host

Re: "ExcludeNodes" for an Apex application

Could STRAM include a poison pill where it simply exits with diagnostic if its host name is blacklisted ? Ram On Thu, Dec 1, 2016 at 11:52 PM, Amol Kekre wrote: > Yarn will deploy AM (Stram) on a node of its choice, therey rendering any > attribute within the app

[jira] [Commented] (APEXMALHAR-2365) LogParser - Operator to parse byte array using log format and emit a POJO

[ https://issues.apache.org/jira/browse/APEXMALHAR-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714919#comment-15714919 ] Sandeep Deshmukh commented on APEXMALHAR-2365: -- Can someone from PMC list assign this

[jira] [Resolved] (APEXMALHAR-2316) Cannot register tuple class in XmlParser Operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda resolved APEXMALHAR-2316. Resolution: Fixed Fix Version/s: 3.7.0 > Cannot register tuple class in

[jira] [Resolved] (APEXMALHAR-2346) DocumentBuilder.parse() should take InputSource as an argument instead of String

[ https://issues.apache.org/jira/browse/APEXMALHAR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda resolved APEXMALHAR-2346. Resolution: Fixed Fix Version/s: 3.7.0 > DocumentBuilder.parse() should

[jira] [Commented] (APEXMALHAR-2316) Cannot register tuple class in XmlParser Operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714792#comment-15714792 ] ASF GitHub Bot commented on APEXMALHAR-2316: Github user asfgit closed the pull request

[GitHub] apex-malhar pull request #506: APEXMALHAR-2316 APEXMALHAR-2346 Moved suitabl...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/506 --- 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

[jira] [Commented] (APEXMALHAR-2365) LogParser - Operator to parse byte array using log format and emit a POJO

[ https://issues.apache.org/jira/browse/APEXMALHAR-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714721#comment-15714721 ] Shraddha commented on APEXMALHAR-2365: -- Hi, I am unable to assign this card to myself. Can

[jira] [Created] (APEXMALHAR-2365) LogParser - Operator to parse byte array using log format and emit a POJO

Shraddha created APEXMALHAR-2365: Summary: LogParser - Operator to parse byte array using log format and emit a POJO Key: APEXMALHAR-2365 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2365

[jira] [Created] (APEXMALHAR-2364) Add user documentation for S3OutputModule

Chaitanya created APEXMALHAR-2364: - Summary: Add user documentation for S3OutputModule Key: APEXMALHAR-2364 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2364 Project: Apache Apex Malhar

Re: "ExcludeNodes" for an Apex application

So all Apex will need to do is - to make sure as a part of the initial configuration validations that the node selected to run the master is not a part of the "excludeNode" list. On Fri, Dec 2, 2016 at 1:47 PM, Sandesh Hegde wrote: > Yarn allows the AppMaster to run on

Re: "ExcludeNodes" for an Apex application

Yarn allows the AppMaster to run on the selected node, Apex shouldn't select the blacklisted nodes, so it is possible to achieve not running the Apex containers on certain nodes. http://stackoverflow.com/questions/29302659/run-my-own-application-master-on-a-specific-node-in-a-yarn-cluster On