IQSS / IQSS/dataverse

update-fields.sh for updating solr schema adds all possible fields

Open
#9,580 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Installer Type: Bug User Role: Sysadmin
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

What steps does it take to reproduce the issue?
Create a new metadatablock and add it to the dataverse asdescribed on the docs: https://guides.dataverse.org/en/latest/admin/metadatacustomization.html

After downloading the generated fields with http://localhost:8080/api/admin/index/solr/schema run the update-fields.sh script

calling curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"
fails, because seemingly all fields are duplicated

  • When does this issue occur?

calling curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"

  • Which page(s) does it occurs on?
    admin api

  • What happens?
    calling curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"
    throws an error with java stack pointing out that the very first (and probably all) field is duplicate

  • To whom does it occur (all users, curators, superusers)?

  • What did you expect to happen?
    status 0 response

Which version of Dataverse are you using?
The Dataverse Project v. 5.12.1 build 1122-cf90431

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with update-fields.sh and reproduce the workflow through the admin API endpoint http://localhost:8080/api/admin/index/solr/schema. Reload the collection with the documented curl command and inspect the Java error; done means the generated fields are not duplicated and the reload returns status 0.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, shell
Domain
backend, search
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.