[JAVA-3792] ChangeStreams are not triggered anymore when AutoEncryptionSettings are used Created: 10/Jul/20 Updated: 17/Aug/20 Resolved: 17/Aug/20 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Reactive Streams, Scala |
| Affects Version/s: | 4.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Martin Thomalla | Assignee: | Ross Lawley |
| Resolution: | Cannot Reproduce | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
windows 7, 10, 2012 |
||
| Case: | (copied to CRM) |
| Description |
|
We activated client side field encryption following the relevant guides.
We use the AutoEncryptionSettings to get transparent En-/Decrypt for one of our fields. Unfortunately this stops all our watches from being triggered on any change.
If we remove the AutoEncryptionSettings from our connection all watches work again. |
| Comments |
| Comment by Ross Lawley [ 17/Aug/20 ] | ||||||||||
|
No worries, glad you were able to resolve the issue. Ross | ||||||||||
| Comment by Martin Thomalla [ 17/Aug/20 ] | ||||||||||
|
Hi @Ross, You are correct, onError wasn't implemented on our site and all errors were just not logged. I did not see that while working with the code which was written by someone else. Sorry for the confusion. Martin | ||||||||||
| Comment by Ross Lawley [ 20/Jul/20 ] | ||||||||||
|
When running:
I do see the error passed to the onError method and it prints it:
I also tested in the sync and reactive streams driver and got the same result. Ross | ||||||||||
| Comment by Ross Lawley [ 17/Jul/20 ] | ||||||||||
|
Thank you for reporting the issue. Agreed there should be a client error passed here to the onError method. This ticket has now been scheduled for fixing. Kind Regards, Ross | ||||||||||
| Comment by Martin Thomalla [ 17/Jul/20 ] | ||||||||||
|
https://support.mongodb.com/case/00671738 explains that CSFLE and watches do not work together. We should get a client error though. | ||||||||||
| Comment by Ross Lawley [ 17/Jul/20 ] | ||||||||||
|
Moved to the JAVA project as the driver version is 4.0.5 which is co hosted with the Java driver. |