Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-426

IllegalArgumentException in com.bigdata.bop.Constant

    Details

      Description

      Some queries fail with an IllegalArgumentException, when a bound input value used in a filter expression does not match any value stored in the database. Stacktrace:

      Caused by: java.lang.IllegalArgumentException
      	at com.bigdata.bop.Constant.<init>(Constant.java:105)
      	at com.bigdata.rdf.sail.BigdataEvaluationStrategyImpl3.toBindingSet(BigdataEvaluationStrategyImpl3.java:952)
      	at com.bigdata.rdf.sail.BigdataEvaluationStrategyImpl3.doEvaluateNatively(BigdataEvaluationStrategyImpl3.java:905)
      	... 34 more
      

        Activity

        Hide
        gjdev gjdev added a comment -

        Sorry for the stacktrace above my comment, please ignore that, I can't edit the ticket...

        Show
        gjdev gjdev added a comment - Sorry for the stacktrace above my comment, please ignore that, I can't edit the ticket...
        Hide
        bryanthompson bryanthompson added a comment -

        Removed the stack trace from the top of the ticket.

        Show
        bryanthompson bryanthompson added a comment - Removed the stack trace from the top of the ticket.
        Hide
        bryanthompson bryanthompson added a comment -

        I've verified the issue. The code rewrites the "majoor" literal into a BigdataLiteralImpl with a null IV binding. This causes a runtime exception when there is an attempt to evaluate the query with that variable binding.

        I'm assigning this to MikeP to provide a fix.

        Show
        bryanthompson bryanthompson added a comment - I've verified the issue. The code rewrites the "majoor" literal into a BigdataLiteralImpl with a null IV binding. This causes a runtime exception when there is an attempt to evaluate the query with that variable binding. I'm assigning this to MikeP to provide a fix.
        Hide
        bryanthompson bryanthompson added a comment -

        The test case now runs without error. I have incorporated the unit test into the test suite to protect against regressions. No code changes were required so this was already fixed as a side-effect of some earlier changes.

        Committed revision r4614.

        Show
        bryanthompson bryanthompson added a comment - The test case now runs without error. I have incorporated the unit test into the test suite to protect against regressions. No code changes were required so this was already fixed as a side-effect of some earlier changes. Committed revision r4614.

          People

          • Assignee:
            bryanthompson bryanthompson
            Reporter:
            gjdev gjdev
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: