-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Combine GatherNoCompactionMarkFilter
and GatherNoDownsampleMark
to prevent code duplication
#5962
Comments
Can you please assign me this, I'd like to work on it. Thanks!! |
hey @RohitKochhar can you please brief me about the syntax and what needs to be done here? |
Hey @nikzayn, sorry that it took so long for me to see your comment here. Basically, you'll see that the implementation for the two filters (one for |
Hey @RohitKochhar, we have to reuse the filter function ? |
Which specific filter function are you referring to? |
function named |
@jatinagwal I don't think there is a strict requirement to use the same function here. The goal is to keep the core filter logic in one place and you can extend it or get it working for different markers. |
Sorry, for late response. I was stuck in the execution. |
Is your proposal related to a problem?
With the addition of the
no-downsample-mark.json
block marker, some logic was retooled from the process to mark a block for no compaction. From this, some duplication has been introduced that should be fixed for clarity and better conformity.Describe the solution you'd like
I would like to open a PR to change the implemented logic for marking a block
no-downsample
to minimize code duplication.Describe alternatives you've considered
N/A
Additional context
To keep the scopes of the PRs focused, I think it is best that the first PR implementing the
no-downsample
logic (#5945) is accepted and merged into master before I open a new PR for this.cc: @fpetkovski
The text was updated successfully, but these errors were encountered: