We're updating the issue view to help you get more done. 

Recent changes in createLiteral have broken TupleResultBuilder in Workbench

Description

I believe the issue is a (now) incorrect assumption in TupleResultBuilder.outputNamedResult(String, Object) that the Object parameter will be something convertible to a Literal. When the parameter is a URL, the call to Literals.createLiteralOrFail(ValueFactory, Object) cannot handle it. The solution is likely to handle the URL case separately in TupleResultBuilder.outputNamedResult(String, Object).

Environment

None

Status

Assignee

Dale W. Visser

Reporter

Dale W. Visser

Labels

None

Components

Fix versions

Affects versions

2.7.0-beta2

Priority

Blocker