[
https://issues.apache.org/jira/browse/SOLR-14257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-14257.
-----------------------------------
Resolution: Not A Problem
What is your analysis chain? Have you looked at the admin/analysis page to see
what's thrown away? Most likely the tokenizer you've specified (or are using by
default) is throwing this away and you need to use a different tokenizer for
the field.
That said, please raise questions like this on the user's list, we try to
reserve JIRAs for known bugs/enhancements rather than usage questions.
See:
http://lucene.apache.org/solr/community.html#mailing-lists-irc
A _lot_ more people will see your question on that list and may be able to help
more quickly.
You might want to review: https://wiki.apache.org/solr/UsingMailingLists
If it's determined that this really is a code issue or enhancement to Solr and
not a configuration/usage problem, we can raise a new JIRA or reopen this one.
> Keyword's not indexed or searchable
> -----------------------------------
>
> Key: SOLR-14257
> URL: https://issues.apache.org/jira/browse/SOLR-14257
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
> Affects Versions: 7.6
> Reporter: Shae Bottum
> Priority: Major
>
> During indexing, if the value of your column is the literal char **** ,
> solr's tokenizer will pass over this value and Not tokenize it. This value
> then is not indexed and therefore not searchable. Need to make this keyword
> searchable. I understand to search it, you would need to add quotes around
> the value * to ensure the asterisk is not treated as a wildcard and return
> all. The use case is searching for the actual value of an asterisk.
>
> tokenizer works for "jo*n" or "j*n"
> tokenizer does Not work for "******"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
