Added timestamp filtering the the AzureTableLogEntity #6638
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… to prevent memory issues
Contributor
|
Thanks for the PR, @Yinzy00 🙌 We will review it as soon as possible 💪 |
Contributor
|
Apologies for the delays on this one @Yinzy00 ! It's been reviewed now, and I'll make sure it's merged. Thanks again for adding the PR 🙌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I added timestamp filtering the the AzureTableLogEntity to prevent memory issues.
I encountered a lot of memory issues when using the original version from the documentation. I think I relied on it a bit too blindly! I wanted to share my experience to help prevent others from running into the same problems 😄
Type of suggestion
Product & version (if relevant)
10, 13, 14, 15