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/08/22 20:18:00 UTC

[jira] [Closed] (RYA-281) Decouple PCJ Creation in RYA and Fluo

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

Caleb Meier closed RYA-281.
---------------------------
       Resolution: Fixed
    Fix Version/s: 3.2.11

> Decouple PCJ Creation in RYA and Fluo
> -------------------------------------
>
>                 Key: RYA-281
>                 URL: https://issues.apache.org/jira/browse/RYA-281
>             Project: Rya
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 3.2.10
>            Reporter: Caleb Meier
>            Assignee: Caleb Meier
>             Fix For: 3.2.11
>
>
> Currently PCJ creation in RYA and FLUO are coupled together.  That is, PCJ creation within RYA is currently a prerequisite for creating a PCJ in Fluo (you need to pass in a PCJ ID when creating the Fluo metadata, and that ID is used to read information about the RYA PCJ from RyaDetails).  In the past this was fine, but now we would like to be able to register a query with Fluo whose results are not necessarily being exported to a PCJ table. Another issue is that the RYA PCJ ID and the Fluo query ID don't align, which requires us to store the PCJ ID in the Fluo table so that the RYA Exporter can write results to the RYA PCJ table.  These two IDs should be the same.



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