[GitHub] incubator-rya pull request #135: Rya 144
GitHub user isper3at opened a pull request: https://github.com/apache/incubator-rya/pull/135 Rya 144 ## Description >What Changed? -Finished kchilton2's mongo based entity secondary indexer -updated to use meiercaleb's new query segment framework -added optimizer for the entity indexer ### Tests >Coverage? Added integration tests for the indexer Note: no assertions are performed ### Links [Jira](https://issues.apache.org/jira/browse/RYA-144) ### Checklist - [ ] Code Review - [ ] Squash Commits People To Reivew @meiercaleb @pujav65 You can merge this pull request into a Git repository by running: $ git pull https://github.com/isper3at/incubator-rya RYA-144 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-rya/pull/135.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #135 commit 2f71ae5ab8a519114a9fd3f9128f77b0374fc299 Author: Kevin ChiltonDate: 2016-09-16T22:22:54Z RYA-144 Mongo DB Entity index. commit 198f4189fafaae3e23d1b1e5f0914bba217f5919 Author: isper3at Date: 2016-11-02T15:36:51Z [WIP]RYA-144: Added optimizer commit 381c25e1f74bd49ba336d181eb981fc8ebed6f94 Author: Caleb Meier Date: 2016-12-13T20:26:29Z RYA-144-ExternalSetMatchingFramework commit e485858e3544f4cd630b3eacb75f56848325e748 Author: isper3at Date: 2016-12-19T19:24:25Z [WIP] repackage mvm -> org.apache commit bd9b581f7511772c4a26ae4e222e1d2dea465716 Author: isper3at Date: 2016-12-30T20:43:00Z Added tests for the entity optimizer and updated to use new segment framework --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (RYA-144) New Secondary Index: Smart URI
[ https://issues.apache.org/jira/browse/RYA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15788414#comment-15788414 ] ASF GitHub Bot commented on RYA-144: GitHub user isper3at opened a pull request: https://github.com/apache/incubator-rya/pull/135 Rya 144 ## Description >What Changed? -Finished kchilton2's mongo based entity secondary indexer -updated to use meiercaleb's new query segment framework -added optimizer for the entity indexer ### Tests >Coverage? Added integration tests for the indexer Note: no assertions are performed ### Links [Jira](https://issues.apache.org/jira/browse/RYA-144) ### Checklist - [ ] Code Review - [ ] Squash Commits People To Reivew @meiercaleb @pujav65 You can merge this pull request into a Git repository by running: $ git pull https://github.com/isper3at/incubator-rya RYA-144 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-rya/pull/135.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #135 commit 2f71ae5ab8a519114a9fd3f9128f77b0374fc299 Author: Kevin ChiltonDate: 2016-09-16T22:22:54Z RYA-144 Mongo DB Entity index. commit 198f4189fafaae3e23d1b1e5f0914bba217f5919 Author: isper3at Date: 2016-11-02T15:36:51Z [WIP]RYA-144: Added optimizer commit 381c25e1f74bd49ba336d181eb981fc8ebed6f94 Author: Caleb Meier Date: 2016-12-13T20:26:29Z RYA-144-ExternalSetMatchingFramework commit e485858e3544f4cd630b3eacb75f56848325e748 Author: isper3at Date: 2016-12-19T19:24:25Z [WIP] repackage mvm -> org.apache commit bd9b581f7511772c4a26ae4e222e1d2dea465716 Author: isper3at Date: 2016-12-30T20:43:00Z Added tests for the entity optimizer and updated to use new segment framework > New Secondary Index: Smart URI > -- > > Key: RYA-144 > URL: https://issues.apache.org/jira/browse/RYA-144 > Project: Rya > Issue Type: New Feature >Reporter: Kevin Chilton >Assignee: Andrew Smith > > This is intended primarily for the Mongo implementation of Rya. > A purpose of this is so that we can discover it though the SPARQL query > interface. > Suppose you have a star entity named 'David': > David is a person > david has an SSN > david has a birthday, > So a URI holding all of this information about David could look like this: > HTTP://Person=david=111-11-=20160101 > This makes it so that instead of using 3 joins it is only a scan. > -- > Current open pull request does not have SPARQL support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)