Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 092A39234 for ; Tue, 5 Jun 2012 19:52:25 +0000 (UTC) Received: (qmail 8632 invoked by uid 500); 5 Jun 2012 19:52:23 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 8499 invoked by uid 500); 5 Jun 2012 19:52:23 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 8487 invoked by uid 99); 5 Jun 2012 19:52:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 19:52:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 64C5E141663 for ; Tue, 5 Jun 2012 19:52:23 +0000 (UTC) Date: Tue, 5 Jun 2012 19:52:23 +0000 (UTC) From: "Aliaksandr Zhuhrou (JIRA)" To: dev@lucene.apache.org Message-ID: <1472364853.41101.1338925943414.JavaMail.jiratomcat@issues-vm> In-Reply-To: <578919323.18440.1305619727356.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (LUCENE-3108) Land DocValues on trunk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LUCENE-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289667#comment-13289667 ] Aliaksandr Zhuhrou commented on LUCENE-3108: -------------------------------------------- Thank you. The thing that make me ask this question is that in the org.apache.lucene.codecs.lucene40.values.FixedStraightBytesImpl.FixedBytesWriterBase#add we have logic that handles cases when => (lastDocID+1 < docID) so I assumed that docId may have gap greater than 1. "in general you should rather ask these kind of questions on the main dev mailing list." Sure. > Land DocValues on trunk > ----------------------- > > Key: LUCENE-3108 > URL: https://issues.apache.org/jira/browse/LUCENE-3108 > Project: Lucene - Java > Issue Type: Task > Components: core/index, core/search, core/store > Affects Versions: CSF branch, 4.0 > Reporter: Simon Willnauer > Assignee: Simon Willnauer > Fix For: 4.0 > > Attachments: LUCENE-3108.patch, LUCENE-3108.patch, LUCENE-3108.patch, LUCENE-3108.patch, LUCENE-3108.patch, LUCENE-3108_CHANGES.patch > > > Its time to move another feature from branch to trunk. I want to start this process now while still a couple of issues remain on the branch. Currently I am down to a single nocommit (javadocs on DocValues.java) and a couple of testing TODOs (explicit multithreaded tests and unoptimized with deletions) but I think those are not worth separate issues so we can resolve them as we go. > The already created issues (LUCENE-3075 and LUCENE-3074) should not block this process here IMO, we can fix them once we are on trunk. > Here is a quick feature overview of what has been implemented: > * DocValues implementations for Ints (based on PackedInts), Float 32 / 64, Bytes (fixed / variable size each in sorted, straight and deref variations) > * Integration into Flex-API, Codec provides a PerDocConsumer->DocValuesConsumer (write) / PerDocValues->DocValues (read) > * By-Default enabled in all codecs except of PreFlex > * Follows other flex-API patterns like non-segment reader throw UOE forcing MultiPerDocValues if on DirReader etc. > * Integration into IndexWriter, FieldInfos etc. > * Random-testing enabled via RandomIW - injecting random DocValues into documents > * Basic checks in CheckIndex (which runs after each test) > * FieldComparator for int and float variants (Sorting, currently directly integrated into SortField, this might go into a separate DocValuesSortField eventually) > * Extended TestSort for DocValues > * RAM-Resident random access API plus on-disk DocValuesEnum (currently only sequential access) -> Source.java / DocValuesEnum.java > * Extensible Cache implementation for RAM-Resident DocValues (by-default loaded into RAM only once and freed once IR is closed) -> SourceCache.java > > PS: Currently the RAM resident API is named Source (Source.java) which seems too generic. I think we should rename it into RamDocValues or something like that, suggestion welcome! > Any comments, questions (rants :)) are very much appreciated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org