Skip to content

Drivers

← MongoDB Feedback Engine

How can we improve the MongoDB Drivers?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

22 results found

  1. CSFLE - Enable automatic decryption of change streams

    Currently change streams are disabled when a CSFLE MonogClient() session is used.
    This is due to this CSFLE specifications.

    Mongocryptd will not support “collectionless” aggregation metadata sources, which read metadata that doesn’t pertain to a particular collection. The drivers should not contact mongocryptd for such commands, since they don’t have a particular schema to pass to mongocryptd, so it is the drivers’ ultimate responsibility to return an error to the application for the collectionless aggregation metadata sources:

        $currentOp
    $changeStream for watching a database or the whole cluster
    $listSessions
    $listLocalSessions

    Enable auto decryption and change streams in the presence of auto-encryption-settings

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Ignore unmapped fields in pojo deserialization

    A recent ticket (00664772) with the mongodb support team confirm that the following case is not handled by the Java driver:

    class Foo {
    int x;
    int y;
    }

    I can successfully write and read it. However, if the Document has extra fields, it cannot be deserialized and no option exists to allow this behavior:

    { x:123, y:456, z:789 } // why can't I ignore 'z'?

    My suggestion is, provide an annotation to support this behavior:
    @BsonIgnoreUnmappedFields
    class Foo {
    int x;
    int y;
    }

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
2 Next →
  • Don't see your idea?

Drivers

Categories

Feedback and Knowledge Base

(thinking…)