[
https://issues.apache.org/jira/browse/CALCITE-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-1870.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.18.0
Fixed in
[b47413a1|http://git-wip-us.apache.org/repos/asf/calcite/commit/b47413a1].
Other things in that change:
* API changes to {{Lattice}}. Rename class {{Lattice.Node}} to {{LatticeNode}},
add sub-class {{LatticeRootNode}} that is immutable and has state that was
previously in {{Lattice}}. {{LatticeSuggester}} makes heavy use of
{{LatticeNode}}. Move column unique name into {{Column}}, and remove the
{{Lattice.uniqueColumnNames}} field.
* {{SqlImplementor}}: Translate simple RexNode to SQL without requiring
{{RelBuilder}}; {{SqlImplementor.Context}} is now static, but not all derived
classes are.
* {{DirectedGraph.toString}} sorts lists of vertices and edges.
* Add materialized views to documentation menu; tweak SQL formatting.
* In HepPlanner, rename {{noDAG}} to {{noDag}}.
Minor things:
* Don't add a query graph if it is cyclic.
* More concise descriptions of join graphs, and add FoodMart test case.
* Add a test based on TPC-DS.
* Make {{FoodMartQueryTest}} a top-level class, and add a test that runs
through all of its queries and suggests lattices.
* Fix a typo in {{UdfTest}}.
> Suggest lattices based on queries and data profiles
> ---------------------------------------------------
>
> Key: CALCITE-1870
> URL: https://issues.apache.org/jira/browse/CALCITE-1870
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Fix For: 1.18.0
>
>
> Create a tool that suggests lattices based on queries and data profiles. We
> already (see CALCITE-344) have a tool that suggests materialized views
> (tiles) within a lattice, so together, these tools would be able to create
> materialized views without a user having to create any kind of model.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
