On Tue, Aug 09, 2011 at 03:23:04PM +0200, Michael Hanselmann wrote: > Am 9. August 2011 15:08 schrieb Iustin Pop <[email protected]>: > > On Tue, Aug 09, 2011 at 02:54:26PM +0200, Michael Hanselmann wrote: > >> One one hand I agree with you—it can indeed be a lot of data. On the > >> other hand all other resources provide the same fields for bulk > >> queries as for individual queries. Should we keep this consistency or > >> not? > > > > Ah, good point. Hmm… one gets the feeling that we would need to add > > fields over RAPI :) > > You mean /2/query/…?fields=name,xyz,bar,baz :-) Okay, jobs aren't in query2 > yet.
Something along those lines, yes. The current situation is fine as long as all the fields have (approximately) the same cost, but when not, it makes sense to optimise. > > I really don't think that getting the log, for example, at each poll is > > useful, so I would be evil this time and break consistency (well > > documented breakage, of course). What do you think? > > I'll send a patch excluding “oplog” and “opresult” from the bulk list. Thanks. iustin
