[
https://issues.apache.org/jira/browse/IGNITE-16859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-16859:
--------------------------------------
Labels: ignite-3 (was: )
> [SQL] Mandatory PK
> ------------------
>
> Key: IGNITE-16859
> URL: https://issues.apache.org/jira/browse/IGNITE-16859
> Project: Ignite
> Issue Type: Epic
> Components: sql
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> Apache Ignite is trying to unite the two worlds SQL and KV together, making
> the user experience of both worlds as natural as possible. Because of this,
> the key is considered mandatory.
> Nevertheless, the SQL standard allows tables without PK specified, and some
> customers potentially could have such tables in ther production. Besides,
> there are external tests (like TCP-H for instance), which don't bothering
> himself by defining PK which they won't be using anyway.
> To make it easier to migrate from tables without a key, let's provide a
> workaround where we could define a PK whose value will be automatically
> generated by some function.
> To make it easier to adopt external tests, we need to provide ability to
> inject the key without changing the source scripts.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
