Adding collation attribute-value pairs corrupts the view of the index

[ttasovac]

Adding collation attribute-value pairs corrupts the view of the index in Monex. Consequently, some less stable people, like myself, freak out :)

Without collation, this is what my index looks like:

the good index

With collation:

<collection xmlns="http://exist-db.org/collection-config/1.0">
<index>
    <range>
        <create qname="orth" 
            type="xs:string" 
            collation="?lang=sr&amp;strength=primary"/>
    </range>
</index>

I get the

the freaky index

The index itself in eXist is ok and can be queried, so this is a Monex issue.

[joewiz]

@ttasovac Interesting.

@wolfgangmm Is this to be expected? I seem to recall that the application of a collation will change the way index values are stored. From the lucene docs on collations, "Collation converts each token into its binary CollationKey using the provided Collator, allowing it to be stored as an index term." So perhaps what @ttasovac is reporting in his "freaky index" screenshot is just these binary values?

[line-o]

The links to the test-data are broken.