APEXMALHAR-2261 Python Binding for HighLevel APIs

Hi All, I would like to take up development for python binding implementation for highlevel APIs (APEXMALHAR-2261 ). I went over High-Level APIs from Apache Malhar Stream API project. It can be initiated as separated project in the Apache Malhar project just like sql or stream project. In first

[jira] [Resolved] (APEXCORE-611) Stram Event Log Levels

[ https://issues.apache.org/jira/browse/APEXCORE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-611. - Resolution: Implemented Fix Version/s: 3.6.0 > Stram Event Log Levels >

[jira] [Updated] (APEXCORE-611) Stram Event Log Levels

[ https://issues.apache.org/jira/browse/APEXCORE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-611: Assignee: Ajay Gupta > Stram Event Log Levels > -- > > Key:

[jira] [Updated] (APEXCORE-611) Stram Event Log Levels

[ https://issues.apache.org/jira/browse/APEXCORE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-611: Priority: Minor (was: Major) > Stram Event Log Levels > -- > >

[jira] [Commented] (APEXCORE-611) Stram Event Log Levels

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

[GitHub] apex-core pull request #454: APEXCORE-611 Added log levels for Stram Events

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

[jira] [Commented] (APEXCORE-627) Unit test AtMostOnceTest intermittently fails

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

[GitHub] apex-core pull request #460: APEXCORE-627 : Unit test AtMostOnceTest intermi...

GitHub user sgolovko opened a pull request: https://github.com/apache/apex-core/pull/460 APEXCORE-627 : Unit test AtMostOnceTest intermittently fails Fixed a race problem for calling checkpointed and committed in RecoverableInputOperator. The original implementation of the class

[GitHub] apex-core pull request #459: Fix download link in README.md

GitHub user tweise opened a pull request: https://github.com/apache/apex-core/pull/459 Fix download link in README.md @davidyan74 review You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/apex-core master Alternatively you

[jira] [Created] (APEXCORE-627) Unit test AtMostOnceTest intermittently fails

Sergey Golovko created APEXCORE-627: --- Summary: Unit test AtMostOnceTest intermittently fails Key: APEXCORE-627 URL: https://issues.apache.org/jira/browse/APEXCORE-627 Project: Apache Apex Core

[jira] [Commented] (APEXCORE-606) Suggestion: Optimise Kryo Output

[ https://issues.apache.org/jira/browse/APEXCORE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843358#comment-15843358 ] ASF GitHub Bot commented on APEXCORE-606: - Github user brightchen closed the pull request at:

[GitHub] apex-core pull request #455: APEXCORE-606-RV: review only: optimise kryo out...

Github user brightchen closed the pull request at: https://github.com/apache/apex-core/pull/455 --- 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

Re: [DISCUSS] Policy for patches

I prefer to go with the second approach as well. My preference is to go not with a strict end of life policy, but by severity of an issue and complexity of providing fixes for all subsequent releases. In a case a contributor decides to fix a bug in an old release, she will need to provide the

[GitHub] apex-core pull request #458: fix the issue by decrementing unallocated conta...

GitHub user sanjaypujare opened a pull request: https://github.com/apache/apex-core/pull/458 fix the issue by decrementing unallocated containers and also released containers so that the exit condition for the shutdown check is satisfied. @sandeshh Pls review and merge. If okay I

Re: [DISCUSS] Policy for patches

+1 for 2nd approach. We can omit those frozen branches and maintain only active branches. Thanks, Matt On Fri, Jan 27, 2017 at 10:16 AM, Sanjay Pujare wrote: > A strong +1 for the second approach for the reasons Pramod mentioned. > > Is it also possible to “prune”

Re: [DISCUSS] Policy for patches

A strong +1 for the second approach for the reasons Pramod mentioned. Is it also possible to “prune” branches so that we have less of this activity of merging fixes across branches? If we can ascertain that a certain branch is not used by any user/customer (by asking in the community) we should

[jira] [Commented] (APEXMALHAR-2239) Null pointer exception in JDBCPojoInputOperator when the field names do not match in Pojo, table

[ https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843119#comment-15843119 ] Dongming Liang commented on APEXMALHAR-2239: [~Hitesh_]I do need some help. I'm not sure

[DISCUSS] Policy for patches

Hi, I wanted to bring up the topic of patches for issues discovered in older releases and start a discussion to come up with a policy on how to apply them. One approach is the patch gets only applied to the release it was discovered in and master. Another approach is it gets applied to all

[jira] [Commented] (APEXCORE-625) Exception from StreamingAppMasterService.execute is lost if eventloop.stop thrown an exception.

[ https://issues.apache.org/jira/browse/APEXCORE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843095#comment-15843095 ] Vlad Rozov commented on APEXCORE-625: - Please provide details (exception stack trace) for the

[jira] [Commented] (APEXCORE-620) Support Fat Jar without POM, allowing Gradle and other build systems

[ https://issues.apache.org/jira/browse/APEXCORE-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843007#comment-15843007 ] Jose Casillas commented on APEXCORE-620: Thank you for looking at this. I'd suggest that Apex

Re: APEXCORE-294 Clean application shutdown

I have updated the documentation for kill v/s shutdown. let me know if anything more is required. - Tushar. On Mon, Jan 23, 2017 at 6:09 PM, Tushar Gosavi wrote: > Hi Thomas, > > I have updated the pull request as well as design document, will take > care of apex

[jira] [Created] (APEXCORE-626) shutdown-app should accept application similar to kill-app command.

Tushar Gosavi created APEXCORE-626: -- Summary: shutdown-app should accept application similar to kill-app command. Key: APEXCORE-626 URL: https://issues.apache.org/jira/browse/APEXCORE-626 Project:

[jira] [Updated] (APEXCORE-626) shutdown-app should accept application name similar to kill-app command.

[ https://issues.apache.org/jira/browse/APEXCORE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-626: --- Summary: shutdown-app should accept application name similar to kill-app command. (was:

[jira] [Commented] (APEXCORE-625) Exception from StreamingAppMasterService.execute is lost if eventloop.stop thrown an exception.

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

[GitHub] apex-core pull request #457: APEXCORE-625 log exception from eventloop.stop,...

GitHub user tushargosavi opened a pull request: https://github.com/apache/apex-core/pull/457 APEXCORE-625 log exception from eventloop.stop, and let original exception to propagate to caller. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (APEXCORE-625) Exception from StreamingAppMasterService.execute is lost if eventloop.stop thrown an exception.

Tushar Gosavi created APEXCORE-625: -- Summary: Exception from StreamingAppMasterService.execute is lost if eventloop.stop thrown an exception. Key: APEXCORE-625 URL: