Analysis CCDB: add ability to have a uniformity column in a CCDB table - #15742
Open
ktf wants to merge 1 commit into
Open
Analysis CCDB: add ability to have a uniformity column in a CCDB table#15742ktf wants to merge 1 commit into
ktf wants to merge 1 commit into
Conversation
Member
Author
|
@aalkin second PR which we discussed today. |
Very often we know that CCDB objects do not change within the same run or the same dataframe (or whatever interval you can think about). For this reason it does not make sense to query for their updates for each timestamp. By specifying a "uniformity" column (e.g. RunNumber) you can short-circuit how often a given CCDB object needs to be fetched. This will eventually evolve in the ability to only have rows for unique CCDB objects fetched.
ktf
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Very often we know that CCDB objects do not change within the same run
or the same dataframe (or whatever interval you can think about). For this
reason it does not make sense to query for their updates for each timestamp.
By specifying a "uniformity" column (e.g. RunNumber) you can short-circuit how
often a given CCDB object needs to be fetched.
This will eventually evolve in the ability to only have rows for unique CCDB objects fetched.