- 
    Type:
Bug
 - 
    Resolution: Works as Designed
 - 
    Priority:
Minor - P4
 - 
    None
 - 
    Affects Version/s: None
 - 
    Component/s: None
 - 
    None
 
- 
        Storage Execution
 - 
        ALL
 - 
        
 - 
        Execution Team 2024-08-19
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
On mongos, if a user runs
db.myColl.createIndex({created: 1}, {expireAfterSeconds: 10.23}) 
the slow query log shows 'expireAfterSeconds' : 10.23
However, the mongod logs report the index is created with 'expireAfterSeconds':10.
This is minor, but could be misleading when debugging index inconsistencies. Especially for tools relying on $listCatalog, which truncates 'expireAfterSeconds' to an integer in 7.3, but preserves the floating point value in 6.0.
It would be nice to log a warning when the 'expireAfterSeconds' is truncated to an integer - or have the 'slow query' logs for a single command reflect consistent TTL fields through mongos and mongod.
- related to
 - 
                    
SERVER-92360 Oplog entries report collMod 'expireAfterSeconds' field as type 'long'
-         
 - Blocked
 
 -