-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Export events continuously rather than loading all events in memory first #11623
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ⚡ Left two questions about some code that was removed.
if not events: | ||
raise NoEventsInTimeRangeError( | ||
"Could not find any events within requested time range. Exiting." | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we retain raising this exception if published_events == 0
in publish_events()
after going through generator results?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is helpful tbh. There is output on how many events got produced and that will just be 0 in this case. but happy to readd it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense! I asked in case this exception is handled maybe in some custom way either in the codebase already or in a customer's project, that could have required further amendments.
🚀 A preview of the docs have been deployed at the following URL: https://11623--rasahq-docs-rasa-v2.netlify.app/docs/rasa |
Proposed changes:
Fixes https://rasahq.atlassian.net/browse/ATO-441