Duplicate fields are being caused by additional dictionary definitions in config.metabib_class_ts_map. NOBLE added a synonym dictionary and applied it to keyword, title, and subject classes with a weight of C. A new view in 3.1, search.best_tsconfig, retrieves keyword, title, and subject classes twice, once for our synonym ts_config and once for the english_nostop ts_config.
I changed the view definition to omit the custom NOBLE ts_config's but not sure if that's the best solution or if the index_weight should be changed from C to something else for the custom ts_config's.
SELECT m.id,
COALESCE(f.ts_config, c.ts_config, 'simple'::text) AS ts_config
FROM config.metabib_field m
LEFT JOIN config.metabib_class_ts_map c ON c.field_class = m.field_class AND c.index_weight = 'C'::bpchar AND c.ts_config <> 'synonym_noble'::text
LEFT JOIN config.metabib_field_ts_map f ON f.metabib_field = m.id AND f.index_weight = 'C'::bpchar;
Duplicate fields are being caused by additional dictionary definitions in config. metabib_ class_ts_ map. NOBLE added a synonym dictionary and applied it to keyword, title, and subject classes with a weight of C. A new view in 3.1, search. best_tsconfig, retrieves keyword, title, and subject classes twice, once for our synonym ts_config and once for the english_nostop ts_config.
I changed the view definition to omit the custom NOBLE ts_config's but not sure if that's the best solution or if the index_weight should be changed from C to something else for the custom ts_config's.
SELECT m.id, f.ts_config, c.ts_config, 'simple'::text) AS ts_config metabib_ field m metabib_ class_ts_ map c ON c.field_class = m.field_class AND c.index_weight = 'C'::bpchar AND c.ts_config <> 'synonym_ noble': :text metabib_ field_ts_ map f ON f.metabib_field = m.id AND f.index_weight = 'C'::bpchar;
COALESCE(
FROM config.
LEFT JOIN config.
LEFT JOIN config.