[
https://issues.apache.org/jira/browse/SAMZA-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573297#comment-16573297
]
Peter Georgantas commented on SAMZA-1743:
-----------------------------------------
Thanks for the info on using the table join. I have spent some time searching
for documentation on that as well without much success.
I agree with the idea of adding the mapWithState, but I'm unsure of where the
StoreDescriptor should be defined. I like that window allows me to define the
store's attributes inline.
Perhaps with overload?
inputStream.map(Maps.statefulMap((store, message) -> store.get(message),
KVSerde.of(new StringSerde(), new StringSerde(), "name"));
 Meanwhile I'll try your suggestion of using the Table mechanism.
> Allow highlevel operators to have access to programmatically created state.
> ---------------------------------------------------------------------------
>
> Key: SAMZA-1743
> URL: https://issues.apache.org/jira/browse/SAMZA-1743
> Project: Samza
> Issue Type: Improvement
> Affects Versions: 0.14.0
> Reporter: Peter Georgantas
> Assignee: Prateek Maheshwari
> Priority: Minor
>
> The window and join highlevel operators must have state by definition. When
> using these operators, the api will programmatically create the config for
> that state. The api should allow more operators (filter, map, etc) access to
> the same programmatic state definition. Having this option would help close
> the gap between code and properties files.
> Relevant code:
> [StatefulOperatorSpec.java|https://github.com/apache/samza/blob/161d1c47a2c7322a7d3197d571a227cce0f1cbbf/samza-core/src/main/java/org/apache/samza/operators/spec/StatefulOperatorSpec.java#L28]
> [JobNode.java|https://github.com/apache/samza/blob/161d1c47a2c7322a7d3197d571a227cce0f1cbbf/samza-core/src/main/java/org/apache/samza/execution/JobNode.java#L166]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
