Web This site Trusted
30 result(s) for “if cram site digginginthedirt sin blogspot com site phoenix apache org site:phoenix.apache.org” of 36 matched · 566 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.
Did you mean if cam site digginginthedirt sin blogspot com site phoenix apache org site:phoenix.apache.org?
Freshness: newest result fetched 24 d ago · median age of these results 24 d · 29 of 30 carry a fetch time
com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/trace/TraceReader
from the top result below
https://phoenix.apache.org/llms-full.txt
# Phoenix Omid Transaction Manager (/docs/addons/phoenix-omid-transaction-manager) The Apache Omid podling has recently decided to graduate as a sub-project of Apache Phoenix
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
HBase as its backing store
Apache Phoenix is fully integrated with other Hadoop products such as Spark, Hive, Pig, Flume, and MapReduce
https://phoenix.apache.org/docs/features/secondary-indexes
Concepts, setup, consistency guarantees, and tooling for Phoenix secondary indexes
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
A default HBase deployment already includes a Metrics2 configuration, so Phoenix Metrics2 config can either replace the existing file (if you do not have custom settings) or be merged into your existing Metrics2 configuration file
https://phoenix.apache.org/
Apache Phoenix, Phoenix, Apache, the Apache Phoenix logo and the ASF logo are either registered trademarks or trademarks of the Apache Software Foundation
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/installation
If you'd rather use a client GUI to interact with Phoenix, download and install SQuirrel
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/phoenix-sync-table
PhoenixSyncTable Tool
Detect data divergence between a source and a target Phoenix table across two HBase clusters via a chunked hash comparison driven by MapReduce
https://phoenix.apache.org/docs/faq
COM;keytab=/etc/security/keytabs/phoenix
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/metrics
enabled to true/false in the client side 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/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/functions
Please see the Data Type reference guide about how Apache Phoenix presently defines the DATE datatype
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/statistics-collection
How Phoenix collects and uses guidepost statistics for query parallelization, with commands and configuration
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/views
Note that until PHOENIX-1499 gets implemented, an INDEX over a VIEW is only maintained if the updates are made through the VIEW (as opposed to through the underlying TABLE)
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/joins
Phoenix join support, join execution strategies, optimization techniques, and configuration for hash and sort-merge joins
https://phoenix.apache.org/docs/features/segment-scan
The number of segments returned is min(N, num_regions):
If N <= num_regions, Phoenix bundles consecutive regions together so you get exactly N segments
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/subqueries
Use IN/EXISTS/comparison subqueries, correlated subqueries, row subqueries, and derived tables in Phoenix
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/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
ON DUPLICATE KEY for atomic row-level updates in Phoenix, with examples and limitations