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

Separate persistent framework metadata types from their in-memory types #1251

Open
makortel opened this issue Feb 18, 2025 · 0 comments
Open
Labels
Maintenance Objective Main unit in planning, consists of one or more Tasks and/or Aspects

Comments

@makortel
Copy link
Contributor

makortel commented Feb 18, 2025

Also make reduced ProcessConfiguration and ProcessHistory their own types

For example

  • use present edm::ProcessConfiguration as the persistent type for TTree
  • create a separate type for persistent type for RNTuple
  • create a separate type for the transient in-memory use
  • possibly utilize namespace versioning
@makortel makortel changed the title Consider making reduced ProcessConfiguration its own type (maybe descope from this activity) Overhaul ProcessConfiguration and ProcessHistory Feb 18, 2025
@makortel makortel added Objective Main unit in planning, consists of one or more Tasks and/or Aspects Maintenance labels Feb 18, 2025
@makortel makortel changed the title Overhaul ProcessConfiguration and ProcessHistory Separate persistent framework metadata types from their in-memory types Feb 18, 2025
@makortel makortel moved this from 🆕 New to 📋 Backlog in Framework objectives Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Objective Main unit in planning, consists of one or more Tasks and/or Aspects
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant