History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-1003
Type: Task Task
Status: Open Open
Priority: Major Major
Assignee: Jeen Broekstra
Reporter: Jeen Broekstra
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Sesame

Investigate overlap between ExternalSet and BindingSetAssignment

Created: 23/May/12 01:17 AM   Updated: 07/Aug/12 10:13 AM
Component/s: Query Model
Affects Version/s: None
Fix Version/s: 2.7.0

Issue Links:
Related
This issue is related to:
SES-1002 Downgrade List<BindingSet> bindingSet... Major Resolved
 


 Description   
ExternalSet is a query model node implementation that for some reason is in the query evaluation package rather than the query model package. At first glance, there seems to be some overlap in functionality with BindingSetAssignment.

 All   Comments   Change History      Sort Order:
Comment by Alessandro Bollini [24/May/12 10:50 AM]
As an injection point, ExternalSet is certainly more flexible. as it may parameterize its results at evaluation time. Moving it to org.openrdf.query.algebra as a standard query node would make it the first option for such tasks.

Comment by Pointbreak [07/Aug/12 10:13 AM]
ExternalSet is used in Alibaba's optimistic repository and in uSeekM for dynamically injecting solutions into a running query. It's indeed more flexible than BindingSetAssignment, since BindingSetAssignment expects a fixed known set of solutions to inject. ExternalSet needs to be subclassed to actually do something (e.g. ExternalModel in Alibaba).

BindingSetAssignment could possibly haven been modelled as a subclass of ExternalSet. Likely Service (for federated services) could also have been modelled as a subclass of ExternalSet.