On Sun, Nov 15, 2015 at 8:47 PM, Sarnath <[email protected]> wrote: > For the experiment below, ES was almost 5x to 8x faster than > kylin. (60ms vs 240ms/450ms)... But then we use ES search REST interface > directly and compare that with kylin's REST interface. So I am not sure > about the SQL translation...overheads in kylin. >
The SQL planner can add significant overhead so such a comparison is pretty apples to oranges. Also, Kylin is premised on cubes not fitting in memory while ES is pretty optimistically assuming they will fit in memory. How do you handle queries that do indirect references to cubes (say by asking for a rollup by region when you only cubed by city)? And do you automatically decide which cubes to use?
