Upgrade 6.5 to 6.6 fails and does not show any data within dataverse: cannot change field "datasetValid" from doc values type=NONE to inconsistent doc values type=SORTED

[inDane]

The Update to 6.6 fails for us. I suspect solr indexing. We are using custom metadatablocks.
The domain1/log/server.log shows a mix of errors similar to this:

[#|2026-06-03T17:58:50.637+0200|WARNING|Payara 6.2025.2|edu.harvard.iq.dataverse.ControlledVocabularyValue|_ThreadID=236;_ThreadName=__ejb-thread-pool10;_TimeMillis=1780502330637;_LevelValue=900;|
  Error finding controlledvocabulary.ResistSeq_Technology.illumina in defaultLang : Can't find bundle for base name propertyFiles/RESIST_Sequencing, locale en|#]

[#|2026-06-03T17:58:50.643+0200|SEVERE|Payara 6.2025.2|org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient|_ThreadID=337;_ThreadName=concurrentUpdateScheduler-2-thread-4-processing-null;_TimeMillis=1780502330643;_LevelValue=1000;|
  error
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error from server at http://localhost:8983/solr/collection1: null



request: http://localhost:8983/solr/collection1
Remote error message: Exception writing document id dataset_3352_draft to the index; possible analysis error: cannot change field "datasetValid" from doc values type=NONE to inconsistent doc values type=SORTED
	at org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient$Runner.sendUpdateStream(ConcurrentUpdateHttp2SolrClient.java:291)
	at org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient$Runner.run(ConcurrentUpdateHttp2SolrClient.java:192)
	at org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:380)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
|#]

I can upload the full log if needed.

What steps does it take to reproduce the issue?
Upgrade from 6.5 to 6.6

• When does this issue occur?
  While indexing with curl http://localhost:8080/api/admin/index

• Which page(s) does it occurs on?
  There are no dataverses/datasets showing on the website

• What happens?
  There are no dataverses/datasets showing on the website

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

• What did you expect to happen?
  Dataverse should show its dataverses and datasets after the upgrade

Which version of Dataverse are you using?
6.5 -> 6.6
6.5 works and as soon as the upgrade is done, no data is showing.

Solr-9.10.1

Any related open or closed issues to this bug report?

Screenshots:

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

I am not a java/payara developer, sorry.

[pdurbin]

@inDane hi! The first thing that jumps out at me in https://github.com/IQSS/dataverse/releases/tag/v6.6 is that Solr 6.8 is recommended for Dataverse 6.6. Can you try that version rather than Solr 9.10.1?

[qqmyers]

and you did step 10a.?

[inDane]

and you did step 10a.?

yes, and i've verified that schema.xml is different after updating.

[inDane]

@inDane hi! The first thing that jumps out at me in https://github.com/IQSS/dataverse/releases/tag/v6.6 is that Solr 6.8 is recommended for Dataverse 6.6. Can you try that version rather than Solr 9.10.1?

Ok, I will do a test with solr 9.8.

I wanted to use 9.10.1 because of CVE-2026-22022. I dont know if this would apply to dataverses usage of solr, but I wanted to be on the safer side.

[inDane]

[#|2026-06-04T15:12:56.475+0200|SEVERE|Payara 6.2025.2|org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient|_ThreadID=210;_ThreadName=concurrentUpdateScheduler-2-thread-1-processing-null;_TimeMillis=1780578776475;_LevelValue=1000;|
  error
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error from server at http://localhost:8983/solr/collection1: null



request: http://localhost:8983/solr/collection1
Remote error message: Exception writing document id dataset_2369_draft to the index; possible analysis error: cannot change field "dsDescriptionDate" from index options=DOCS_AND_FREQS_AND_POSITIONS to inconsistent index options=DOCS
	at org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient$Runner.sendUpdateStream(ConcurrentUpdateHttp2SolrClient.java:291)
	at org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient$Runner.run(ConcurrentUpdateHttp2SolrClient.java:192)
	at org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:380)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
|#]

log is full of those errors. So the outcome is unfortunately the same with solr-9.8.1.

[qqmyers]

Did you follow https://guides.dataverse.org/en/latest/installation/prerequisites.html#solr ? Specifically the steps to set up collection1?

[inDane]

yes, sure!
Just to add more info: On working dv-6.5 with solr-9.10.1 i get warnings, but the dv is working jsut fine
curl http://localhost:8080/api/admin/index/clear
curl http://localhost:8080/api/admin/index

the logs shows Warnings, but DV is working:

[#|2026-06-04T16:44:28.174+0200|WARNING|Payara 6.2024.6|edu.harvard.iq.dataverse.ControlledVocabularyValue|_ThreadID=253;_ThreadName=__ejb-thread-pool2;_TimeMillis=1780584268174;_LevelValue=900;|
  Error finding controlledvocabulary.resistMetaDataType.document in defaultLang : Can't find bundle for base name propertyFiles/RESIST_MetaData, locale en|#]

[#|2026-06-04T16:44:28.174+0200|WARNING|Payara 6.2024.6|edu.harvard.iq.dataverse.ControlledVocabularyValue|_ThreadID=253;_ThreadName=__ejb-thread-pool2;_TimeMillis=1780584268174;_LevelValue=900;|
  Error finding controlledvocabulary.resistMetaDataType.document in defaultLang : Can't find bundle for base name propertyFiles/RESIST_MetaData, locale en|#]

[qqmyers]

Not sure what to suggest.

AI suggest that the possible analysis error: cannot change field "dsDescriptionDate" from index options=DOCS_AND_FREQS_AND_POSITIONS to inconsistent index options=DOCS indicates that there may have been old docs in solr. That said /api/admin/index/clear should have fixed that.

The Error finding controlledvocabulary.resistMetaDataType.document in defaultLang warnings should be harmless - they are because the system can't find language specific property files for your custom blocks and the default is to just use the text in the tsv block definition instead.

[pdurbin]

DOCS_AND_FREQS_AND_POSITIONS

When we saw that error in the past we recommended clearing the Solr index and reloading the core:

• prevent DOCS_AND_FREQS_AND_POSITIONS Solr error #11140