I think it makes sense to see what the actual overhead is of CBO before making the assumption it'll be so high that we need to have two code paths. I'm happy to provide thorough benchmarking and analysis when it reaches a testing phase.
I'm excited to see where this goes. I think it sounds very forward looking and opens up a lot of possibilities. Jon On Tue, Dec 12, 2023 at 4:25 PM guo Maxwell <cclive1...@gmail.com> wrote: > Nothing expresses my thoughts better than +1 > ，It feels like it means a lot to Cassandra. > > I have a question. Is it easy to turn off cbo's optimizer or by pass in > some way? Because some simple read and write requests will have better > performance without cbo, which is also the advantage of Cassandra compared > to some rdbms. > > > David Capwell <dcapw...@apple.com>于2023年12月13日 周三上午3:37写道： > >> Overall LGTM. >> >> >> On Dec 12, 2023, at 5:29 AM, Benjamin Lerer <ble...@apache.org> wrote: >> >> Hi everybody, >> >> I would like to open the discussion on the introduction of a cost based >> optimizer to allow Cassandra to pick the best execution plan based on the >> data distribution.Therefore, improving the overall query performance. >> >> This CEP should also lay the groundwork for the future addition of >> features like joins, subqueries, OR/NOT and index ordering. >> >> The proposal is here: >> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-39%3A+Cost+Based+Optimizer >> >> Thank you in advance for your feedback. >> >> >>
