Ticket #885 (closed Defect: wontfix)
Limitting the result set size via getRelatedTopics() seems not to work
Reported by: | Malte | Owned by: | |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.8 |
Component: | DeepaMehta Standard Distribution | Version: | 4.7 |
Keywords: | Cc: | jri, JuergeN | |
Complexity: | 3 | Area: | |
Module: | deepamehta-core |
Description
To develop a migration i want to work just with 10 items instead of 1300+.
Now, when i do this:
ResultList<RelatedTopic> entries = topic.getRelatedTopics("dm4.core.aggregation", "dm4.core.child", "dm4.core.parent", "ka2.geo_object", 10); logger.info("### Identified " + entries.getSize() + " Related Geo Objects #####");
I most surely get the following output and NOT a result-set size of 10.
Nov 13, 2015 10:07:28 AM de.kiezatlas.etl.migrations.Migration5 run INFORMATION: ### Identified 1352 Related Geo Objects #####
Can you confirm this?
Change History
Note: See
TracTickets for help on using
tickets.
Since at least DM 4.3 (possibly earlier) the maxResultSize parameter is not supported anymore by the Core API. It will possibly be removed in the next DM release.
ticket:741#comment:2
ticket:741#comment:4
At the moment the Core provides no means of result limiting or paging.