We've created a couple of simple REST 2.0 services via ISD to retrieve data from a database via a DataStage job and have got them working.
We're now looking to see how we can implement the following and I'm looking for guidance/recommended approaches for doing this:
1. Pagination - When the underlying query returns more than a certain number of rows (e.g. 100), how can the resultset be paginated. REST practices recommend including a Limit/Offset or a next/previous link; however I'm curious as to the approaches members have taken with ISD and how they've been implemented.
2. Data shaping - for wide tables, how can the fields returned be controlled based on the fields required by the service consumer? For example, I have a customer table with 100's of fields, however, based on the list of fields specified via a query string parameter (e.g. ?fields=custName, custID,custCity), I'd like to return only the fields specified.
ISD Jobs are stateless; so there is no way to "buffer" or save rows for a particular user or session to get them on a subsequent call. You would have to code such logic yourself...perhaps saving ro ...
We're trying to steer the design away from these approaches primarily due to the complexity and customization associated with implementing the logic to achieve this.
We'll keep the options you've provided in mind when finalizing the design.
Add To Favorites View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
