[
https://issues.apache.org/jira/browse/LUCENE-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829599#comment-16829599
]
Michael Gibney commented on LUCENE-4312:
----------------------------------------
(following on discussion at
[LUCENE-8776|https://issues.apache.org/jira/browse/LUCENE-8776?focusedCommentId=16829561&#comment-16829561]):
[~mikemccand], agreed that for query-time cases, graphs can and should be
handled as you say.
But functionality that relies on reconstituting _index_-time token graphs (as
produced by synonym-/WDGF-type analysis) would require position length to be
stored in the index (and reported back via PostingsEnum at query-time), no? And
per [~rcmuir]'s suggestion above, the only way to do this currently would be by
encoding position length in Payloads.
My question is a more general one about the utility of indexing position
length, and whether anyone would be interested in considering integrating full
support for indexed token graphs.
> Index format to store position length per position
> --------------------------------------------------
>
> Key: LUCENE-4312
> URL: https://issues.apache.org/jira/browse/LUCENE-4312
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/codecs
> Affects Versions: 6.0
> Reporter: Gang Luo
> Priority: Minor
> Labels: Suggestion
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Mike Mccandless said:TokenStreams are actually graphs.
> Indexer ignores PositionLengthAttribute.Need change the index format (and
> Codec APIs) to store an additional int position length per position.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
