-
Notifications
You must be signed in to change notification settings - Fork 108
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
Remove block open logic from DBS3Reader and WorkQueue #11123
Conversation
Jenkins results:
|
Jenkins results:
|
FYI @belforte Stefano, I removed another DBS3Reader method that wasn't mentioned in the initial GH issue. Please check out the first description of this PR with a summary to make sure it won't catch you by surprise ;) |
thanks @amaltaro . No problem for CRAB, none of those was used. |
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.
Thanks @amaltaro
Looking good to me. Please give us further info upon testing.
|
||
logging.warning("Open FileBlock located at PNN: %s to use is FileBlock: %s ", pnn, blockRef['Name']) | ||
return blockRef | ||
return DbsFileBlock( Name = blockName) |
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.
Please, add the new line the end of the file :)
more OpenForWriting removals fix DataBlockGenerator removed DBS3Reader listOpenFileBlocks method new line at the end of the module
update unit tests
Jenkins results:
|
Thanks for the review over the weekend, Stefano and Todor. |
Fixes #11120
Partial fix for #11048
Status
not-tested
Description
As described in the issue, this feature was needed back in the days of DBS2.
This PR removes DBS/WorkQueue logic related to:
IsOpen
blockIsOpen
has been removedlistOpenFileBlocks
has been removed (uselistFileBlocks
instead)getDBSFileBlock
has been removedOpenForNewData
to FalseaddNewFilesToOpenSubscriptions
has been removed, since we no longer add new files to open subscriptions (To be tested: what happens when new elements are pulled down?)Is it backward compatible (if not, which system it affects?)
NO (in the sense that it removes a feature)
Related PRs
PR #11119 will have to be rebased once this one goes through.
External dependencies / deployment changes
None