About Enis

Enis · ‎06-06-2016

You can just omit the TTL parameter (meaning that do not specify) in which case it will default to FOREVER. I am not sure whether we used to parse TTL => 'FOREVER' as an expression before 2.4.

Enis · ‎06-06-2016

HBase base version in HDP-2.3 abd HDP-2.4 is very similar, so this should work with HDP-2.4 as well.

Enis · ‎05-16-2016

You can either hbase.thrift.info.port and hbase.regionserver.thrift.port in your hbase-site.xml, or start the thrift server by passing -p <port> and --infoport <info_port> as command line arguments. Note that port and info port are different ports. Port is used for RPCs while the info port is for the web UI.

Enis · ‎05-13-2016

I would suspect a version mismatch between an installed version of ruby / jruby and the one required by HBase.

Enis · ‎04-29-2016

You can check how many regions you have from the HBase master's web UI. A good rule of thumb is to keep number of regions per regionserver to be under 1000. You can also inspect the start and end keys of regions and regions sizes from the Master web UI or by going in to a RegionServers WebUI and checking various tabs. HBase splits the regions based on range boundaries of the keyspace. HBase ALWAYS does range-splitting, not hash-based splitting. This means that depending on your key design, you maybe temporarily hotspotting some parts of the keyspace causing excessive region splits. It is likely that you have a timeseries based key design that you have to revisit. You can check out the HBase book, and there are also presentations available that talks about row key and schema design.

Enis · ‎03-24-2016

Each region flushes independently of each other. If a region flushes, all of its column families are flushed together by default (unless a different flush policy is used in recent code bases). A region's flush does not affect other regions.

Enis · ‎03-18-2016

The SyncTool is not in HDP releases yet, but we are tracking it to bring the tool to released versions.

Enis · ‎03-09-2016

In HBase, you do not have to pre-declare the set of columns as you would in a RDBMS. You can have each row have a different set of columns which is one of the powerful features of HBase. Phoenix exposes this, through a feature called "dynamic columns". You can declare a set of columns in the Phoenix table schema, but at query time or insertion time, you can do querying by specifying the columns on-the-fly. Check out https://phoenix.apache.org/dynamic_columns.html for syntax.

Enis · ‎03-04-2016

@Artem Ervits is right. There is no purge of snapshots by design. Snapshots are used for referring to data at a later time. Taking a snapshot and keeping a snapshot is an explicit decision that depends only on operations. HBase in no case will delete a snapshot without an explicit command.

Enis · ‎02-23-2016

You can check the official compatibility documentation here: https://hbase.apache.org/book.html#hbase.versioning. What you are looking for is "wire compatibility" between the client and server. In short, 1.x releases among different versions are client / sever wire compatible. 0.98 to 1.x might have some rough edges but it is still supported. HDP-2.2 is 0.98 based, and HDP-2.3 and 2.4 is HBase-1.1.1 based, thus inherits the upstream compatibility gurantees.

Online	Offline
Last Visited	‎09-26-2022 06:38 PM

Member Since	‎09-29-2015 07:06 PM
Last Visited	‎09-26-2022 06:38 PM
Posts	94
Kudos received	114

Cloudera Community

Re: Need an easy and performant way to purge data ...

Re: hbase job throwing exception

Re: How do Zookeeper save HBase Column and Column ...

Re: MapReduce performance on the HBase input table...

Re: Significance of ScanNext Latency in HBase Metr...

Re: Hi..Is anything changed on TTL => 'FOREVER' on...

Re: Can Lily work with HDP2.4 distribution?

Re: configuring Thrift Server on default port

Re: ArgumentError: wrong number of arguments (3 fo...

Re: Total region count

Re: HBase memstore adjacent families flush

Re: Resynchronize the HBase data betweentwo cluste...

Re: How to efficiently map data columns from exter...

Re: How we would go about configuring the number o...

Re: HBase Client and DB backward compatibility