[ 
https://issues.apache.org/jira/browse/BEAM-8306?focusedWorklogId=335431&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-335431
 ]

ASF GitHub Bot logged work on BEAM-8306:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Oct/19 09:13
            Start Date: 29/Oct/19 09:13
    Worklog Time Spent: 10m 
      Work Description: timrobertson100 commented on issue #9660: [BEAM-8306] 
improve estimation datasize elasticsearch io
URL: https://github.com/apache/beam/pull/9660#issuecomment-547325482
 
 
   This LGTM - waiting to see green to merge
   
   I am not entirely sure this will work when aliasing indexes. I don't believe 
you can get an estimate of size like this but as far as I can see the same is 
true in the current implementation too. I think we would need to determine the 
indices that form part of the alias and then accumulate the sizes. Surely out 
of the scope of this PR though.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 335431)
    Time Spent: 1h 50m  (was: 1h 40m)

> improve estimation of data byte size reading from source in ElasticsearchIO
> ---------------------------------------------------------------------------
>
>                 Key: BEAM-8306
>                 URL: https://issues.apache.org/jira/browse/BEAM-8306
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-elasticsearch
>    Affects Versions: 2.14.0
>            Reporter: Derek He
>            Assignee: Derek He
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> ElasticsearchIO splits BoundedSource based on the Elasticsearch index size. 
> We expect it can be more accurate to split it base on query result size.
> Currently, we have a big Elasticsearch index. But for query result, it only 
> contains a few documents in the index.  ElasticsearchIO splits it into up 
> to1024 BoundedSources in Google dataflow. It takes long time to finish the 
> processing the small numbers of Elasticsearch document in Google dataflow.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to