[
https://issues.apache.org/jira/browse/SAMZA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622466#comment-16622466
]
ASF GitHub Bot commented on SAMZA-1854:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/645
> Caching table descriptor should not take run-time objects
> ---------------------------------------------------------
>
> Key: SAMZA-1854
> URL: https://issues.apache.org/jira/browse/SAMZA-1854
> Project: Samza
> Issue Type: Bug
> Reporter: Jagadish
> Assignee: Wei Song
> Priority: Major
> Fix For: 1.0
>
>
> Currently, users can use composition to construct composite tables using the
> CachingTableDescriptor. An example use-case is to have a RocksDb table as a
> cache in front of a remote database table. Currently users have to provide a
> concrete "table" instance to compose/instantiate a "CachingTableDescriptor".
> This is undesirable, since the table is an object that contains runtime state
> while a descriptor is merely a logical specification. To ensure a cleaner
> separation, we should ensure that creating a "CachingTableDescriptor" only
> takes a "tableDescriptor" instance instead of an actual table instance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
