TestNamedGraphs (Blazegraph Database Platform 2.1.5 API)

java.lang.Object
- junit.framework.Assert
- - junit.framework.TestCase
  - - junit.framework.TestCase2
    - - com.bigdata.bop.engine.AbstractQueryEngineTestCase
      - com.bigdata.rdf.sparql.ast.AbstractASTEvaluationTestCase
        
        com.bigdata.rdf.sparql.ast.eval.AbstractDataAndSPARQLTestCase
        
        com.bigdata.rdf.sparql.ast.eval.AbstractDataDrivenSPARQLTestCase
        
        com.bigdata.rdf.sparql.ast.eval.TestNamedGraphs

All Implemented Interfaces:

junit.framework.Test
```
public class TestNamedGraphs
extends AbstractDataDrivenSPARQLTestCase
```
Test suite for named and default graph stuff.

Author:

Bryan Thompson

Nested Class Summary
- Nested classes/interfaces inherited from class com.bigdata.rdf.sparql.ast.eval.AbstractDataDrivenSPARQLTestCase
  AbstractDataDrivenSPARQLTestCase.TestHelper, AbstractDataDrivenSPARQLTestCase.UpdateTestHelper
- Nested classes/interfaces inherited from class com.bigdata.rdf.sparql.ast.eval.AbstractDataAndSPARQLTestCase
  AbstractDataAndSPARQLTestCase.AbsHelper
- Nested classes/interfaces inherited from class junit.framework.TestCase2
  TestCase2.MyProperties, TestCase2.RandomType

Field Summary
- Fields inherited from class com.bigdata.rdf.sparql.ast.AbstractASTEvaluationTestCase
  baseURI, store, valueFactory
- Fields inherited from class junit.framework.TestCase2
  _randomType

Constructor Summary

Constructors
Constructor and Description

TestNamedGraphs()

TestNamedGraphs(String name)

Constructors
Constructor and Description
`TestNamedGraphs()`
`TestNamedGraphs(String name)`

Method Summary

Methods
Modifier and Type	Method and Description
`void`	`test_8_2_1()` 8.2.1 Specifying the Default Graph
`void`	`test_8_2_3()` 8.2.3 Combining FROM and FROM NAMED
`void`	`test_8_3_1()` 8.3.1 Accessing Graph Names The following two graphs will be used in examples:
`void`	`test_8_3_2()` 8.3.2 Restricting by Graph IRI The following two graphs will be used in examples:
`void`	`test_8_3_3()` 8.3.3 Restricting Possible Graph IRIs The following two graphs will be used in examples:
`void`	`test_default_graph_joins_01a()` One graph in the defaultGraphs set, but the specified graph has no data.
`void`	`test_default_graph_joins_01b()` The data set is not specified.
`void`	`test_default_graph_joins_01c()` Two graphs (c1,c2) are used.
`void`	`test_default_graph_joins_01d()` Named graph query finds everyone who loves someone and the graph in which that relationship was asserted.
`void`	`test_default_graph_joins_01e()` Named graph query finds everyone who loves someone and the state in which they live.
`void`	`test_default_graph_joins_01f()` Named graph query finds everyone who loves someone and the graph in which that relationship was asserted, and the state in which they live.
`void`	`test_named_graphs_ticket_359()` Unit test for case where there is a single named group which will be visited by the query.
`void`	`test_named_graphs_ticket_888()` Note: This is a duplicate of	`void`	`test_named_graphs_ticket_888b()` Unit test of a work around for `test_named_graphs_ticket_888()`.
`void`	`test_namedGraphs_01a()` A series of quads mode unit tests for named and default graph query of a data set containing a single triple.
`void`	`test_namedGraphs_01b()` This version of the query specifies a FROM clause and hence causes the `Dataset` to become non-`null` but does not specify any FROM NAMED clauses.
`void`	`test_namedGraphs_01c()`
`void`	`test_namedGraphs_01d()`

Methods inherited from class com.bigdata.rdf.sparql.ast.AbstractASTEvaluationTestCase
assertSameAST, asSet, asSet, asSet, asSet, asSet, enableDeleteMarkersInIndes, getBOpContext, getProperties, getStore, makeIV, setUp, tearDown

Methods inherited from class com.bigdata.bop.engine.AbstractQueryEngineTestCase
assertSameSolutions, assertSameSolutions, assertSameSolutions, assertSameSolutionsAnyOrder, assertSameSolutionsAnyOrder, assertSameSolutionsAnyOrder, assertSameSolutionsAnyOrder, assertSameSolutionsAnyOrder, assertSameSolutionsAnyOrder, compareGraphs, compareTupleQueryResults, diff

