pengzhiwei created CALCITE-2448:
---
Summary: AggregateProjectPullUpConstantsRule throws AssertionError
Key: CALCITE-2448
URL: https://issues.apache.org/jira/browse/CALCITE-2448
Project: Calcite
I
OK, I see.
Flink doesn't have support for JDBC yet.
Would need to look into that.
2018-08-02 21:35 GMT+02:00 Julian Hyde :
> Quidem can run on top of any JDBC data source (you just need to invoke
> with a connection factory by implementing a simple SPI). But it requires
> queries to terminate (i.
(Forgive the cross-posting. The sqlline dev list isn’t very active, and many of
the sqlline community are in the calcite community. Please reply to calcite dev
only.)
There have been a number of enhancements to sqlline recently[1] (thanks,
Sergey!). Is it time for a release of sqlline? Or shoul
If a JDBC driver is a problem, it shouldn’t be hard to mock a connection that
can create a statement that can describe itself and execute a query. Quidem
makes light use of JDBC.
> On Aug 6, 2018, at 10:33 AM, Fabian Hueske wrote:
>
> OK, I see.
> Flink doesn't have support for JDBC yet.
> Wou
It’s hard to automatically recommend a set of MVs from past queries. The design
space is just too large. But if you are designing MVs for interactive BI, you
can use the “lattice” model. This works because many queries will be
filter-join-aggregate queries on a star schema (i.e. a central fact t
You can find an overview of the work that has been done in Hive for
materialized view integration in the following link:
https://cwiki.apache.org/confluence/display/Hive/Materialized+views
Materialized views can be stored in external tables such as Druid-backed
tables too. Druid rules that in Calci
Regarding the SCOPE paper you reference. That was on my mind too (I went to the
talk at SIGMOD). A materialized view is created only if the same query is used
*textually identically* in different parts of the ETL process, so it is mainly
for optimizing batch jobs that are largely the same night
