def~query-type

Definition

Controls how def~tables are exposed to queries

Hudi supports the following views of stored data

• def~read-optimized-query

  Queries see the latest snapshot of the def~table as of a given commit / compaction def~instant-action; exposes only the base / columnar files in latest file slices to the queries and guarantees the same columnar query performance compared to a non-hudi columnar def~table.

  Following table summarizes the trade-offs between the different def~query-types.

  Trade-off	def~read-optimized-query	def~snapshot-query
  Data Latency	Higher	Lower
  Query Latency	Lower (raw base / columnar file performance)	Higher (merge  base / columnar file+ row based delta/log files)

• def~incremental-query

  Queries only see new records written to the def~table, since a given commit /delta-commit def~instant-action; effectively provides change streams to enable incremental data pipelines.

• Error rendering macro 'excerpt-include'

  No link could be created for 'def~realtime-view'.

Following table summarizes the trade-offs between the different def~query-types.

Related concepts

1. def~read-optimized-query
2. def~incremental-query
3. def~realtime-view
4. def~timeline
5. def~table
6. def~commit
7. def~table-type