You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Teraslice jobs you can set the "stateful": true, property and the workers will be slightly different (see docs). I've realized that this is actually a property of the asset in use, and should probably be set automatically simply by using a "stateful" asset.
In general this is the stateful processor being used:
This probably needs some internal API added to Teraslice that the processor will use to indicate that it is stateful. Perhaps a property on the processor that Teraslice uses.
The text was updated successfully, but these errors were encountered:
We have this notion of "Stateful Workers" as described here:
https://terascope.github.io/teraslice/docs/configuration/clustering-k8s/#stateful-workers
In Teraslice jobs you can set the
"stateful": true,
property and the workers will be slightly different (see docs). I've realized that this is actually a property of the asset in use, and should probably be set automatically simply by using a "stateful" asset.In general this is the stateful processor being used:
https://github.com/terascope/elasticsearch-assets/tree/master/asset/src/elasticsearch_state_storage
This probably needs some internal API added to Teraslice that the processor will use to indicate that it is stateful. Perhaps a property on the processor that Teraslice uses.
The text was updated successfully, but these errors were encountered: