Web This site Trusted
30 result(s) for “okapi bm25 site hotchips pp site modes kb be site hbase apache org site:phoenix.apache.org” of 37 matched · 474 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 22 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
my_table (v) ASYNC
The map reduce job that populates the index table must be kicked off separately through the HBase command line like this:
${HBASE_HOME}/bin/hbase org
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/storage-formats
These defaults can be overridden by setting the following config value in hbase-site
https://phoenix.apache.org/salted.html
rowKeyOrderSaltedTable=true 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/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/installation
Download and expand the latest phoenix-hbase-[hbase
https://phoenix.apache.org/docs/faq
For example, to specify the HBase root ZNode, the ZooKeeper port must also be specified
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/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/grammar
HBase table and column configuration options may be passed through as key/value pairs to configure the HBase table as desired
https://phoenix.apache.org/docs/features/row-timestamp-column
Row Timestamp Column
Map HBase row timestamps to a Phoenix primary-key column and use ROW_TIMESTAMP in table design and upserts
https://phoenix.apache.org/docs/explain-plan
When ORDERED is used, the GROUP BY operation is applied to the leading part of the primary key constraint, which allows the aggregation to be done in place rather than keeping all distinct groups in memory on the server side
https://phoenix.apache.org/docs/features/views
Define updatable and read-only Phoenix views over shared HBase tables, including indexing behavior and limitations
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/quick-start
Check out my presentation for various existing and to-be-done Phoenix features to support your favorite HBase trick
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/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
Given that the row must be locked and read when the ON DUPLICATE KEY clause is used, there will be a performance penalty (much like there is for an HBase Put versus a CheckAndPut)
https://phoenix.apache.org/docs/features/segment-scan
;
Phoenix translates these predicates into the underlying HBase scan bounds for you, so a worker pool can stay in plain SQL — each worker runs its own query against one segment, in parallel
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/table-sampling
Given a sampling rate, it leverages Phoenix statistics and HBase region distribution to perform table sampling