[
https://issues.apache.org/jira/browse/APEXMALHAR-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ananth updated APEXMALHAR-2278:
-------------------------------
Summary: Implement Kudu Output Operator for non-transactional streams
(was: Implement Kudu Operator for non-transactional streams)
> 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)
