lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Trejkaz <trej...@trypticon.org>
Subject Re: What does "found existing value for PerFieldPostingsFormat.format" mean?
Date Tue, 18 Oct 2016 00:05:14 GMT
Additional investigation:

The index has two segments. Both segments have this "path-position" in
the FieldInfo only once. The settings look the same:

    FieldInfo in first sub-reader:
        name = "path-position"
        number = 6
        docValuesType = NONE
        storeTermVector = false
        omitNorms = true
        indexOptions = DOCS_AND_FREQS_AND_POSITIONS
        storePayloads = false
        attributes =
            "PerFieldPostingsFormat.format" -> "Lucene50"
            "PerFieldPostingsFormat.suffix" -> "0"
        dvGen = -1

    FieldInfo in second sub-reader:
        name = "path-position"
        number = 6
        docValuesType = NONE
        storeTermVector = false
        omitNorms = true
        indexOptions = DOCS_AND_FREQS_AND_POSITIONS
        storePayloads = false
        attributes =
            "PerFieldPostingsFormat.format" -> "Lucene50"
            "PerFieldPostingsFormat.suffix" -> "0"
        dvGen = -1

So I'm confused. addIndexes, I thought, merged the data from the given
readers into the destination writer. And here I have two fields with
the same name, number and every other setting, and somehow it's
failing to merge them because when it gets to the second one, it fails
because the first one existed already... which to me, seems like the
point of merging, but maybe that's just me.

TX

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


Mime
View raw message