Work on this is happening on JENA-500 as well as discussions on the dev@
list.
JENA-500 has just been marked resolved and initial bindings will be
applied before optimization. There is no change to existing successful
use - new cases are now enabled.
Andy
dev@ discussion:
Holger
Yes that more common case you've identified would be affected so switching
this optimizer off until we've resolved this is the way to go
Rob
On 8/4/13 6:05 PM, Holger Knublauch hol...@knublauch.com wrote:
On 8/3/2013 23:09, Andy Seaborne wrote:
Please file a JIRA for this and attach
On 8/3/2013 23:09, Andy Seaborne wrote:
Please file a JIRA for this and attach the test case.
Done.
It would also be good to find out why this case arises when other
cases when FILTER/unbound evaluation is detected have not arisen.
Maybe the situations are simply less common.
I have
On 02/08/13 11:34, Holger Knublauch wrote:
Hi,
I believe there is a regression bug somewhere between 2.7.2 and 2.10.2.
See test case which works green in the old version but fails on the
latest snapshot. I believe the cause is that
TransformFilterImplicitJoin.testSpecialCaseUnused() incorrectly
Hi,
I believe there is a regression bug somewhere between 2.7.2 and 2.10.2.
See test case which works green in the old version but fails on the
latest snapshot. I believe the cause is that
TransformFilterImplicitJoin.testSpecialCaseUnused() incorrectly assumes
it can ignore the whole query
Holger
This is down to a new optimizer in 2.10.2, however that optimizer is based
off an existing optimizer that has been present in ARQ for a long time
which makes the same assumption.
So the following query would give the exact same behavior when used with
initial bindings:
ASK
{
FILTER
