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

jerico updated SOLR-3692:
-------------------------

    Comment: was deleted

(was: The error does not occur when executing the query: q=all_de_DE:typisch 
AND (article_id:test-inst-2172 OR article_id:test-inst-2155), i.e. querying the 
token "typisch" itself.)
    
> Error when highlighting document
> --------------------------------
>
>                 Key: SOLR-3692
>                 URL: https://issues.apache.org/jira/browse/SOLR-3692
>             Project: Solr
>          Issue Type: Bug
>          Components: highlighter
>    Affects Versions: 3.6, 3.6.1
>         Environment: linux
>            Reporter: jerico
>         Attachments: luke-test-inst-2155.xml, luke-test-inst-2172.xml, 
> schema.xml, solrconfig.xml
>
>
> When executing the query "q=all_de_DE:Wissenschaft AND 
> (article_id:test-inst-2172 OR article_id:test-inst-2155)" with highlighting 
> switched on solr issues "Token typisch exceeds length of provided text sized 
> 15879". I'll provide our solr configuration, schema and the two documents as 
> displayed by luke.
> Querying a single article is no problem. Both "q=all_de_DE:Wissenschaft AND 
> article_id:test-inst-2172" and "q=all_de_DE:Wissenschaft AND 
> article_id:test-inst-2155" work as expected. The exception only occurs when 
> the two given articles appear together in the result set.
> This error does not occur when executing the query: "q=all_de_DE:typisch AND 
> (article_id:test-inst-2172 OR article_id:test-inst-2155)", i.e. querying the 
> token "typisch" itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to