You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "Caleb Meier (JIRA)" <ji...@apache.org> on 2017/02/28 18:05:45 UTC

[jira] [Resolved] (RYA-234) StatementMetaData Optimizer

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

Caleb Meier resolved RYA-234.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 3.2.10

StatementMetadata Optimizer has been implemented with tests and an example in RyaDirectExamples.

> StatementMetaData Optimizer
> ---------------------------
>
>                 Key: RYA-234
>                 URL: https://issues.apache.org/jira/browse/RYA-234
>             Project: Rya
>          Issue Type: New Feature
>          Components: clients
>    Affects Versions: 3.2.10
>            Reporter: Caleb Meier
>            Assignee: Caleb Meier
>             Fix For: 3.2.10
>
>
> Create a Statement Meta data query node and an optimizer to match such nodes.  The purpose of the node is to match reified queries for statement metadata and during evaluation, issue the appropriate scan to Rya to extract the metadata.  The objective here is to reduce the number of joins required to query metadata for a given statement.  The reified metadata query will be reduced to a single scan where metadata properties are extracted from the value field of each serialized Rya statement.  The user will have the option of specifying which metadata properties to query over in the event that some of the triples have been reified and others have not.  If no statement metadata properties are specified, all properties associated with the reified blank node will be packaged into the StatementMetadataNode and only triples satisfying all of those properties will be returned (along with the values of the specified properties).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)