Web This site Trusted
30 result(s) for “okapi bm25 site www eyespy cy site www be cy site phoenix apache org site:phoenix.apache.org” of 48 matched · 918 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 23 d ago · median age of these results 23 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
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/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/docs/features/secondary-indexes
Concepts, setup, consistency guarantees, and tooling for Phoenix secondary indexes
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/features/metrics
enabled to true/false in the client side 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/salted.html
rowKeyOrderSaltedTable=true in hbase-site
https://phoenix.apache.org/docs/installation
Download and expand the latest phoenix-hbase-[hbase
https://phoenix.apache.org/docs/array-type
Use JDBC ARRAY columns in Phoenix, including DDL, inserts, indexing syntax, and built-in array functions
https://phoenix.apache.org/docs/contributing
Eclipse code formatting settings and import order settings (which can also be imported into Intellij IDEA) are available in the dev directory of the Phoenix codebase
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/functions
Please see the Data Type reference guide about how Apache Phoenix presently defines the DATE datatype
https://phoenix.apache.org/docs/faq
getConnection("jdbc:phoenix:[zookeeper quorum hosts]");
stmt = con
https://phoenix.apache.org/docs/grammar
Use the ON DUPLICATE KEY clause (available in Phoenix 4
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/views
Updates made through the underlying TABLE or the parent VIEW will not be reflected in the index (PHOENIX-1499)
https://phoenix.apache.org/docs/features/phoenix-row-timestamp
PHOENIX_ROW_TIMESTAMP()
Read the per-row last-modified timestamp Phoenix maintains automatically — usable in projections, predicates, and indexes for fast time-bounded reads
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/ttl
Phoenix supports per-row time-to-live (TTL) so that rows can be expired and removed without an application-issued DELETE
https://phoenix.apache.org/docs/features/table-sampling
Use TABLESAMPLE in Phoenix for Bernoulli-style sampling, with performance notes, repeatability behavior, and tuning guidance
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/subqueries
Region);
Phoenix optimizes such queries by rewriting them into equivalent join queries so that the inner query only needs to be executed once instead of once per outer row
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