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 16:01:59 UTC
[jira] [Created] (RYA-224) Rya Fluo Application Visibility Join Bug
Caleb Meier created RYA-224:
-------------------------------
Summary: Rya Fluo Application Visibility Join Bug
Key: RYA-224
URL: https://issues.apache.org/jira/browse/RYA-224
Project: Rya
Issue Type: Bug
Affects Versions: 3.2.10
Reporter: Caleb Meier
Assignee: Caleb Meier
Fix For: 3.2.10
There is a bug in how the Rya Fluo application processes joins for BindingSet results with visibilities. When a new BindingSet join result is processed by the JoinObserver for a given node, it scans for results associated with the sibling node. When the triggering BindingSet has a visibility, there is currently a bug with how the scan prefix is formed to scan the sibling results. The visibility is incorrectly added to the String to form the prefix, leading to missed results in certain situations. Line 153 in JoinResultUpdater needs to be changed to remedy this problem. In particular, the "childBindingSetString" formed on that line needs to be split on the delimiter "\u0001" to remove the visibility appended to that String by the VisibilityBindingSetStringConverter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)