You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Bharath Kumarasubramanian (JIRA)" <ji...@apache.org> on 2019/01/07 20:29:00 UTC

[jira] [Assigned] (SAMZA-2055) Design and Implement async API for high level

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

Bharath Kumarasubramanian reassigned SAMZA-2055:
------------------------------------------------

    Assignee: Bharath Kumarasubramanian  (was: Peng Du)

> Design and Implement async API for high level
> ---------------------------------------------
>
>                 Key: SAMZA-2055
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2055
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Bharath Kumarasubramanian
>            Assignee: Bharath Kumarasubramanian
>            Priority: Major
>
> In Samza, Table API provides a consistent and simple way to perform IO with non-stream data sources, eg. key-value stores. It can be used in high-level API in the form of stream-table join and sendTo operators. Low-level API integration is also being worked on. 
> The current set of Table APIs only consists of synchronous versions in that all calls are blocking. Unlike local tables, there is a strong need to have async for remote tables to deliver higher throughput which can otherwise be hindered with full sync executions. 
> Given there is currently no async support in Samza high-level API, the design in this document is mainly targeted for low-level API. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)