Hostname based queue assignment variants that optionally limit queue name length #598
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.
Adds 2 new queue assignment policies that extend the existing
HostnameQueueAssignmentPolicy
andSurtAuthorityQueueAssignmentPolicy
by adding support for limiting the number of domain segments used in constructing the queue name. The limit can be set on a per-sheet bases.The SURT variant has been in use in our crawls for many years with no issue. Among other uses, it has proven very important for crawling sites with a large number of dynamically generated subdomains (e.g. username.blogsite.com) where we might otherwise hammer the site excessively.
An argument could be made for adding the functionality into the existing policies, I've done it this way mostly because we've had this in our Heritrix "extras" lib where it was simpler to subclass.