Methods inherited from class junit.framework.TestCase2
assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEqualsWithinUlps, assertSameArray, assertSameArray, assertSameBigDecimal, assertSameBigDecimal, assertSameBigInteger, assertSameBigInteger, assertSameIterator, assertSameIterator, assertSameIteratorAnyOrder, assertSameIteratorAnyOrder, assertSameValue, assertSameValue, assertZeroUlps, assertZeroUlps, fail, getInnerCause, getNormalInt, getProjectBuildPath, getRandomObject, getRandomObject, getRandomOrder, getRandomString, getTestInputStream, getTestResource, getTestResource, getUlps, getUlps, isDEBUG, isDEBUG, isINFO, isINFO, isInnerCause, logProperties

Methods inherited from class junit.framework.TestCase
assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, countTestCases, createResult, fail, fail, failNotEquals, failNotSame, failSame, format, getName, run, run, runBare, runTest, setName, toString

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

- Constructor Detail
  - TestNamedGraphs
```
public TestNamedGraphs()
```
  - TestNamedGraphs
```
public TestNamedGraphs(String name)
```
- Method Detail
  - test_namedGraphs_01a
```
public void test_namedGraphs_01a()
                          throws Exception
```
    A series of quads mode unit tests for named and default graph query of a data set containing a single triple.
    
    Throws:
    
    Exception
  - test_namedGraphs_01b
```
public void test_namedGraphs_01b()
                          throws Exception
```
    This version of the query specifies a FROM clause and hence causes the Dataset to become non-null but does not specify any FROM NAMED clauses. However, this query (like all the others in this series) is only querying the named graphs.
    Note: The correct result for this query should be NO solutions. This is one of the cases covered by the DAWG/TCK graph-02 and graph-04 tests. One of those tests verifies that when the data is from the default graph and the query is against the named graphs then there are no solutions. The other test verifies that the opposite is also true - that when the data are from the named graphs and the query is against the default graph that there are no solutions.
    
    Throws:
    
    Exception
  - test_namedGraphs_01c
```
public void test_namedGraphs_01c()
                          throws Exception
```
    Throws:
    
    Exception
  - test_namedGraphs_01d
```
public void test_namedGraphs_01d()
                          throws Exception
```
    Throws:
    
    Exception
  - test_8_2_1
```
public void test_8_2_1()
                throws Exception
```
    8.2.1 Specifying the Default Graph
    Each FROM clause contains an IRI that indicates a graph to be used to form the default graph. This does not put the graph in as a named graph.
    In this example, the RDF Dataset contains a single default graph and no named graphs:
```
 # Default graph (stored at http://example.org/foaf/aliceFoaf)
```
    Throws:
    
    Exception
  - test_8_2_3
```
public void test_8_2_3()
                throws Exception
```
    8.2.3 Combining FROM and FROM NAMED
    The FROM clause and FROM NAMED clause can be used in the same query.
```
 # Default graph (stored at http://example.org/dft.ttl)
```
    Throws:
    
    Exception
  - test_8_3_1
```
public void test_8_3_1()
                throws Exception
```
    8.3.1 Accessing Graph Names The following two graphs will be used in examples:
```
 # Named graph: http://example.org/foaf/aliceFoaf
```
    Throws:
    
    Exception
  - test_8_3_2
```
public void test_8_3_2()
                throws Exception
```
    8.3.2 Restricting by Graph IRI The following two graphs will be used in examples:
```
 # Named graph: http://example.org/foaf/aliceFoaf
```
    Throws:
    
    Exception
  - test_8_3_3
```
public void test_8_3_3()
                throws Exception
```
    8.3.3 Restricting Possible Graph IRIs The following two graphs will be used in examples:
```
 # Named graph: http://example.org/foaf/aliceFoaf
```
    Throws:
    
    Exception
  - test_default_graph_joins_01a
```
public void test_default_graph_joins_01a()
                                  throws Exception
```
    One graph in the defaultGraphs set, but the specified graph has no data. There should be no solutions.
    
    Throws:
    
    Exception
  - test_default_graph_joins_01b
```
public void test_default_graph_joins_01b()
                                  throws Exception
```
    The data set is not specified. The query will run against the "default" defaultGraph. For Sesame, I am assuming that the query is run against the RDF merge of all graphs, including the null graph. Rather than expanding the access path, we put a distinct triple filter on the access path. The filter will strip off the context information and filter for distinct (s,p,o).
    Note: In this case there is a duplicate solution based on the duplicate (john,loves,mary) triple which gets filtered out.
    
    Throws:
    
    Exception
  - test_default_graph_joins_01c
