Re: Specifying a cells version

[James Taylor]

See
http://phoenix.apache.org/faq.html#Can_phoenix_work_on_tables_with_arbitrary_timestamp_as_flexible_as_HBase_API
and http://phoenix.apache.org/rowtimestamp.html

Thanks,
James

On Fri, Sep 9, 2016 at 3:43 PM, Paul Jones  wrote:

> I see that when I create a table using phoenix I can specify how many
> versions of a cell I want to keep. Is it possible to specify a version
> value when I perform an upsert? I am receiving data in order from the
> customer but would like to be able to process it out of order but specify
> the version value to be the timestamp that the customer gave us the data
> rather than the timestamp that the data is inserted. Is that possible using
> phoenix?
>
> http://hbase.apache.org/0.94/book/versions.html
>
> Thanks,
> Paul
>
>

Specifying a cells version

[Paul Jones]

I see that when I create a table using phoenix I can specify how many versions 
of a cell I want to keep. Is it possible to specify a version value when I 
perform an upsert? I am receiving data in order from the customer but would 
like to be able to process it out of order but specify the version value to be 
the timestamp that the customer gave us the data rather than the timestamp that 
the data is inserted. Is that possible using phoenix?

http://hbase.apache.org/0.94/book/versions.html

Thanks,
Paul

Re: Cloning a table in Phoenix

[Kumar Palaniappan]

Will do James.

On Fri, Sep 9, 2016 at 10:27 AM, James Taylor 
wrote:

> Good idea - this would make a great contribution. Please file a JIRA.
>
> On Fri, Sep 9, 2016 at 6:29 AM, Kumar Palaniappan <
> kpalaniap...@marinsoftware.com> wrote:
>
>> Yes James.
>>
>> Kumar Palaniappan 
>> 
>>  [image: Description: Macintosh HD:Users:Kumarappan:Desktop:linkedin.gif]
>> 
>>
>> On Sep 9, 2016, at 12:53 AM, Heather, James (ELS-LON) <
>> james.heat...@elsevier.com> wrote:
>>
>> This does rather suggest that it would be fairly easy to implement a SHOW
>> CREATE TABLE statement. Is that right?
>>
>> It would be useful if so.
>>
>> James
>>
>> On 9 September 2016 2:43:51 a.m. "dalin.qin"  wrote:
>>
>>> Hi Kumar,
>>>
>>> I believe right now there is no way to directly generate the DDL
>>> statement for the existing table,better to write down you sql immedately
>>> after exection  (in oracle ,dbms_metadata is so perfect ,in hive show
>>> create table also works )
>>> however you can query system.catalog for all the information you need .
>>>
>>> ++--+-+-
>>> ---++---+--+
>>> +-+-+---
>>> +--+-++-+
>>> | TABLE_CAT  | TABLE_SCHEM  | TABLE_NAME  |COLUMN_NAME |
>>> DATA_TYPE  | TYPE_NAME | COLUMN_SIZE  | BUFFER_LENGTH  |
>>> DECIMAL_DIGITS  | NUM_PREC_RADIX  | NULLABLE  | REMARKS  | COLUMN_DEF  |
>>> SQL_DATA_TYPE  | SQL_DAT |
>>> ++--+-+-
>>> ---++---+--+
>>> +-+-+---
>>> +--+-++-+
>>> || SYSTEM   | CATALOG | TENANT_ID  |
>>> 12 | VARCHAR   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | TABLE_SCHEM|
>>> 12 | VARCHAR   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | TABLE_NAME |
>>> 12 | VARCHAR   | null | null   | null
>>>  | null| 0 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | COLUMN_NAME|
>>> 12 | VARCHAR   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | COLUMN_FAMILY  |
>>> 12 | VARCHAR   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | TABLE_SEQ_NUM  |
>>> -5 | BIGINT| null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | TABLE_TYPE |
>>> 1  | CHAR  | 1| null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | PK_NAME|
>>> 12 | VARCHAR   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | COLUMN_COUNT   |
>>> 4  | INTEGER   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | SALT_BUCKETS   |
>>> 4  | INTEGER   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | DATA_TABLE_NAME|
>>> 12 | VARCHAR   | null | null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | INDEX_STATE|
>>> 1  | CHAR  | 1| null   | null
>>>  | null| 1 |  | | null
>>>   | null|
>>> || SYSTEM   | CATALOG | IMMUTABLE_ROWS   

