Github user kaspersorensen commented on a diff in the pull request:

    https://github.com/apache/metamodel/pull/130#discussion_r79616005
  
    --- Diff: 
cassandra/src/test/java/org/apache/metamodel/cassandra/CassandraDataContextTest.java
 ---
    @@ -113,7 +114,7 @@ public void testSchemaAndSimpleQuery() throws Exception 
{
     
         @Test
         public void testWhereColumnEqualsValues() throws Exception {
    -        DataSet ds = 
dc.query().from(testTableName).select("id").and("title").where("id").isEquals(firstRowId)
    +        DataSet ds = 
dc.query().from(testTableName).select("id").and("title").where("title").isEquals(firstRowTitle)
    --- End diff --
    
    No but the query no longer represented a "filtered dataset" type query 
because it got optimized. In fact the new test method is identical to the old 
test method, except that the assertion of it being a `InMemoryDataSet` is there 
to show the different paths that the two queries take depending on what column 
is being filtered on.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to