[jira] [Assigned] (APEXMALHAR-2413) Improve PojoInnerJoin Accumulation

[ https://issues.apache.org/jira/browse/APEXMALHAR-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kolhatkar reassigned APEXMALHAR-2413: - Assignee: Hitesh Kapoor (was: Chinmay Kolhatkar) > Improve

[jira] [Assigned] (APEXMALHAR-2414) Improve performance of PojoInnerJoin accum by using PojoUtils

[ https://issues.apache.org/jira/browse/APEXMALHAR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kolhatkar reassigned APEXMALHAR-2414: - Assignee: (was: Chinmay Kolhatkar) > Improve performance of

[jira] [Resolved] (APEXMALHAR-2418) Update the twitter library to 4.0.6

[ https://issues.apache.org/jira/browse/APEXMALHAR-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXMALHAR-2418. - Resolution: Fixed Assignee: (was: Priyanka Gugale) Fix

[jira] [Assigned] (APEXMALHAR-2418) Update the twitter library to 4.0.6

[ https://issues.apache.org/jira/browse/APEXMALHAR-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale reassigned APEXMALHAR-2418: --- Assignee: Priyanka Gugale > Update the twitter library to 4.0.6 >

[jira] [Commented] (APEXMALHAR-2418) Update the twitter library to 4.0.6

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

[GitHub] apex-malhar pull request #558: APEXMALHAR-2418 Updated twitter4j library ver...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/558 --- 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 #440: APEXCORE-580-581 custom control tuple support

Github user bhupeshchawda closed the pull request at: https://github.com/apache/apex-core/pull/440 --- 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-580) Interface for processing and emitting control tuples

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

[jira] [Commented] (APEXCORE-580) Interface for processing and emitting control tuples

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

[GitHub] apex-core pull request #440: APEXCORE-580-581 custom control tuple support

GitHub user bhupeshchawda reopened a pull request: https://github.com/apache/apex-core/pull/440 APEXCORE-580-581 custom control tuple support You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhupeshchawda/apex-core

[jira] [Commented] (APEXCORE-642) Catch all exceptions in StreamingAppMasterService.serviceInit() and create a StramEvent

[ https://issues.apache.org/jira/browse/APEXCORE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877070#comment-15877070 ] Sanjay M Pujare commented on APEXCORE-642: -- I am going to close this JIRA as "Won't Fix"

[jira] [Commented] (APEXMALHAR-2419) KafkaSinglePortExactlyOnceOutputOperator fails on recovery

[ https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876656#comment-15876656 ] Sandesh commented on APEXMALHAR-2419: - Fix is here, until it is merged.

[jira] [Assigned] (APEXMALHAR-2419) KafkaSinglePortExactlyOnceOutputOperator fails on recovery

[ https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandesh reassigned APEXMALHAR-2419: --- Assignee: Sandesh > KafkaSinglePortExactlyOnceOutputOperator fails on recovery >

[jira] [Commented] (APEXMALHAR-2419) KafkaSinglePortExactlyOnceOutputOperator fails on recovery

[ https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876641#comment-15876641 ] Sandesh commented on APEXMALHAR-2419: - largestCompletedWindow will be -1, if the recovery is not

[jira] [Closed] (APEXMALHAR-2410) KafkaSinglePortExactlyOnceOutputOperator fails if an operator crashes in the very first window

[ https://issues.apache.org/jira/browse/APEXMALHAR-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandesh closed APEXMALHAR-2410. --- > KafkaSinglePortExactlyOnceOutputOperator fails if an operator crashes in the > very first window

[jira] [Resolved] (APEXMALHAR-2410) KafkaSinglePortExactlyOnceOutputOperator fails if an operator crashes in the very first window

[ https://issues.apache.org/jira/browse/APEXMALHAR-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandesh resolved APEXMALHAR-2410. - Resolution: Duplicate Duplicate of APEXMALHAR-2419 >

Re: Occasional Out of order tuples when emitting from a thread

Sunil, You can poll the queue in end window since process method in the input port does not get called if there is no incoming tuple. However, end window is called irrespective of there are incoming tuples or not. Regards, Ashwin. On Tue, Feb 21, 2017 at 11:32 AM, Sunil Parmar

Re: Occasional Out of order tuples when emitting from a thread

Ram, Thanks for the prompt response. If we use the approach you suggested we're dependent on main thread's process call I.e. Tuples in the thread safe queue gets only processed when main thread is processing incoming tuples. How can we explicitly call the process from polling of delay queue ?

Re: Occasional Out of order tuples when emitting from a thread

Please note that tuples should not be emitted by any thread other than the main operator thread. A common pattern is to use a thread-safe queue and have worker threads enqueue tuples there; the main operator thread then pulls tuples from the queue and emits them. Ram On Tue, Feb 21, 2017 at

Occasional Out of order tuples when emitting from a thread

Hi there, We have the following setup: * we have a generic operator that's processing tuples in its input port * in the input port's process method, we check for a condition, and: * if the condition is met, the tuple is emitted to the next operator right away (in the process

Re: Redshift Output Operator

Chaitanya, This is good first cut. Post this work, do take a look at loading data before file rotation. Thks Amol *Follow @amolhkekre* *Join us at Apex Big Data World-San Jose , April 4, 2017!* [image: http://www.apexbigdata.com/san-jose-register.html]

[jira] [Commented] (APEXMALHAR-2419) KafkaSinglePortExactlyOnceOutputOperator fails on recovery

[ https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876082#comment-15876082 ] Munagala V. Ramanath commented on APEXMALHAR-2419: -- The expectation seems to be that

[jira] [Created] (APEXMALHAR-2419) KafkaSinglePortExactlyOnceOutputOperator fails on recovery

Munagala V. Ramanath created APEXMALHAR-2419: Summary: KafkaSinglePortExactlyOnceOutputOperator fails on recovery Key: APEXMALHAR-2419 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2419

[jira] [Commented] (APEXMALHAR-2418) Update the twitter library to 4.0.6

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

[GitHub] apex-malhar pull request #558: APEXMALHAR-2418 Updated twitter4j library ver...

GitHub user Shubham0411 opened a pull request: https://github.com/apache/apex-malhar/pull/558 APEXMALHAR-2418 Updated twitter4j library version for twitter demo ap… There was a known issue of Build Failure for twitter version 4.0.4. So for successfully building and launching

Re: [jira] [Commented] (APEXMALHAR-2381) Change FSWindowManager for peraformance issues in Kinesis Input Operator

On o Zxdfxxffxd hu On Feb 21, 2017 2:21 PM, "ASF GitHub Bot (JIRA)" wrote: [ https://issues.apache.org/jira/browse/APEXMALHAR-2381? page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel& focusedCommentId=15875616#comment-15875616 ] ASF GitHub Bot

[jira] [Updated] (APEXMALHAR-2418) Update the twitter library to 4.0.6

[ https://issues.apache.org/jira/browse/APEXMALHAR-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shubham Agrawal updated APEXMALHAR-2418: Summary: Update the twitter library to 4.0.6 (was: Updating the supported

[jira] [Created] (APEXMALHAR-2418) Updating the supported version in Twitter Library.

Shubham Agrawal created APEXMALHAR-2418: --- Summary: Updating the supported version in Twitter Library. Key: APEXMALHAR-2418 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2418 Project:

[jira] [Resolved] (APEXMALHAR-2381) Change FSWindowManager for performance issues in Kinesis Input Operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya resolved APEXMALHAR-2381. --- Resolution: Fixed Fix Version/s: 3.7.0 > Change FSWindowManager for performance

[GitHub] apex-malhar pull request #550: APEXMALHAR-2381 Change WindowManager for perf...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/550 --- 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] [Updated] (APEXMALHAR-2381) Change FSWindowManager for performance issues in Kinesis Input Operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya updated APEXMALHAR-2381: -- Issue Type: Improvement (was: Bug) > Change FSWindowManager for performance issues in

[jira] [Created] (APEXMALHAR-2417) Add PojoOuterJoin (left, right and full) accumulation

Hitesh Kapoor created APEXMALHAR-2417: - Summary: Add PojoOuterJoin (left, right and full) accumulation Key: APEXMALHAR-2417 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2417 Project: