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

Changes TaggerFstCorpus to allow SolrDocuments that do not define the "storedField" #6

Merged
merged 1 commit into from
Jul 4, 2013

Conversation

westei
Copy link
Contributor

@westei westei commented Jul 4, 2013

There are two possible reasons, why IndexableField storedField = document.getField(storedFieldName); returns null:

  1. The field definition in the schema is faulty (stored=false) and therefor the labels for the current entity are missing in the Index
  2. The field definition is correct, but the entity does not have any labels

If storedFieldName represents the field use to store labels in a specific language (e.g. German) it is a total valid case that an entity might not have a label in that specific language.

This change will allow to create per language FST corpora as suggested by Issue #5

…fields of processed documents. This is important to support the creation of FST Corpora for Vocabularies where some entries (Solr Documents) do not have a label (e.g. in multilingual scenarios)
dsmiley added a commit that referenced this pull request Jul 4, 2013
Changes TaggerFstCorpus to allow SolrDocuments that do not define the "storedField"
@dsmiley dsmiley merged commit 9360290 into OpenSextant:master Jul 4, 2013
@dsmiley
Copy link
Member

dsmiley commented Jul 4, 2013

Nice; I liked the addition of the warning.

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

Successfully merging this pull request may close these issues.

2 participants