Skip to content

Compass

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

9 results found

  1. Export the analysed schema as Typescript interface or type

    After analysing the schema, it is shown which types the fields have. It would be very nice if it could be exported as typescript interface or type accordingly.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Schema Analysis  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Entity Relationship Diagram

    I would appreciate a feature that enables the designer to map entity relationships in similar fashion to SQL entity relationship diagrams (ERD). At present I’m using Datensen’s Meteor Modeler for this purpose. It would be nice to have this capability rolled into Compass.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Schema Analysis  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. The JSON Schema export should be producing a jsonschema file that can be used immediately with schema validation

    It currently dumps a bunch of analysis information even though the menu item is "Share Schema as JSON". This file is useless for trying to harden or define a schema, even in non-mongodb tools (like validating documents match schema in our programs).

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Export schema analysis for documentation

    Users should be able to export the results of the schema analysis such that they can use it as a part of their documentation.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Schema analysis should recognize dictionaries

    In a sub-document, the keys may be common across most documents in the collection, or they may contain a set of random values. For example, using hostnames as the keys in the "hosts" sub-document.

    {
        ...
        hosts: {
            server1a: { ... }
            server2a: { ... }
            server3a: { ... }
        }
        } 
        {
        ...
        hosts: {
            server1b: { ... }
            server2b: { ... }
            server3b: { ... }
        }
    }
    

    The schema analysis should recognize the above situation to avoid creating thousands of sub-fields in the schema.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Sync Database Schema & Collection Schema

    To efficiently work in a development environment and then apply changes to the database changes, something like diff between development (source) and production (target) database, there has to be a feature of synchronising Schema only (without data) with optional opt in for Data as well. It should be bi directional. While synchronising Collections, Schema validation should also be allowed to synchronise apart from indexes. All these options should be allowed to select or de select with proper warnings.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Generate jsonSchema Validation Based on Schema Analysis

    Since Compass already provides a schema analysis, it would be useful if that analysis could be used generate jsonSchema. The result could be a starting point for the Validation tab or used in other tools such as https://hamidihamza.com/Angular6-json-schema-form/.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Configurable sample size in schema analyzer

    Sometimes larger or smaller sampling sizes (default is 1000) are desired since queries are taking too long or the sample size is not statistically useful.

    Could be a part of progressive loading/sampling.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Display GeoJSON types other than points in Schema Map view

    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.

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base