You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@rya.apache.org by "Kevin Chilton (JIRA)" <ji...@apache.org> on 2016/08/04 18:26:20 UTC

[jira] [Updated] (RYA-107) Use RyaDetails table to Configure PrecomputedJoinUpdaters for PrecomputedJoinIndexer

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

Kevin Chilton updated RYA-107:
------------------------------
    Parent Issue: RYA-81  (was: RYA-105)

> Use RyaDetails table to Configure PrecomputedJoinUpdaters for PrecomputedJoinIndexer
> ------------------------------------------------------------------------------------
>
>                 Key: RYA-107
>                 URL: https://issues.apache.org/jira/browse/RYA-107
>             Project: Rya
>          Issue Type: Sub-task
>          Components: dao
>    Affects Versions: 3.2.10
>            Reporter: Caleb Meier
>            Assignee: Caleb Meier
>             Fix For: 3.2.10
>
>
> Currently Rya has only one update strategy for PrecomputedJoins, which is to use Fluo.  A Batch and a No_Update strategy need to implemented and integrated with the PrecomputedJoinIndexer.  The PrecomputedJoinIndexer should use the RyaDetails table to determine which update strategy to use - if at least one table for the Rya instance requires either a Fluo or Batch update strategy, then the PrecomputedJoinIndexer should utilize those updaters.



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