Re: Adding new log4j appender to Apex core

+1 for approach 2. Regards, Ajay On Wed, Nov 23, 2016 at 12:16 PM, David Yan wrote: > The goal of this log4j appender is to provide a log offset and the fixed > name of the container log file (instead of apex.log becoming apex.log.1 and > then apex.log.2, etc due to

[jira] [Commented] (APEXMALHAR-2351) Exception while fetching properties for Operators using JdbcStore

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

[GitHub] apex-malhar pull request #505: APEXMALHAR-2351 fix to extract operator prope...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/505 --- 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: Adding new log4j appender to Apex core

The goal of this log4j appender is to provide a log offset and the fixed name of the container log file (instead of apex.log becoming apex.log.1 and then apex.log.2, etc due to rotation) as part of an error STRAM event so users can easily locate the log entries around the error. The user can

[jira] [Resolved] (APEXCORE-379) Latency is stuck when an operator is stuck (before the 1000 window threshold)

[ https://issues.apache.org/jira/browse/APEXCORE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-379. --- Resolution: Fixed Fix Version/s: 3.5.0 > Latency is stuck when an operator is stuck

[jira] [Resolved] (APEXCORE-544) Latency values are out of whack immediately after app is launched

[ https://issues.apache.org/jira/browse/APEXCORE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-544. --- Resolution: Fixed Fix Version/s: 3.5.0 > Latency values are out of whack immediately

[jira] [Commented] (APEXCORE-544) Latency values are out of whack immediately after app is launched

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

[GitHub] apex-core pull request #401: APEXCORE-544 APEXCORE-379 #resolve fixed latenc...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/401 --- 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-malhar pull request #504: APEXMALHAR-2340 code changes to initialize th...

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

[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=15689019#comment-15689019 ] ASF GitHub Bot commented on APEXMALHAR-2316: GitHub user Hitesh-Scorpio opened a pull

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

GitHub user Hitesh-Scorpio opened a pull request: https://github.com/apache/apex-malhar/pull/506 APEXMALHAR-2316 APEXMALHAR-2346 Moved suitable code to activate() for… … initializing tuple class attribute and changed the argument type of DocumentBuilder.parse() to InputSource.

[GitHub] apex-malhar pull request #484: APEXMALHAR-2316 Moved suitable code to activa...

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

[jira] [Commented] (APEXCORE-498) Named Checkpoints - Checkpoint the DAG with a name/tag and start the app from that point

[ https://issues.apache.org/jira/browse/APEXCORE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15688960#comment-15688960 ] David Yan commented on APEXCORE-498: In addition to this, there are many components and operators in

Re: Adding new log4j appender to Apex core

Hi, Thomas, Yes log4j is ultimately owned by user, and they should be able to override it. What I am trying to do is provide a default behavior for Apex. In case user isn't using any logger of their own we should use this new appender of Apex rather than using standard log4j appender as per

Re: Core 3.5.0 release

Thomas, Agreed, both issues are not critical. I don't expect that APEXCORE-456 (and related JIRAs) require API changes, so they may be released as part of the next minor release. At the same time, APEXCORE-456 is an enhancement/improvement and does not qualify for the minor bug fix release.

[jira] [Updated] (APEXCORE-461) Hidden ports in extended operators appear in the application package

[ https://issues.apache.org/jira/browse/APEXCORE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-461: Assignee: Bhupesh Chawda > Hidden ports in extended operators appear in the application package >

[jira] [Commented] (APEXCORE-498) Named Checkpoints - Checkpoint the DAG with a name/tag and start the app from that point

[ https://issues.apache.org/jira/browse/APEXCORE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15688437#comment-15688437 ] Sanjay M Pujare commented on APEXCORE-498: -- If a user decides to use savepoints (named

Re: Adding new log4j appender to Apex core

The only way to “enforce” this new appender is to update the archetypes (apex-app-archetype and apex-conf-archetype under apex-core/ ) to use the new ones as default. But there does not seem to be a way to enforce this for anyone not using the archetypes. I agree with not relying on ~/.dt in

[jira] [Commented] (APEXMALHAR-2352) Improve performance of keyed windowed operators

[ https://issues.apache.org/jira/browse/APEXMALHAR-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15688259#comment-15688259 ] bright chen commented on APEXMALHAR-2352: - This is an issue causes memory leak:

[jira] [Updated] (APEXMALHAR-2352) Improve performance of keyed windowed operators

[ https://issues.apache.org/jira/browse/APEXMALHAR-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bright chen updated APEXMALHAR-2352: Description: refer to https://issues.apache.org/jira/browse/APEXMALHAR-2339 to the

[jira] [Created] (APEXMALHAR-2352) Improve performance of keyed windowed operators

bright chen created APEXMALHAR-2352: --- Summary: Improve performance of keyed windowed operators Key: APEXMALHAR-2352 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2352 Project: Apache Apex

[GitHub] apex-core pull request #347: [APEXCORE-332][WIP] Improve partitioning to sup...

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

[GitHub] apex-core pull request #348: [APEXMALHAR-1978] Replaced usages of {groupId} ...

Github user ilganeli closed the pull request at: https://github.com/apache/apex-core/pull/348 --- 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-1978) Replace ${groupId} with ${project.groupId} in modules and project pom

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

[jira] [Commented] (APEXCORE-332) Support Even Distribution Of Tuples To A Non Power Of 2 Number Of Partitions

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

Re: Core 3.5.0 release

Vlad, I'm hoping to get the release done to fix a dependency issue in Beam. IMO the issues above aren't critical for the release, they can go either into a patch or the next minor version? Thanks On Tue, Nov 22, 2016 at 2:17 PM, Vlad Rozov wrote: > Can the release 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=15688112#comment-15688112 ] Thomas Weise commented on APEXCORE-526: --- It would be good to document what we have for Malhar so

Re: Core 3.5.0 release

Can the release be postponed by a week or two? I suggest to include https://issues.apache.org/jira/browse/APEXCORE-539 and https://issues.apache.org/jira/browse/APEXCORE-456. With APEXCORE-456 and few related JIRAs (to be filed) I expect 2x performance improvement sending tuples over the wire.

Re: Malhar release 3.6

IMO we should not delay the release any longer. I will cut the RC tomorrow unless there is an objection. Thomas On Tue, Nov 22, 2016 at 2:05 PM, David Yan wrote: > Thomas, > > We need more time for the timebucket change and the purging feature, and we > need to do

[jira] [Commented] (APEXCORE-148) Auto metric: metric aggregations test is failing

[ https://issues.apache.org/jira/browse/APEXCORE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15688055#comment-15688055 ] Vlad Rozov commented on APEXCORE-148: - Any update on the JIRA? I suggest lowering the priority. >

Re: Malhar release 3.6

Thomas, We need more time for the timebucket change and the purging feature, and we need to do benchmarking after those features have been implemented. Is it possible to postpone the release? If not, we can shoot for completing the features for the 3.7.0 release. David On Tue, Nov 22, 2016 at

Re: Adding new log4j appender to Apex core

The log4j configuration is ultimately owned by the user, so how do you want to enforce a custom appender? I don't think that this should rely on anything in ~/.dt either Thomas On Tue, Nov 22, 2016 at 10:00 AM, Priyanka Gugale wrote: > Hi, > > I am working on

Re: Core 3.5.0 release

Hi Thomas, Would like to get this merged for Apex Core 3.5.0 release if possible: https://github.com/apache/apex-core/pull/401 Thanks, David On Tue, Nov 22, 2016 at 11:59 AM, Thomas Weise wrote: > Hi, > > I would like to propose the 3.5.0 release of Apex core: > >

Re: Malhar release 3.6

David, Siyuan, Any update, I would like to cut the RC. Thanks On Sun, Nov 20, 2016 at 10:23 PM, Siyuan Hua wrote: > Yes yes, > We need to put the clear plan upfront > > This ticket was thought and scheduled to be done after the APEXMALHAR-2271 > SpillableSetMultimap

Re: Core 3.5.0 release

+1 On Tue, Nov 22, 2016 at 11:59 AM, Thomas Weise wrote: > Hi, > > I would like to propose the 3.5.0 release of Apex core: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20APEXCORE%20AND% > 20fixVersion%20%3D%203.5.0%20ORDER%20BY%20status%20ASC% >

Core 3.5.0 release

Hi, I would like to propose the 3.5.0 release of Apex core: https://issues.apache.org/jira/issues/?jql=project%20%3D%20APEXCORE%20AND%20fixVersion%20%3D%203.5.0%20ORDER%20BY%20status%20ASC%2C%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC There are several enhancements that we should

[jira] [Resolved] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

[ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-532. --- Resolution: Fixed > New dynamically added operator does not start with correct windowId. >

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

[ https://issues.apache.org/jira/browse/APEXMALHAR-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687670#comment-15687670 ] bright chen commented on APEXMALHAR-2339: - The performance of KeyedWindowed operator decrease

Adding new log4j appender to Apex core

Hi, I am working on APEXCORE-563 As per this Jira we should put log file name in container/operator events. The problem is current RollingFileAppender keeps renaming files from 1 to 2 to ... n as files reach maximum allowed file size. Because

[jira] [Commented] (APEXMALHAR-2351) Exception while fetching properties for Operators using JdbcStore

[ https://issues.apache.org/jira/browse/APEXMALHAR-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686273#comment-15686273 ] ASF GitHub Bot commented on APEXMALHAR-2351: GitHub user Hitesh-Scorpio opened a pull

[GitHub] apex-malhar pull request #505: APEXMALHAR-2351 fix to extract operator prope...

GitHub user Hitesh-Scorpio opened a pull request: https://github.com/apache/apex-malhar/pull/505 APEXMALHAR-2351 fix to extract operator properties for Jdbc Poll i/p … …operator @bhupeshchawda please review You can merge this pull request into a Git repository by running: