[
https://issues.apache.org/jira/browse/ASTERIXDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392321#comment-16392321
]
Till commented on ASTERIXDB-2310:
---------------------------------
I think that it makes sense to leave the decision to create (and use) the
primary key index to the user.
That way the user can decide on the trade-offs.
> Use Primary Key Index to Enforce Insert Key Uniqueness
> ------------------------------------------------------
>
> Key: ASTERIXDB-2310
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2310
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: ING - Ingestion, STO - Storage
> Reporter: Chen Luo
> Assignee: Chen Luo
> Priority: Major
>
> **Currently when ingesting data using INSERT operations, we always check the
> primary index to ensure key uniqueness. However, this implies in most cases
> all ingested records might be accessed, which will slow down the ingestion
> performance a lot when the records cannot be cached. To handle this, we can
> enforce key uniqueness by checking the primary key index, which is much
> smaller and can be more easily cached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
