[jira] [Updated] (APEXMALHAR-2278) Implement Kudu Output Operator for non-transactional streams

[ https://issues.apache.org/jira/browse/APEXMALHAR-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ananth updated APEXMALHAR-2278: --- Description: Here are some benefits of integrating Kudu and Apex: Kudu is just declared 1.0

[jira] [Updated] (APEXMALHAR-2278) Implement Kudu Output Operator for non-transactional streams

[ https://issues.apache.org/jira/browse/APEXMALHAR-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ananth updated APEXMALHAR-2278: --- Description: Here are some benefits of integrating Kudu and Apex: Kudu is just declared 1.0

[jira] [Updated] (APEXMALHAR-2278) Implement Kudu Output Operator for non-transactional streams

[ https://issues.apache.org/jira/browse/APEXMALHAR-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ananth updated APEXMALHAR-2278: --- Description: Here are some benefits of integrating Kudu and Apex: Kudu is just declared 1.0

Re: open/close ports and active/inactive streams

+1. This has come up with Apex customers on batch use cases. This will make batch use cases easy and robust. Today a lot of external tooling is needed. For Apex, this means reduction in stack of tech used. Thks Amol E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre*

[jira] [Created] (APEXMALHAR-2472) Implement Kudu Input Operator

Ananth created APEXMALHAR-2472: -- Summary: Implement Kudu Input Operator Key: APEXMALHAR-2472 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2472 Project: Apache Apex Malhar Issue Type:

[Design] - Kudu Output Operator

Hello All, I would like to the community's opinion on the implementation of Kudu output operator. A first cut implementation was made available in November last year but I guess we did not get time to discuss this thoroughly on the mailing list and hence the PR did not get merged. This

[jira] [Assigned] (APEXCORE-469) Website: Rewrite fetch releases script

[ https://issues.apache.org/jira/browse/APEXCORE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dean Lockgaard reassigned APEXCORE-469: --- Assignee: Dean Lockgaard > Website: Rewrite fetch releases script >

[jira] [Updated] (APEXMALHAR-2284) POJOInnerJoinOperatorTest fails in Travis CI

[ https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXMALHAR-2284: --- Priority: Minor (was: Blocker) > POJOInnerJoinOperatorTest fails in Travis CI >

[jira] [Commented] (APEXMALHAR-2284) POJOInnerJoinOperatorTest fails in Travis CI

[ https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952246#comment-15952246 ] Vlad Rozov commented on APEXMALHAR-2284: Lowered priority from blocker. If this is an

open/close ports and active/inactive streams

All, Currently Apex assumes that an operator can emit on any defined output port and all streams defined by a DAG are active. I'd like to propose an ability for an operator to open and close output ports. By default all ports defined by an operator will be open. In the case an operator for

[jira] [Updated] (APEXCORE-469) Website: Rewrite fetch releases script

[ https://issues.apache.org/jira/browse/APEXCORE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-469: -- Component/s: Website > Website: Rewrite fetch releases script >

[jira] [Updated] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient

[ https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-656: Description: Upgrade org.apache.httpcomponents.httpclient dependency to the latest 4.3.x version.

[jira] [Updated] (APEXMALHAR-2284) POJOInnerJoinOperator is broken

[ https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2284: - Priority: Major (was: Minor) > POJOInnerJoinOperator is broken >

[jira] [Updated] (APEXMALHAR-2284) POJOInnerJoinOperator is broken

[ https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2284: - Summary: POJOInnerJoinOperator is broken (was: POJOInnerJoinOperatorTest fails in

[jira] [Updated] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient

[ https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-656: Description: Upgrade org.apache.httpcomponents.httpclient dependency to the latest 4.3.x version.

[jira] [Created] (APEXMALHAR-2469) Upgrade org.apache.httpcomponents.httpclient

Vlad Rozov created APEXMALHAR-2469: -- Summary: Upgrade org.apache.httpcomponents.httpclient Key: APEXMALHAR-2469 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2469 Project: Apache Apex Malhar

[jira] [Commented] (APEXMALHAR-2284) POJOInnerJoinOperator is broken

[ https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952280#comment-15952280 ] Thomas Weise commented on APEXMALHAR-2284: -- Chaitanya please provide an update on this. Is

[GitHub] apex-malhar pull request #553: upgrade httpclient version

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/553 --- 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: open/close ports and active/inactive streams

Sounds like a good idea, +1 Couple of questions/comments: - "...re-open the port and wait till the stream becomes active again...". How is the operator informed that the stream is active again or is it just a property of the output port that the operator needs to check? - Say an operator has 2

Re: open/close ports and active/inactive streams

Please see my comments inline. Thank you, Vlad //On 4/1/17 09:13, Sanjay Pujare wrote: Sounds like a good idea, +1 Couple of questions/comments: - "...re-open the port and wait till the stream becomes active again...". How is the operator informed that the stream is active again or is it

[jira] [Commented] (APEXMALHAR-2465) Travis build is failing because of excessive logging

[ https://issues.apache.org/jira/browse/APEXMALHAR-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952302#comment-15952302 ] Thomas Weise commented on APEXMALHAR-2465: -- It is important that the CI infrastructure

[jira] [Updated] (APEXMALHAR-2465) Travis build is failing because of excessive logging

[ https://issues.apache.org/jira/browse/APEXMALHAR-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2465: - Priority: Critical (was: Minor) > Travis build is failing because of excessive

Re: open/close ports and active/inactive streams

What's a use case for this ? Ram On Sat, Apr 1, 2017 at 8:12 AM, Vlad Rozov wrote: > All, > > Currently Apex assumes that an operator can emit on any defined output > port and all streams defined by a DAG are active. I'd like to propose an > ability for an operator to

[jira] [Created] (APEXMALHAR-2470) Centralize log4j configuration for tests

Thomas Weise created APEXMALHAR-2470: Summary: Centralize log4j configuration for tests Key: APEXMALHAR-2470 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2470 Project: Apache Apex Malhar

Re: open/close ports and active/inactive streams

> "It should behave as if the upstream operator does not emit anything on the port." But as per your earlier description the upstream operator "..for any reason decides that it will not emit tuples on the output port, it may close it..." . So this is not just the case where the upstream operator

Re: open/close ports and active/inactive streams

Correct, a statefull downstream operator can only be undeployed at a checkpoint window after it consumes all data emitted by upstream operator on the closed port. It will be necessary to distinguish between closed port and inactive stream. After port is closed, stream may still be active and

[jira] [Created] (APEXMALHAR-2471) Upgrade apex-core dependency to 3.5.0

Thomas Weise created APEXMALHAR-2471: Summary: Upgrade apex-core dependency to 3.5.0 Key: APEXMALHAR-2471 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2471 Project: Apache Apex Malhar

Re: open/close ports and active/inactive streams

Generally a good idea. Care should be taken around fault tolerance and idempotency. Close stream would need to stop accepting new data but still can't actually close all the streams and un-deploy operators till committed. Idempotency might require the close stream to take effect at the end of the

[jira] [Commented] (APEXMALHAR-2471) Upgrade apex-core dependency to 3.5.0

[ https://issues.apache.org/jira/browse/APEXMALHAR-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952329#comment-15952329 ] Pramod Immaneni commented on APEXMALHAR-2471: - +1 > Upgrade apex-core dependency to