You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2015/07/06 11:47:04 UTC

[jira] [Resolved] (STANBOL-1434) Indexing Vocabularies with bnode and LDPath does not work

     [ https://issues.apache.org/jira/browse/STANBOL-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Westenthaler resolved STANBOL-1434.
------------------------------------------
    Resolution: Fixed

fixed with http://svn.apache.org/r1689339 in trunk. Merged with http://svn.apache.org/r1689348 to 0.12.1

> Indexing Vocabularies with bnode and LDPath does not work
> ---------------------------------------------------------
>
>                 Key: STANBOL-1434
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1434
>             Project: Stanbol
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 1.0.0, 0.12.1
>
>
> STANBOL-765 added support for indexing bnodes by converting them to URIs. As it turns out when doing so the {{org.apache.stanbol.entityhub.indexing.core.processor.LdpathSourceProcessor}} can no longer follow paths with a bnode representing one of the traversed resources.
> The reason for that is that the Bnode is converted to an URI but the RDFBackendImplementation of the Jena TDB indexing source does not convert the parsed URI based to a Bnode before looking it up in the triple store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)