Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6430

Move WT_CONN_SERVER flags into their own field

    • Type: Icon: Technical Debt Technical Debt
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.9.0, 4.4.4, 4.2.13, 4.0.24
    • Affects Version/s: None
    • Component/s: None
    • None
    • v4.2, v4.0

      I added a new connection flag on a branch I'm working on today. I noticed that all the connection flags are already used up. (I'll work around that for now.) However the automatic flag generation script happily adds in a new one, potentially overflowing the field. It would be nice if the script could somehow detect it.

      Nearly all flag fields are 32 bits, including the connection flags. There are several paths that whoever works on this can consider. We could bump the field to 64 bits. We could separate out some of them to a new field (for instance WT_CONN_SERVER_*). Or something else.

            sue.loverso@mongodb.com Susan LoVerso
            sue.loverso@mongodb.com Susan LoVerso
            0 Vote for this issue
            4 Start watching this issue