Web This site Trusted
30 result(s) for “if com site stanfield com site www inter com to site hbase apache org site:phoenix.apache.org” of 37 matched · 914 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 · 29 of 30 carry a fetch time
Set up a system to use transactions in Phoenix with the following steps: Add the following config to your client-side `hbase-site
from the top result below
https://phoenix.apache.org/llms-full.txt
## Entity Class Suppose we have the following `TestClass` we want to query in our data store: ```java // class must be annotated with Entity import com
https://phoenix.apache.org/docs/features/user-defined-functions
Add the following parameters to hbase-site
https://phoenix.apache.org/docs/features/query-server
Metrics can be filtered based on certain tags, which can be configured by the property specified in hbase-site
https://phoenix.apache.org/docs/features/secondary-indexes
At read time, Phoenix will select the index table to use that will produce the fastest query time and directly scan it just like any other HBase table
https://phoenix.apache.org/docs
Apache Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates those scans to produce regular JDBC result sets
https://phoenix.apache.org/docs/features/bulk-loading
You should use:
HADOOP_CLASSPATH=$(hbase mapredcp):/path/to/hbase/conf hadoop jar phoenix-<version>-client
https://phoenix.apache.org/docs/features/tracing
Phoenix leverages Cloudera's HTrace library to integrate with HBase tracing utilities
https://phoenix.apache.org/
1
SQL Support
Phoenix takes your SQL query, compiles it into HBase scans, and orchestrates execution to produce JDBC result sets
https://phoenix.apache.org/docs/features/transactions
Set up a system to use transactions in Phoenix with the following steps:
Add the following config to your client-side hbase-site
https://phoenix.apache.org/docs/faq
COM;keytab=/etc/security/keytabs/phoenix
https://phoenix.apache.org/docs/contributing
If you're unsure whether certain behavior in Phoenix is a bug, please send a mail to the user mailing list to check
https://phoenix.apache.org/docs/grammar
Example
CREATE FUNCTION my_reverse(varchar) returns varchar as 'com
https://phoenix.apache.org/salted.html
rowKeyOrderSaltedTable=true in hbase-site
https://phoenix.apache.org/docs/features/storage-formats
These defaults can be overridden by setting the following config value in hbase-site
https://phoenix.apache.org/docs/features/high-availability
enabledfalse — set true in the source cluster's hbase-site
https://phoenix.apache.org/docs/features/metrics
enabled to true/false in the client side hbase-site
https://phoenix.apache.org/docs/installation
If you'd rather use a client GUI to interact with Phoenix, download and install SQuirrel
https://phoenix.apache.org/docs/features/phoenix-sync-table
The tool is conceptually similar to HBase's HashTable/SyncTable pair but is Phoenix-aware (honors tenant id, indexes, the column-encoding scheme, and a bounded time range via --from-time/--to-time) and runs as a single MapReduce job, writing results directly to a Phoenix table instead of staging hashes in HDFS between
https://phoenix.apache.org/docs/datatypes
The purpose of this type is to map to existing HBase data that was serialized using this HBase utility method
https://phoenix.apache.org/docs/features/namespace-mapping
Enable Phoenix schema-to-namespace mapping in HBase, including configuration, migration, and behavior by table type
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
https://phoenix.apache.org/docs/features/views
The standard SQL view syntax (with some limitations) is now supported by Phoenix to enable multiple virtual tables to all share the same underlying physical HBase table
https://phoenix.apache.org/docs/features/row-size
ROW_SIZE() and RAW_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
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/atomic-upsert
To support atomic upsert, an optional ON DUPLICATE KEY clause, similar to the MySQL syntax, has been incorporated into the UPSERT VALUES command as of Phoenix 4
https://phoenix.apache.org/docs/features/segment-scan
Segment Scan turns a Phoenix table into N contiguous, non-overlapping key ranges that you can hand out to a pool of workers to drive a parallel full-table scan
https://phoenix.apache.org/docs/features/statistics-collection
Phoenix breaks up queries into multiple scans and runs them in parallel to reduce latency
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/conditional-ttl
"
If retention is a flat duration that applies uniformly to all rows, use the regular time-based TTL property
https://phoenix.apache.org/docs/features/phoenix-row-timestamp
It's effectively the row's last-modified time, available on any Phoenix table without you having to declare or manage a timestamp column yourself