Google Cloud Datastore
Java Python Makefile Other
Latest commit 1a4139a Apr 6, 2017 @eddavisson eddavisson committed on GitHub Merge pull request #167 from eddavisson/master
Python 7.0.1 release

README.md

Google Cloud Datastore

Note: This repository contains low-level Java and Python client libraries for Google Cloud Datastore. For more idiomatic and usable client libraries in these languages, please visit the Google Cloud Client Libraries for Java and Google Cloud Client Libraries for Python repositories. You can also find the full list of supported client libraries in a variety of languages on the Client Libraries page of Cloud Datastore.

Cloud Datastore is a highly-scalable NoSQL database for your applications. Cloud Datastore automatically handles sharding and replication, providing you with a highly available and durable database that scales automatically to handle your applications' load. Cloud Datastore provides a myriad of capabilities such as ACID transactions, SQL-like queries, indexes and much more. For more information, see the Cloud Datastore documentation.

This repository contains clients that are deliberately low-level and map directly to the underlying Datastore RPC model. They're designed to provide more flexibility to developers and higher level library implementers.

Samples

Proto

Client Libraries

You can learn more about client libraries for Cloud Datastore here.

pip install googledatastore
  • Java (Maven):
<dependency>
  <groupId>com.google.cloud.datastore</groupId>
  <artifactId>datastore-v1-protos</artifactId>
  <version>1.3.0</version>
</dependency>
<dependency>
  <groupId>com.google.cloud.datastore</groupId>
  <artifactId>datastore-v1-proto-client</artifactId>
  <version>1.3.0</version>
</dependency>

Documentation

For more information, see the Cloud Datastore documentation.

Filing Issues

  1. For production issues and support options, see Cloud Datastore support.
  2. For bugs or feature requests, please first look at existing issues.
  3. When applicable, create a new report.
  4. For bugs, detail the steps to reproduce the problem and the affected version number.
  5. For feature requests, articulate the use case you are trying solve and describe any current workaround(s).

Contributing changes

Licensing