Jetty Lucene logs has errors org.apache.solr.common.SolrException: Document contains at least one immense term...

We have multiple errors in our JellyTrisoftSolrLucene log for non english languages (whose UTF8 encoding is longer than the max length of 32766) Please correct the analyzer to not produce such terms. The prefix of the first immense term is '[48,49,,47...]. Does anyone know which setting needs to be adjusted to address this issue?

emoji
  • Hi Akheil,

    This honestly looks more like a Customer Support ticket, then a community general discussion entry.

    Logging the ticket would help as you could immediately share

    • An example problematic data set... There is something atypical about the (OASIS DITA) xml or the object's metadata
    • A full log file of Solr

    In the end the "Trisoft SolrLucene" Windows service is preconfigured to handle a lot of situations. Seemingly you found an edge case which we inherited by doing functional/security updates on Solr and in turn Lucene. The product team would be happy to learn and improve from your sample to make it go smoother for the next upgrades.

    A first internet search, thanks to mentioning your exact error messsage, landed me on pages like https://stackoverflow.com/questions/37070593/how-to-deal-with-document-contains-at-least-one-immense-term-in-solr ... Again please log a Customer Support ticket, potentially linking to this thread and attach some more data/log details.

    Best wishes,
    Dave

    emoji