Web This site Trusted
30 result(s) for “if can site digginginthedirt sin blogspot com site phoenix apache org site:phoenix.apache.org” of 41 matched · 741 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
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
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
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
Uncovered indexes lift that restriction — Phoenix can use a global index even when the query needs columns that aren't in it, by joining back to the data table on the server side to fetch the missing columns (PHOENIX-6458)
https://phoenix.apache.org/docs/features/bulk-loading
The first option can be done by running:
sudo -u hbase 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/faq
You can see in explain plan if Phoenix is using the index table
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
Request level metrics can be turned on/off for every Phoenix JDBC connection
https://phoenix.apache.org/docs/features/high-availability
enabledfalse — set true in the source cluster's hbase-site
https://phoenix.apache.org/salted.html
During a parallel scan across regions, Phoenix can use this property to perform a client-side merge sort
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/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/features/bson
The point of the type is not just to hold documents — it's that Phoenix can read, filter, and mutate individual fields on the server without the client ever deserializing the whole document
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/statistics-collection
can occur in Phoenix versions earlier than 4
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
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/joins
Phoenix will extract and sort multiple key parts from the join keys so that it can get the most accurate key hints/ranges possible for the parent table scan
https://phoenix.apache.org/docs/features/segment-scan
Segment Scan
Get N evenly-bucketed key ranges for a Phoenix table so a client can drive a parallel full-table scan
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 turns a Phoenix table into a stream of change events that downstream consumers can read using regular 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/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