[jira] [Assigned] (APEXMALHAR-2476) Unable to override tupleSeparator property of GenericFileOutputOperator using configurations

[Yogi Devendra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXMALHAR-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yogi Devendra reassigned APEXMALHAR-2476:
-

Assignee: Yogi Devendra

> Unable to override tupleSeparator property of GenericFileOutputOperator using 
> configurations  
> --
>
> Key: APEXMALHAR-2476
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2476
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Reporter: Yogi Devendra
>Assignee: Yogi Devendra
>Priority: Minor
>
> Default value for the tupleSeparator is derived from line.seperator from 
> System properties. 
> But, if user supplies different value to override the default. User supplied 
> value is not honored by the operator for this property.
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (APEXMALHAR-2476) Unable to override tupleSeparator property of GenericFileOutputOperator using configurations

[Yogi Devendra (JIRA)]

Yogi Devendra created APEXMALHAR-2476:
-

 Summary: Unable to override tupleSeparator property of 
GenericFileOutputOperator using configurations  
 Key: APEXMALHAR-2476
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2476
 Project: Apache Apex Malhar
  Issue Type: Bug
Reporter: Yogi Devendra
Priority: Minor


Default value for the tupleSeparator is derived from line.seperator from System 
properties. 
But, if user supplies different value to override the default. User supplied 
value is not honored by the operator for this property.

 




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957609#comment-15957609
 ] 

ASF GitHub Bot commented on APEXCORE-469:
-

Github user asfgit closed the pull request at:

https://github.com/apache/apex-site/pull/72


> Website: Rewrite fetch releases script
> --
>
> Key: APEXCORE-469
> URL: https://issues.apache.org/jira/browse/APEXCORE-469
> Project: Apache Apex Core
>  Issue Type: Task
>  Components: Website
>Reporter: Thomas Weise
>Assignee: Dean Lockgaard
>
> The logic of the fetch releases task in gulpfile.js needs to be changed for 
> new dist folder and layout / naming convention.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] apex-site pull request #72: APEXCORE-469 fix gulpfile fetch-releases task to...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/apex-site/pull/72


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (APEXCORE-690) Embedded app launcher does not apply HEARTBEAT_MONITORING setting

[Pramod Immaneni (JIRA)]

 [ 
https://issues.apache.org/jira/browse/APEXCORE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pramod Immaneni resolved APEXCORE-690.
--
Resolution: Fixed

> Embedded app launcher does not apply HEARTBEAT_MONITORING setting
> -
>
> Key: APEXCORE-690
> URL: https://issues.apache.org/jira/browse/APEXCORE-690
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Thomas Weise
>Assignee: Thomas Weise
>Priority: Minor
> Fix For: 3.6.0
>
>
> The setting is only applied when true (which is the default). The purpose of 
> the setting is to be able to turn it off though, such as for debugging the 
> DAG in the IDE.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (APEXCORE-690) Embedded app launcher does not apply HEARTBEAT_MONITORING setting

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957066#comment-15957066
 ] 

ASF GitHub Bot commented on APEXCORE-690:
-

Github user asfgit closed the pull request at:

https://github.com/apache/apex-core/pull/504


> Embedded app launcher does not apply HEARTBEAT_MONITORING setting
> -
>
> Key: APEXCORE-690
> URL: https://issues.apache.org/jira/browse/APEXCORE-690
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Thomas Weise
>Assignee: Thomas Weise
>Priority: Minor
> Fix For: 3.6.0
>
>
> The setting is only applied when true (which is the default). The purpose of 
> the setting is to be able to turn it off though, such as for debugging the 
> DAG in the IDE.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] apex-core pull request #504: APEXCORE-690 apply HEARTBEAT_MONITORING setting...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/apex-core/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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] apex-core pull request #504: APEXCORE-690 apply HEARTBEAT_MONITORING setting...

[tweise]

GitHub user tweise opened a pull request:

https://github.com/apache/apex-core/pull/504

APEXCORE-690 apply HEARTBEAT_MONITORING setting in embedded app launcher



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tweise/apex-core APEXCORE-690

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/504.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #504


