[ 
https://issues.apache.org/jira/browse/FLINK-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-5080:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned 
pull-request-available  (was: auto-deprioritized-major auto-unassigned 
pull-request-available stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> Cassandra connector ignores saveAsync result onSuccess
> ------------------------------------------------------
>
>                 Key: FLINK-5080
>                 URL: https://issues.apache.org/jira/browse/FLINK-5080
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Cassandra
>    Affects Versions: 1.1.3
>            Reporter: Jakub Nowacki
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, 
> auto-unassigned, pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When a record is saved to Cassandra it may return a ResultSet to the callback 
> given in the saveAsync; e.g. when we do {{INSERT ... IF NOT EXISTS}}, a 
> ResultSet is returned with column {{applied: false}} if the record exists and 
> the new record has not been inserted. Thus, we loose data in such case. 
> The minimal solution would be to log the result. The best solution would be 
> to add possibility of passing a custom callback; in this way we could deal 
> with a success or failure in more custom way.  Other solution is to add a 
> possibility to pass onSuccess and onFailure functions, which would be 
> executed inside the callback.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to