GeoTools
  1. GeoTools
  2. GEOT-1258

Memory data store is not order preserving

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.1
    • Fix Version/s: None
    • Component/s: main
    • Labels:
      None

      Description

      A Geoserver user noted the inline feature rendering order is not predictable. This is because inline features are put into a memory data store, and the latter is not order preserving, because uses a HashMap instead of a LinkedHashMap. I'm also wondering if a map is really needed, it ensures no two features have the same id, but it seems a little overkill (its memory requirements are far higher than a plain arraylist).

        Issue Links

          Activity

          Hide
          Andrea Aime added a comment -
          Fixed on 2.3.x (r25619) and trunk (r25621)
          Show
          Andrea Aime added a comment - Fixed on 2.3.x (r25619) and trunk (r25621)

            People

            • Assignee:
              Andrea Aime
              Reporter:
              Andrea Aime
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: