apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ananth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXMALHAR-2472) Implement Kudu Input Operator
Date Sat, 22 Apr 2017 10:35:04 GMT

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

Ananth updated APEXMALHAR-2472:
-------------------------------
    Issue Type: New Feature  (was: Bug)

> Implement Kudu Input Operator 
> ------------------------------
>
>                 Key: APEXMALHAR-2472
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2472
>             Project: Apache Apex Malhar
>          Issue Type: New Feature
>          Components: adapters database
>            Reporter: Ananth
>            Assignee: Ananth
>
> This operator would allow Kudu to be used as an Input store. This has multiple advantages
like : 
> - Ability to solve the dedup problem from entire data set perspective. The dedupe operators
we have today are primarily window based and this might not meet all of the use cases in real
world. 
> - Ability to selectively stream data based on a SQL expression. Since Kudu is a structural
store, we could effectively allow a SQL expression based "input" definition that would allow
for selective streaming for all downstream operators. This could potentially be an alternative
streaming store pattern as compared to Kafka as Kafka does not allow for selective streaming
of tuples. 



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

Mime
View raw message