Correct. You still have to deal with slice / shard retries. But it should
work fine.
On Wed, Jul 8, 2015 at 11:58 PM, Antonio Fornié Casarrubios <
antonio.for...@gmail.com> wrote:
> Thanks Tom. So it's that all? The only difference/disadvantage of this
> approach would be to have less performance
Thanks Tom. So it's that all? The only difference/disadvantage of this
approach would be to have less performance?
El miércoles, 8 de julio de 2015, 20:52:25 (UTC+2), Tom Kaitchuck escribió:
>
> The point of DatastoreMutationPool is to provide batching of updates to
> increase throughput. It is
The point of DatastoreMutationPool is to provide batching of updates to
increase throughput. It is fine to use something else.
On Wed, Jul 8, 2015 at 7:34 AM, Antonio Fornié Casarrubios <
antonio.for...@gmail.com> wrote:
>
> Hi all. I didn't find any answer or info for this:
>
> *Context*: Java G
Hi all. I didn't find any answer or info for this:
*Context*: Java Google App Engine project, using Datastore. For a certain
kind, Sale, I save the entities in two ways:
1. From a typical SaleDAO#save(saleEntity)
2. During MapReduce, from my SaleReducer#emit(saleEntity)
So I was inv
