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

bulk configuration string doesn't detect illegal values

    • Type: Icon: Task Task
    • Resolution: Done
    • WT1.5.0
    • Affects Version/s: None
    • Component/s: None

      The bulk configuration was changed to type "string" and then the "bitmap" string was added, but we no longer detect bad values, that is, configuring a cursor with "bulk=foo" doesn't result in an illegal configuration error.

      There's some odd code in *wt_curfile_create() (but not in *wt_curfile_open??) that calls __wt_config_gets_defno for "bulk" and then does a string match, that probably has to change.

      I'd suggest we make bulk a boolean again, and then add a new cursor configuration boolean "bulk-bitmap" that configures for the special bitmap load.

      Alternatively, we could change the bulk configuration type to 'choices', and list true, false and bitmap as the list of choices, but then we are requiring applications to specify "bulk=true", it's an API change.

      Interestingly enough, the bulk configuration string is the only configuration string that uses a type of 'string', do we still need it?

      Michael, can you decide what, if anything, you want done, and then assign it back to me and I'll code it up.

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: