You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/27 14:57:00 UTC

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

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

ASF GitHub Bot commented on APEXMALHAR-2472:
--------------------------------------------

tweise closed pull request #667: APEXMALHAR-2472 Kudu Input Operator implementation
URL: https://github.com/apache/apex-malhar/pull/667
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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.4.14#64029)