Web This site Trusted
30 result(s) for “if can site www collinear com site www inter com to site hbase apache org site:phoenix.apache.org” of 37 matched · 1418 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 · 29 of 30 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/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/user-defined-functions
Add the following parameters to hbase-site
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/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/features/bulk-loading
To load CSV data, provide connection information for your HBase cluster, the target table name, and one or more CSV file paths
https://phoenix.apache.org/docs/features/tracing
You can modify this to set your own custom classes as well, if you have them
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/salted.html
rowKeyOrderSaltedTable=true in hbase-site
https://phoenix.apache.org/docs/faq
So if you stored integers by HBase native API and want to access them by Phoenix, make sure that all your data types are UNSIGNED types
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/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/grammar
The list of columns is optional and if not present, the values will map to the column in the order they are declared in the schema
https://phoenix.apache.org/docs/installation
jar to the classpath of all HBase region servers and masters, and remove any previous version
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/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/features/namespace-mapping
0 onward, users can map Phoenix schemas to HBase namespaces so that any table created with a schema is created in the corresponding HBase namespace
https://phoenix.apache.org/docs/explain-plan
To get hold of the info, you can use corresponding columns in the result set returned by the explain plan statement
https://phoenix.apache.org/docs/features/views
This is important in HBase as there are limits to the number of regions which HBase can manage
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
View TTL
Per-view retention on top of a shared base table — different views can age data out on different schedules without splitting the table
https://phoenix.apache.org/docs/features/atomic-upsert
This feature provides a superset of the HBase Increment and CheckAndPut functionality to enable atomic upserts
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
useCurrentTime
An advanced server-side parameter that, if true, causes the current time on the server-side to be used as the timestamp of rows in the statistics table when background tasks such as compactions or splits occur
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
https://phoenix.apache.org/docs/features/change-data-capture
A partition isn't an abstract shard — it corresponds to a specific HBase region of the data table at a point in time, and it has a finite lifetime: it's born when the region is created (or as the result of a split/merge) and it's closed when that region itself splits or merges into something new