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 "Mike Klaas (JIRA)" <ji...@apache.org> on 2008/06/06 01:38:45 UTC
[jira] Closed: (SOLR-460) Improvement to highlighting
infrastructure
[ https://issues.apache.org/jira/browse/SOLR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Klaas closed SOLR-460.
---------------------------
Resolution: Won't Fix
No patch, breaks backward compatibility
> Improvement to highlighting infrastructure
> ------------------------------------------
>
> Key: SOLR-460
> URL: https://issues.apache.org/jira/browse/SOLR-460
> Project: Solr
> Issue Type: Improvement
> Components: highlighter
> Affects Versions: 1.3
> Reporter: Sergey Dryganets
> Assignee: Otis Gospodnetic
> Priority: Minor
>
> Now I'm write a plugin for SOLR to highlight custom user data
> ie my application send to handler on Solr set of documents to highlight in xml format
> handler parse xml, create list of Document (not Lucene object just my abstraction which content Map<fieldName,fieldValue>
> it's enough to properly highlight fields)
> So I'm think you can change SolrHighlighter:
> public NamedList<Object> doHighlighting(DocList docs, Query query, SolrQueryRequest req, String[] defaultFields)
> to
> public NamedList<Object> doHighlighting(List<Document> docs, Query query, SolrQueryRequest req, String[] defaultFields)
> or create some type of provider to retrieve list of abstract Document's
> and Highlighter will be more reusable :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.