[
https://issues.apache.org/jira/browse/BEAM-12093?focusedWorklogId=713211&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-713211
]
ASF GitHub Bot logged work on BEAM-12093:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jan/22 13:28
Start Date: 22/Jan/22 13:28
Worklog Time Spent: 10m
Work Description: egalpin commented on pull request #14347:
URL: https://github.com/apache/beam/pull/14347#issuecomment-1019264557
@mattwelke The javadoc[1] that is generated has some description and
examples, though admittedly not as fully descriptive as it could be. I would
welcome any additional examples or documentation added by others, and will keep
in mind to add more examples when time permits!
Do you have any specific questions or a use case you would like help
determining how to best use this IO? I might suggest that we move the
conversation to the user mailing list or slack[2] so that others could more
easily benefit from our conversation 🙂
[1]
https://beam.apache.org/releases/javadoc/2.35.0/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIO.html
[2] https://beam.apache.org/community/join-beam/
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 713211)
Time Spent: 16h 40m (was: 16.5h)
> Overhaul ElasticsearchIO#Write
> ------------------------------
>
> Key: BEAM-12093
> URL: https://issues.apache.org/jira/browse/BEAM-12093
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
> Reporter: Evan Galpin
> Assignee: Evan Galpin
> Priority: P2
> Labels: elasticsearch
> Fix For: 2.31.0
>
> Time Spent: 16h 40m
> Remaining Estimate: 0h
>
> The current ElasticsearchIO#Write is great, but there are two related areas
> which could be improved:
> # Separation of concern
> # Bulk API batch size optimization
> Â
> Presently, the Write transform has 2 responsibilities which are coupled and
> inseparable by users:
> # Convert input documents into Bulk API entities, serializing based on user
> settings (partial update, delete, upsert, etc)
> # Batch the converted Bulk API entities together and interface with the
> target ES cluster
> Â
> Having these 2 roles tightly coupled means testing requires an available
> Elasticsearch cluster, making unit testing almost impossible. Allowing access
> to the serialized documents would make unit testing much easier for pipeline
> developers, among numerous other benefits to having separation between
> serialization and IO.
> Relatedly, the batching of entities when creating Bulk API payloads is
> currently limited by the lesser of Beam Runner bundling semantics, and the
> `ElasticsearchIO#Write#maxBatchSize` setting. This is understandable for
> portability between runners, but it also means most Bulk payloads only have a
> few (1-5) entities. By using Stateful Processing to better adhere to the
> `ElasticsearchIO#Write#maxBatchSize` setting, we have been able to drop the
> number of indexing requests in an Elasticsearch cluster by 50-100x.
> Separating the role of document serialization and IO allows supporting
> multiple IO techniques with minimal and understandable code.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
