[
https://issues.apache.org/jira/browse/LUCENE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558825#action_12558825
]
gsingers edited comment on LUCENE-1016 at 1/14/08 2:57 PM:
------------------------------------------------------------------
I'm curious if the build part of this would be faster than reanalyzing a
document. Just thinking outloud, but I have wondering about a Highlighter that
uses the new TermVectorMapper, but using that doesn't account for
non-TermVector based Documents that need to be analyzed. Was thinking this
might account for both cases, all through the TermVectorMapper mechanism. Just
doesn't seem like it would be very fast.
was (Author: gsingers):
I'm curious if the build part of this would be faster than reanalyzing a
document. Just thinking outloud, but I have wondering about a Highlighter that
uses the new TermVectorMapper, but that doesn't account for non-TermVector
based. Was thinking this might account for both cases.
> TermVectorAccessor, transparent vector space access
> ----------------------------------------------------
>
> Key: LUCENE-1016
> URL: https://issues.apache.org/jira/browse/LUCENE-1016
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Term Vectors
> Affects Versions: 2.2
> Reporter: Karl Wettin
> Priority: Minor
> Attachments: LUCENE-1016.txt
>
>
> This class visits TermVectorMapper and populates it with information
> transparent by either passing it down to the default terms cache (documents
> indexed with Field.TermVector) or by resolving the inverted index.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
