Web This site Trusted
18 result(s) for “okapi bm25 site hotchips pp site does apache org site phoenix apache org site:phoenix.apache.org” of 48 matched · page 2 · 837 ms
Scope: Nishi’s own index (our crawl + Common Crawl) — not the whole live web. Some sites block all automated crawlers (anti-bot walls), so their pages may be absent here even though we never filter lawful content.
Freshness: newest result fetched 24 d ago · median age of these results 24 d · 18 of 18 carry a fetch time
https://phoenix.apache.org/docs/features/skip-scan
How Phoenix Skip Scan uses key-range hints to efficiently skip non-matching row-key regions
https://phoenix.apache.org/docs/features/cursor
Use CURSOR statements in Phoenix to process query results in controlled row batches
https://phoenix.apache.org/docs/features/paged-queries
Phoenix supports standard SQL constructs to enable paged queries:
Row Value Constructors (RVC)
(4, 'foo', 3
https://phoenix.apache.org/docs/features/change-data-capture
Change Data Capture (CDC)
Query row-level change events on a Phoenix table using standard SQL — pull pre/post images and change deltas with bounded, resumable reads
https://phoenix.apache.org/docs/features/eventually-consistent-indexes
An eventually consistent global index behaves like a regular Phoenix global index at the SQL level — same DDL, same INCLUDE, same query planning — but Phoenix maintains it asynchronously instead of on the synchronous write path
https://phoenix.apache.org/docs/features/segment-scan
Segment Scan
Get N evenly-bucketed key ranges for a Phoenix table so a client can drive a parallel full-table scan
https://phoenix.apache.org/docs/features/row-timestamp-column
Row Timestamp Column
Map HBase row timestamps to a Phoenix primary-key column and use ROW_TIMESTAMP in table design and upserts
https://phoenix.apache.org/docs/features/view-ttl
A Phoenix view is a logical table that shares a single physical HBase table with its sibling views
https://phoenix.apache.org/docs/features/bson
Document Data: BSON
Store, query, filter, and atomically update Binary JSON (BSON) documents inside a Phoenix table — without round-tripping the document to the client
https://phoenix.apache.org/docs/features/conditional-ttl
Phoenix compaction: expired rows are physically removed by Phoenix's compaction during HBase region compactions
https://phoenix.apache.org/docs/features/multi-tenancy
Tenants open tenant-specific connections to Phoenix
https://phoenix.apache.org/docs/features/varbinary-encoded
FROM old_table; (Phoenix re-encodes the values into the new physical layout for you)
https://phoenix.apache.org/docs/quick-start
Check out my presentation for various existing and to-be-done Phoenix features to support your favorite HBase trick
https://phoenix.apache.org/docs/sequences
Create, configure, and use SQL sequences in Phoenix, including caching, cycling, and NEXT/CURRENT VALUE semantics
https://phoenix.apache.org/docs/fundamentals/performance-testing
If <userDefined>true</userDefined> is set, rule will only apply override when type and name match the column name in Phoenix
https://phoenix.apache.org/docs/features/dynamic-columns
Define and query late-bound dynamic columns in Phoenix when full schema cannot be declared upfront
https://phoenix.apache.org/docs/features/row-size
Built-in SQL functions that return the on-the-wire HBase byte footprint of a row — useful for hot-row diagnosis, capacity planning, and finding outliers directly from SQL.
ROW_SIZE() and RAW_ROW_SIZE() return the HBase byte footprint of
https://phoenix.apache.org/docs/explain-plan
When stats collection is not enabled or if for some reason Phoenix cannot provide the estimate information, the columns return null