Hi James, I have to admit, I've never seen that error before. My guess is there's something odd/different (or incorrect) with the data that you are trying to import. But, I don't know what it could be. That error mentions the "query" field is the problematic one. Have you looked at the data you are trying to import to see why that "query" field is so long? Maybe something is incorrect in that import data, or maybe it's encoded improperly and the script is stumbling over it?
Tim On Monday, September 11, 2023 at 3:49:56 PM UTC-5 James Holobetz wrote: > > (I sent it early be mistake) > > > https://mail.google.com/mail/u/0/?tab=rm&ogbl#search/Exception+writing+document+id/FMfcgzGtvsbMhlrcPsHZXVSJjRcZSsvW > > > https://stackoverflow.com/questions/37070593/how-to-deal-with-document-contains-at-least-one-immense-term-in-solr > > > 1) What would cause this (on the production machine)? > > 2) How do I resolve this issue? > > Thank you > > On Mon, Sep 11, 2023 at 2:46 PM James Holobetz <[email protected]> wrote: > >> I am moving data from our production dspace 7.6 server to our development >> dspace 7.6 server and I am repeatedly receiving this error: >> >> holobetj dspace $ dsp /opt/dspace/bin/dspace solr-import-statistics -c >> No index name provided, defaulting to "statistics". >> Exception: Error from server at http://localhost:8983/solr/statistics: >> Exception writing document id 01072706-6b8a-420d-9bc0-cc637bce3df4 to the >> index; possible analysis error: Document contains at least one immense term >> in field="query" (whose UTF8 encoding is longer than the max length 32766), >> all of which were skipped. Please correct the analyzer to not produce such >> terms. The prefix of the first immense term is: '[117, 110, 101, 120, 105, >> 115, 116, 105, 110, 103, 47, 46, 46, 47, 46, 46, 47, 46, 46, 47, 46, 46, >> 47, 46, 46, 47, 46, 46, 47, 46]...', original message: bytes can be at most >> 32766 in length; got 34396. Perhaps the document has an indexed string >> field (solr.StrField) which is too large >> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: >> Error from server at http://localhost:8983/solr/statistics: Exception >> writing document id 01072706-6b8a-420d-9bc0-cc637bce3df4 to the index; >> possible analysis error: Document contains at least one immense term in >> field="query" (whose UTF8 encoding is longer than the max length 32766), >> all of which were skipped. Please correct the analyzer to not produce such >> terms. The prefix of the first immense term is: '[117, 110, 101, 120, 105, >> 115, 116, 105, 110, 103, 47, 46, 46, 47, 46, 46, 47, 46, 46, 47, 46, 46, >> 47, 46, 46, 47, 46, 46, 47, 46]...', original message: bytes can be at most >> 32766 in length; got 34396. Perhaps the document has an indexed string >> field (solr.StrField) which is too large >> >> >> Looking in the forums here I have seen the error very rarely: >> >> -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/6810f574-69e6-4676-95ec-717b4ca22a72n%40googlegroups.com.
