NishiSearch

Web This site Trusted

11 result(s) for “if can site digginginthedirt sin blogspot com site phoenix apache org site:phoenix.apache.org” of 41 matched · page 2 · 657 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 25 d · 11 of 11 carry a fetch time

Atomic Upsert

https://phoenix.apache.org/docs/features/atomic-upsert
Java applications using the Phoenix thick JDBC client can drive the same atomic-return semantics directly through typed methods on PhoenixStatement and PhoenixPreparedStatement, without putting RETURNING * in the SQL: executeAtomicUpdateReturnRow — returns the row state after the mutation (or the unchanged row when

Express row expiration as a SQL boolean expression evaluated against the

https://phoenix.apache.org/docs/features/conditional-ttl
Phoenix compaction: expired rows are physically removed by Phoenix's compaction during HBase region compactions

bin/pherf-standalone.py -h

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

Create, configure, and use SQL sequences in Phoenix, including caching

https://phoenix.apache.org/docs/sequences
Create, configure, and use SQL sequences in Phoenix, including caching, cycling, and NEXT/CURRENT VALUE semantics

TTL

https://phoenix.apache.org/docs/features/ttl
Phoenix supports per-row time-to-live (TTL) so that rows can be expired and removed without an application-issued DELETE

Row Timestamp Column

https://phoenix.apache.org/docs/features/row-timestamp-column
When upserting rows for a table with a row timestamp column (using UPSERT VALUES or UPSERT SELECT), you can explicitly provide the row timestamp value or let Phoenix set it automatically

Tenants open tenant-specific connections to Phoenix. These connections

https://phoenix.apache.org/docs/features/multi-tenancy
Tenants open tenant-specific connections to Phoenix

VARBINARY_ENCODED

https://phoenix.apache.org/docs/features/varbinary-encoded
FROM old_table; (Phoenix re-encodes the values into the new physical layout for you)

Historical Phoenix performance comparisons and feature-level

https://phoenix.apache.org/docs/fundamentals/performance
Historical Phoenix performance comparisons and feature-level improvements for scans, salting, and query execution

Use TABLESAMPLE in Phoenix for Bernoulli-style sampling, with

https://phoenix.apache.org/docs/features/table-sampling
Use TABLESAMPLE in Phoenix for Bernoulli-style sampling, with performance notes, repeatability behavior, and tuning guidance

compiling your SQL queries to native HBase scans

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