Package org.aksw.commons.rx.lookup
package org.aksw.commons.rx.lookup
-
ClassDescriptionEntryService<K,
V> Map a stream of items to a stream of entriesItemService<I,O> Take a stream of input items and transform it to a stream of output itemsA wrapper for a paginator which groups items into batches A batch is now a first class citizen, and retrievals and counts refer to the batchesListPaginatorMapWrapper<K,V, T> ListService<C,T> ListServiceFromList<C,T> ListServiceMapWrapper<C,K, V, T> LookupService<K,V> A lookup service builds a cold flowable that upon execution retrieves data for the given set of keys.A cache for already retrieved values.LookupServiceFromMapService<K,V, C> LookupServiceTransformKey<KI,KO, V> Create a new LookupService which maps keys to a target domain before passing them to the delegate service.LookupServiceTransformKey2<KI,KO, V> LookupServiceTransformValue<K,W, V> LookupTask<K,V> MapPaginator<K,V> I think the ListService interface should be changed to: ListService.createPaginator(Concept) TODO: There is an overlap with the RangedSupplierMapPaginatorTransformItem<K,I, O> FIXME Possibly extend with generic transform instead of just valueMapService<C,K, V> A list service is actually quite similar to JPA's TypedQuery, the main difference is, that we use a Map<K, V> here instead of a List<T> The rationale behind that is to be able to use the keys with further LookupServices I also had in mind retrieving data from JSON documents, where (before json-ld) there was no standard way for a designated ID attribute; so the idea was, that the list service indexes the result by whatever is the key.MapServiceFromListService<C,T, K, V> MapServiceTransformItem<C,K, I, O> A list service that transforms the input concept to another which gets passed to the underlying list serviceThis paginator maps each item through a lookup service by batching the lookup requests It does not change the count of items from the base paginator Note: Retains null valuesInterface for obtaining a stream of entries for a given range.