```
public void test_default_graph_joins_01c()
                                  throws Exception
```
    Two graphs (c1,c2) are used. There should be one solution.
    There is a second solution if c4 is considered, but it should not be since it is not in the default graph.
    If you are getting an extra (john,mark,paul) solution then the default graph access path is not enforcing "DISTINCT SPO" semantics.
    
    Throws:
    
    Exception
  - test_default_graph_joins_01d
```
public void test_default_graph_joins_01d()
                                  throws Exception
```
    Named graph query finds everyone who loves someone and the graph in which that relationship was asserted.
    Note: There is an additional occurrence of the relationship in [c4], but the query does not consider that graph and that occurrence should not be matched.
    Note: there is a statement duplicated in two of the named graphs (john,loves,mary) so we can verify that both occurrences are reported.
    Note: This query DOES NOT USE JOINS. See the next example below for one that does.
    
    Throws:
    
    Exception
  - test_default_graph_joins_01e
```
public void test_default_graph_joins_01e()
                                  throws Exception
```
    Named graph query finds everyone who loves someone and the state in which they live. Each side of the join is drawn from one of the two named graphs (the graph variables are bound).
    
    Throws:
    
    Exception
  - test_default_graph_joins_01f
```
public void test_default_graph_joins_01f()
                                  throws Exception
```
    Named graph query finds everyone who loves someone and the graph in which that relationship was asserted, and the state in which they live.
    Note: There is an additional occurrence of the relationship in [c4], but the query does not consider that graph and that occurrence should not be matched.
    Note: there is a statement duplicated in two of the named graphs (john,loves,mary) so we can verify that both occurrences are reported.
    Note: This test case can fail if the logic is leaving [c] unbound when it should be restricting [c] to the specific graphs in the FROM NAMED clauses.
    
    Throws:
    
    Exception
  - test_named_graphs_ticket_359
```
public void test_named_graphs_ticket_359()
                                  throws Exception
```
    Unit test for case where there is a single named group which will be visited by the query. In this case, the decision tree says that we should bind the context position to the IV for that graph in order to restrict the query to exactly the desired graph (rather than using an expander pattern). However, the graph variable also needs to become bound in the query solutions. If we simply replace the graph variable with a constant, then the as-bound value of the graph variable will not be reported in the result set.
    
    Throws:
    
    Exception
    See Also:
    https://sourceforge.net/apps/trac/bigdata/ticket/359
  - test_named_graphs_ticket_888
```
public void test_named_graphs_ticket_888()
                                  throws Exception
```
    Note: This is a duplicate of Throws:
    Exception
    See Also:
    test_named_graphs_ticket_888b
    
    public void test_named_graphs_ticket_888b() throws Exception
    
    Unit test of a work around for test_named_graphs_ticket_888().
    
    Throws:
    
    Exception
    See Also:
    
    Overview
    
    Package
    
    Class
    
    Use
    
    Tree
    
    Deprecated
    
    Index
    
    Help
    - Prev Class
    - Next Class
    - Frames
    - No Frames
    - All Classes
    Summary:
    
    Nested |
    
    Field |
    
    Constr |
    
    Method
    
    Detail:
    
    Field |
    
    Constr |
    
    Method
    Copyright © 2006–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.

Class TestNamedGraphs

Nested Class Summary

Nested classes/interfaces inherited from class com.bigdata.rdf.sparql.ast.eval.AbstractDataDrivenSPARQLTestCase

Nested classes/interfaces inherited from class com.bigdata.rdf.sparql.ast.eval.AbstractDataAndSPARQLTestCase

Nested classes/interfaces inherited from class junit.framework.TestCase2

Field Summary

Fields inherited from class com.bigdata.rdf.sparql.ast.AbstractASTEvaluationTestCase

Fields inherited from class junit.framework.TestCase2

Constructor Summary

Method Summary

Methods inherited from class com.bigdata.rdf.sparql.ast.AbstractASTEvaluationTestCase

Methods inherited from class com.bigdata.bop.engine.AbstractQueryEngineTestCase

Methods inherited from class junit.framework.TestCase2

Methods inherited from class junit.framework.TestCase

Methods inherited from class java.lang.Object

Constructor Detail

TestNamedGraphs

TestNamedGraphs

Method Detail

test_namedGraphs_01a

test_namedGraphs_01b

test_namedGraphs_01c

test_namedGraphs_01d

test_8_2_1

test_8_2_3

test_8_3_1

test_8_3_2

test_8_3_3

test_default_graph_joins_01a

test_default_graph_joins_01b

test_default_graph_joins_01c

test_default_graph_joins_01d

test_default_graph_joins_01e

test_default_graph_joins_01f

test_named_graphs_ticket_359

test_named_graphs_ticket_888

test_named_graphs_ticket_888b