[
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-unassigned pull-request-available
stale-minor (was: auto-deprioritized-major auto-unassigned
pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, auto-unassigned,
> pull-request-available, stale-minor
> 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)
