Assuming (and it wasn't clear from your problem statement) that you need to search tokens in your field, this approach should be fine. I think Markus' comment was assuming that you did _not_ need to search the field. If you do, a copyField seems best.
Do be aware, though, that this will make for a very large index. Not quite sure how this will scale. On Tue, Jan 5, 2016 at 5:59 AM, Markus Jelsma <markus.jel...@openindex.io> wrote: > Hello - indeed, this is not going to work. But since you are using the token > filter as some preprocessor, you could easily use an update request processor > to do the preprocessing work for you. Check out the documentation, i think > you can use the RegexReplaceProcessor. > > https://cwiki.apache.org/confluence/display/solr/Update+Request+Processors > http://lucene.apache.org/solr/5_4_0/solr-core/org/apache/solr/update/processor/RegexReplaceProcessorFactory.html > > -----Original message----- >> From:Alok Bhandari <alokomprakashbhand...@gmail.com> >> Sent: Tuesday 5th January 2016 14:47 >> To: solr-user@lucene.apache.org >> Subject: How to use DocValues with TextField >> >> Hello , >> >> I have a field which is defined to be a textField with PatternTokenizer >> which splits on ";". >> Now for one of the use case I need to use /export handler to export this >> field. As /export handler needs field to support docValues , so if I try to >> mark that field as docValues="true" it says that TextField does not support >> docValues. >> If I think of using String fields then that does not support adding >> tokenizers. >> >> I am thinking of adding copy-field which is a string , so I query on >> original field but return a copy-field which is string which can be marked >> as docValues="true". This looks like solving my issue , is any better >> approach known. >> >> Thanks >> >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/How-to-use-DocValues-with-TextField-tp4248647.html >> Sent from the Solr - User mailing list archive at Nabble.com. >>
