[
https://issues.apache.org/jira/browse/SAMZA-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524205#comment-16524205
]
Peng Du commented on SAMZA-1763:
--------------------------------
Summary of the design:
* Extending ReadableTable and ReadWriteTable with async methods
* Use callbacks to be the async tokens between app and table framework
* Add async methods to Table functions to leverage native async support
* Wrap the callbacks from the task to provide common logging and metrics
* Extend CachingTable with the same set of async methods
* Add a queue to buffer pending requests and a thread to dispatch them for
non-blocking rate limiting
> Implement async versions of the table API
> ------------------------------------------
>
> Key: SAMZA-1763
> URL: https://issues.apache.org/jira/browse/SAMZA-1763
> Project: Samza
> Issue Type: Improvement
> Reporter: Peng Du
> Assignee: Peng Du
> 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)
