Revisit the exclusiveness of the application relationship between Segment and Application
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1
- Forks
- 2
- Avg merge
- 7h 30m
- Merged PRs (30d)
- 3
Description
The requirement of exclusivity of the relationship between Segment and application is probably a bit too strict. While it is true that this is a requirement at run time (the time of generate_modules call), when creating the schema, this is not strictly necessary and it enforces a certain rigidity and duplication in the configuration database.
We should investigate:
- impact of removing the exclusivity constraint
- Moving the check in a verification step and at run time
Example of issues caused by this have been reported also in the case of daqsystemtest: see 19 August 2025 SWIT meeting, slides here
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Segment–Application relationship through schema creation and the generate_modules entry point, using the daqsystemtest duplication example and linked meeting slides as context. Document the impact of removing exclusivity and define how verification and runtime checks would establish completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100