Class Distributions for data feature
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Currently we store class distributions for data features. I found a bug in the way this was stored: there was no bound on the string field in the xsd, potentially cutting of the end of the json representation.
I added a bound of 16384 (to ensure that in its utf-8 format it still fits within the mysql text field) but now not all descriptions fit in it. This should be solved, somehow.
Contributor guide
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 the XSD string bound, JSON representation, and MySQL TEXT field as the relevant storage boundary, but names no repository files or tests. Trace the class-distribution data path from its XSD definition and inspect how PHP persists it in MySQL. Done means full JSON representations and descriptions are stored without truncation, with defined handling for values beyond the field limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, mysql, php
- Domain
- data, databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100