Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-6505

Use Enum instead of String for RegionConfig

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.9.0
    • None
    • None

    Description

      Why

      For the java developer, especially for newbie of gemfire/geode, it is confusing to get exact type of region correct.

      As Java developer
      I want there to be a pre-defined region type, such as constant interface, enum or otherwise
      So that I can refer to it and pass it as a parameter in my code to get quick feedback if I misspell something.

      Acceptance Criteria

      Scenario: auto-complete like functionality
      Given I am creating a region via the RegionConfig class
      When I use the method .setType()
      Then there is a pre-defined region type for me to choose from with one of the following options (see setShortcutAttributes on RegionConfig.class)
      LOCAL,LOCAL_HEAP_LRU,LOCAL_OVERFLOW,LOCAL_PERSISTENT,LOCAL_PERSISTENT_OVERFLOW,PARTITION,PARTITION_HEAP_LRU,PARTITION_OVERFLOW,PARTITION_PERSISTENT,PARTITION_PERSISTENT_OVERFLOW,PARTITION_PROXY,PARTITION_PROXY_REDUNDANT,PARTITION_REDUNDANT,PARTITION_REDUNDANT_HEAP_LRU,PARTITION_REDUNDANT_OVERFLOW,PARTITION_REDUNDANT_PERSISTENT,PARTITION_REDUNDANT_PERSISTENT_OVERFLOW,REPLICATE,REPLICATE_HEAP_LRU,REPLICATE_OVERFLOW,REPLICATE_PERSISTENT,REPLICATE_PERSISTENT_OVERFLOW,REPLICATE_PROXY
         AND an example usage is provided on the wiki
      Scenario: Wiki
      Given I am looking at our wiki page
      When I review the example code for create region
      Then I am able to see all of the possible region types and how to properly specify each.
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            ptran Peter Tran
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 3h 40m
                3h 40m