`parquet_url` incorrectly provided for non-arff formats
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
As you can see here, anything that is not 'Sparse_ARFF' gets a parquet_url. This is incorrect, see e.g., www.openml.org/d/1243 which has Rimage data format (not supported).
The check should probably be changed to == "ARFF" instead based on the list of stored formats (the test server also sports additional formats, including lower-case 'sparse_arff'):
Went ahead and labeled this wontfix since API V2 is on the way and it doesn't really impact people (I imagine all datasets that are not ARFF never got out of processing anyway). It's a minor fix though so be my guest.
We might also consider deactivating any of the non-arff datasets (as part of the dataset clean up).
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
Start at openml_OS/models/api/v1/Api_data.php around line 766, where the issue identifies the format check that supplies parquet_url. Compare that check with the stored-format examples in the issue, including ARFF, Sparse_ARFF, and Rimage, then verify that parquet_url is only produced for the intended supported format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100