Merge pull request #1015: [proxima-direct-io-cassandra] fix USING TTL query construction

Author: je-ik

direct/io-cassandra/src/main/java/cz/o2/proxima/direct/io/cassandra/DefaultCqlFactory.java

@@ -272,7 +272,7 @@ private Optional<BoundStatement> elementDelete(StreamElement ingest) {
 
   @Override
   protected String createInsertStatement(StreamElement element) {
-    String ttlStatement = ttl > 0 ? ("USING TTL " + ttl + " ") : "";
+    String ttlStatement = ttl > 0 ? ("AND TTL " + ttl + " ") : "";
     if (element.getAttributeDescriptor().isWildcard()) {
       // use the first part of the attribute name
       String colName = toColName(element.getAttributeDescriptor());

direct/io-cassandra/src/test/java/cz/o2/proxima/direct/io/cassandra/DefaultCqlFactoryTest.java

@@ -212,7 +212,7 @@ public void testIngestWithTtl() {
     assertSame(bound, boundStatement.get());
     assertEquals(1, preparedStatement.size());
     assertEquals(
-        "UPDATE my_table USING TIMESTAMP ? USING TTL 86400 SET my_attribute=? WHERE hgw=?",
+        "UPDATE my_table USING TIMESTAMP ? AND TTL 86400 SET my_attribute=? WHERE hgw=?",
         preparedStatement.get(0));
   }