You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Site stuck with Import status: Running file import.
I got attached logs from solr.log file which complain about the max-length of UTF8 encoding.
org.apache.solr.common.SolrException: Exception writing document id /test/aaa.docx to the index; possible analysis error: Document contains at least one immense term in field="Text_TextEntry_ss" (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: '[107, 101, 121, 119, 111, 114, 100, 61, 88, 77, 76, 58, 99, 111, 109, 46, 97, 100, 111, 98, 101, 46, 120, 109, 112, 44, 32, 118, 97, 108]...', original message: bytes can be at most 32766 in length; got 36995. Perhaps the document has an indexed string field (solr.StrField) which is too large.
Do anyone know how can we resolve this issue?
The text was updated successfully, but these errors were encountered:
Site stuck with Import status: Running file import.
I got attached logs from solr.log file which complain about the max-length of UTF8 encoding.
org.apache.solr.common.SolrException: Exception writing document id /test/aaa.docx to the index; possible analysis error: Document contains at least one immense term in field="Text_TextEntry_ss" (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: '[107, 101, 121, 119, 111, 114, 100, 61, 88, 77, 76, 58, 99, 111, 109, 46, 97, 100, 111, 98, 101, 46, 120, 109, 112, 44, 32, 118, 97, 108]...', original message: bytes can be at most 32766 in length; got 36995. Perhaps the document has an indexed string field (solr.StrField) which is too large.
Do anyone know how can we resolve this issue?
The text was updated successfully, but these errors were encountered: