Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corpora with version metadatum create duplicate resolver entries on import with overwrite #549

Open
amir-zeldes opened this issue Jan 12, 2017 · 2 comments
Labels

Comments

@amir-zeldes
Copy link
Collaborator

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?

  1. Import GUM
  2. Increment the version datum and reimport + overwrite
  3. 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.

@amir-zeldes
Copy link
Collaborator Author

This seems to persist even if I delete and then import the corpus fresh.

@rainsfordtm
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants