Web This site Trusted
11 result(s) for “if can site basis com site row see part com site have apache org site:phoenix.apache.org” · 985 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 · 11 of 11 carry a fetch time
For example, the `jdbc:phoenix::::principal:/home/user/keytab` URL can be used to specify the kerberos principal and keytab, while using the default connection specified in hbase-site
from the top result below
https://phoenix.apache.org/llms-full.txt
Currently, it supports HBase integration through Apache Phoenix, and can be extended with other implementations
https://phoenix.apache.org/docs/features/secondary-indexes
In HBase, you have a single index that is lexicographically sorted on the primary row key
https://phoenix.apache.org/docs/faq
You can see in explain plan if Phoenix is using the index table
https://phoenix.apache.org/docs/grammar
Otherwise, data is buffered on the client and, if auto commit is on, committed in row batches as specified by the UpsertBatchSize connection property (or the phoenix
https://phoenix.apache.org/docs/features/conditional-ttl
Express row expiration as a SQL boolean expression evaluated against the row itself
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/phoenix-row-timestamp
If you have declared one, both mechanisms read/write the same underlying timestamp, so PHOENIX_ROW_TIMESTAMP() returns the value of the ROW_TIMESTAMP column for that row
https://phoenix.apache.org/docs/features/paged-queries
If the columns you supply in your row value constructor match in order the columns from your primary key (or from a secondary index), then Phoenix will be able to turn the row value constructor expression into the start row of your scan
https://phoenix.apache.org/docs/features/row-size
A query using either function reads more bytes per row than the same query without it, because the scan can no longer use empty-column / key-only / encoded-qualifier optimizations
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
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