[COMPASS-3922] Documents with a "length" field break a few things Created: 05/Oct/19  Updated: 25/Aug/23  Resolved: 30/Jun/22

Status: Closed
Project: Compass
Component/s: Compass, Documents, UI / UX
Affects Version/s: 1.19.12
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Felicia Hsieh Assignee: Unassigned
Resolution: Declined Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS X 10.14.6


Attachments: PNG File 2019103111584599.png     PNG File 2019103112063205.png     PNG File 2020090813240574.png     File Screen Recording 2019-12-04 at 11.52.47-1.mov     File Screen Recording 2019-12-04 at 11.52.47.mov    
Issue Links:
Duplicate
is duplicated by COMPASS-4404 Indices with a "length" field break a... Closed
Related
related to COMPASS-4756 Indexes on a 'length' field breaks th... Closed
related to COMPASS-5973 Indexes with a key "length" will not ... Closed
Sprint: Iteration Ragamuffin

 Description   

Compass with a database with GridFS collections, fs.files and fs.chunks may see a complete blank screen when the collection(s) is selected.

Awaiting additional devtools info.

 



 Comments   
Comment by Jessica Sigafoos [ 30/Jun/22 ]

Thanks for your feedback! If you are still seeing this issue in the latest version of the application, please file a new ticket.

Comment by Jessica Sigafoos [ 09/Sep/20 ]

From COMPASS-4404:

Compass with a database with GridFS collections, fs.files and fs.chunks may see a complete blank screen when the collection(s) is selected.
 
This issue still exists in version 1.22.1

The behavior in 1.22.1 is slightly improved, does not crash the entire interface, but the "Indexes" tab is still blank, not even showing the "_id" index.

Comment by L [ 31/Oct/19 ]

Steps to reproduce:

  1. connect to a db with Compass
  2. create a new collection
  3. create an index on that new collection, with a "length" key, e.g. { "length": 1 }
  4. after you click the create button, the screen becomes blank.
Comment by L [ 31/Oct/19 ]

The suspected problem should be the collection's index. This bug exists for whatever collection that have an index with a "length" key.

Seems that when there is a "length" property in the key, the key object is treated as an array instead of object, and the data handling logic breaks.

Generated at Wed Feb 07 22:34:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.