Thanks, I was able to get past all that but now have a new issue. I am getting the following exception when I do a search that I know has results. The Lucene code inside of Emerse is unable to find a Document by it’s ID, but I can see that the Document does exists in SOLR as expected when I query for it via the SOLR UI. Note that the ID is a big string originally sourced from Mongodb. Is this just a lag time thing?
Caused by: edu.umich.med.emerse.domain.DocumentNotFoundException: 5e45e1bb5808eee774af32ba
at edu.umich.med.emerse.service.search.LuceneSearcher.getDocumentFragments(LuceneSearcher.java:252) ~[emerse-service-4.10.8.jar:?]