[jira] Created: (SOLR-2145) Give warning or error when StrField is used with analyzer definition

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (SOLR-2145) Give warning or error when StrField is used with analyzer definition

JIRA jira@apache.org
Give warning or error when StrField is used with analyzer definition
--------------------------------------------------------------------

                 Key: SOLR-2145
                 URL: https://issues.apache.org/jira/browse/SOLR-2145
             Project: Solr
          Issue Type: Improvement
          Components: Schema and Analysis
            Reporter: Erik Hatcher


This illustrates the problem <http://search.lucidimagination.com/search/document/c7faf8d497b94b08/case_insensitive_phrase_query_for_string_fields>

{code}
<fieldType name="ci_string" class="solr.StrField">
      <analyzer>
         <filter class="solr.LowerCaseFilterFactory"/>
         <tokenizer class="solr.KeywordTokenizerFactory"/>
      </analyzer>
</fieldType>
{code}

StrField doesn't use the analyzer *except* improperly with the analysis.jsp tool currently.  

This mistake should be a startup error or warning.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-2145) Give warning or error when StrField is used with analyzer definition

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919219#action_12919219 ]

Jan H√łydahl commented on SOLR-2145:
-----------------------------------

Perhaps also give an error if there are <filter> tags before <tokenizer>, or <charfilter> tags after <tokenizer>

> Give warning or error when StrField is used with analyzer definition
> --------------------------------------------------------------------
>
>                 Key: SOLR-2145
>                 URL: https://issues.apache.org/jira/browse/SOLR-2145
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Erik Hatcher
>
> This illustrates the problem <http://search.lucidimagination.com/search/document/c7faf8d497b94b08/case_insensitive_phrase_query_for_string_fields>
> {code}
> <fieldType name="ci_string" class="solr.StrField">
>       <analyzer>
>          <filter class="solr.LowerCaseFilterFactory"/>
>          <tokenizer class="solr.KeywordTokenizerFactory"/>
>       </analyzer>
> </fieldType>
> {code}
> StrField doesn't use the analyzer *except* improperly with the analysis.jsp tool currently.  
> This mistake should be a startup error or warning.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-2145) Give warning or error when StrField is used with analyzer definition

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919255#action_12919255 ]

Erik Hatcher commented on SOLR-2145:
------------------------------------

bq. Perhaps also give an error if there are <filter> tags before <tokenizer>, or <charfilter> tags after <tokenizer>

Yeah, maybe, but order doesn't currently matter for those does it?  It makes it confusing to see, though.

> Give warning or error when StrField is used with analyzer definition
> --------------------------------------------------------------------
>
>                 Key: SOLR-2145
>                 URL: https://issues.apache.org/jira/browse/SOLR-2145
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Erik Hatcher
>
> This illustrates the problem <http://search.lucidimagination.com/search/document/c7faf8d497b94b08/case_insensitive_phrase_query_for_string_fields>
> {code}
> <fieldType name="ci_string" class="solr.StrField">
>       <analyzer>
>          <filter class="solr.LowerCaseFilterFactory"/>
>          <tokenizer class="solr.KeywordTokenizerFactory"/>
>       </analyzer>
> </fieldType>
> {code}
> StrField doesn't use the analyzer *except* improperly with the analysis.jsp tool currently.  
> This mistake should be a startup error or warning.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-2145) Give warning or error when StrField is used with analyzer definition

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919257#action_12919257 ]

Jonathan Rochkind commented on SOLR-2145:
-----------------------------------------

Regardless of order, with a StrField use a <filter> at all, or is it completely non-analyzed?  I thought it was non-analyzed.

> Give warning or error when StrField is used with analyzer definition
> --------------------------------------------------------------------
>
>                 Key: SOLR-2145
>                 URL: https://issues.apache.org/jira/browse/SOLR-2145
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Erik Hatcher
>
> This illustrates the problem <http://search.lucidimagination.com/search/document/c7faf8d497b94b08/case_insensitive_phrase_query_for_string_fields>
> {code}
> <fieldType name="ci_string" class="solr.StrField">
>       <analyzer>
>          <filter class="solr.LowerCaseFilterFactory"/>
>          <tokenizer class="solr.KeywordTokenizerFactory"/>
>       </analyzer>
> </fieldType>
> {code}
> StrField doesn't use the analyzer *except* improperly with the analysis.jsp tool currently.  
> This mistake should be a startup error or warning.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-2145) Give warning or error when StrField is used with analyzer definition

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919272#action_12919272 ]

Erik Hatcher commented on SOLR-2145:
------------------------------------

bq. Regardless of order, with a StrField use a <filter> at all, or is it completely non-analyzed? I thought it was non-analyzed.

A StrField (during indexing/querying) will not use any <analyzer> stuff at all.  (but again, the analysis.jsp is broken in that it actually does use it currently)

> Give warning or error when StrField is used with analyzer definition
> --------------------------------------------------------------------
>
>                 Key: SOLR-2145
>                 URL: https://issues.apache.org/jira/browse/SOLR-2145
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Erik Hatcher
>
> This illustrates the problem <http://search.lucidimagination.com/search/document/c7faf8d497b94b08/case_insensitive_phrase_query_for_string_fields>
> {code}
> <fieldType name="ci_string" class="solr.StrField">
>       <analyzer>
>          <filter class="solr.LowerCaseFilterFactory"/>
>          <tokenizer class="solr.KeywordTokenizerFactory"/>
>       </analyzer>
> </fieldType>
> {code}
> StrField doesn't use the analyzer *except* improperly with the analysis.jsp tool currently.  
> This mistake should be a startup error or warning.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (SOLR-2145) Give warning or error when StrField is used with analyzer definition

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man resolved SOLR-2145.
----------------------------

    Resolution: Duplicate

> Give warning or error when StrField is used with analyzer definition
> --------------------------------------------------------------------
>
>                 Key: SOLR-2145
>                 URL: https://issues.apache.org/jira/browse/SOLR-2145
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Erik Hatcher
>
> This illustrates the problem <http://search.lucidimagination.com/search/document/c7faf8d497b94b08/case_insensitive_phrase_query_for_string_fields>
> {code}
> <fieldType name="ci_string" class="solr.StrField">
>       <analyzer>
>          <filter class="solr.LowerCaseFilterFactory"/>
>          <tokenizer class="solr.KeywordTokenizerFactory"/>
>       </analyzer>
> </fieldType>
> {code}
> StrField doesn't use the analyzer *except* improperly with the analysis.jsp tool currently.  
> This mistake should be a startup error or warning.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]