Using secondary indexes for accessing tables

Hi, I am investigating the possibility of using Apache Calcite as a cost-based optimizer for Apache Ignite project [1]. Apache Calcite looks a very powerful and versatile tool for the such kind of tasks. I've started this investigation a couple days ago - read docs, played with examples, expl

Re: Using secondary indexes for accessing tables

Roman Kondakov, I didn’t look into your use case details, but the secondary indexes may be used mainly for 2 scenarios: 1. Table index scan 2. The dim table join (key look up) Calcite does not support secondary indexes metadata yet, or even (indexes). But I think you can extend it with the Meta

Re: Using secondary indexes for accessing tables

See [1], a talk I gave with Maryann Xue about optimizing queries for Phoenix for secondary indexes. We modeled them as materialized views that are sorted projects. Julian [1] https://www.slideshare.net/julianhyde/costbased-query-optimization-in-apache-phoenix-using-apache-calcite