Avoid storing duplicate information in the database
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Information may be stored in multiple times in the database, this came to light in https://github.com/openml/openml-python/issues/1289#issuecomment-1792250138. We should avoid storing duplicate information in the database, because it can easily lead to multiple truths. This issue can be used to keep track of all duplicate data, with the intention to refactor our database in the future to avoid these pitfalls:
- Feature attributes (e.g.,
ignore_attributes) information is duplicated between theexpdb.datasettable and theexpdb.data_featurestable.
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
The issue identifies duplicate feature-attribute information in the expdb.dataset and expdb.data_features tables. Start by locating the definitions and uses of those tables, then inventory the other duplicate data named in the issue. Done requires an agreed refactoring plan for avoiding multiple sources of truth, not just another duplicate-data entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100