You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/01/02 20:13:00 UTC

[jira] [Commented] (RYA-416) Add the ability use the MongoDB aggregation pipeline to evaluate simple SPARQL expressions

    [ https://issues.apache.org/jira/browse/RYA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308635#comment-16308635 ] 

ASF GitHub Bot commented on RYA-416:
------------------------------------

Github user kchilton2 commented on the issue:

    https://github.com/apache/incubator-rya/pull/254
  
    Just a heads up, this is going to conflict with RYA-414 because of changes to MongoDBRdfConfiguration.java.


> Add the ability use the MongoDB aggregation pipeline to evaluate simple SPARQL expressions
> ------------------------------------------------------------------------------------------
>
>                 Key: RYA-416
>                 URL: https://issues.apache.org/jira/browse/RYA-416
>             Project: Rya
>          Issue Type: New Feature
>            Reporter: Jesse Hatfield
>            Assignee: Jesse Hatfield
>
> MongoDB provides the [aggregation pipeline framework|https://docs.mongodb.com/manual/core/aggregation-pipeline/] for multi-stage data processing. Currently, the query engine invokes this framework to apply individual statement patterns (using a "$match" expression for each and iterating through the results), then applies higher-level query operations (join, filter, select, project, etc) client-side.
> In principle, those high-level query operations could be rewritten as aggregation pipeline stages as well ($group, $match, $project, etc). This would allow more query evaluation logic to be executed by the MongoDB server itself, enabling server-side optimization. This could be used as a general query optimization, but would additionally be useful for any tool that only needed to write query results back to the server: adding a write step to the end of the resulting pipeline could obviate the need to communicate individual results to the client at all.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)