On Tue, Jun 23, 2015 at 6:41 PM, Adrien Grand <[email protected]> wrote: > For the record, there is an experimental postings format in > lucene/sandbox called IDVersionPostingsFormat that stores both the ID > and version in a postings format. This way you don't have to perform > additional seeks to look up the version, and it's even optimized for > id look ups with a minimum version for faster optimistic concurrency.
Yeah, I have looked at it in the past but in the context of updateable DocValues, I feel that there is no way to support updateable doc values if we use the IDVersionPostingsFormat. This is because we must update a DocValue field together with the version field atomically or else we run into consistency issues. > > On Mon, Jun 22, 2015 at 4:41 PM, Ishan Chattopadhyaya > <[email protected]> wrote: >> Hi all, >> I am looking to try out _version_ as a docvalue (SOLR-6337) as a precursor >> to SOLR-5944. Towards that, I want the _version_ field to be >> stored=indexed=false, docValues=true. >> >> Does someone know about the performance implications of retrieving the >> _version_ as a docvalue, e.g. accessing docvalue vs. a stored field? Is >> there any known inefficiency when using a docvalue (as opposed to a stored >> field) due to random disk seeks, for example? >> Regards, >> Ishan > > > > -- > Adrien > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Regards, Shalin Shekhar Mangar. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
