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 2016/11/22 03:23:59 UTC
[jira] [Created] (RYA-223) LeftJoin Column Visibility Bug in Rya
Fluo App
Caleb Meier created RYA-223:
-------------------------------
Summary: LeftJoin Column Visibility Bug in Rya Fluo App
Key: RYA-223
URL: https://issues.apache.org/jira/browse/RYA-223
Project: Rya
Issue Type: Bug
Affects Versions: 3.2.10
Reporter: Caleb Meier
Assignee: Caleb Meier
Fix For: 3.2.10
The column visibilities for LeftJoin results in the Rya Fluo App are not being handled correctly. For a given query Q1, if the BindingSet [x = Bob, y = Dog] has visibility v_1 is LeftJoined with the BindingSet [x=Bob, z = Cat] with visibility v_2, the resulting BindingSet [x = Bob, y = Dog, z = Cat] with visibility v_1&v_2 is written to Fluo. In the event that a user with authorization v_1 issues the query Q1 and uses PCJs, he will not see the result [x = Bob, y = Dog, z = Cat] given that it has visibilities v_1&v_2. Given that the query is is a LeftJoin, the user should see the result [x = Bob, y = Dog] (which has visibility v_1), but he doesn't because this BindingSet is not being written. So when the LeftJoin for Q1 is evaluated using BindingSets with different visibilities, the joined result (with concatenated visibilities) and the left BindingSet should be written to Fluo. So in the above example, the results [x = Bob, y = Dog, z = Cat] with visibility v_1&v_2 and [x = Bob, y = Dog] with visibility v_1 should be written to the Fluo table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)