[SERVER-70392] Add a test shell extension to create a named pipe and push (bson) data into it Created: 10/Oct/22  Updated: 29/Oct/23  Resolved: 18/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Yoon Soo Kim Assignee: Kevin Cherkauer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-69687 Add the $_externalDataSource option t... Closed
Backwards Compatibility: Fully Compatible
Sprint: QE 2022-10-31, QE 2022-11-14, QE 2022-11-28
Participants:
Linked BF Score: 20

 Description   

To pump up the data to named pipes and send a pipeline request with an external data source, a special program should be written for testing.

Add test shell extension that is explained in Test Driver



 Comments   
Comment by Githook User [ 18/Nov/22 ]

Author:

{'name': 'Kevin Cherkauer', 'email': 'kevin.cherkauer@mongodb.com', 'username': 'kevin-cherkauer'}

Message: SERVER-70392 Named Pipes add "unknown exception" messages
Branch: master
https://github.com/mongodb/mongo/commit/4ecad751532c5a04a8a8febb4b4f829f71e2e3c8

Comment by Kevin Cherkauer [ 17/Nov/22 ]

Main PR is merged, but right after that I realized I want to add one more tiny change in a second PR, so I am not closing this ticket yet. This will be to output a "caught an unknown exception" message when NamedPipeHelper::writeToPipe() or NamedPipeHelper::writeToPipeObjects() catches a non-DBException, instead of absorbing it completely silently, else we have no way of detecting that such an exception happened, and silent swallowing of exceptions can lead to much hair pulling while attempting to troubleshoot.

Comment by Githook User [ 17/Nov/22 ]

Author:

{'name': 'Kevin Cherkauer', 'email': 'kevin.cherkauer@mongodb.com', 'username': 'kevin-cherkauer'}

Message: SERVER-70392 Named Pipes _writeTestPipe shell function
Branch: master
https://github.com/mongodb/mongo/commit/3fdd9c6c3e71e9be3478f840afab8eea93c2061c

Comment by Kevin Cherkauer [ 21/Oct/22 ]

See also spec entry heading "Test Driver" in spec (where this heading-specific link turns out not to go to the heading it is supposed to): https://docs.google.com/document/d/1pRjz9k-vogrXsrHt72tZfokgeefa5TtfTwKlMh2KzY0/edit#heading=h.oe0jno8rm43m

and additional info in "Plan for next step" doc https://docs.google.com/document/d/1KLX8E5uI2Ml0ZarZhBVXDnKcxGPhvkaU-kBPxGOAbA0/edit

 

Generated at Thu Feb 08 06:16:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.