id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
154 |
COMPASS-3157
|
09/28/2018 12:58:34
|
Enforce maxTimeMS for every query sent to the server
|
Currently query filters that can be entered in the "Documents" panel don't use the {{maxtimems}} parameter. It is possible with non selective filters not supported by indexes to cause to run very heavy queries (COLLSCAN) on the MongoDB server causing possibly performance issues for the other clients. The parameter {{maxTimeMS}} is not set in the count and in the find commands sent. For example I loaded 5.7M tweets on a test MongoDB instances and I tried to use the filter {source: "a"} which causes a full collection scan over 5.7M documents: {code} 2018-09-28T10:42:42.588+0200 I NETWORK [conn6] received client metadata from 127.0.0.1:51337 conn6: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.6" }, os: { type: "Darwin", name: "Mac OS X", architecture: "x86_64", version: "17.7.0" } } 2018-09-28T10:44:52.172+0200 I COMMAND [conn5] command test.tweets command: count { count: "tweets", query: { source: "a" }, skip: 0, lsid: { id: UUID("884572c0-9842-4d2f-ada2-72250fc64b9a") }, $db: "test" } planSummary: COLLSCAN keysExamined:0 docsExamined:5712169 numYields:47574 reslen:44 locks:{ Global: { acquireCount: { r: 95150 } }, Database: { acquireCount: { r: 47575 } }, Collection: { acquireCount: { r: 47575 } } } protocol:op_query 137667ms 2018-09-28T10:46:53.077+0200 I COMMAND [conn1] command test.tweets appName: "MongoDB Compass Beta" command: find { find: "tweets", filter: { source: "a" }, limit: 20, returnKey: false, showRecordId: false, lsid: { id: UUID("884572c0-9842-4d2f-ada2-72250fc64b9a") }, $db: "test" } planSummary: COLLSCAN keysExamined:0 docsExamined:5712169 cursorExhausted:1 numYields:47243 nreturned:0 reslen:99 locks:{ Global: { acquireCount: { r: 94488 } }, Database: { acquireCount: { r: 47244 } }, Collection: { acquireCount: { r: 47244 } } } protocol:op_query 120877ms {code} The query is limited to 20 documents but has no {{maxTimeMS}} set. If you use the schema tab and you run the same filter, {{maxTimeMS}} is used, but I noticed that the same queries are then run without the timeout set: {code} 2018-09-28T13:33:44.380+0200 I COMMAND [conn10] command test.tweets command: count { count: "tweets", query: { source: "a" }, maxTimeMS: 10000, lsid: { id: UUID("bbda3184-e246-44bd-a5dd-43650f767757") }, $db: "test" } planSummary: COLLSCAN numYields:5903 reslen:182 locks:{ Global: { acquireCount: { r: 11808 } }, Database: { acquireCount: { r: 5904 } }, Collection: { acquireCount: { r: 5904 } } } protocol:op_query 10019ms 2018-09-28T13:33:44.390+0200 I COMMAND [conn8] command test.tweets command: count { count: "tweets", query: { source: "a" }, maxTimeMS: 10000, lsid: { id: UUID("e927734d-2de4-4d15-b958-5ed758860118") }, $db: "test" } planSummary: COLLSCAN numYields:5916 reslen:182 locks:{ Global: { acquireCount: { r: 11834 } }, Database: { acquireCount: { r: 5917 } }, Collection: { acquireCount: { r: 5917 } } } protocol:op_query 10017ms 2018-09-28T13:36:03.315+0200 I COMMAND [conn11] command test.tweets command: count { count: "tweets", query: { source: "a" }, skip: 0, lsid: { id: UUID("f153a56e-d826-4256-bc41-3402c718bf42") }, $db: "test" } planSummary: COLLSCAN keysExamined:0 docsExamined:5712169 numYields:48309 reslen:44 locks:{ Global: { acquireCount: { r: 96620 } }, Database: { acquireCount: { r: 48310 } }, Collection: { acquireCount: { r: 48310 } } } protocol:op_query 148950ms 2018-09-28T13:38:24.293+0200 I COMMAND [conn10] command test.tweets command: find { find: "tweets", filter: { source: "a" }, limit: 20, returnKey: false, showRecordId: false, lsid: { id: UUID("f153a56e-d826-4256-bc41-3402c718bf42") }, $db: "test" } planSummary: COLLSCAN keysExamined:0 docsExamined:5712169 cursorExhausted:1 numYields:47984 nreturned:0 reslen:99 locks:{ Global: { acquireCount: { r: 95970 } }, Database: { acquireCount: { r: 47985 } }, Collection: { acquireCount: { r: 47985 } } } protocol:op_query 140951ms {code} I tested this with Compass 1.16.0 beta 7.
| 3 |
155 |
COMPASS-3170
|
10/01/2018 12:25:53
|
Spike Lazy Linked List in Hadron Document
|
Spike turning hadron document into a configurable lazy linked list.
| 5 |
156 |
COMPASS-3190
|
10/11/2018 15:35:10
|
refactor edge case tests for python
|
Right now we have a few tests that are not JSON based, and therefore are only being tested from javascript. Refactor those tests so that we can easily test them from Python as well, and move them into JSON form where possible.
| 5 |
157 |
COMPASS-3192
|
10/11/2018 15:37:19
|
Add class layer between ANTLR and visitor classes
|
Right now there is a lot of repeated code between the python and javascript/shell visitors. Add a class layer in between the ANTLR-generated classes and the language-specific classes so that methods that all visitors have can be written in one place.
| 8 |
158 |
COMPASS-3202
|
10/16/2018 16:00:44
|
Fix auto-argument casting for functions
|
Works for javascript, but the python implementation uncovered some odd behavior so go through and verify that the casting mechanism is working correctly. And document it!
| 5 |
159 |
COMPASS-3224
|
10/30/2018 16:48:17
|
Add native regex type to python
|
Other than optional and named args, this is the last feature required for python as an input language.
| 3 |
160 |
COMPASS-3226
|
10/31/2018 13:31:11
|
api: library takes in and outputs a bson document
|
on this pass output document should have: * -name- * -path- * -regular type- * -iterate over nested documents and have the above information- * -bson_type- * -values- * -add arrays at type-
| 3 |
161 |
COMPASS-3227
|
10/31/2018 13:42:15
|
api: use typed_builder crate to support passin in options
|
https://docs.rs/typed-builder/0.1.1/typed_builder/
| 3 |
162 |
COMPASS-3235
|
11/06/2018 15:10:56
|
Eliminate multiple keychain password requests
|
The multiple keychain password prompt has been a long-running unexplained behavior we haven't been able to get to the bottom of. A roll-up of bug reports: - COMPASS-1767 - COMPASS-3091 - COMPASS-3147 - COMPASS-3215 My hunch after re-reading these tickets is this happens after an auto-update or a manual upgrade. What's most likely is that we simply need to call {{keytar}} methods from the main process via ipc rather than from the renderer as we do today. [See this example on stackoverflow|https://stackoverflow.com/a/43239854]. [From this blog post|https://medium.com/cameron-nokes/how-to-securely-store-sensitive-information-in-electron-with-node-keytar-51af99f1cfc4]: {quote} One other important note: I recommend you only call node-keytar from the main process. If you set a password from the main process and then attempt to get it from a renderer process, it’ll prompt a permissions dialog for the user (this is macOS only, Windows doesn’t seem to mind either way). Additionally, I think it’s cleaner and clearer to the user if the access control list has your app name and it’s icon, instead of MyApp Helper and the generic app icon which is what you get when a renderer sets it. {quote} More notes from previous tickets rolled up below. --- [{{SecKeychainFindGenericPassword}}|https://developer.apple.com/documentation/security/1397301-seckeychainfindgenericpassword?language=objc], which is the method [{{keytar}} uses to read a stored connection password|https://github.com/atom/node-keytar/blob/master/src/keytar_mac.cc#L107]. In the discussion: {quote} This function automatically calls the function [{{SecKeychainUnlock}}|https://developer.apple.com/documentation/security/1400341-seckeychainunlock?language=objc] to display the Unlock Keychain dialog box if the keychain is currently locked. {quote} A few ideas on what might need to happen: - Maybe something in the keytar bindings is too specific? Maybe when we run app-migrations today, macOS needs to re-validate or something? - Maybe a bulk-read call to fetch all passwords with {{FindPassword}} would guarantee this unlock dialog is shown once and only once in all cases (a single, implicit {{SecKeychainUnlock}} call), but there are some potential security implications to consider.
| 3 |
163 |
COMPASS-3252
|
11/14/2018 13:27:12
|
Paginate Document List Elements 20 at a time
|
Paginate the elements in the document in the document list 20 at a time.
| 5 |
164 |
COMPASS-3253
|
11/14/2018 13:28:32
|
Paginate Document Table View Columns 20 at a time
|
Paginate columns in the document list table view 20 at a time. Needs update to hadron-document to accept a number to the flush method.
| 5 |
165 |
COMPASS-3254
|
11/14/2018 14:11:30
|
Make Embedded Elements Lazy Loaded
|
Linked List in hadron-document is now lazy, but needs to expand further to lazy load embedded arrays and documents.
| 5 |
166 |
COMPASS-3255
|
11/14/2018 15:08:19
|
api: add unique and duplicate fields
|
each type has a count field. to see if there are duplicates the following checks should be done: * type.name is _Null_ or _Undefined_, check is type.count > 1 * if there is a type.values, check if the vec is all unique
| 5 |
167 |
COMPASS-3256
|
11/14/2018 15:11:44
|
testing: test to process a json file
|
should take in a json file (fanclub.json), convert it to bson, be able to parse it and return the current result. bson crate should have a deserializer for json implemented (hopefully). should also track timing.
| 5 |
168 |
COMPASS-3260
|
11/15/2018 11:04:46
|
Implement syntax for object generator
|
Support syntax like equality, math, etc.
| 5 |
169 |
COMPASS-3263
|
11/15/2018 15:06:51
|
library: performance metrics
|
compare results in rust to node. there is a way to write tests in rust as benchmarks. and that's what should be done for some of these.
| 2 |
170 |
COMPASS-3270
|
11/20/2018 09:20:22
|
Need a way to interrrupt/kill long running queries
|
If you run a long running query (this is easy to do if you get a keyname wrong) there is no way to interrupt the query before it times out or completes. The only option is to kill the window.
| 5 |
171 |
COMPASS-3291
|
11/23/2018 16:32:39
|
Agg. Pipeline settings
|
h3. User story As a Compass user I want to set sample size, number of docs in preview and maxTimeMS So that I have better control over how Compass is executing and displaying my pipeline. h3. Acceptance Criteria - There is a place in the UI where I can set sample size, number of docs in preview and maxTimeMS - By default, these settings are set to the default that is in Compass today - When I change one of these values, the new configuration is preserved across different Compass sessions h3. Notes - Should the setting be per collection, per pipeline, or global? How does that resonate with tabs (COMPASS-3289)?
| 5 |
172 |
COMPASS-3292
|
11/23/2018 16:32:59
|
Export to language discoverability
|
h3. User story As a Compass user I want a quick and discoverable access to “export to language” So that I can easily find it and I can take advantage of it to speed up my application development. h3. Acceptance Criteria - When I look at the Agg. Pipeline builder, I want to know it is possible to export my pipeline to different languages
| 1 |
173 |
COMPASS-3295
|
11/23/2018 16:34:31
|
Full-screen stage editor
|
h3. User story As a Compass user I want more real estate for my stage editor So that I can see everything I type into the editor without a lot of scrolling, even when my stage contains a lot of code. h3. Acceptance Criteria - When I am working on a stage, I can make the stage editor full-screen - When the stage editor is full-screen, I can see: -- The stage selector -- The code editor -- A way to reach the documentation/examples for the current stage -- A way to delete the stage -- A way to disable the stage -- A sample of the data entering the stage -- A sample of the data outputted by the stage -- A way to access the agg. pipeline settings, in case I need to adjust for instance the timeout if the current stage is too slow - When I close the full-screen editor, the changes I made are reflected in the “small editor” and the results in the preview are updated
| 1 |
174 |
COMPASS-3322
|
11/28/2018 12:16:13
|
library: refactor schema parser to use internal structs
|
currently using bson to manipulate data, should be using rust-specific methods.
| 5 |
175 |
COMPASS-3323
|
11/28/2018 12:17:41
|
api: investigate error handling
|
no errors are currently handled or thrown (200 path only!), this should be fixed.
| 3 |
176 |
COMPASS-3324
|
11/28/2018 12:23:49
|
library: modularize crate into separate components
|
right now everything is in one giant file, and that's a bit unsustainable. So: *lib.rs – public facing api* *schema_parser.rs – SchemaParser trait* *field_type.rs – FieldType trait* and possible have, *field.rs – Field trait*
| 3 |
177 |
COMPASS-3325
|
11/28/2018 12:24:56
|
library: investigate current use of lifetime
|
i *think* the lifetime situation is not as stable and efficient as it's meant to be. Look into (+ask advice) on how to improve this.
| 3 |
178 |
COMPASS-3328
|
11/28/2018 14:18:39
|
api: should allow for SchemaParser struct output
|
currently output is directly converted to json in _flush_ method. The api should allow for either of the two to be an output, or have a way for user to call `to_json` or `to_bson`, `to_struct` methods (or something of the sort) for easier conversions
| 5 |
179 |
COMPASS-3331
|
11/29/2018 13:44:50
|
Move Metrics To External Package
|
Move the metrics internal package to an external package in 10gen on the new plugin template.
| 3 |
180 |
COMPASS-3354
|
12/12/2018 14:23:06
|
Write error state tests for object generation
|
Fill out error tests with object generation
| 5 |
181 |
COMPASS-3356
|
12/12/2018 14:25:26
|
Fill out the rest of the tests for object generation
|
The leftover test files are builders, imports, and non-idiomatic. Should be filled out with object to compare with.
| 1 |
182 |
COMPASS-3370
|
01/03/2019 11:17:42
|
library: refactor field_type and fields vectors into a more efficient data structure
|
when iterating over the input document we need to be checking whether an existing field already exist, and if it does update its field type. this requires two iterations over the 'fields' and 'field_type' vectors. this should be rewritten to be a more efficient data structure that would not require the double iteration and overwriting of an existing field_type struct.
| 5 |
183 |
COMPASS-3371
|
01/03/2019 12:02:56
|
library: add assert_eq!(), test::Bencher and test::black_box() tests
|
the library is missing a large chuck of tests. to make sure future development is a bit more consistent, should add more tests \o/
| 3 |
184 |
COMPASS-3373
|
01/04/2019 12:58:48
|
bson: add Decimal128 implementation to bson crate
|
bson crate - [https://docs.rs/bson/0.13.0/bson/index.html] - does not currently support Decimal128 implementation. To be able to pattern match on all available bson types, we will have to PR in support for Decimal128.
| 8 |
185 |
COMPASS-3378
|
01/07/2019 15:44:28
|
bson: add wasm support for bson-rs crate
|
bson-rs crate is currently not wasm compatible as it makes system calls to get machine_id and process_id to make ObjectId bson type. This doesn't work in the browser and should be done as randomly generated numbers (like the node's bson package)
| 3 |
186 |
COMPASS-3379
|
01/08/2019 14:58:00
|
wasm: use regular result type in wasm exported functions
|
currently library wraps around the existing methods to export them for wasm as the usual "Result<T, E>" doesn't quite work in wasm. There is an outstanding issue on wasm-bindgen project to improve this experience: https://github.com/rustwasm/wasm-bindgen/issues/1017 this ticket is mostly for monitoring and talking to the rust-wasm team to improve the current implementation
| 3 |
187 |
COMPASS-3403
|
01/23/2019 15:04:43
|
wasm: set up compasss to allow for a dynamic import of npm package with wasm
|
to be able to consume the produced npm package with wasm, we need to be able to import it async. this requires for compass to handle an async import. possible things to look at: * babel plugins * webpack plugins: wasm-load, and adding `.wasm` in extensions.
| 3 |
188 |
COMPASS-3411
|
01/28/2019 16:22:04
|
api: should update fields and values in nested documents
|
currently only top level keys and values get updated with the parser, so values vectors of things like `_id.oid` don't get updated.
| 3 |
189 |
COMPASS-3412
|
01/28/2019 16:29:42
|
api: should include probability field for every field
|
should count the probability of a given field existing over a sample collection set. previously used calculation: {color:#24292e}field{color}{color:#24292e}.{color}{color:#24292e}probability{color} {color:#d73a49}={color} {color:#24292e}field{color}{color:#24292e}.{color}{color:#24292e}count{color} {color:#d73a49}/{color} {color:#24292e}parent{color}{color:#24292e}.{color}{color:#24292e}count{color}{color:#24292e};{color}
| 3 |
190 |
COMPASS-3413
|
01/28/2019 16:33:04
|
wasm: should be able to pass in a cursor from js side
|
instead of reading a file and reading it line by line, should be able to take a cursor and : # at first convert it to json and send to rust # and (not sure if this is possible) take a node created cursor and pass it to rust for a rust driver to read off data from the cursor
| 5 |
191 |
COMPASS-3423
|
01/31/2019 12:32:23
|
api: count fields should start at 1
|
count currently starts at zero for all the different fields, but should start at 1. all structs should have a method to update their respective count fields
| 1 |
192 |
COMPASS-3424
|
01/31/2019 12:34:07
|
library: implement fuzz testing for public api
|
there is a good library to do some fuzz testing in rust: [https://docs.rs/proptest/0.8.7/proptest/] idea here: make sure lib doesn't crash. example on how to do it: https://github.com/datrs/sleep-parser/blob/master/fuzz/fuzz_targets/header-from-vec.rs
| 3 |
193 |
COMPASS-3425
|
01/31/2019 12:35:42
|
library: implement dealing with array as value types
|
should destructure the array and put all the values inside the field_type values vector. Currently no matching or further processing is done for arrray bson type.
| 5 |
194 |
COMPASS-3426
|
01/31/2019 12:37:39
|
oss: write up docs on working with wasm-pack
|
we've been using wasm-pack to bundle a js + wasm package. They are currently in need of some docs to help people get this working in their own environments. This ticket is for putting a few of our use cases together for them.
| 1 |
195 |
COMPASS-3427
|
01/31/2019 13:11:36
|
api: nested documents in json should stay nested in SchemaParser struct
|
current output: {code:java} { "name": "city", "path": "address.city", "count": 0, "field_type": null, "probability": null, "has_duplicates": true, "types": [ { "name": "String", "path": "address.city", "count": 99, "bsonType": "String", "probability": null, "values": [ { "Str": "El Paso, Texas" }, { "Str": "El Paso, Texas" }, ] } ] }, { "name": "street", "path": "address.street", "count": 0, "field_type": null, "probability": null, "has_duplicates": false, "types": [ { "name": "String", "path": "address.street", "count": 99, "bsonType": "String", "probability": null, "values": [ { "Str": "133 Aloha Ave" }, { "Str": "290 East George Rd" } ] } ] } {code} expected output: {code:java} { "name": "address", "path": "address", "count": 100, "types": [{ "name": "Document", "bsonType": "Document", "path": "address", "count": 100, "fields": [ { "name": "city", "path": "address.city", "count": 100, "types": [{ "name": "String", "bsonType": "String", "path": "address.city", "count": 100, "values": ["El Paso, Texas", "El Paso, Texas"] }] }, { "name": "street", "path": "address.street", "count": 100, "types": [{ "name": "String", "bsonType": "String", "path": "address.street", "count": 100, "values": ["133 Aloha Ave", "290 East George Rd"] }] }] }] } {code}
| 5 |
196 |
COMPASS-3429
|
01/31/2019 13:26:38
|
api: to_json should strip off the ValueType type
|
I _think_ there should be a serde_json tag I can add to remove the current behaviour of value vector: {code:java} "values": [{"Str":"+17438917865"},{"Str":"+17518179206"},{"Str":"+14108799192"}] {code} should really just be: {code:java} "values": ["+17438917865", "+17518179206", "+14108799192"}] {code} investigate in serde_json docs
| 2 |
197 |
COMPASS-3432
|
02/01/2019 12:35:49
|
Render Visual Explain Plan for Any Explain Output
|
As a user I would like to drag the output of an explain plan into the Compass Explain tab and have the visual representation of it shown. - User can drag a file that the the output of an explain plan onto the explain tab and see the visual representation of it. - User can paste via CTRL/CMD+V the same output from the clipboard and see the visual representation of it.
| 2 |
198 |
COMPASS-3436
|
02/04/2019 13:47:22
|
api: should deal with a semantic_type option
|
SchemaParser::new() should accept an option to handle semantic types. setting this to Some should allow for parsing of an email "type" and a geojson "type" along with the regular bson types. should look for crates that could do the geojson check for us; email should be a rather straight forward regex.
| 5 |
199 |
COMPASS-3437
|
02/04/2019 13:48:05
|
api: should deal with a store_values option
|
when store_values is set to none, don't store values.
| 3 |
200 |
COMPASS-3438
|
02/04/2019 13:55:03
|
library: handle null and undefined data values
|
if either null or undefined, should remove all the field_type values in the finalizing step. this is currently done in the js land: {code:java} if (type.name === 'Null' || type.name === 'Undefined') { delete type.values; type.unique = type.count === 0 ? 0 : 1; type.has_duplicates = type.count > 1; } {code}
| 2 |
201 |
COMPASS-3439
|
02/04/2019 14:00:47
|
library: handle missing fields
|
if parent_count - field_count > 0, some fields are missing. Create an Undefined type to add this information: {code:java} field.types["Undefined"] = { name: 'Undefined', type: 'Undefined', path: field.path, count: parent_count - field_count }; {code}
| 3 |
202 |
COMPASS-3440
|
02/04/2019 14:03:26
|
compass: move schema analyser into its own plugin
|
We will not be able to use wasm modules directly inside compass (needs current version of webpack), so will need to have this moved from internal-plugins/ in compass into its own plugin. Work was started here: https://github.com/10gen/compass-schema
| 8 |
203 |
COMPASS-3445
|
02/05/2019 13:35:21
|
Extract Instance Header Plugin
|
Extract the instance header plugin to an external plugin on the new template.
| 8 |
204 |
COMPASS-3446
|
02/05/2019 13:36:24
|
Extract Sidebar Plugin
|
Extract the sidebar plugin to an external plugin on the new plugin template.
| 8 |
205 |
COMPASS-3447
|
02/05/2019 13:37:00
|
Extract Schema Plugin
|
Extract the schema plugin to an external plugin on the new plugin template.
| 8 |
206 |
COMPASS-3448
|
02/05/2019 13:37:31
|
Extract App Plugin
|
Extract the app plugin to an external plugin on the new plugin template.
| 8 |
207 |
COMPASS-3449
|
02/05/2019 13:38:17
|
Extract Home Plugin
|
Extract the home plugin to an external plugin on the new plugin template.
| 8 |
208 |
COMPASS-3450
|
02/05/2019 13:40:29
|
Webpackify Compass
|
Build Compass using Webpack. - Create Webpack configurations. - Remove compile cache. - Remove style manager. - Remove module cache. * Need to break up into multiple stories*
| 8 |
209 |
COMPASS-3452
|
02/06/2019 14:37:40
|
Move Collection Store into Collection Plugin
|
Move the Collection store into the collection plugin. - Convert to Redux store. - Change store structure to have multiple collections. - Bring in collection data for each collection. (readonly, capped, etc) - Switch all collection plugins to use new store.
| 8 |
210 |
COMPASS-3453
|
02/06/2019 14:39:29
|
TabNavBar Programatically Renders Tabs
|
Change the TabNavBar to programatically render tabs, instead of just setting display to none. - Change all plugins with the dependency: - compass-collection - compass-database - compass-instance
| 5 |
211 |
COMPASS-3454
|
02/06/2019 14:39:47
|
library: field should create a different field_type if type does not exist
|
currently, if two different types for the same field are in use, only one field_type will be used; should use two different field_types.
| 3 |
212 |
COMPASS-3482
|
03/04/2019 15:33:08
|
Save pipeline modal
|
Moves from inline to modal - {{↵}} in modal to save - {{Save}} on an unsaved pipeline brings up modal to specify a name - {{Save}} on an existing saved pipeline just saves - {{Save As...}} Enter new name {{➡️}} clone current pipeline - If canceling from {{Save As...}} the current pipeline is not cloned - {{Save As...}} from an unsaved pipeline should instead go to {{Save}}
| 3 |
213 |
COMPASS-3486
|
03/06/2019 12:39:34
|
wasm: pass bson from js side
|
Instead of serializing json on JS side and then deserializing it _and_ converting it to bson on rust side, we should just pass bson. This requires a change to mongodb-schema-parser to accept bson and collection-sampler to return bson.
| 8 |
214 |
COMPASS-3488
|
03/06/2019 13:02:02
|
library: finalize_schema should be the only place to count unique
|
currently probability, duplicates, and unique counts are calculated when _every_ new field is added. We want to do this only once, when we finalize the schema. This way if fields are also missing, we are able to get accurate counts.
| 3 |
215 |
COMPASS-3501
|
03/12/2019 13:53:45
|
1.18.0-beta.1 on macOS blocked by gatekeeper?
|
(from [slack|https://mongodb.slack.com/archives/C0U7K0MC3/p1552392785045300] HT [~brian.blevins])
| 1 |
216 |
COMPASS-3508
|
03/15/2019 14:41:02
|
Handle Large Namespaces in Tabs
|
Handle overflow of large namespaces in the collection tabs.
| 1 |
217 |
COMPASS-3509
|
03/15/2019 14:42:33
|
Collection Tab Keyboard Shortcuts
|
Add CTRL+T & CTRL+W to open/close tabs, plus CTRL+# to go to that tab index + 1
| 2 |
218 |
COMPASS-3510
|
03/15/2019 14:43:39
|
Drag+Drop Tab Reordering
|
Add ability to reorder collection tabs via drag+drop.
| 3 |
219 |
COMPASS-3511
|
03/15/2019 14:44:39
|
Add Configure Store Function to Collection tab Roles
|
When plugins define roles, add configure store option to the role.
| 2 |
220 |
COMPASS-3512
|
03/15/2019 14:45:36
|
Create Tab Carousel
|
When a large number of collection tabs are opened, allow user to scroll through them.
| 3 |
221 |
COMPASS-3513
|
03/15/2019 14:46:47
|
Collection Tabs are Subtab Aware
|
The collection tabs should display the currently active subtab in the collection.
| 3 |
222 |
COMPASS-3514
|
03/15/2019 14:50:42
|
All Collection Plugins Use Configure Store
|
Change all collection tab plugins to use the configure store pattern.
| 3 |
223 |
COMPASS-3515
|
03/15/2019 14:51:53
|
Add Select Namespace Event to Sidebar
|
The sidebar collection entries should emit the select-namespace event when clicking on a collection.
| 2 |
224 |
COMPASS-3516
|
03/15/2019 14:53:25
|
Collection Plugin Configures Stores
|
The collection plugin should configure the stores for each collection tab role and then pass the configured store into the plugin props.
| 5 |
225 |
COMPASS-3517
|
03/15/2019 14:54:42
|
Move Instance Header Plugin into Sidebar
|
As per the designs, move the instance header into the sidebar.
| 3 |
226 |
COMPASS-3518
|
03/15/2019 14:55:47
|
Collection HUD Plugins Take Data as Params
|
Change the Collection HUD plugins to take their required data as properties.
| 5 |
227 |
COMPASS-3519
|
03/15/2019 14:57:04
|
Pass Sub App Registry to Collection Tabs
|
Pass a new app registry to each of the collection tabs that is scoped only to the collection.
| 5 |
228 |
COMPASS-3520
|
03/15/2019 14:58:50
|
Scope Events to Sub App Registry
|
Field store, import/export, refresh events should be scoped to the collection app registry and not the global app registry.
| 3 |
229 |
COMPASS-3523
|
03/19/2019 08:47:49
|
Create a View from an aggregation pipeline
|
h3. User story As a Compass user I want to create a View from an aggregation pipeline So that I can make sure my data is in the right shape to be used in my application or to create a chart from it. h3. Acceptance criteria - When I am in the aggregation pipeline builder and I have written a valid aggregation, I want to be able to save it as a View and give it a name - When the server is older than 3.4, Save as a View is hidden - When an aggregation is saved as a View, it immediately appears in the sidebar - When an aggregation is saved as a View and I open the Database screen, I can see the newly created View - It is possible to create a View on top of another View - When I am trying to create a new View with the same name of an existing View, I want to see a meaningful error message - When the server returns errors (e.g., the user doesn't have the necessary permissions to create a view), Compass needs to handle the errors nicely - When the View has been created, Compass will open the new View in the main screen (in a new tab, as soon as tabs are available)
| 5 |
230 |
COMPASS-3524
|
03/19/2019 09:14:21
|
Using a View
|
h3. User story As a Compass user I want to see the details of a View when I select it So that I can: - easily understand that it is a View and I can see what collection it is based on - see the documents that are in the View and run queries and aggregations on top of it h3. Acceptance criteria - When I open a View in Compass, I can clearly see that I am actually looking at a View - When I open a View in Compass, I can see what collection the View is based on - When I open a View in Compass, I don't want to see N/A placeholders for the details we can't display (see screeenshot attached) - When I am building aggregations on top of a View, I want so see meaningful errors when I try to use [operators that are not supported on Views|https://docs.mongodb.com/manual/reference/method/db.createView]
| 1 |
231 |
COMPASS-3525
|
03/19/2019 09:24:21
|
Modify a View
|
h3. User story As a Compass user I want to edit a View (as in "edit the aggregation pipeline behind the View") So that I can go and adjust the details if the documents I am seeing are not in the shape I expected them to be h3. Acceptance criteria - In the sidebar, I have an entry point to go and edit the aggregation behind each View - In the main screen, when I am looking at a View, I have entry points to go and edit the aggregation behind the View - When I go and edit the aggregation behind a View, I am editing it in the aggregation pipeline builder of the Collection or View the View I am editing is based on - When I am done with editing the aggregation pipeline, I can update the View with the new pipeline - When the server returns errors (e.g., the user doesn't have the necessary permissions to modify a View), Compass needs to handle the errors nicely h3. Questions - When a View has been updated, can we jump back to wherever the user was when they clicked on an entry point to editing the View?
| 5 |
232 |
COMPASS-3526
|
03/19/2019 09:31:10
|
Duplicate a View
|
h3. User story As a Compass user I want to duplicate an existing View So that I don't need to start from scratch when I want to create a new, similar one h3. Acceptance criteria - In the sidebar, I have an entry point to duplicate a View - When I click on the entry point to duplicate a View, I can specify the name for the new View and then the new View is created with the same aggregation pipeline that is behind the original View - When the duplicate View is created, a new tab is opened pointing to the Documents view of the new View - When the server returns errors (e.g., the user doesn't have the necessary permissions to create a new view), Compass needs to handle the errors nicely
| 1 |
233 |
COMPASS-3537
|
03/22/2019 14:23:19
|
Allow User Data Directoy to be Configurable
|
The user data directory should be configurable on the Windows MSI installer.
| 3 |
234 |
COMPASS-3543
|
03/27/2019 16:13:26
|
Trim whitespaces on username field in Connect screen
|
In the connect screen, make sure white spaces are trimmed for the username field.
| 1 |
235 |
COMPASS-3573
|
04/15/2019 19:36:45
|
macOS dmg file size has doubled
|
While testing COMPASS-3496, I noticed the macOS installer sizes have ballooned substantially. Unpacked dmg is now 900+ Mb. This also impacts launch performance. Appears source maps are being included in installed payloads for 1 or more plugins... Seeing the below in devtools console: {code} DevTools failed to parse SourceMap: file:///Applications/MongoDB Compass Dev.app/Contents/Resources/app.asar/node_modules/@mongodb-js/compass-indexes/lib/index.js.map {code}
| 3 |
236 |
COMPASS-3589
|
04/24/2019 14:29:47
|
Connection model should parse all URI options
|
Update the connection model to parse all connection options that URI can have. Use the node driver URI parser for it instead of mongodb-url. - Replace mongodb-js/url parser with parseConnectionString from mongodb-js/mongodb-core - Update tests according to changes in the code - Add tests for parsing URI - Update returning object structure For more info the about connection string: https://docs.mongodb.com/manual/reference/connection-string/
| 5 |
237 |
COMPASS-3601
|
04/29/2019 10:54:32
|
Query History Support in Collection Tabs
|
Support Query History plugin in collection tabs.
| 5 |
238 |
COMPASS-3602
|
04/29/2019 10:55:13
|
Support Query Bar in Collection Tabs
|
Support for Query Bar in collection tabs.
| 5 |
239 |
COMPASS-3604
|
04/29/2019 10:56:20
|
Support Import/Export in Collection Tabs
|
Support for import/export in collection tabs.
| 5 |
240 |
COMPASS-3759
|
07/05/2019 13:11:17
|
Expose S3 download links for Compass releases
|
Some customers want to script the installation of the _latest stable version_ of Compass in enterprise environments. In order to do that, they would like to have a predictable URL to download the release artifacts. Can we provide a solution to this without hitting Github as we currently do?
| 5 |
241 |
COMPASS-3768
|
07/19/2019 19:46:02
|
Check if port is blocked by firewall
|
One of the first things we ask our students who have issues connecting to Atlas with Compass is to ensure port 27017 is not blocked by their firewall. We ask the student to navigate to: [http://portquiz.net:27017/] It would be nice for Compass to integrate a similar check to guide the user a little more when they experience a connection issue.
| 3 |
242 |
COMPASS-3780
|
07/26/2019 12:46:14
|
Display GeoJSON types other than points in Schema Map view
|
As a customer, I have a data set which contains both GeoJSON polygons and GeoJSON LinesStrings. It would be really useful to be able to see these rendered in the map view in the Schema tab.
| 3 |
243 |
COMPASS-3781
|
07/26/2019 12:48:33
|
Create other Geo-Queries in the Schema map view
|
As a customer, I would like the ability to click to draw a polygon, in the same way as I can currently drag out a circle, to create a GeoWithin Query.
| 2 |
244 |
COMPASS-3809
|
08/12/2019 08:42:29
|
Re-add drag circle functionality in mapview
|
This affects university students who can't complete the shipwrecks exercise without this functionality.
| 3 |
245 |
COMPASS-3817
|
08/14/2019 15:36:02
|
Update Electron to Latest Non-Backwards Breaking Stable Version
|
Need to update Electron to latest.
| 5 |
246 |
COMPASS-3818
|
08/14/2019 15:36:41
|
Update Plugin API Major Version
|
Update the Plugin API Major version to account for collection tabs.
| 5 |
247 |
COMPASS-3825
|
08/16/2019 14:01:57
|
Export CSV
|
h3. User story As a Compass user I want to export documents to a CSV file So that I can use them with tools outside the MongoDB ecosystem h3. Acceptance Criteria - Compass can export documents to a CSV file - When filter, project, sort or limit are specified for the collection the user is exporting, the user has the option to use them as the settings for the export (https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/347756471) - When an error happens during the export ** Compass shows a meaningful error message ** Compass says how many documents it managed to export - During the export, progress is displayed in the export modal
| 3 |
248 |
COMPASS-3826
|
08/16/2019 14:03:53
|
Import CSV: select fields
|
h3. User story As a Compass user I want to specify the fields I want to import from CSV So that I can control what data I want to have in my collection and specify the schema h3. Acceptance Criteria - Before the CSV import starts, users can select the fields that are included in the import (https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/344502152, COMPASS-2956) h3. Notes - We pre-read a portion of the CSV file (headerline and a few lines) to display the preview in the field/type selector.
| 2 |
249 |
COMPASS-3829
|
08/16/2019 14:06:28
|
Import JSON
|
h3. User story As a Compass user I want to import documents from a JSON file So that I can quickly seed my collection with existing data h3. Acceptance Criteria - Compass can import a valid JSON file (an array of documents, COMPASS-3185) - Compass cam import extended JSON (COMPASS-3384) - Compass can import a valid JSONL file (http://jsonlines.org/) - When an error happens during the import ** Compass shows a meaningful error message ** Compass says how many documents it managed to import - When the JSON is invalid ** Compass displays a meaningful error (COMPASS-3755) - During the import, progress is displayed in the import modal h3. Notes - JSONL = whatever is the spec that mongoimport handles
| 3 |
250 |
COMPASS-3830
|
08/16/2019 14:07:09
|
Import/Export entry points
|
As a Compass user I want to contextual entry points to import/export So that I can find and access the functionality where I needed h3. Acceptance criteria - -The contextual menu in the Collections view contains an entry point to Import (-[-https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135807).-|https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135807).-] - -The contextual menu for a collection in the side bar contains an entry point to Import ([https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135808])-. - The empty state of the documents tab contains an entry point to Import ([https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135808]) - The toolbar of the documents tab contains an entry point to Import ([https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135808]) - The entry point to Import opens the Import dialog in the context of the collection the user selected - -The contextual menu in the Collections view contains an entry point to Export (-[-https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135807).-|https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135807).-] - -The contextual menu for a collection in the side bar contains an entry point to Export (-[-https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135808)-|https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135808)-] - The entry point to Export opens the Export dialog in the context of the collection the user selected. By default, the whole collection will be exported. - The toolbar of the documents tab contains an entry point to Export ([https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/316135808]) - When Export is selected in the documents tab toolbar, Export defaults to the current filter, project, sort and limit h3. Notes - This story is only worth doing once the new implementation for import/export is ready.
| 3 |
251 |
COMPASS-3851
|
08/28/2019 15:17:21
|
Select fields when exporting a collection
|
h3. User story As a Compass user I want to select the fields that will be written into the exported JSON or CSV file So that I only export what is needed and I can keep the file small h3. Acceptance Criteria - Before exporting, the user can choose the fields that are exported (https://mongodb.invisionapp.com/share/BVNOZB4DYT3#/screens/349364209) - When fields are selected/deselected, if a projection exists, it is modified according to the new selection - Because the list of fields is probably generated from a sample of the collection, we give the user the possibility of adding other fields that may not exist in the sample - When the export is completed, only the fields that the user selected are exported
| 3 |
252 |
COMPASS-3853
|
08/28/2019 15:18:07
|
Replace backend of the feature with better CSV/JSON parsers
|
This task is about replacing the backend of the feature with community-maintained libraries that are battle-tested for CSV and JSON parsing/creation. This is timeboxed to 1 week and the main goal is that after this is done, Import/Export in Compass *with the existing UX* works reliably, no matter the size of the collection: * CSV are exported according to the CSV spec and can be imported back * JSON is imported with no errors. For the time being, since we don't change the UX, it's ok to still only support JSONL but let's keep in mind that eventually we want to also support JSON arrays. JSON is also exported with no errors, and an exported JSON can be imported back. If we are unable to make this work, we will fallback to using mongoimport/mongoexport.
| 5 |
253 |
COMPASS-3882
|
09/05/2019 20:08:25
|
Support tooltip in aggregations plugin (part 2)
|
Added one liners for $merge and $searchBeta
| 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.