You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Thomas Peuss (JIRA)" <ji...@apache.org> on 2007/07/18 09:36:04 UTC
[jira] Created: (SOLR-309) A solr.StrField that has analyzers
configured should emit warning to log
A solr.StrField that has analyzers configured should emit warning to log
------------------------------------------------------------------------
Key: SOLR-309
URL: https://issues.apache.org/jira/browse/SOLR-309
Project: Solr
Issue Type: Improvement
Components: search
Reporter: Thomas Peuss
A solr.StrField that has analyzers configured in schema.xml should emit a warning/error to the log. As I understand StrFields never get tokenized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-309) A solr.StrField that has analyzers
configured should emit warning to log
Posted by "Andy Blower (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564042#action_12564042 ]
Andy Blower commented on SOLR-309:
----------------------------------
Has this been changed in the latest version of SOLR? I'm using v1.2.0 and it was unclear from the documentation whether it is valid to specify analyzers for non-text fields. I tried it when I wanted a simple tokenized string field, and it appears to work. Here's my field definition:
<!-- Fieldtype for simple tokenized strings. (Don't use for sorting, do use for space separated codes) -->
<fieldType name="stringText" class="solr.TextField" positionIncrementGap="0" omitNorms="true">
<analyzer>
<tokenizer class="solr.WhitespaceTokenizerFactory"/>
</analyzer>
</fieldType>
I use it for fields that have whitespace separated codes e.g. "101 104 15a 075". Just using a string field meant I could only find the exact full string rather than individual codes.
> A solr.StrField that has analyzers configured should emit warning to log
> ------------------------------------------------------------------------
>
> Key: SOLR-309
> URL: https://issues.apache.org/jira/browse/SOLR-309
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Thomas Peuss
> Priority: Minor
>
> A solr.StrField that has analyzers configured in schema.xml should emit a warning/error to the log. As I understand StrFields never get tokenized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-309) A solr.StrField that has analyzers
configured should emit warning to log
Posted by "Thomas Peuss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Peuss updated SOLR-309:
------------------------------
Priority: Minor (was: Major)
> A solr.StrField that has analyzers configured should emit warning to log
> ------------------------------------------------------------------------
>
> Key: SOLR-309
> URL: https://issues.apache.org/jira/browse/SOLR-309
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Thomas Peuss
> Priority: Minor
>
> A solr.StrField that has analyzers configured in schema.xml should emit a warning/error to the log. As I understand StrFields never get tokenized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-309) A solr.StrField that has analyzers
configured should emit warning to log
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514882 ]
Hoss Man commented on SOLR-309:
-------------------------------
personally, i'd vote for changing the FieldType loading code to allow analyzers for any field type (instead of the special logic that currently only looks for them in the case of TextField) ... even if i have an instance of SortableIntFieldType i should be able to put an analyzer in front of it that will massage the input data into something thta parses cleanly as an integer.
> A solr.StrField that has analyzers configured should emit warning to log
> ------------------------------------------------------------------------
>
> Key: SOLR-309
> URL: https://issues.apache.org/jira/browse/SOLR-309
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Thomas Peuss
> Priority: Minor
>
> A solr.StrField that has analyzers configured in schema.xml should emit a warning/error to the log. As I understand StrFields never get tokenized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-309) A solr.StrField that has analyzers
configured should emit warning to log
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564055#action_12564055 ]
Yonik Seeley commented on SOLR-309:
-----------------------------------
> I tried it when I wanted a simple tokenized string field
The analyzer you show *is* a text field (which is what you want when doing analysis).
Why would you want an "analyzed" string field when that is exactly what a text field is?
> A solr.StrField that has analyzers configured should emit warning to log
> ------------------------------------------------------------------------
>
> Key: SOLR-309
> URL: https://issues.apache.org/jira/browse/SOLR-309
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Thomas Peuss
> Priority: Minor
>
> A solr.StrField that has analyzers configured in schema.xml should emit a warning/error to the log. As I understand StrFields never get tokenized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.