[
https://issues.apache.org/jira/browse/SAMZA-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530981#comment-15530981
]
Jose Martinez commented on SAMZA-681:
-------------------------------------
I think the patch has a bug: the InMemoryTaskContext implementation is using a
Map as the store but in samza we're using an embeded RocksDB store which is a
KeyValueStore<?,?>.
The inMemoryTaskContext (line 50) has a private member store which is a Map:
private Map store;
But it should be:
private KeyValueStore<K, V> store;
and then we need to change the signature of:
public Map<K, V> getStore(String name) ;
to
public KeyValueStore <K, V> getStore(String name);
> Create a unit test harness to easily test samza tasks
> -----------------------------------------------------
>
> Key: SAMZA-681
> URL: https://issues.apache.org/jira/browse/SAMZA-681
> Project: Samza
> Issue Type: Test
> Components: test
> Affects Versions: 0.9.0
> Reporter: Luis De Pombo
> Attachments: SAMZA-381.patch
>
>
> We don't have a standardized test framework for unit testing samza tasks.
> Currently, in order to test the proper functionality of a task we have to
> bring up the system (kafka) and its dependencies (zk).
> Goals:
> - The harness should abstract several notions around the system and its
> partitions, without mocking them, and hold task context and state in memory.
> - The harness should let you inject several <key,value> pairs that would
> normally be passed in by the `SystemStream` provided in `tasks.input`.
> - The same harness should offer an interface to visualize all the
> corresponding <key,value> pairs collected in the message `Collector`, which
> are the output of the `process`ed or `window`ed input <key,value> pairs
> previously injected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
