Selections from materialized views my have different entity properties that impact generated queries. Remove noisy/expensive selection of ttl and write time until we need/use it for cache correctness properties (if ever).

src/main/java/net/helenus/core/operation/SelectOperation.java

@@ -133,12 +133,12 @@ public final class SelectOperation<E> extends AbstractFilterStreamOperation<E, S
     Objects.requireNonNull(materializedViewClass);
     HelenusEntity entity = Helenus.entity(materializedViewClass);
     this.alternateTableName = entity.getName().toCql();
-    this.allowFiltering = true;
+    this.props.clear();
-    return this;
+    entity
-  }
+        .getOrderedProperties()
-
+        .stream()
-  public SelectOperation<E> from(String alternateTableName) {
+        .map(p -> new HelenusPropertyNode(p, Optional.empty()))
-    this.alternateTableName = alternateTableName;
+        .forEach(p -> this.props.add(p));
     return this;
   }
 
@@ -243,6 +243,7 @@ public final class SelectOperation<E> extends AbstractFilterStreamOperation<E, S
                 + prop.getEntity().getMappingInterface());
       }
 
+      /* TODO: is this useful information to gather when caching?
       if (cached) {
         switch (prop.getProperty().getColumnType()) {
           case PARTITION_KEY:
@@ -261,6 +262,7 @@ public final class SelectOperation<E> extends AbstractFilterStreamOperation<E, S
             break;
         }
       }
+      */
     }
 
     if (entity == null) {

src/test/java/net/helenus/test/integration/core/views/MaterializedViewTest.java

@@ -70,7 +70,7 @@ public class MaterializedViewTest extends AbstractEmbeddedCassandraTest {
   public void testMv() throws Exception {
     session
         .select(Cyclist.class)
-        .<CyclistsByAge>from(CyclistsByAge.class)
+        .from(CyclistsByAge.class)
         .where(cyclist::age, eq(18))
         .sync();
   }