Can we make readPreference in @MongoEntity configurable while using mongodb panache ?

[nitinty]

Hi Team,

Seems readPreference is not configurable in @MongoEntity which will require code deployment if we make any changes in readPreference at entity level.

Is there any plan to make it config based so that no code deployment required if we make any change in readPreference ?

@MongoEntity(collection = "reactive_user_collection", readPreference = "secondary")

I can do the required changes if you guys allow me

[quarkus-bot[bot]]

/cc @FroMage (panache), @loicmathieu (mongodb,panache), @radcortez (config)

[loicmathieu]

This will mix configuration for MongoDB with Panache inside the MongoDB client wich is not only used by MongoDB with Panache so it cannot be done like that.

What will be the expectation of a user of the MongoDB client when he does mongoClient.getCollection("user_collection") with this configuration ?

[nitinty]

With the above configuration, The user_collection will use a secondary readPreference by default. If you need to switch to primary, you can simply update the configuration, without requiring any code changes at the entity layer. And there is no separate named mongoclient required.

I can add this support in Quarkus framework.

[loicmathieu]

I think we don't understand, did you plan to configure that at the MongoDB client level when building the client?

[nitinty]

By overriding the behaviour of getCollection method of MongoDatabaseImpl class we can achieve it

public <TDocument> MongoCollection<TDocument> getCollection(String collectionName, Class<TDocument> documentClass)

[loicmathieu]

@nitinty sorry to come back to this so late, can you opened a feature request inside the repository so we didn't loose track?