commit 869e166e1c733fc8bfe1acf189f5d9ff7f654fdc
Author: Thomas Weise 
Date:   2017-04-05T15:17:26Z

APEXCORE-690 apply HEARTBEAT_MONITORING setting in embedded app launcher.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (APEXCORE-690) Embedded app launcher does not apply HEARTBEAT_MONITORING setting

[Thomas Weise (JIRA)]

Thomas Weise created APEXCORE-690:
-

 Summary: Embedded app launcher does not apply HEARTBEAT_MONITORING 
setting
 Key: APEXCORE-690
 URL: https://issues.apache.org/jira/browse/APEXCORE-690
 Project: Apache Apex Core
  Issue Type: Bug
Affects Versions: 3.5.0
Reporter: Thomas Weise
Assignee: Thomas Weise
Priority: Minor
 Fix For: 3.6.0


The setting is only applied when true (which is the default). The purpose of 
the setting is to be able to turn it off though, such as for debugging the DAG 
in the IDE.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[ANNOUNCE] Apache Apex Malhar 3.7.0 released

[Thomas Weise]

Dear Community,

The Apache Apex community is pleased to announce release 3.7.0 of the Apex
Malhar library.

Apache Apex is an enterprise grade big data-in-motion platform that unifies
stream and batch processing. Apex was built for scalability and low-latency
processing, high availability and operability. The Apex engine is
supplemented by Malhar, the library of pre-built operators, including
connectors that integrate with many existing technologies as sources and
destinations, like message buses, databases, files or social media feeds.

This release adds a number of new operators, including S3 line reader
(parallel block based), S3 output for tuples and file copy, fixed length
parser, Redshift output, and more accumulations for the windowed operator.
The release also adds several new user documentation
 sections.

See full release notes

for all changes in this release.

Apex provides features that similar platforms currently don’t offer, such
as fine grained, incremental recovery to only reset the portion of a
topology that is affected by a failure, support for elastic scaling based
on the ability to acquire (and release) resources as needed as well as the
ability to alter topology and operator properties on running applications.

Apex early on brought the combination of high throughput, low latency and
fault tolerance with strong processing guarantees to the stream data
processing space and gained maturity through important production use cases
at several organizations. See the powered by page and resources on the
project web site for more information:

http://apex.apache.org/powered-by-apex.html
http://apex.apache.org/docs.html

An easy way to get started with Apex is to pick one of the examples as
starting point. They cover many common and recurring tasks, such as data
consumption from different sources, output to various sinks, partitioning
and fault tolerance:

https://github.com/apache/apex-malhar/tree/master/examples/

Apex Malhar and Core (the engine) are separate repositories and releases.
We expect more frequent releases of Malhar to roll out new connectors and
other operators based on a stable engine API. This release 3.7.0 works on
existing Apex Core 3.4.0. Users only need to upgrade the library Maven
dependency in their application project.

The source release can be found at:

http://apex.apache.org/downloads.html

We welcome your help and feedback. For more information on the project and
how to get involved, visit our website at:

http://apex.apache.org/

Regards,
The Apache Apex community

[jira] [Commented] (APEXMALHAR-2431) Create Kinesis Input operator which emits byte array as tuple

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956683#comment-15956683
 ] 

ASF GitHub Bot commented on APEXMALHAR-2431:


GitHub user deepak-narkhede opened a pull request:

https://github.com/apache/apex-malhar/pull/601

APEXMALHAR-2431 Create Kinesis Input operator which emits byte array



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/deepak-narkhede/apex-malhar APEXMALHAR-2431

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/601.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #601


commit fd4f61f2aa5c872734427b48b04350a31cee222e
Author: deepak-narkhede 
Date:   2017-04-05T08:21:58Z

APEXMALHAR-2431 Create Kinesis Input operator which emits byte array as a 
tuple




> Create Kinesis Input operator which emits byte array as tuple
> -
>
> Key: APEXMALHAR-2431
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2431
> Project: Apache Apex Malhar
>  Issue Type: Improvement
>Reporter: Deepak Narkhede
>Assignee: Deepak Narkhede
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] apex-malhar pull request #601: APEXMALHAR-2431 Create Kinesis Input operator...

