Step 2: Navigate to your desired collection Step 3: Click Collection. It will still be omitted if it is undefined. Step 1: Connect to the deployment containing the collection you wish to export data from. Alternatively, you can right-click on any server, database, or collection in the Connection Tree and choose Export (Collections, Buckets, Views). deselect the sub-fields) then the output will contain the config field regardless of whether it is null or an object. Once c onnected to a MongoDB database, open the Export Wizard by clicking on Export in the Global Toolbar. In any documents where config is null, the config field is omitted. just select the sub-fields), then the output documents will only contain the config field if there is data for the sub-fields. To resolve this, you can either deselect config or only select config. This error occurs when a certain object contains properties (/fields and values) in some documents and is empty in others. This makes it impossible to export a collection with a filter applied. The reason for this is a self-inflicted path collision error (see picture 1). I am unable to enter any text into the 'filters' input when exporting a collection. When I export in Compass and it asks me to select fields, I get 3 options:īy having the root field and the sub-fields selected, there is an overlap in the fields that are exported, hence the path collision issue. Description Problem Description The collection export function of Compass 1.26.0 is faulty. In my case I have documents with a config field that can be either an object or null: Gustavo is correct about the two types issue, but the solution depends on your use case and the data you're interested in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |