[ 
https://issues.apache.org/jira/browse/CALCITE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181919#comment-15181919
 ] 

Michael Mior commented on CALCITE-1104:
---------------------------------------

While trying to put a reasonable set of tests together, I encountered the 
following warning that prevents Calcite from using a materialized view which 
includes "IS NOT NULL" and a query which tests the same column against a string 
constant

[main] WARN  - Support for checking =(CAST($2):CHAR(3) CHARACTER SET 
"ISO-8859-1" COLLATE "ISO-8859-1$en_US$primary", 'fOGctyIDES') => IS NOT 
NULL($2) is not there

Any ideas how this can be resolved? It seems like deciding that a non-null 
string constant is not null should be trivial but I'm sure I'm missing some 
complexities.



> Materialized view support for Cassandra adapter
> -----------------------------------------------
>
>                 Key: CALCITE-1104
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1104
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Michael Mior
>            Assignee: Julian Hyde
>            Priority: Minor
>
> I managed to get support for a subset of Cassandra [materialized 
> views|https://www.datastax.com/dev/blog/new-in-cassandra-3-0-materialized-views].
>  ( Thanks owed to some hints from [~maryannxue]!)
> The one thing I noticed so far which is not supported is UUID literals in the 
> WHERE clauses in the Cassandra view definition. However, I don't think that's 
> a common use case. The adapter will log a warning if it encounters a view 
> that can't be processed. At the very least, the view will be exposed as a 
> table to Calcite (it wasn't in the previous version of the adapter).
> As per [CALCITE-1101|https://issues.apache.org/jira/browse/CALCITE-1101], 
> there is probably a better way to hook in and add these views. I thought I 
> would still put this up for now. I'd still like to add some tests before 
> considering this viable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to