[deepak-narkhede]

GitHub user deepak-narkhede opened a pull request:

https://github.com/apache/apex-malhar/pull/601

APEXMALHAR-2431 Create Kinesis Input operator which emits byte array



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/deepak-narkhede/apex-malhar APEXMALHAR-2431

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/601.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #601


commit fd4f61f2aa5c872734427b48b04350a31cee222e
Author: deepak-narkhede 
Date:   2017-04-05T08:21:58Z

APEXMALHAR-2431 Create Kinesis Input operator which emits byte array as a 
tuple




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (APEXMALHAR-2459) KafkaInputoperator using 0.10.* Kafka consumer API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956619#comment-15956619
 ] 

ASF GitHub Bot commented on APEXMALHAR-2459:


GitHub user chaithu14 opened a pull request:

https://github.com/apache/apex-malhar/pull/600

APEXMALHAR-2459 1)Refactor the existing Kafka Input Operator. 2)Added the 
support of KafkaInputOperator using 0.10 consumer API



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chaithu14/incubator-apex-malhar 
APEXMALHAR-2459-Kafkainput

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/600.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #600






> KafkaInputoperator using 0.10.* Kafka consumer API
> --
>
> Key: APEXMALHAR-2459
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2459
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: Chaitanya
>Assignee: Chaitanya
>
> Changes in 0.10.0.0 version of Kafka
> -
>Message format in 0.10.0 has changed. Messages now include a time-stamp 
> field and compressed messages include relative offsets. 
> 
>Please refer the below link about the changes in Kafka 0.10.0.0 version:
> https://kafka.apache.org/documentation/#upgrade_10_breaking.
> Design
> -
>   I'm proposing the below design for new Kafka connectors by refactoring the 
> existing Kafka connector(0.9.* version)
> 1) Split up the malhar-kafka to malhar-kafka-common, malhar-kafka_0.9, 
> malhar-kafka_0.10. Directory structure would be as follows:
>   malhar-kafka
>   |--malhar-kafka-common
>   |--malhar-kafka_0.9
>   |--malhar-kafka_0.10
> If possible, will add the connectors for 0.8.x version.
> 2) Convert the KafkaConsumerWrapper to AbstractKafkaConsumerWrapper by adding 
> the abstract methods over the consumer API's.
> 3) "malhar-kafka-common" package consists of the abstract classes and by 
> default it builds over the 0.9.x version of Kafka.
> 4) "malhar-kafka-0.*" consists of concrete classes and its corresponding 
> KafkaConsumerWrapper.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] apex-malhar pull request #600: APEXMALHAR-2459 1)Refactor the existing Kafka...

[chaithu14]

GitHub user chaithu14 opened a pull request:

https://github.com/apache/apex-malhar/pull/600

APEXMALHAR-2459 1)Refactor the existing Kafka Input Operator. 2)Added the 
support of KafkaInputOperator using 0.10 consumer API



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/chaithu14/incubator-apex-malhar 
APEXMALHAR-2459-Kafkainput

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/600.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #600






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (APEXMALHAR-2458) Move kafka related examples from datatorrent examples to apex-malhar examples

[Velineni Lakshmi Prasanna (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956350#comment-15956350
 ] 

Velineni Lakshmi Prasanna commented on APEXMALHAR-2458:
---

The hdfs2kafka example is already written against 0.8 
https://github.com/DataTorrent/examples/blob/master/tutorials/hdfs2kafka/pom.xml
In my PR earlier I had updated the example to 0.9, but now I am rethinking that 
strategy and wondering if it should be left against 0.8 since it was originally 
written that way.

> Move kafka related examples from datatorrent examples to apex-malhar examples
> -
>
> Key: APEXMALHAR-2458
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2458
> Project: Apache Apex Malhar
>  Issue Type: Sub-task
>Reporter: Velineni Lakshmi Prasanna
>Assignee: Velineni Lakshmi Prasanna
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)