You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Michael J. Carey (JIRA)" <ji...@apache.org> on 2018/03/22 00:09:00 UTC
[jira] [Comment Edited] (ASTERIXDB-2335) Improved feed duplicate
handling semantics
[ https://issues.apache.org/jira/browse/ASTERIXDB-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408815#comment-16408815 ]
Michael J. Carey edited comment on ASTERIXDB-2335 at 3/22/18 12:08 AM:
-----------------------------------------------------------------------
Or to put it another way, it would be nice to also support three variations w.r.t. what-to-do-on-duplicate-key:
# Insert - incoming record is discarded and error is logged.
# Insert-if-absent - the data sender is "at least once" - so keep what's already there and DON'T log an error.
# Upsert - the incoming record is new data, so overwrite (replace) the old data with it.
was (Author: dtabass):
Or to put it another way, it would be nice to also support three variations w.r.t. what-do-do-on-duplicate-key:
# Insert - incoming record is discarded and error is logged.
# Insert-if-absent - the data sender is "at least once" - so keep what's already there and DON'T log an error.
# Upsert - the incoming record is new data, so overwrite (replace) the old data with it.
> Improved feed duplicate handling semantics
> ------------------------------------------
>
> Key: ASTERIXDB-2335
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2335
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Michael J. Carey
> Priority: Minor
>
> Currently we have insert once, and upsert feeds. It would be nice to have a way to specify upsert coniditonally based on some property between the duplicate and existing record.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)