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

Possible wrong data type definition for the dynamicField "*_t" in solr7 #277

Open
shahmanash opened this issue May 20, 2019 · 0 comments
Open

Comments

@shahmanash
Copy link
Contributor

Possibly , wrong data type definition for the dynamicField "*_t" causes the following error leading to failed loading of biocache core in solr7

https://github.com/AtlasOfLivingAustralia/ala-install/blob/master/ansible/roles/solrcloud_config/templates/biocache_schema_docvalues.xml#L877

<dynamicField name="*_t" type="text" indexed="true" stored="true" docValues="true"/>

null:org.apache.solr.core.SolrCoreInitializationException: SolrCore 'biocache' is not available due to init failure: 
Could not load conf for core biocache: Can't load schema /opt/solr/server/solr/mycores/biocache/conf/schema.xml: 
Field type text{class=org.apache.solr.schema.TextField,&#8203;analyzer=org.apache.solr.analysis.TokenizerChain,&#8203;args={positionIncrementGap=100,&#8203; class=solr.TextField}} does not support doc values

When the field type is changed to string , the loading of core does not show previous error

<dynamicField name="*_t" type="string" indexed="true" stored="true" docValues="true"/>

Should the field be changed to string or should it remain as text and the problem addressed in a different way ?

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

No branches or pull requests

1 participant