Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- links to