[ https://issues.apache.org/jira/browse/BEAM-8306?focusedWorklogId=318943&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-318943 ]
ASF GitHub Bot logged work on BEAM-8306: ---------------------------------------- Author: ASF GitHub Bot Created on: 26/Sep/19 12:59 Start Date: 26/Sep/19 12:59 Worklog Time Spent: 10m Work Description: iemejia commented on issue #9660: [BEAM-8306] improve estimation datasize elasticsearch io URL: https://github.com/apache/beam/pull/9660#issuecomment-535490565 R: @echauchot @timrobertson100 Can some of you PTAL at this one, looks like an interesting improvement. ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 318943) Remaining Estimate: 0h Time Spent: 10m > 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: 10m > 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)