THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Controls how def~tables are exposed to queries
Excerpt | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Given such flexible and comprehensive layout of data and rich def~timeline, Hudi is able to support three different ways of querying a def~table, depending on its def~table-type
Hudi supports the following type of queries of stored data Excerpt Include | | def~read-optimized-query | def~read-optimized-query | |||||||||||||||||||||
Excerpt Include | def~incremental-query | def~incremental-query | ||||||||||||||||||||||
Excerpt Include | def~snapshot-query | def~snapshot-query | ||||||||||||||||||||||
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)
Related concepts
- def~read-optimized-query
- def~incremental-query
- def~snapshot-query
- def~timeline
- def~table
- def~commit
- def~table-type
...