You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the Confluence Snowflake Connector and some other examples the only way of finding if an insert via the ingestion SDK has been successful is by polling the channel status end point for the last successfully written request token. Here for example
This then asks the question of how long to continue to poll until it can be considered the insert request has failed or is still processing?
This kind of wait parameterisation (poll n times) is dependent on platform load and hence not reliable.
I'd like to raise a feature request for the API be able to poll the status of a request token on a channel, is it pending, processing or failed for example and not just respond with the last request token that was successful written.
Of course how long would the request token be kept around for, I would imagine a time to live would be set on the channel for all request tokens submitted or an ACK could be sent via the client API to clear the token out for example.
The text was updated successfully, but these errors were encountered:
Looking at the Confluence Snowflake Connector and some other examples the only way of finding if an insert via the ingestion SDK has been successful is by polling the channel status end point for the last successfully written request token. Here for example
This then asks the question of how long to continue to poll until it can be considered the insert request has failed or is still processing?
This kind of wait parameterisation (poll n times) is dependent on platform load and hence not reliable.
I'd like to raise a feature request for the API be able to poll the status of a request token on a channel, is it pending, processing or failed for example and not just respond with the last request token that was successful written.
Of course how long would the request token be kept around for, I would imagine a time to live would be set on the channel for all request tokens submitted or an ACK could be sent via the client API to clear the token out for example.
The text was updated successfully, but these errors were encountered: