[jira] [Commented] (APEXCORE-687) Update docs, change supported Hadoop version to 2.6

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

Re: Towards Apache Apex 3.6.0 release

I'd like to request that 687, 692 and 693 be included in the 3.6.0 release. I will send PRs for these shortly. Thanks, Dean On Fri, Apr 14, 2017 at 5:05 AM, Amol Kekre wrote: > +1 to cut a release > > Thks > Amol > > > E:a...@datatorrent.com | M: 510-449-2606 |

[GitHub] apex-core pull request #512: APEXCORE-687 update docs for supported Hadoop v...

GitHub user deanlockgaard opened a pull request: https://github.com/apache/apex-core/pull/512 APEXCORE-687 update docs for supported Hadoop version 2.6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/deanlockgaard/apex-core

[jira] [Commented] (APEXCORE-687) Update docs, change supported Hadoop version to 2.6

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

[GitHub] apex-core pull request #508: APEXCORE-687 change supported Hadoop v2.6 in do...

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

[GitHub] apex-site pull request #73: APEXCORE-693 update 3rd party downloads, include...

GitHub user deanlockgaard opened a pull request: https://github.com/apache/apex-site/pull/73 APEXCORE-693 update 3rd party downloads, include binary build for existing clusters You can merge this pull request into a Git repository by running: $ git pull

[GitHub] apex-malhar pull request #604: Apexmalhar 2467 Move JMS related examples fro...

GitHub user prasannapramod opened a pull request: https://github.com/apache/apex-malhar/pull/604 Apexmalhar 2467 Move JMS related examples from datatorrent examples to apex-malhar examples @amberarrow @tweise @ashwinchandrap please review You can merge this pull request into a Git

[jira] [Commented] (APEXCORE-693) Add Apex binary build download for existing clusters

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

[GitHub] apex-core pull request #513: APEXCORE-692 dev setup sandbox section to defer...

GitHub user deanlockgaard opened a pull request: https://github.com/apache/apex-core/pull/513 APEXCORE-692 dev setup sandbox section to defer to Apex downloads page You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (APEXCORE-692) Apex Dev Setup doc should reference Apex Sandbox

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

[jira] [Updated] (APEXCORE-701) Upgrade Malhar version in archetype to 3.7.0

