getAllIndexedFS() may yield strange results in combination with custom indexes

[GoogleCodeExporter]

As far as I can tell from FSIndexRepositoryImpl.getAllIndexedFS(Type, 
List<FSIterator<FeatureStructure>>), the index repository is scanned for some 
index for the specified type:

1) if a auto-generated index is present, that is used (auto-generated means, 
the user did not explicitly generate one)
2) if the user did generate an index or of the type is an annotation type (UIMA 
always generates a sorted index for those), it looks first for some sorted index
3) if no sorted index could be found, it tries a bag index, then a set index.

From the index found by the above procedure, all FSes of the specified type and 
its subtypes are extracted.

For most cases this should work well. If a user creates multiple custom indexes 
and adds FSes to some, but not to others, strange things might happen. When 
uimaFIT has better support for custom indexes, we should probably add some test 
cases in this department, in particular for the methods like CasUtil.selectFS() 
or JCasUtil.select() in combination with custom indexes.

Original issue reported on code.google.com by richard.eckart on 16 Mar 2011 at 7:06

[GoogleCodeExporter]

The approach suggested in issue #65 would offer a way to make such issues 
controllable by allowing the user to specify on what he wants to operate.

Original comment by richard.eckart on 18 Mar 2011 at 4:16

[GoogleCodeExporter]

Original comment by richard.eckart on 7 Jan 2013 at 4:51

• Added labels: ASFJira-No