You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "tanjialiang (Jira)" <ji...@apache.org> on 2022/12/20 10:29:00 UTC

[jira] [Updated] (FLINK-30460) Support writing HBase's CEIL TTL metadata

     [ https://issues.apache.org/jira/browse/FLINK-30460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

tanjialiang updated FLINK-30460:
--------------------------------
    Description: 
When i using flink sql to sink hbase, i found i can't set the ceil ttl.  Can we support writing the ceil ttl metadata like this?
{code:java}
CREATE TABLE hTable (
 rowkey INT,
 family1 ROW<q1 INT>,
 ttl BIGINT METADATA FROM 'ttl',
 PRIMARY KEY (rowkey) NOT ENFORCED
) WITH (
 'connector' = 'hbase-2.2',
 'table-name' = 'mytable',
 'zookeeper.quorum' = 'localhost:2181'
);{code}
 

 

  was:
When i using flink sql to sink hbase, i found i can't set the ceil ttl.  Can we support writing the ceil ttl metadata like this?

 
{code:java}
CREATE TABLE hTable (
 rowkey INT,
 family1 ROW<q1 INT>,
 ttl BIGINT METADATA FROM 'ttl',
 PRIMARY KEY (rowkey) NOT ENFORCED
) WITH (
 'connector' = 'hbase-2.2',
 'table-name' = 'mytable',
 'zookeeper.quorum' = 'localhost:2181'
);{code}
 

 


> Support writing HBase's CEIL TTL metadata
> -----------------------------------------
>
>                 Key: FLINK-30460
>                 URL: https://issues.apache.org/jira/browse/FLINK-30460
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / HBase
>            Reporter: tanjialiang
>            Priority: Major
>
> When i using flink sql to sink hbase, i found i can't set the ceil ttl.  Can we support writing the ceil ttl metadata like this?
> {code:java}
> CREATE TABLE hTable (
>  rowkey INT,
>  family1 ROW<q1 INT>,
>  ttl BIGINT METADATA FROM 'ttl',
>  PRIMARY KEY (rowkey) NOT ENFORCED
> ) WITH (
>  'connector' = 'hbase-2.2',
>  'table-name' = 'mytable',
>  'zookeeper.quorum' = 'localhost:2181'
> );{code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)