alessandrobenedetti edited a comment on pull request #129: URL: https://github.com/apache/solr/pull/129#issuecomment-847790405
Thinking a little more about this I'll make even a bigger provocation: I don't think it should exist a StrField type at all, it is textual information and we can get the same through a text field which is just "Keyword tokenized", and should be the only way, there's no benefit/differentiation in having two ways for the same index output. But removing the StrField type is definitely not in scope in this issue, so in my opinion, we should at least have consistent behavior, and today if you define a field as StrField type or text Keyword tokenized, you produce the same index as far as I know, but at query time the sow works correctly just for the latter. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org