-
Notifications
You must be signed in to change notification settings - Fork 406
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
Docs: Create your own batch processor documentation inconsistency #2688
Comments
great catch @erikayao93 - we had a major refactor recently and the old name wasn't updated in this section of the docs. I'll double check the correct one and update the docs today. UPDATE: Correct one: THANK YOU! |
One more thing to note here -- the |
This is now released under 2.20.0 version! |
Hello @erikayao93! Thank you for pointing that out. Indeed, the Reopening the issue. |
I'm working on it and plan to create a PR tomorrow. |
|
This is now released under 2.36.0 version! |
What were you searching in the docs?
While investigating the capabilities of the batch processor in Python for a similar implementation in TypeScript, I found an inconsistency in the description compared to the code example.
The description states that developers should inherit the
BasePartialProcessor
class, which would require them to implement the abstract methods ofprepare
,clean
, andprocess_record
(orasync_process_record
).However, the code example creates a class that inherits the
BasePartialBatchProcessor
class.Is this related to an existing documentation section?
https://docs.powertools.aws.dev/lambda/python/2.19.0/utilities/batch/#create-your-own-partial-processor
How can we improve?
There should be clarity on which class developers are meant to inherit from.
If developers should inherit from
BasePartialProcessor
, the code example should be updated so that the code is usable. This may require other backend updates, as several pieces of functionality in the code example are reliant on capabilities of theBasePartialBatchProcessor
class.Got a suggestion in mind?
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: