Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1181 closed defect (fixed)

Metadata records indexed twice when language-index-fields.xsl present

Reported by: simonp Owned by: geonetwork-devel@…
Priority: major Milestone: v2.8.0
Component: General Version: v2.8.0RC2
Keywords: Cc:

Description

Some small bugs in iso19139/language-index-fields.xsl cause metadata records to be indexed twice as merge with default language was not correct.

See also this report by brian.ohare@…:

I have a question about lucene indexing and document locales. I'm developing a search interface based on tabsearch UI which uses the 'q' fast index service. If I run a spatial-only search without the 'any' parameter, the documents returned from the index are missing some fields, eg abstract, keywords, responsibleParty etc. The same search with the 'any' param returns complete documents , ie they include all the lucene 'dump fields' as per the lucene config.

Presumably this has to do with the language detection based on the presence of the 'any' parameter? There appear to be two entries in the 'eng' index for each document (same _id and uuid), one with a _locale field and one without. The entry with the _locale field has all dump fields stored, the other one does not. I'm not sure why this is the case but I think it should be possible to do a spatial-only search and get back documents with all the dump fields.

I notice that if I provide a '_locale' parameter in the search request I can get full results so this may be a workaround? Just wondering if this is a bug or is expected behaviour? I'm running a clean install of the latest 2.8 RC2.

Change History (2)

comment:1 by simonp, 12 years ago

Resolution: fixed
Status: newclosed

Fixed in commit 85dc7b983dbd902ebe84b94a253a84ef72458cb9

comment:2 by ianwallen, 12 years ago

Milestone: v2.9.0v2.8.0
Note: See TracTickets for help on using tickets.