-
Notifications
You must be signed in to change notification settings - Fork 123
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
MRQ fails with pymongo WriteError if job result conains dots in dictionary keys #132
Comments
Hi @DataGreed! We indeed store results as-is by default, to make them searchable for instance. If you don't want this behaviour it should be easy to write a subclass to Another easier way would also be to subclass If you have any suggestion on how to make it easier for users, we'd be happy to discuss them! I understand it may be a common issue for others. Cheers! |
Any thoughts @DataGreed ? |
Add this in common issues / FAQ ? #195 |
We've recently tried to switch from celery to MRQ and ran into a problem. One of our tasks was returning some debug queryset data in a dictionary with keys that contained dots in them (e.g. "result.debug.qs.parameters.some").
The stacktrace was as follows:
I think that storing task result "as is" may not be always the right behavior, I suppose there should be some setting that lets you store task results as their string representation to avoid non-obvios errors like this one :)
The text was updated successfully, but these errors were encountered: