-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic task payload (de)serialization using different serializers. #6
Comments
I think the good way to specialize these options would be passing string |
And in order to be able to deserialize task payloads we need either to save serialization method in database representation of |
Probably, we need to work with task meta-information. For example, we can encode serialization/deserialization information in task-id. Or we can use (probably fixed) part of payload for that. Anyway, it looks like serialization/deserialization should live inside a |
I think in the most popular case the same payload (de)serialization method would be used for all the tasks in any given queue. If we decide to store this exact piece of metadata in the |
Right now we only support
raw
payloads. Would be nice to have options forpickle
,safe_pickle
,json
,yaml
and so on.The text was updated successfully, but these errors were encountered: