lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4998) be more precise about IOContext for reads
Date Sun, 20 Oct 2013 10:11:42 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800116#comment-13800116
] 

ASF subversion and git services commented on LUCENE-4998:
---------------------------------------------------------

Commit 1533870 from [~mikemccand] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1533870 ]

LUCENE-4998: can't use Lucene3x (test requires doc values)

> be more precise about IOContext for reads
> -----------------------------------------
>
>                 Key: LUCENE-4998
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4998
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Shikhar Bhushan
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 4.5.1, 4.6, 5.0
>
>         Attachments: LUCENE-4998.patch
>
>
> Set the context as {{IOContext.READ}} / {{IOContext.READONCE}} where applicable
> ----
> Motivation:
> Custom {{PostingsFormat}} may want to check the context on {{SegmentReadState}} and branch
differently, but for this to work properly the context has to be specified correctly up the
stack.
> For example, {{DirectPostingsFormat}} only loads postings into memory if the {{context
!= MERGE}}. However a better condition would be {{context == Context.READ && !context.readOnce}}.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message