Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relocate custom defined fields and create in Solr before schematizing #346

Open
ghost opened this issue Aug 8, 2023 · 2 comments
Open

Comments

@ghost
Copy link

ghost commented Aug 8, 2023

The custom defined fields should be moved out of the managed_schema into a persistent entity.

It is not recommended to modify the managed_schema directly.

https://solr.apache.org/guide/solr/latest/indexing-guide/schema-api.html

@ghost ghost assigned ghost and unassigned ghost Aug 9, 2023
@ghost ghost changed the title Add index field type creation Relocate custom defined fields and create in Solr before schematizing Aug 10, 2023
@wwelling
Copy link

Here are explicitly defined field type and dynamic field type.

https://github.com/TAMULib/scholars-discovery/blob/tamu-main/solr/configsets/scholars-discovery/conf/managed-schema.xml#L206

The scholars-discovery Solr client can create these before schematize (poorly named process of creating the fields ad copy fields). We should persist them and a database may be preferred over additional configuration. This requires JPA entity, CRUD endpoints, and additional administrative tab in scholars-angular. I think provisioning is a reasonable identifier for this state and can refactor schematize while doing so. These field types have to be defined before the addition of fields and copy fields.

@wwelling
Copy link

Blocked by #367

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant