Details

    • Type: Bug
    • Status: Done
    • Priority: Highest
    • Resolution: Done
    • Affects Version/s: BIGDATA_RELEASE_1_5_0
    • Fix Version/s: None
    • Component/s: Bigdata RDF Database
    • Labels:
      None

      Description

      com.bigdata.rdf.sail.webapp.TestReificationDoneRightParser is not being executed from com.bigdata.rdf.sail.webapp.TestAll and when executed all tests fail.

      Why is this test suite failing? It was originally written to test the AST generated by parsing RDR SPARQL queries. Either fix it or remove it if we have appropriate coverage elsewhere.


      - BLZG-805 Migrate to openrdf 2.7
      - BLZG-25 Update openrdf 2.7 to 2.7.15
      - BLZG-1231 SPARQL* fails to recognize nested statement in object position

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        I have fixed some problems in the RDR parser test suite that were introduced by the PrefixDeclProcessor change to always inject the "well known" prefix declarations into a query. This probably dates back to the openrdf 2.7 migration (BLZG-805).

        At this point, one RDR parser tests fails. It has the following input:

            /**
             * A unit test when the triple reference pattern is a constant.
             * 
             * <pre>
             * prefix : <http://example.com/>
             * SELECT ?a {
             *    ?d ?e <<?a ?b ?c>> . 
             * }
             * </pre>
             * 
             * Should be translated as :
             * 
             * <pre>
             * SP(?a, ?b, ?c) as ?sid-1 .
             * SP(?d, ?e, ?-sid-1).
             * </pre>
             * 
             * Note that the SP for the first bound triple pattern will enforce the
             * semantics that the triple must exist in the data in order for the query
             * to succeed.
             */
        


        - See BLZG-805 Migrate to openrdf 2.7
        - See BLZG-25 Update openrdf 2.7 to 2.7.15

        Show
        bryanthompson bryanthompson added a comment - I have fixed some problems in the RDR parser test suite that were introduced by the PrefixDeclProcessor change to always inject the "well known" prefix declarations into a query. This probably dates back to the openrdf 2.7 migration ( BLZG-805 ). At this point, one RDR parser tests fails. It has the following input: /** * A unit test when the triple reference pattern is a constant. * * <pre> * prefix : <http://example.com/> * SELECT ?a { * ?d ?e <<?a ?b ?c>> . * } * </pre> * * Should be translated as : * * <pre> * SP(?a, ?b, ?c) as ?sid-1 . * SP(?d, ?e, ?-sid-1). * </pre> * * Note that the SP for the first bound triple pattern will enforce the * semantics that the triple must exist in the data in order for the query * to succeed. */ - See BLZG-805 Migrate to openrdf 2.7 - See BLZG-25 Update openrdf 2.7 to 2.7.15
        Hide
        bryanthompson bryanthompson added a comment -

        Partial fix for RDR parser test suite (enabled, runs, one failure).

        The one failure appears to be a problem with the SPARQL* parser extensions to the SPARQL parser. I.e., a grammar bug.

        Note that SPARQL* support in QUADS_DATA blocks for SPARQL UPDATE also appears to be broken per BLZG-1229

        Commit 4add76bddecd349e18c7220e846d2df0159a6e5f to rdr_tests branch.

        Show
        bryanthompson bryanthompson added a comment - Partial fix for RDR parser test suite (enabled, runs, one failure). The one failure appears to be a problem with the SPARQL* parser extensions to the SPARQL parser. I.e., a grammar bug. Note that SPARQL* support in QUADS_DATA blocks for SPARQL UPDATE also appears to be broken per BLZG-1229 Commit 4add76bddecd349e18c7220e846d2df0159a6e5f to rdr_tests branch.
        Hide
        bryanthompson bryanthompson added a comment -

        I re-enabled these tests several weeks ago. Today I went through an added them to the set of known bad tests so they are not failing CI builds.

        Show
        bryanthompson bryanthompson added a comment - I re-enabled these tests several weeks ago. Today I went through an added them to the set of known bad tests so they are not failing CI builds.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: