[ 
https://issues.apache.org/jira/browse/BEAM-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000642#comment-16000642
 ] 

ASF GitHub Bot commented on BEAM-991:
-------------------------------------

GitHub user cph6 opened a pull request:

    https://github.com/apache/beam/pull/2948

    [BEAM-991] Comply with byte limit for Datastore Commit.

    This changes the Datastore connector to limit RPCs both by overall size and 
by the number of entities contained, to fit within the Datastore API limits 
https://cloud.google.com/datastore/docs/concepts/limits .
    
    A similar change for the Python SDK is already written and will be 
submitted separately.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cph6/beam datastore_request_size_limit_java

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/2948.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2948
    
----
commit efec2acd92f0142f2f9741590c9e34ed0d5c84bf
Author: Colin Phipps <[email protected]>
Date:   2017-04-25T15:28:28Z

    Comply with byte limit for Datastore Commit.

----


> DatastoreIO Write should flush early for large batches
> ------------------------------------------------------
>
>                 Key: BEAM-991
>                 URL: https://issues.apache.org/jira/browse/BEAM-991
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-gcp
>            Reporter: Vikas Kedigehalli
>            Assignee: Vikas Kedigehalli
>
> If entities are large (avg size > 20KB) then the a single batched write (500 
> entities) would exceed the Datastore size limit of a single request (10MB) 
> from https://cloud.google.com/datastore/docs/concepts/limits.
> First reported in: 
> http://stackoverflow.com/questions/40156400/why-does-dataflow-erratically-fail-in-datastore-access



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to