aaron-collier
commented
5 years ago I think it's likely that we've drifted from our solr config: https://github.com/sul-dlss/dlme/blob/master/solr/config/solrconfig.xml
Closed aaron-collier closed 5 years ago
aaron-collier
commented
5 years ago I think it's likely that we've drifted from our solr config: https://github.com/sul-dlss/dlme/blob/master/solr/config/solrconfig.xml
ndushay
commented
5 years ago more likely the Solr schema is the issue, but same general gist, yeah.
Not sure if this is useful: http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201606.mbox/%3Ccfe3d868-1911-7c12-8d6f-73d7bd60c638@elyograg.org%3E
This happens when you add a document where the value of a field is a
key/value construct, but isn't actually an atomic update. In JSON, this
is represented with curly braces. In Java, it is a Map object. This
kind of construct is only used for Atomic Updates -- the key must be one
of the atomic operations: set, add, delete, inc. The warning message
that I quoted indicates that the the key in the key/value construct for
that document was 3932885930.
If you are using SolrJ, then the value of one or more fields is being
set to a Map object, which isn't right unless you intend to do an Atomic
Update. If you are using JSON formatted updates, there are probably
curly braces where they don't belong.esp If you are using JSON formatted updates, there are probably curly braces where they don't belong.
mjgiarlo
commented
5 years ago The "bug" was when we would run multiple traject configs, each using convert_to_language_hash on the same field.
Will add more information as available, for now, the following SOLR error is logged when attempting to ingest an item: