[
https://issues.apache.org/jira/browse/BEAM-14115?focusedWorklogId=742173&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-742173
]
ASF GitHub Bot logged work on BEAM-14115:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Mar/22 10:53
Start Date: 16/Mar/22 10:53
Worklog Time Spent: 10m
Work Description: OreOreDa commented on pull request #17102:
URL: https://github.com/apache/beam/pull/17102#issuecomment-1068992402
R: @y1chi
--
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: 742173)
Remaining Estimate: 0h
Time Spent: 10m
> Update find criteria limited to _id
> -----------------------------------
>
> Key: BEAM-14115
> URL: https://issues.apache.org/jira/browse/BEAM-14115
> Project: Beam
> Issue Type: Bug
> Components: io-java-mongodb
> Affects Versions: 2.37.0
> Reporter: Olivier Le Quellec
> Priority: P2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Documents update during write operations specify a find criteria, which is
> currently hard-coded to be on "_id" only. This is blocking for a lot
> scenarios, where we would like to upsert on a business-related document field
> By adding "findKey" in UpdateConfiguration, we can specify a find criteria on
> any field of the document. The "findKey" will default to "_id" if not
> specified
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
