Hi, Many of our documents contain a unique, non-indexed text field that contains html-content which we display to our users (let's call it "html_content"). The reason we store this field in Solr in the first place is because of Solr's highlighting capabilities: the query itself is against the non-html version of the field. Unfortunately, sometimes the field is very large and causes the users' browsers to crash when displayed.
Currently, our proposed solution is to implement an update processor which will split this field into several other non-indexed fields (such as "html_content1", "html_content2" and so on), so that the displaying website will be able to query and show only a portion of the full content at any given part. Can anyone suggest a more elegant solution? Again, we are storing the field in Solr because we need highlighting. Also, the UI team cannot implement the "paging" of this field in their side because their server cannot manage user sessions and should remain stateless. -- View this message in context: http://lucene.472066.n3.nabble.com/Splitting-large-non-stored-field-tp4317570.html Sent from the Solr - User mailing list archive at Nabble.com.
