[
https://issues.apache.org/jira/browse/STANBOL-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-1433.
------------------------------------------
Resolution: Fixed
Fix Version/s: 0.12.1
fixed with http://svn.apache.org/r1689339 in trunk. Merged with
http://svn.apache.org/r1689348 to 0.12.1
> Assume '*' for FieldValueFilter in case excludes are present
> ------------------------------------------------------------
>
> Key: STANBOL-1433
> URL: https://issues.apache.org/jira/browse/STANBOL-1433
> Project: Stanbol
> Issue Type: Improvement
> Components: Entityhub
> Affects Versions: 0.12.0
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
> Fix For: 1.0.0, 0.12.1
>
>
> The EntityProcessor
> {{org.apache.stanbol.entityhub.indexing.core.processor.FieldValueFilter}}
> allows to filter Entities based on values of a field. The typical use case is
> to filter Entities based on their {{rdf:type}} statement.
> The processor is typically configured by the
> {{indexing/config/entityTypes.properties}}:
> Usage example include:
> * only index Persons: {{values=schema:Person}}
> * index Person and Organizations: {{values=schema:Person;schema:Organization}}
> * index Persons and Entities without type: {{values=schema:Person;null}}
> * index everything other than Persons: {{values=*;!schema:Person}}
> * exclude Entities without a type: {{values=*;!null}}
> When using the tool I noticed that including the * when writing exclusions is
> not intuitive so this will change the behavior so that * is no longer needed.
> E.g.
> * index everything other than Persons: {{values=!schema:Person}}
> * exclude Entities without a type: {{values=!null}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