[ https://issues.apache.org/jira/browse/APEXCORE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-701: -- Priority: Trivial (was: Major) > Upgrade Malhar version in archetype to 3.7.0 >

[jira] [Resolved] (APEXCORE-701) Upgrade Malhar version in archetype to 3.7.0

[ https://issues.apache.org/jira/browse/APEXCORE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-701. --- Resolution: Fixed Assignee: Thomas Weise Fix Version/s: 3.6.0 > Upgrade

[jira] [Resolved] (APEXCORE-687) Update docs, change supported Hadoop version to 2.6

[ https://issues.apache.org/jira/browse/APEXCORE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-687. --- Resolution: Fixed Fix Version/s: 3.6.0 > Update docs, change supported Hadoop

[jira] [Commented] (APEXCORE-701) Upgrade Malhar version in archetype to 3.7.0

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

[GitHub] apex-core pull request #511: APEXCORE-701 bump Malhar version to 3.7.0

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

[GitHub] apex-core pull request #512: APEXCORE-687 update docs for supported Hadoop v...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/512 --- 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-687) Update docs, change supported Hadoop version to 2.6

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

Re: Towards Apache Apex 3.6.0 release

+1 to cut a release Thks Amol E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre* www.datatorrent.com On Thu, Apr 13, 2017 at 9:22 AM, Pramod Immaneni wrote: > +1 > > I would like to see 699 and 700 addressed as well. > > On Wed, Apr 12, 2017 at 10:16

[jira] [Updated] (APEXCORE-143) Graceful shutdown of test applications

[ https://issues.apache.org/jira/browse/APEXCORE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-143: Fix Version/s: (was: 3.6.0) > Graceful shutdown of test applications >

Re: Towards Apache Apex 3.6.0 release

+1 to cut the release. APEXCORE-678 is optional as it is not a regression and there is no PR open for it. It should not block the release. Thank you, Vlad On 4/12/17 22:16, Tushar Gosavi wrote: Hi, It has been four month since 3.5.0 Apex Core release. There are several new features added

[jira] [Resolved] (APEXCORE-686) AppPackage fails when .apa contains zero length stored entry

[ https://issues.apache.org/jira/browse/APEXCORE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-686. -- Resolution: Fixed > AppPackage fails when .apa contains zero length stored entry >

[jira] [Commented] (APEXCORE-686) AppPackage fails when .apa contains zero length stored entry

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

[GitHub] apex-core pull request #502: APEXCORE-686 AppPackage fails when .apa contain...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/502 --- 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] [Updated] (APEXCORE-692) Apex Dev Setup doc should reference download page

[ https://issues.apache.org/jira/browse/APEXCORE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-692: -- Summary: Apex Dev Setup doc should reference download page (was: Apex Dev Setup doc should

Re: Towards Apache Apex 3.6.0 release

If there are JIRAs that should be completed, then those should be marked with the fix version so that a report can be run. IMO such items should only be added when they are either critical for the release or will be completed in the next couple of days. On Thu, Apr 13, 2017 at 7:27 PM, Vlad

Re: Towards Apache Apex 3.6.0 release

Dean, 692 and 693 are web site documentation issues and are not part of the Apex core 3.6.0 release. 687 can be covered in the release README (known issues). Thank you, Vlad On 4/13/17 14:11, Dean Lockgaard wrote: I'd like to request that 687, 692 and 693 be included in the 3.6.0 release.

[jira] [Updated] (APEXCORE-692) Apex Dev Setup doc should reference Apex Sandbox

[ https://issues.apache.org/jira/browse/APEXCORE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-692: -- Fix Version/s: 3.6.0 > Apex Dev Setup doc should reference Apex Sandbox >

[jira] [Created] (APEXCORE-701) Upgrade Malhar version in archetype to 3.7.0

Thomas Weise created APEXCORE-701: - Summary: Upgrade Malhar version in archetype to 3.7.0 Key: APEXCORE-701 URL: https://issues.apache.org/jira/browse/APEXCORE-701 Project: Apache Apex Core

[jira] [Commented] (APEXCORE-701) Upgrade Malhar version in archetype to 3.7.0

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

Re: Programmatic log4j appender in Apex

+1 Also the proposed feature would need to be implemented in a way that avoids a hard dependency on log4j. The interface for logging is slf4j and it should be possible to use other logger backends. On Mon, Apr 10, 2017 at 9:21 PM, Sergey Golovko wrote: > I don't think

[jira] [Commented] (APEXCORE-678) Shutdown of application should start from input nodes

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

[jira] [Assigned] (APEXCORE-480) Change the container log name from dt.log to apex.log

[ https://issues.apache.org/jira/browse/APEXCORE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise reassigned APEXCORE-480: - Assignee: Thomas Weise > Change the container log name from dt.log to apex.log >

[GitHub] apex-core pull request #511: APEXCORE-701 bump Malhar version to 3.7.0

GitHub user tweise opened a pull request: https://github.com/apache/apex-core/pull/511 APEXCORE-701 bump Malhar version to 3.7.0 R: @vrozov You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/apex-core APEXCORE-701

[jira] [Commented] (APEXCORE-480) Change the container log name from dt.log to apex.log

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

[GitHub] apex-core pull request #510: APEXCORE-480 change log file name to apex.log

GitHub user tweise opened a pull request: https://github.com/apache/apex-core/pull/510 APEXCORE-480 change log file name to apex.log R: @davidyan74 @vrozov You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/apex-core

[jira] [Updated] (APEXCORE-660) Documentation for Control tuple support changes

[ https://issues.apache.org/jira/browse/APEXCORE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-660: -- Fix Version/s: 3.6.0 > Documentation for Control tuple support changes >

[GitHub] apex-core pull request #509: APEXCORE-678 Fixed shutdown of input nodes in S...

GitHub user bhupeshchawda opened a pull request: https://github.com/apache/apex-core/pull/509 APEXCORE-678 Fixed shutdown of input nodes in StreamingContainer This was a straightforward bug. Also did not find any easy way to add test for it. @tushargosavi please see You

[jira] [Commented] (APEXCORE-660) Documentation for Control tuple support changes

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

[GitHub] apex-core pull request #484: APEXCORE-660 Added documentation for custom con...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/484 --- 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] [Resolved] (APEXCORE-511) DAG.addOperator, addStream and addModule should check for null and empty names

[ https://issues.apache.org/jira/browse/APEXCORE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-511. - Resolution: Implemented Fix Version/s: 3.6.0 > DAG.addOperator, addStream and addModule

Re: Towards Apache Apex 3.6.0 release

+1 I would like to see 699 and 700 addressed as well. On Wed, Apr 12, 2017 at 10:16 PM, Tushar Gosavi wrote: > Hi, > > It has been four month since 3.5.0 Apex Core release. There are several new > features added to core after 3.5.0. I would like to propose the 3.6.0 >

[jira] [Commented] (APEXCORE-511) DAG.addOperator, addStream and addModule should check for null and empty names

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

[jira] [Resolved] (APEXCORE-660) Documentation for Control tuple support changes

[ https://issues.apache.org/jira/browse/APEXCORE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-660. --- Resolution: Fixed > Documentation for Control tuple support changes >

[GitHub] apex-core pull request #501: APEXCORE-511 add null and empty checks for addO...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/501 --- 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] [Assigned] (APEXCORE-700) Make the plugin registration interface uniform

[ https://issues.apache.org/jira/browse/APEXCORE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-700: Assignee: Pramod Immaneni > Make the plugin registration interface uniform >