When using the BigdataSailConnection.evaluate method that accepts a BindingSet iteration I have observed the following behaviour:
When an input bindingset contains a value that is not backed by the database (has no termid) that will result in a ClassCastException. The same query (with the same binding-value) when using the overload does not show that behaviour.
Allthough this is not a huge issue to me: during normal operation our query evaluator probably won't stream non existent values into the evaluation. But there may be edge cases that make this a possibility, and they would ideally be handled a bit more graceful than with a ClassCastException.
Could you please give me your thoughts on this?