Web This site Trusted
30 result(s) for “if can open now site address wilhelm de site hbase apache org site:phoenix.apache.org” of 37 matched · 1183 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/user-defined-functions
Add the following parameters to hbase-site
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
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
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/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
Above and beyond the row-level transactional semantics of HBase, Phoenix adds cross row and cross table transaction support with full ACID semantics by integrating with Tephra, now an Apache incubator project
https://phoenix.apache.org/docs/features/high-availability
enabledfalse — set true in the source cluster's hbase-site
https://phoenix.apache.org/docs/installation
Download and expand the latest phoenix-hbase-[hbase
https://phoenix.apache.org/docs/features/metrics
enabled to true/false in the client side hbase-site
https://phoenix.apache.org/salted.html
rowKeyOrderSaltedTable=true in 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/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/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
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/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/views
The standard SQL view syntax (with some limitations) is now supported by Phoenix to enable multiple virtual tables to all share the same underlying physical HBase table
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/explain-plan
When stats collection is not enabled or if for some reason Phoenix cannot provide the estimate information, the columns return null
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/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
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
Java applications using the Phoenix thick JDBC client can drive the same atomic-return semantics directly through typed methods on PhoenixStatement and PhoenixPreparedStatement, without putting RETURNING * in the SQL:
executeAtomicUpdateReturnRow — returns the row state after the mutation (or the unchanged row when
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
can occur in Phoenix versions earlier than 4
https://phoenix.apache.org/docs/features/conditional-ttl
Phoenix compaction: expired rows are physically removed by Phoenix's compaction during HBase region compactions
https://phoenix.apache.org/docs/features/phoenix-row-timestamp
Feature
PHOENIX_ROW_TIMESTAMP() functionReturn the underlying HBase row timestamp Phoenix already maintains on every row's empty cell