[jira] [Resolved] (APEXMALHAR-2063) Integrate WAL to FS WindowDataManager

[ https://issues.apache.org/jira/browse/APEXMALHAR-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2063. -- Resolution: Fixed Fix Version/s: 3.5.0 > Integrate WAL to FS

[jira] [Commented] (APEXMALHAR-2063) Integrate WAL to FS WindowDataManager

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

[GitHub] apex-malhar pull request #322: APEXMALHAR-2063 Made window data manager use ...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/322 --- 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] [Resolved] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2206. -- Resolution: Fixed > Some Application tests taking too long >

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

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

[jira] [Closed] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXMALHAR-2206. > Some Application tests taking too long > -- > >

[GitHub] apex-malhar pull request #384: APEXMALHAR-2206 : Application tests fixes

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/384 --- 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-malhar pull request #384: APEXMALHAR-2206 : Application tests fixes

GitHub user yogidevendra reopened a pull request: https://github.com/apache/apex-malhar/pull/384 APEXMALHAR-2206 : Application tests fixes 1. Fixing placement for lc.shutdown() 2. Disabling log messages for console output in JsonFormatterTest. You can merge this pull request

[GitHub] apex-malhar pull request #384: APEXMALHAR-2206 : Application tests fixes

Github user yogidevendra closed the pull request at: https://github.com/apache/apex-malhar/pull/384 --- 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-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440495#comment-15440495 ] ASF GitHub Bot commented on APEXMALHAR-2206: GitHub user yogidevendra reopened a pull

[jira] [Comment Edited] (APEXCORE-516) StramLocalCluster should always use loopback address for buffer server location

[ https://issues.apache.org/jira/browse/APEXCORE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440431#comment-15440431 ] Vlad Rozov edited comment on APEXCORE-516 at 8/27/16 2:17 AM: -- Example of

[jira] [Commented] (APEXCORE-516) StramLocalCluster should always use loopback address for buffer server location

[ https://issues.apache.org/jira/browse/APEXCORE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440431#comment-15440431 ] Vlad Rozov commented on APEXCORE-516: - Example of bad configurion from builds.apache.org: {noformat}

[jira] [Created] (APEXCORE-516) StramLocalCluster should always use loopback address for buffer server location

Vlad Rozov created APEXCORE-516: --- Summary: StramLocalCluster should always use loopback address for buffer server location Key: APEXCORE-516 URL: https://issues.apache.org/jira/browse/APEXCORE-516

[jira] [Closed] (APEXMALHAR-2134) Catch NullPointerException if some Kafka partition has no leader broker

[ https://issues.apache.org/jira/browse/APEXMALHAR-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua closed APEXMALHAR-2134. -- Resolution: Fixed > Catch NullPointerException if some Kafka partition has no leader

[jira] [Commented] (APEXMALHAR-2134) Catch NullPointerException if some Kafka partition has no leader broker

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

[GitHub] apex-malhar pull request #379: APEXMALHAR-2134 Fix the NullPointerException,...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/379 --- 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-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

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

[jira] [Commented] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

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

[jira] [Resolved] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2199. -- Resolution: Fixed Fix Version/s: 3.5.0 > 0.8 kafka input operator doesn't

[GitHub] apex-malhar pull request #380: APEXMALHAR-2199 Added the support chroot zook...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/380 --- 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-malhar pull request #387: APEXMALHAR-2199 make 0.8 kafka input operator...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/387 --- 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] [Created] (APEXMALHAR-2208) High-level API beam examples

Siyuan Hua created APEXMALHAR-2208: -- Summary: High-level API beam examples Key: APEXMALHAR-2208 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2208 Project: Apache Apex Malhar Issue

[jira] [Closed] (APEXMALHAR-2208) High-level API beam examples

[ https://issues.apache.org/jira/browse/APEXMALHAR-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua closed APEXMALHAR-2208. -- Resolution: Fixed > High-level API beam examples > > >

[jira] [Commented] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

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

[GitHub] apex-malhar pull request #387: APEXMALHAR-2199 fix chroot path for 0.8 kafka...

GitHub user siyuanh opened a pull request: https://github.com/apache/apex-malhar/pull/387 APEXMALHAR-2199 fix chroot path for 0.8 kafka input operator support Simplify the zookeeper url parser to use whatever user specified and support chroot path You can merge this pull request

[jira] [Commented] (APEXMALHAR-2190) Use reusable buffer to serial spillable data structure

[ https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440182#comment-15440182 ] bright chen commented on APEXMALHAR-2190: - Confirmed with David, he will SpillableMap to

[jira] [Updated] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2199: --- Affects Version/s: (was: 3.4.0) > 0.8 kafka input operator doesn't support chroot

[jira] [Updated] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2199: --- Assignee: Siyuan Hua (was: Chaitanya) > 0.8 kafka input operator doesn't support chroot

[GitHub] apex-malhar pull request #386: APEXMALHAR-2205 State management benchmark

GitHub user brightchen opened a pull request: https://github.com/apache/apex-malhar/pull/386 APEXMALHAR-2205 State management benchmark You can merge this pull request into a Git repository by running: $ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2205

Re: Malhar 3.5.0 release

Remember we have the change log for details and complete list. For the announcement probably the first 2 categories are more relevant. On Fri, Aug 26, 2016 at 3:18 PM, Sandesh Hegde wrote: > We can have categorized highlights, individuals can update it in the proper

Re: Malhar 3.5.0 release

We can have categorized highlights, individuals can update it in the proper categories. New Operators New Features Major Bug Fixes Miscellaneous On Fri, Aug 26, 2016 at 2:04 PM Thomas Weise wrote: > There are 2 issues left which unless they get resolved today I

[jira] [Resolved] (APEXMALHAR-2200) Enable checkstyle for demos

[ https://issues.apache.org/jira/browse/APEXMALHAR-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2200. -- Resolution: Fixed Fix Version/s: 3.5.0 > Enable checkstyle for demos >

[jira] [Updated] (APEXMALHAR-2202) Move accumulations to correct package

[ https://issues.apache.org/jira/browse/APEXMALHAR-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2202: - Issue Type: Sub-task (was: Task) Parent: APEXMALHAR-2142 > Move

[jira] [Commented] (APEXMALHAR-2200) Enable checkstyle for demos

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

Re: Malhar 3.5.0 release

There are 2 issues left which unless they get resolved today I suggest we move to 3.6 There is a lot of good stuff going into this release that users may want to know about. Can everyone please have a look at resolved issues and reply if you see items that you think we should highlight in the

[jira] [Updated] (APEXMALHAR-2207) JsonFormatterTest application test should check for presence of expected results

[ https://issues.apache.org/jira/browse/APEXMALHAR-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2207: - Description: Implement proper assertions and test termination. Remove all console

[jira] [Commented] (APEXMALHAR-2201) Suppress console output in Stream API tests

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

[GitHub] apex-malhar pull request #385: APEXMALHAR-2201 Suppressed console output in ...

GitHub user ShunxinLu opened a pull request: https://github.com/apache/apex-malhar/pull/385 APEXMALHAR-2201 Suppressed console output in tests of High-Level API … …demos. You can merge this pull request into a Git repository by running: $ git pull

Flaky unit tests

I see occasional failures with these two tests in the last few days: Failed tests: JMSOutputOperatorTest.testBatch:279 Batch should not be written expected:<20> but was:<15> POJOTimeBasedJoinOperatorTest.testFullOuterJoinOperator:370 Number of tuple emitted expected:<3> but was:<1> Can

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

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

[GitHub] apex-malhar pull request #384: APEXMALHAR-2206 : Application tests fixes

GitHub user yogidevendra opened a pull request: https://github.com/apache/apex-malhar/pull/384 APEXMALHAR-2206 : Application tests fixes 1. Fixing placement for lc.shutdown() 2. Disabling log messages for console output in JsonFormatterTest. You can merge this pull request into

[jira] [Created] (APEXMALHAR-2207) JsonFormatterTest application test should check for presence of expected results

Yogi Devendra created APEXMALHAR-2207: - Summary: JsonFormatterTest application test should check for presence of expected results Key: APEXMALHAR-2207 URL:

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439313#comment-15439313 ] Thomas Weise commented on APEXMALHAR-2206: -- Another example of useless test:

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439309#comment-15439309 ] Yogi Devendra commented on APEXMALHAR-2206: --- Yes. It has ConsoleOutputOperator output =

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439306#comment-15439306 ] Thomas Weise commented on APEXMALHAR-2206: -- com.datatorrent.lib.formatter.JsonFormatterTest?

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439293#comment-15439293 ] Thomas Weise commented on APEXMALHAR-2206: -- There is a lot of console output in the CI that

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439236#comment-15439236 ] Thomas Weise commented on APEXMALHAR-2206: -- I would suggest to ask the author of the code to

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439220#comment-15439220 ] Yogi Devendra commented on APEXMALHAR-2206: --- I propose to create separate newbie ticket for

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439215#comment-15439215 ] Yogi Devendra commented on APEXMALHAR-2206: --- Problem regarding anti pattern in the unit

[jira] [Reopened] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise reopened APEXMALHAR-2206: -- Assignee: Yogi Devendra (was: Bhupesh Chawda) > Some Application tests taking

[jira] [Commented] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439124#comment-15439124 ] Thomas Weise commented on APEXMALHAR-2206: -- [~devendra] can you please look at the PR

[jira] [Updated] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2206: - Fix Version/s: (was: 3.5.0) > Some Application tests taking too long >

Re: Malhar 3.5.0 release

See comments on PR. On Fri, Aug 26, 2016 at 7:16 AM, Yogi Devendra wrote: > Fix for APEXMALHAR-2206 has been reviewed and merged into asf master. > > ~ Yogi > > On 26 August 2016 at 19:04, Yogi Devendra > wrote: > > > We noticed that

[jira] [Resolved] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogi Devendra resolved APEXMALHAR-2206. --- Resolution: Fixed > Some Application tests taking too long >

Re: Malhar 3.5.0 release

Fix for APEXMALHAR-2206 has been reviewed and merged into asf master. ~ Yogi On 26 August 2016 at 19:04, Yogi Devendra wrote: > We noticed that lc.runAsync() is called without corresponding > lc.shutdown() at couple of places in unit tests. > > This caused: > 1.

[jira] [Comment Edited] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438856#comment-15438856 ] Bhupesh Chawda edited comment on APEXMALHAR-2206 at 8/26/16 12:59 PM:

[jira] [Updated] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda updated APEXMALHAR-2206: --- Description: Some Application Tests seems to be running for a long time.

[jira] [Updated] (APEXMALHAR-2206) Some Application tests taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda updated APEXMALHAR-2206: --- Summary: Some Application tests taking too long (was: Deduper Application test

Re: Malhar 3.5.0 release

Hi Thomas, https://issues.apache.org/jira/browse/APEXMALHAR-2206 is one small bug which Yogi pointed out. It was intermittently taking too long to complete the travis builds. We thought it would be a good idea to get it in for the release. I have just opened a PR:

[jira] [Updated] (APEXMALHAR-2206) Deduper Application test taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda updated APEXMALHAR-2206: --- Fix Version/s: 3.5.0 > Deduper Application test taking too long >

[jira] [Commented] (APEXMALHAR-2206) Deduper Application test taking too long

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

[GitHub] apex-malhar pull request #383: APEXMALHAR-2206: Fixed application test. Limi...

GitHub user bhupeshchawda opened a pull request: https://github.com/apache/apex-malhar/pull/383 APEXMALHAR-2206: Fixed application test. Limited the input rate for t… …he test app. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (APEXMALHAR-2206) Deduper Application test taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438803#comment-15438803 ] Bhupesh Chawda commented on APEXMALHAR-2206: The input data generator operator does not

[jira] [Assigned] (APEXMALHAR-2206) Deduper Application test taking too long

[ https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhupesh Chawda reassigned APEXMALHAR-2206: -- Assignee: Bhupesh Chawda > Deduper Application test taking too long >

[jira] [Created] (APEXMALHAR-2206) Deduper Application test taking too long

Bhupesh Chawda created APEXMALHAR-2206: -- Summary: Deduper Application test taking too long Key: APEXMALHAR-2206 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2206 Project: Apache Apex

[jira] [Commented] (APEXMALHAR-2195) LineReaderContext gives incorrect results for files not ending with the newline

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

[jira] [Resolved] (APEXMALHAR-2195) LineReaderContext gives incorrect results for files not ending with the newline

[ https://issues.apache.org/jira/browse/APEXMALHAR-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2195. -- Resolution: Fixed > LineReaderContext gives incorrect results for files not ending

[jira] [Commented] (APEXMALHAR-2134) Catch NullPointerException if some Kafka partition has no leader broker

[ https://issues.apache.org/jira/browse/APEXMALHAR-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438594#comment-15438594 ] ASF GitHub Bot commented on APEXMALHAR-2134: GitHub user chaithu14 reopened a pull

[jira] [Commented] (APEXMALHAR-2134) Catch NullPointerException if some Kafka partition has no leader broker

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

[GitHub] apex-malhar pull request #379: APEXMALHAR-2134 Fix the NullPointerException,...

Github user chaithu14 closed the pull request at: https://github.com/apache/apex-malhar/pull/379 --- 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-malhar pull request #379: APEXMALHAR-2134 Fix the NullPointerException,...

GitHub user chaithu14 reopened a pull request: https://github.com/apache/apex-malhar/pull/379 APEXMALHAR-2134 Fix the NullPointerException, if the kafka partition has no leader broker You can merge this pull request into a Git repository by running: $ git pull

[GitHub] apex-malhar pull request #372: APEXMALHAR-2195 - Fix LineReaderContext last ...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/372 --- 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-2202) Move accumulations to correct package

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

[GitHub] apex-malhar pull request #381: APEXMALHAR-2202 Moved accumulations to org.ap...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/381 --- 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: GenericFileOutputOpeator doesn't work for all hadoop file systems

I propose alternate approach to than the 3 options mentioned above: In AbstractFileOutputOperator we can introduce one flag saying isFileSystemAppendSupported. This flag should be set based on the filePath in setup or activate method. It can be done in 2 ways: 1. Adding if else rules based on

[jira] [Commented] (APEXMALHAR-2195) LineReaderContext gives incorrect results for files not ending with the newline

[ https://issues.apache.org/jira/browse/APEXMALHAR-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438541#comment-15438541 ] ASF GitHub Bot commented on APEXMALHAR-2195: GitHub user yogidevendra reopened a pull

[jira] [Commented] (APEXMALHAR-2195) LineReaderContext gives incorrect results for files not ending with the newline

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

[GitHub] apex-malhar pull request #372: APEXMALHAR-2195 - Fix LineReaderContext last ...

GitHub user yogidevendra reopened a pull request: https://github.com/apache/apex-malhar/pull/372 APEXMALHAR-2195 - Fix LineReaderContext last record 2. Changes in the test app You can merge this pull request into a Git repository by running: $ git pull

[GitHub] apex-malhar pull request #372: APEXMALHAR-2195 - Fix LineReaderContext last ...

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