[
https://issues.apache.org/jira/browse/STANBOL-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-297.
-----------------------------------------
Resolution: Fixed
implemented with #1149562
For the RESTful interface this change is fully backwards compatible
For the JavaAPI please note the deprecation of the TextConstraint.getText()
method.
> Add support for optional text constraints to FieldQuery
> -------------------------------------------------------
>
> Key: STANBOL-297
> URL: https://issues.apache.org/jira/browse/STANBOL-297
> Project: Stanbol
> Issue Type: New Feature
> Components: Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> Currently TextConstraint only supports a singe Text. The semantic is that
> returned Entities must contain the whole text. This extension will allow to
> explicit search for "Text1" OR "Text2".
> Implementations are encouraged to boost the Rank of Results that contain
> more/all of the optionally parsed texts.
> This types of queries are planed to be used by the Taxonomy Engine to search
> for Entities based on Chunks selected within the Text. Currently multiple
> queries need to be executed by first searching for the whole Chunk and if no
> results are found repeating the search with omitted Words.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
