hbase,phoenix,google-cloud-bigtable
Custom co-processors are not supported as of June 1, 2015.
google-app-engine,google-datastore,google-cloud-bigtable
Based on experience with Datastore and reading the BigTable docs, the main differences are: BigTable seems to be designed for HBase compatibility, whereas Datastore is more geared towards Python/Java/Go web app developers (originally App Engine) BigTable is 'a bit more IaaS' than Datastore in that it's not 'just there' but...
java,google-cloud-dataflow,google-cloud-bigtable
Cloud BigTable requires the NPN/ALPN networking jar. This is currently not installed on the Dataflow workers. So accessing Cloud BigTable directly from a ParDo won't work. One possible work around is to use the HBase REST API to setup a REST server to access Cloud Bigtable on a VM outside...
hbase,bigtable,google-cloud-bigtable
Create a Cloud Bigtable cluster Test that it works by running the Quickstart. Start up a HBase Export MapReduce We recommend you store the parts on Google Cloud Storage. Setup a HBase 1.0.x environment and put the hbase-site.xml file that you created as part of the Quickstart into your...
HBase hasn't yet been certified to run with Java 8. For the time being, stick with Java 7. Here are two HBase / Hadoop tracking bugs for this: https://issues.apache.org/jira/browse/HADOOP-11090 https://issues.apache.org/jira/browse/HBASE-7608...
Yes, we have plans for Cloud Bigtable to be HIPAA compliant in the future. For additional information about Google Cloud Platform and HIPAA, please take a look at this blog post....
bigtable,google-cloud-bigtable
you can set environment variables on the system level as outlined for the following question so that eclipse gets the env variables; Set environment variables on Mac OS X Lion...
java,hbase,google-cloud-bigtable
SingleColumnValueFilter supports the following comparators: BinaryComparator BinaryPrefixComparator RegexStringComparator. See this link for an up-to-date list: https://cloud.google.com/bigtable/docs/hbase-differences...
bigtable,google-cloud-bigtable
For running locally, you need to make sure that the environment variable GOOGLE_APPLICATION_CREDENTIALS is set to your key.json you got from cloud console. (This is the likely cause in your case).
high-availability,google-cloud-platform,google-cloud-bigtable
On replication: The answer you referenced is referring to replication of data across Bigtable Clusters, which is not supported at this time. (For example, a Bigtable Cluster in the United States replicating its writes to a second Cluster in Europe) This concept is separate from replication of data within a...