See https://github.com/mongodb/mongo-hibernate/pull/27#discussion_r1943302102 for the context. Originally, we thought things like timeout are to be handled in MongoPreparedStatement/MongoStatement, but given that QueryOptions are specified via SqlAstTranslator.translate, we should encode that in our AstNode.

The timeout ticket has been rectified at https://jira.mongodb.org/browse/HIBERNATE-55, so this ticket would exclude it and focus on the following options potentially we could implement:

• FlushMode getFlushMode();
• Boolean isReadOnly();
• AppliedGraph getAppliedGraph(); (depends on table joining implementation: https://jira.mongodb.org/browse/HIBERNATE-65)
• @Nullable TupleTransformer<?> getTupleTransformer();
• @Nullable ResultListTransformer<?> getResultListTransformer();

• Boolean isResultCachingEnabled();
• Set<String> getEnabledFetchProfiles(); (depends on table joining implementation: https://jira.mongodb.org/browse/HIBERNATE-65)
• List<String> getDatabaseHints();

The following methods we are certain we can't implement in MongoDB:

• LockOptions getLockOptions();

Note that the following options have been tracked by creating associated tickets already:

• Integer getTimeout(): https://jira.mongodb.org/browse/HIBERNATE-55
• String getComment(); https://jira.mongodb.org/browse/HIBERNATE-53
• Integer getFetchSize(); https://jira.mongodb.org/browse/HIBERNATE-54
• Limit getLimit(); https://jira.mongodb.org/browse/HIBERNATE-70

Given the current status, it seems the priority of this ticket could be lowered even out of GA.