[SERVER-42215] View Definition validity inconsistent between primary and secondary Created: 12/Jul/19  Updated: 27/Oct/23  Resolved: 29/Jul/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mikhail Ivkov (Inactive) Assignee: Mikhail Ivkov (Inactive)
Resolution: Gone away Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:
Linked BF Score: 17

 Description   

replicated_collection_infos.js

(function() {
 const rst = new ReplSetTest(
 
{nodes: 2}
 
);
 rst.startSet();
 rst.initiate();
 
const testDB = rst.getPrimary().getDB('$gt');
 assert.commandWorked(testDB.createView('testView', 'testColl', []));
 rst.awaitReplication();
 rst.getPrimary().getDB('$gt').getCollectionInfos({name: {$in: ['testView', 'testColl']}});
 
rst.getSecondary().getDB('$gt').getCollectionInfos({name: {$in: ['testView', 'testColl']}});
 
rst.stopSet();
 })();

Run as: resmoke replicated_collection_infos.js

The primary.getCollectionInfos succeeds but the secondary.getCollectionInfos fails.



 Comments   
Comment by Githook User [ 29/Jul/19 ]

Author:

{'name': 'Misha Ivkov', 'email': 'misha.ivkov@10gen.com', 'username': 'mivkov'}

Message: SERVER-42215 Add test that invalid views fail
Branch: master
https://github.com/mongodb/mongo/commit/655bd3b4d0b8e87e93cd1e1445a354cbc87382af

Comment by Sam Mercier [ 25/Jul/19 ]

misha.ivkov this is ur BF! go you!

 

Generated at Thu Feb 08 04:59:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.