Skip to content
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

Add schema evolution hooks to Frame #413

Merged
merged 9 commits into from
Jun 27, 2023

Conversation

tmadlener
Copy link
Collaborator

@tmadlener tmadlener commented May 4, 2023

BEGINRELEASENOTES

  • Introduce podio::SchemaEvolution that can hold schema evolution functions and that offers an evolveBuffers method that does the schema evolution on these buffers before collections are created.
  • Add hooks in podio::Frame to call this when collections are read from the FrameData.

ENDRELEASENOTES

This introduces a podio::SchemaEvolution registry that holds schema evolution functions and that offers an evolveBuffers method that takes podio::CollectionReadBuffers, a schema version and the type of the collection that will be constructed from these buffers and evolves them to the current schema version (potentially by doing nothing at all). This will not yet introduce any machinery to actually also populate this registry, that will be another PR.

TODO:

@tmadlener tmadlener changed the title [WIP] Add schema evolution hooks to Frame Add schema evolution hooks to Frame Jun 27, 2023
Copy link
Collaborator

@hegner hegner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides a rename of SchemaEvolution into SchemaEvolutionRegistry I am fine with this. thanks!

* that the registration still happens on a single thread. After this
* initialization evolutions can be done from multiple threads.
*/
class SchemaEvolution {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure why you talk about SchemaEvolution and SchemaEvolutionRegistry interchangeably. Maybe one should just make a global (and stupid) rename?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the registry bits again. They were leftovers from when it was not yet entirely clear to me what the name should be.

@hegner hegner merged commit c4e11bc into AIDASoft:master Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants