4 ms·
this is accurate, thank you. You can try asof join: SELECT pickup_datetime, cab_type, trip_type, tempF, skyCover, windSpeed FROM trips ASOF JOIN weather; Thi
by bluestreak 6y ago
this is accurate, thank you.
You can try asof join:
SELECT pickup_datetime, cab_type, trip_type, tempF, skyCover, windSpeed FROM trips ASOF JOIN weather;
This joins 1.6B to 130K roughly.
Generally we provide both row and column based access despite being column store. So anything a traditional database does we can do too.
- sa46 6y ago> Generally we provide both row and column based access despite being column store. So anything a traditional database does we can do too. Does quest DB use the same physical data layout for the row based access? My understanding was providing an entire row of data from a columnar file is expensive because you have to assemble the row from num_columns different slices of the columnar file.
- bluestreak 6y agoThe data layout is indeed the same for both cases. We don't assemble row as such. In QuestDB row is a collection of data addresses, each of which is calculated lazily using row_id and bitshift