[
https://issues.apache.org/jira/browse/SOLR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated SOLR-460:
----------------------------------
Priority: Minor (was: Major)
Assignee: Otis Gospodnetic
Summary: Improvement to highlighting infrastructure (was: Improvment to
highlighting infrastructure)
I'm not a DocList expert, but it doesn't look like you can just change the
DocList argument into List<Document> and expect things to keep working.
If you have a patch, please attach it. If not, I'm tempted to mark this as
Won't Fix in a few days unless somebody speaks up and says a change like this
makes sense and is doable.
> 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.
