Re: Unset `MAX_FILESIZE` for index table

gt; ‘table_att_unset’, NAME => ‘MAX_FILESIZE’ > > JMS > > 2016-08-04 13:53 GMT-04:00 Simon Wang <mailto:simon.w...@airbnb.com>>: > Hi all, > > Global index tables have `MAX_FILESIZE` automatically set upon creation. This > option can be overridden by setting `MAX_F

Unset `MAX_FILESIZE` for index table

Hi all, Global index tables have `MAX_FILESIZE` automatically set upon creation. This option can be overridden by setting `MAX_FILESIZE = xx` in DDL. But how can we force it to be unset in DDL? Thanks in advance! Best, Simon

Re: Phoenix Create table timeout

This isn’t a solution but I have encountered this problem before. It also seemed that the table becomes available in Phoenix even if the creation dies to an error. I am also interested in a workaround! (Maybe a MR job? - Simon > On Jul 28, 2016, at 1:49 AM, Parveen Jain wrote: > > Hi All, >

Re: Local Phoenix installation for testing

> Hi Simon, > Do you mean to run the unit tests? There's no setup required. You can > directly run the unit tests through maven or Eclipse. > Thanks, > James > > On Thu, Jul 21, 2016 at 2:34 PM, Simon Wang <mailto:simon.w...@airbnb.com>> wrote: > Hi all, >

Local Phoenix installation for testing

Hi all, Does anyone have previous experience of setting up Phoenix locally for testing purposes? I looked into HBase mini cluster but I can’t figure out how Phoenix should work with it. Thanks in advance! Best, Simon

Re: Get region for row key

use case, perhaps you could look into > supporting Hive 0.13-1. I'm not sure of the level of effort, as others > contributed this integration. How about filing a JIRA to discuss? > > We'll have an RC up for 4.8 in the next day or so. > > Thanks, > James > >

Re: Get region for row key

; > Thanks, > James > > On Tue, Jul 12, 2016 at 7:14 AM, Simon Wang <mailto:simon.w...@airbnb.com>> wrote: > As I read more Phoenix code, I feel that I should do: > > 1. Use `PhoenixRuntime.getTable` to get a `PTable` > 2. Use `table.getPKColumns` to get

Re: Get region for row key

`ImmutableBytesPtr`, and do `table.newKey(ptr, pksByteArray)` 5. Eventually, get salted key as `SaltingUtil.getSaltedKey(ptr, table.getBucketNum())` I appreciate anyone that can help me check this is correct. :) Thanks a lot! Best, Simon > On Jul 10, 2016, at 4:24 PM, Simon Wang wrote: > >

Re: Read Full Phoenix Table

I actually recently did something similar. If you are joining on primary keys, you can do batch query with the IN clause. > On Jul 11, 2016, at 9:05 PM, Mohanraj Ragupathiraj > wrote: > > Hi, > > I have a Scenario in which i have to load a phoenix table as a whole and join > it with multip

Re: Index tables at scale

tps://phoenix.apache.org/update_statistics.html>. > > On Mon, Jul 11, 2016 at 2:31 PM, Simon Wang <mailto:simon.w...@airbnb.com>> wrote: > This indexes will be salted indeed. (so is the data table). If all indexes > reside in the same table, there will be only 512 regions in total (256 for

Re: Index tables at scale

gger than one index table)? > > On Monday, July 11, 2016, Simon Wang <mailto:simon.w...@airbnb.com>> wrote: > Thanks, Mujtaba. What you wrote is exactly what I meant. While not all our > tables needs these many regions and indexes, the num of regions/region server > can gr

Re: Index tables at scale

but with 12 separate index tables or 1 index > table, the amount of data will be the same. Won't there be the same number of > regions either way? > > Thanks, > James > > On Sun, Jul 10, 2016 at 10:50 PM, Simon Wang <mailto:simon.w...@airbnb.com>> wrote: >

Re: Get region for row key

partitioning the dataFrame according to the HBase region. Any help is appreciated! Best, Simon > On Jul 10, 2016, at 2:01 PM, Simon Wang wrote: > > Hi all, > > Happy weekend! > > I am writing to ask if there is a way that I can get the region number of any > given row

Get region for row key

Hi all, Happy weekend! I am writing to ask if there is a way that I can get the region number of any given row key? For the case will salting is applied, I discovered `SaltingUtils.getSaltedKey` method, but I am not sure how I can get serialize the key as `ImmutableBytesWritable`. In genera

Re: Index tables at scale

extra > write-time cost? > > From a code consistency standpoint, using the same approach across local, > global, and view indexes might simplify things, though. Please file a JIRA > with a bit more detail on your use case. > > Thanks, > James > > > > On Fri, J

Index tables at scale

Hi all, I am writing to ask if there is a way to let Phoenix store all indexes on a single table in the same HBase table. If each index must be stored in a separate table, creating more than a few indexes on table with a large number of regions will not scale well. From what I have learned, wh

Re: Bulk loading and index

Thanks, James. I created JIRA created at PHOENIX-3032 . I am currently looking into the code and see if I can make this change. How would you suggest the logic should be? Having spent a few hours reading the code, I am considering a workflow

Re: phoenix do not show my tables

Do you mean your HBase tables? They don’t have Phoenix schema. Try map a HBase table into Phoenix.  -Tongzhou > On Jun 27, 2016, at 10:18 PM, 易剑 wrote: > > Why do not phoenix show my tables except SYSTEM

Salt _IDX_ table

Hi all, Is there any way to salt the _IDX_xx table? I understand that I can salt an index individually. But that creates an individual table for that index. In my use case, there will be potentially many indexes on a single large table. Making many tables is hardy a scalable solution. By the w

Column family name in index creation

Hi all, I encountered a problem with column family name in index creation. It appears that the column family name isn’t properly handled in this example: create table t1 (pk varchar not null primary key, "a"."id" bigint); create index idx on t1 ("id"); I get the following error

Verify validity of Phoenix table

Hi all, I recently created a Phoenix table over a huge existing HBase table (~1TB) using the following SQL: CREATE TABLE “table_name" ( PK VARCHAR NOT NULL PRIMARY KEY, "a"."id” VARCHAR, "a"."created_at" VARCHAR ) DEFAULT_COLUMN_FAMILY = 'a’; I can’t recall exactly but the command eit