Re: Cloning a table in Phoenix

[James Taylor]

Good idea - this would make a great contribution. Please file a JIRA.

On Fri, Sep 9, 2016 at 6:29 AM, Kumar Palaniappan <
kpalaniap...@marinsoftware.com> wrote:

> Yes James.
>
> Kumar Palaniappan 
> 
>  [image: Description: Macintosh HD:Users:Kumarappan:Desktop:linkedin.gif]
> 
>
> On Sep 9, 2016, at 12:53 AM, Heather, James (ELS-LON) <
> james.heat...@elsevier.com> wrote:
>
> This does rather suggest that it would be fairly easy to implement a SHOW
> CREATE TABLE statement. Is that right?
>
> It would be useful if so.
>
> James
>
> On 9 September 2016 2:43:51 a.m. "dalin.qin"  wrote:
>
>> Hi Kumar,
>>
>> I believe right now there is no way to directly generate the DDL
>> statement for the existing table,better to write down you sql immedately
>> after exection  (in oracle ,dbms_metadata is so perfect ,in hive show
>> create table also works )
>> however you can query system.catalog for all the information you need .
>>
>> ++--+-+-
>> ---++---+--+
>> +-+-+---
>> +--+-++-+
>> | TABLE_CAT  | TABLE_SCHEM  | TABLE_NAME  |COLUMN_NAME |
>> DATA_TYPE  | TYPE_NAME | COLUMN_SIZE  | BUFFER_LENGTH  |
>> DECIMAL_DIGITS  | NUM_PREC_RADIX  | NULLABLE  | REMARKS  | COLUMN_DEF  |
>> SQL_DATA_TYPE  | SQL_DAT |
>> ++--+-+-
>> ---++---+--+
>> +-+-+---
>> +--+-++-+
>> || SYSTEM   | CATALOG | TENANT_ID  |
>> 12 | VARCHAR   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | TABLE_SCHEM|
>> 12 | VARCHAR   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | TABLE_NAME |
>> 12 | VARCHAR   | null | null   | null
>>  | null| 0 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | COLUMN_NAME|
>> 12 | VARCHAR   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | COLUMN_FAMILY  |
>> 12 | VARCHAR   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | TABLE_SEQ_NUM  |
>> -5 | BIGINT| null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | TABLE_TYPE |
>> 1  | CHAR  | 1| null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | PK_NAME|
>> 12 | VARCHAR   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | COLUMN_COUNT   |
>> 4  | INTEGER   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | SALT_BUCKETS   |
>> 4  | INTEGER   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | DATA_TABLE_NAME|
>> 12 | VARCHAR   | null | null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | INDEX_STATE|
>> 1  | CHAR  | 1| null   | null
>>  | null| 1 |  | | null
>>   | null|
>> || SYSTEM   | CATALOG | IMMUTABLE_ROWS |
>> 16 | BOOLEAN   | null | null   | null
>>  | null| 1 |  | | null
>>   | null 

Re: Cloning a table in Phoenix

[Kumar Palaniappan]

Yes James.

Kumar Palaniappan   

