uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Resolved] (UIMA-5496) uv3 replace FsIndex_set_sorted, apply many fixes to replaced one
Date Fri, 01 Sep 2017 18:41:00 GMT

     [ https://issues.apache.org/jira/browse/UIMA-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marshall Schor resolved UIMA-5496.
    Resolution: Fixed

> uv3 replace FsIndex_set_sorted, apply many fixes to replaced one
> ----------------------------------------------------------------
>                 Key: UIMA-5496
>                 URL: https://issues.apache.org/jira/browse/UIMA-5496
>             Project: UIMA
>          Issue Type: Improvement
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 3.0.0SDK-beta
> The first implementation of FsIndex_set_sorted assumed the underlying index was implemented
by OrderedFsSet_array2.  This did a complex set of tradeoffs that improved insert/remove performance
at the expense of more complex iteration. The OrderedFsSet_array2 impl was complex and was
buggy (many bugs were removed, though, in this most recent commit).
> This implementation was based on "NavigableSet" apis, which required creation of multiple
iterators as direction of iteration was reversed, and was quite complex.
> This change reverts both of these to a simpler more straight forward implementation,
closer to how UIMA v2 did this, but with significant improvements in both iteration and insert/remove.
 The underlying OrderedFsSet_array keeps the indexed items for one type in a compacted array,
with free space possible at the begin and/or end, and rebalancing done as needed.  The iterator
implementation removed several layers of indirection and is now implemented directly on top
of the OrderedFsSet_array itself.

This message was sent by Atlassian JIRA

View raw message