Repository navigation
v0.11.0
- A list page (the first page or a later one) that gets
504 QBD_REQUEST_TIMEOUTis no longer thrown at once: the SDK long-polls the request until it ends or the call's time budget passes, like every other call and like the other SDKs, and never resends the page. It throwsRequestPendingExceptionif the request is still running at the deadline. - A write whose outcome was unknown and that the platform later recovered (request
succeeded,outcomeapplied,recovered: true,resultnull,recoveredObjectIdset) throws the newResultUnavailableExceptionfromRequestHandle.await(),RequestHandle.result()and the long poll after504 QBD_REQUEST_TIMEOUT. They threw aDaapiExceptionfrom parsing the missing result. It extendsInternalExceptionand carriesrequestId(),outcome()applied,retryable()false andrecoveredObjectId(); retrieve the object by that ID and do not send the write again. This holds also when the result is past retention (resultExpiredtrue). 500 INTERNAL_ERRORwithdetails.reasonresult_unavailable(the result is no longer available) throwsResultUnavailableException(recoveredObjectId()null) and is never retried, even whenDaapi-Should-Retrysays true. For a write that was applied (outcome: applied), never send it again and read the object instead; for a read (outcome: not_applicable), it is safe to send the read again.PriceLevelListParams.itemId(String)is an alias ofitemIds(String)with Conductor's name for this filter, so Conductor code ports unchanged. Both take one item ID; setting both to different values returns400 INVALID_PARAMETER.BatchPriceLevelListInputQueryhas the same alias for batch members.
All versions: CHANGELOG.md.