Hi Jordan, Thank you for detailed response. The only thing not clear to me is this. For simple calculations if say I have 1 index only how much is the price and how it is calculated?
In price calculator I can see Document Index $2/GB. It seems too expensive. Is this index the same index made from Datastore automatic index generation? Thank you, --Constantine On Tuesday, May 29, 2018 at 8:12:18 AM UTC-7, Jordan (Cloud Platform Support) wrote: > > Since Google Cloud Datastore > <https://cloud.google.com/datastore/docs/concepts/overview> is a > non-relational, NoSQL, highly-scalable database, you must create a script > in the supported language of your choice that reads your CSV, converts your > data into Datastore Entities > <https://cloud.google.com/datastore/docs/concepts/entities#creating_an_entity>, > > and then saves those Entities to your Datastore. Once your data is loaded > into the Datastore you can then easily export it and import it into other > projects' Datastores via the Managed Import/Export service > <https://cloud.google.com/datastore/docs/export-import-entities#importing_entities> > . > > The way to minimize costs in the Datastore is to use the least amount of > indexes <https://cloud.google.com/datastore/docs/concepts/indexes> as > possible. You can think of an index as a sorted table. For every query you > use, you need an associated sorted index (aka a copy of your data sorted > specifically for that query). By default, an index is automatically created > for each field of each Entity Kind > <https://cloud.google.com/datastore/docs/concepts/entities#kinds_and_identifiers>. > > Therefore to avoid having 200 automatically created indexes, it is > recommended to mark all of the properties that you do not plan on querying > as un-indexed > <https://cloud.google.com/datastore/docs/concepts/indexes#unindexed_properties> > > to save you money. > > It is actually recommended to use Datastore's automatic key generation > <https://cloud.google.com/datastore/docs/best-practices#keys>when saving > Entities, instead of creating custom keys. Datastore will ensure that your > data is properly sharded and evenly distributed across Datastore servers in > order to avoid hotspots and latency when specific entities are accessed a > lot. Therefore, your link to Google Cloud Storage should be saved as an > additional Entity property that will be returned when you query for an > Entity. In general it is recommended to follow the Best Practices for > Datastore <https://cloud.google.com/datastore/docs/best-practices>. > > - Note that Google Groups is reserved for general product discussions and > not for technical support. If you require further technical support for the > Datastore, it is recommended to post your detailed questions > <https://stackoverflow.com/help/how-to-ask> to Stack Exchange > <https://cloud.google.com/support/docs/stackexchange> using the supported > Cloud tags. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a384720d-30c0-4095-9662-a70b75f3c41c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
