[ 
https://issues.apache.org/jira/browse/DRILL-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570180#comment-17570180
 ] 

ASF GitHub Bot commented on DRILL-8259:
---------------------------------------

cgivre commented on PR #2596:
URL: https://github.com/apache/drill/pull/2596#issuecomment-1192943886

   @luocooong Thanks for submitting this.  I was wondering, is there a reason 
why we are storing these variables in `drill-override.conf` instead of the 
configuration for the storage plugin?  IMHO, it is better to put it in the 
config so that you don't have to restart Drill any time you make a config change




> Support advanced HBase persistence storage options
> --------------------------------------------------
>
>                 Key: DRILL-8259
>                 URL: https://issues.apache.org/jira/browse/DRILL-8259
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Storage - HBase
>            Reporter: Cong Luo
>            Assignee: Cong Luo
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Its contents are as follows
> {code:java}
> sys.store.provider: {
>   class: "org.apache.drill.exec.store.hbase.config.HBasePStoreProvider",
>   hbase: {
>     table : "drill_store",
>     config: {
>       "hbase.zookeeper.quorum": "zk_host3,zk_host2,zk_host1",
>       "hbase.zookeeper.property.clientPort": "2181",
>       "zookeeper.znode.parent": "/hbase-test"
>     },
>     table_config : {
>       "durability": "ASYNC_WAL",
>       "compaction_enabled": false,
>       "split_enabled": false,
>       "max_filesize": 10737418240,
>       "memstore_flushsize": 536870912
>     },
>     column_config : {
>       "versions": 1,
>       "ttl": 2626560,
>       "compression": "SNAPPY",
>       "blockcache": true,
>       "blocksize": 131072,
>       "data_block_encoding": "FAST_DIFF",
>       "in_memory": true,
>       "dfs_replication": 3
>     }
>   }
> }{code}
>  



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

Reply via email to