Steve's comment is much more germane. KeywordTokenizer, used in alphaOnlySort last I knew is not appropriate at all. Do you really want single tokens that consist of the entire document for sorting purposes? Wouldn't the first 1K be enough?
It looks like this was put in in 4.0, so I'm guessing your analysis chain is different now between the two versions. It doesn't really matter though, this is not going to be changed. You'll have to do something about your long fields or your analysis chain. And/or revisit what you hope to accomplish with using that field type on such a field, I'm almost certain your use case is flawed. Best, Erick On Tue, May 1, 2018 at 10:35 AM, THADC <timothy.clotworthy.j...@gmail.com> wrote: > Erick, thanks for the response. I have a number of documents in our database > where solr is throwing the same exception against *_tsing types. > > However, when I index against the same document with our solr 4.7, it is > successfully indexed. So, I assume something is different between 4.7 and > 7.3. I was assuming I could adjust the dynamic field somehow so that it > indexes against these documents without errors when using 7.3. > > I can't remove the offending documents. Its my customer's data > > Is there some adjustment I can make to the dynamic field? > > Thanks again. > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