> On Sep 9, 2016, at 12:53 AM, Heather, James (ELS-LON) 
>  wrote:
> 
> This does rather suggest that it would be fairly easy to implement a SHOW 
> CREATE TABLE statement. Is that right?
> 
> It would be useful if so.
> 
> James
> 
>> On 9 September 2016 2:43:51 a.m. "dalin.qin"  wrote:
>> 
>> Hi Kumar,
>> 
>> I believe right now there is no way to directly generate the DDL statement 
>> for the existing table,better to write down you sql immedately after 
>> exection  (in oracle ,dbms_metadata is so perfect ,in hive show create table 
>> also works )
>> however you can query system.catalog for all the information you need .
>> 
>> ++--+-+++---+--++-+-+---+--+-++-+
>> | TABLE_CAT  | TABLE_SCHEM  | TABLE_NAME  |COLUMN_NAME | 
>> DATA_TYPE  | TYPE_NAME | COLUMN_SIZE  | BUFFER_LENGTH  | 
>> DECIMAL_DIGITS  | NUM_PREC_RADIX  | NULLABLE  | REMARKS  | COLUMN_DEF  | 
>> SQL_DATA_TYPE  | SQL_DAT |
>> ++--+-+++---+--++-+-+---+--+-++-+
>> || SYSTEM   | CATALOG | TENANT_ID  | 12  
>>| VARCHAR   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | TABLE_SCHEM| 12  
>>| VARCHAR   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | TABLE_NAME | 12  
>>| VARCHAR   | null | null   | null
>> | null| 0 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | COLUMN_NAME| 12  
>>| VARCHAR   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | COLUMN_FAMILY  | 12  
>>| VARCHAR   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | TABLE_SEQ_NUM  | -5  
>>| BIGINT| null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | TABLE_TYPE | 1   
>>| CHAR  | 1| null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | PK_NAME| 12  
>>| VARCHAR   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | COLUMN_COUNT   | 4   
>>| INTEGER   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | SALT_BUCKETS   | 4   
>>| INTEGER   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | DATA_TABLE_NAME| 12  
>>| VARCHAR   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | INDEX_STATE| 1   
>>| CHAR  | 1| null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | IMMUTABLE_ROWS | 16  
>>| BOOLEAN   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | VIEW_STATEMENT | 12  
>>| VARCHAR   | null | null   | null
>> | null| 1 |  | | null   | 
>> null|
>> || SYSTEM   | CATALOG | DEF

Re: Cloning a table in Phoenix

[Heather, James (ELS-LON)]

This does rather suggest that it would be fairly easy to implement a SHOW 
CREATE TABLE statement. Is that right?

It would be useful if so.

James

On 9 September 2016 2:43:51 a.m. "dalin.qin"  wrote:

Hi Kumar,

I believe right now there is no way to directly generate the DDL statement for 
the existing table,better to write down you sql immedately after exection  (in 
oracle ,dbms_metadata is so perfect ,in hive show create table also works )
however you can query system.catalog for all the information you need .

++--+-+++---+--++-+-+---+--+-++-+
| TABLE_CAT  | TABLE_SCHEM  | TABLE_NAME  |COLUMN_NAME | 
DATA_TYPE  | TYPE_NAME | COLUMN_SIZE  | BUFFER_LENGTH  | DECIMAL_DIGITS 
 | NUM_PREC_RADIX  | NULLABLE  | REMARKS  | COLUMN_DEF  | SQL_DATA_TYPE  | 
SQL_DAT |
++--+-+++---+--++-+-+---+--+-++-+
|| SYSTEM   | CATALOG | TENANT_ID  | 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | TABLE_SCHEM| 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | TABLE_NAME | 12 
| VARCHAR   | null | null   | null| 
null| 0 |  | | null   | null
|
|| SYSTEM   | CATALOG | COLUMN_NAME| 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | COLUMN_FAMILY  | 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | TABLE_SEQ_NUM  | -5 
| BIGINT| null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | TABLE_TYPE | 1  
| CHAR  | 1| null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | PK_NAME| 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | COLUMN_COUNT   | 4  
| INTEGER   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | SALT_BUCKETS   | 4  
| INTEGER   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | DATA_TABLE_NAME| 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | INDEX_STATE| 1  
| CHAR  | 1| null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | IMMUTABLE_ROWS | 16 
| BOOLEAN   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | VIEW_STATEMENT | 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | DEFAULT_COLUMN_FAMILY  | 12 
| VARCHAR   | null | null   | null| 
null| 1 |  | | null   | null
|
|| SYSTEM   | CATALOG | DISABLE_WAL| 16 
| BOOLEAN   | null | null   | null