[
https://issues.apache.org/jira/browse/ASTERIXDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392006#comment-16392006
]
Chen Luo commented on ASTERIXDB-2310:
-------------------------------------
[~tillw], right now this feature is used only when the user has created the
primary key index first. Otherwise, the system's behavior for insert is still
the same as before. Making the primary key index by default could be easily
done from a technical perspective, but I think it needs more justifications and
could be done separately from this patch.
> 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)
