HBase uses the./conf/hbase-default.xml file for configuration. Some properties do not resolve to existing directories because the JVM runs on Windows. This is the major issue to keep in mind when working with Cygwin: within the shell all paths are *nix-alike, hence relative to the root /. However, every parameter that is to be consumed within the windows processes themself, need to be Windows settings, hence C: -alike.
Change following propeties in the configuration file, adjusting paths where necessary to conform with your own installation: • hbase.rootdir must read e.g. File:///C:/cygwin/root/tmp/hbase/data or hdfs://127.0.0.1:9000/hbase in case of hadoop file system.
In your cygwin window, type in the following commands. This is assuming the installation of version 0.20.2 of Hadoop. Newer versions do not get along with Windows 7 (mainly, the tasktracker daemon which requires permissions. Info: For more info on privilege separation read /usr/share/doc/openssh/READ ME.privsep. Thanks for contributing an answer to Super User! Please be sure to answer the question.Provide details and share your research! Asking for help, clarification, or responding to other answers.
![Install Hadoop On Windows Without Cygwin Commands Usr Install Hadoop On Windows Without Cygwin Commands Usr](https://2.bp.blogspot.com/-Dbr7NAbmVrk/VDLiU1_RvzI/AAAAAAAAD6Y/dJ-Q3j75yXg/w1200-h630-p-k-no-nu/sdk2.png)
• hbase.tmp.dir must read C:/cygwin/root/tmp/hbase/tmp • hbase.zookeeper.quorum must read 127.0.0.1 because for some reason localhost doesn't seem to resolve properly on Cygwin. Make sure the configured hbase.rootdir and hbase.tmp.dir directories exist and have the proper rights set up e.g. By issuing a chmod 777 on them. Go to c:/cygwin/root/usr/local/hbase-1.2.3/conf and add the following in hbase-site.xml file. 2016-09-18 12:59:10,944 INFO [main] server.ZooKeeperServer: Server environment:java.library.path=C: java jdk1.8.0_101 bin;C: WINDOWS Sun Java bin;C: WINDOWS system32;C: WINDOWS;C: cygwin root bin;C: WINDOWS system32;C: WINDOWS;C: WINDOWS System32 Wbem;C: WINDOWS System32 WindowsPowerShell v1.0;%JAVA_HOME% bin;%CYGWIN_HOME% bin;%HADOOP_BIN_PATH%;%HADOOP_HOME% bin;%MAVEN_HOME% bin. Now, lets play with some hbase commands. We’ll start with a basic scan that returns all columns in the cars table.
Using a long column family name, such as columnfamily1 is a horrible idea in production. Every cell (i.e. Every value) in HBase is stored fully qualified. This basically means that long column family names will balloon the amount of disk space required to store your data. In summary, keep your column family names as small as possible To start, I’m going to create a new table named cars. My column family is vi, which is an abbreviation of vehicle information. The schema that follows below is only for illustration purposes, and should not be used to create a production schema.
In production, you should create a Row ID that helps to uniquely identify the row, and that is likely to be used in your queries. Therefore, one possibility would be to shift the Make, Model and Year left and use these items in the Row ID. Create 'cars', 'vi'.