[
https://issues.apache.org/jira/browse/APEXMALHAR-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647571#comment-15647571
]
ASF GitHub Bot commented on APEXMALHAR-2278:
--------------------------------------------
GitHub user ananthc opened a pull request:
https://github.com/apache/apex-malhar/pull/486
APEXMALHAR-2278 Implement KuduNonTransactional Output Operator
@tweise / @PramodSSImmaneni : Could you please review or suggest the
right person who can complete this review for me?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ananthc/apex-malhar
APEXMALHAR-2278.KuduNonTransactionalOutputOperator
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-malhar/pull/486.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 #486
----
commit af6944f53c86d0fb355798b9c48d0156964648c9
Author: ananthc <[email protected]>
Date: 2016-11-08T13:28:28Z
APEXMALHAR-2278 Implement KuduNonTransactional Output Operator
----
> Implement Kudu Output Operator for non-transactional streams
> ------------------------------------------------------------
>
> Key: APEXMALHAR-2278
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2278
> Project: Apache Apex Malhar
> Issue Type: New Feature
> Components: adapters database
> Reporter: Ananth
> Assignee: Ananth
>
> Here are some benefits of integrating Kudu and Apex:
> Kudu is just declared 1.0 and has just been declared production ready.
> Kudu as a store might a good a fit for many architectures in the years to
> come because of its capabilities to provide mutability of data ( unlike HDFS
> ) and optimized storage formats for low latency scans.
> It seems to also withstand high-throughput write patterns which makes it
> a stable sink for Apex workflows which operate at very high volumes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
