You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the used ANNIS version?
3.5.0-SNAPSHOT (rev. 39d5ba4, built 2016-12-09 10:30:36)
What browser and operating system did you use?
Chrome, Win 7 64
What steps will reproduce the problem?
Import GUM
Increment the version datum and reimport + overwrite
Open any example query
What is the expected result?
Normal visualizers as defined by resolver_vis_map
What happens instead?
All visualizers are duplicated (again and again, for each import+overwrite)
Please provide any additional information below. Also please add a screenshot if possible.
It seems on import corpus metadata containing the string 'version' is recognized and the version field in corpus.annis is filled. Once a new version of the corpus is imported, the old version is overwritten, but old entries in resolver_vis_map are not deleted. Instead, the new entries are appended, creating duplicate visualizations.
The text was updated successfully, but these errors were encountered:
I've just encountered the same issue (v. 3.6.0). I confirm it is caused by a "version" metadatum in the corpus. and fixed by removing it. Also the most serious issue I've encountered working with ANNIS, since it corrupts the resolver_vis_map table in the database and the only fixes I found were (i) reset the whole database or (ii) never use the corpus name again, neither of which are convenient workarounds!
What is the used ANNIS version?
3.5.0-SNAPSHOT (rev. 39d5ba4, built 2016-12-09 10:30:36)
What browser and operating system did you use?
Chrome, Win 7 64
What steps will reproduce the problem?
What is the expected result?
Normal visualizers as defined by resolver_vis_map
What happens instead?
All visualizers are duplicated (again and again, for each import+overwrite)
Please provide any additional information below. Also please add a screenshot if possible.
It seems on import corpus metadata containing the string 'version' is recognized and the version field in corpus.annis is filled. Once a new version of the corpus is imported, the old version is overwritten, but old entries in resolver_vis_map are not deleted. Instead, the new entries are appended, creating duplicate visualizations.
The text was updated successfully, but these errors were encountered: