[jira] [Updated] (IGNITE-16856) Sql. Ability to create table without specifying PK
[
https://issues.apache.org/jira/browse/IGNITE-16856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-16856:
---
Fix Version/s: 3.0.0-alpha5
> Sql. Ability to create table without specifying PK
> --
>
> Key: IGNITE-16856
> URL: https://issues.apache.org/jira/browse/IGNITE-16856
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> Despite a keyless use case currently is not supported by Ignite-3, SQL
> standard allows to create such tables, and many external tests (TCP-H for
> instance) are taking advantage of this.
> To make it easier to adopt such a tests, let's provide a special mode for
> Ignite, where implicit PK will be created in case of lack explicit one.
> Key points to consider:
> * This mode considered for test purpose only, hence the implementation
> should be as less invasive as possible.
> * An implicit key column should not be returned by {{SELECT *}} queries. It
> may be accessed by its name though.
> * Type of this column doesn't matter, but the range of possible values
> should be big enough to support billiones of unique values.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16856) Sql. Ability to create table without specifying PK
[
https://issues.apache.org/jira/browse/IGNITE-16856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-16856:
--
Description:
Despite a keyless use case currently is not supported by Ignite-3, SQL standard
allows to create such tables, and many external tests (TCP-H for instance) are
taking advantage of this.
To make it easier to adopt such a tests, let's provide a special mode for
Ignite, where implicit PK will be created in case of lack explicit one.
Key points to consider:
* This mode considered for test purpose only, hence the implementation should
be as less invasive as possible.
* An implicit key column should not be returned by {{SELECT *}} queries. It
may be accessed by its name though.
* Type of this column doesn't matter, but the range of possible values should
be big enough to support billiones of unique values.
was:
Despite a keyless use case currently is not supported by Ignite-3, SQL standard
allows to create such tables, and many external tests (TCP-H for instance) are
taking advantage of this.
To ease of adoption such a tests, let's provide a special mode for Ignite,
where implicit PK will be created in case of lack explicit one.
Key points to consider:
* This mode considered for test purpose only, hence the implementation should
be as less invasive as possible.
* An implicit key column should not be returned by {{SELECT *}} queries. It
may be accessed by its name though.
* Type of this column doesn't matter, but the range of possible values should
be big enough to support billiones of unique values.
> Sql. Ability to create table without specifying PK
> --
>
> Key: IGNITE-16856
> URL: https://issues.apache.org/jira/browse/IGNITE-16856
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
>
> Despite a keyless use case currently is not supported by Ignite-3, SQL
> standard allows to create such tables, and many external tests (TCP-H for
> instance) are taking advantage of this.
> To make it easier to adopt such a tests, let's provide a special mode for
> Ignite, where implicit PK will be created in case of lack explicit one.
> Key points to consider:
> * This mode considered for test purpose only, hence the implementation
> should be as less invasive as possible.
> * An implicit key column should not be returned by {{SELECT *}} queries. It
> may be accessed by its name though.
> * Type of this column doesn't matter, but the range of possible values
> should be big enough to support billiones of unique values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16856) Sql. Ability to create table without specifying PK
[
https://issues.apache.org/jira/browse/IGNITE-16856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-16856:
--
Epic Link: IGNITE-16859
> Sql. Ability to create table without specifying PK
> --
>
> Key: IGNITE-16856
> URL: https://issues.apache.org/jira/browse/IGNITE-16856
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
>
> Despite a keyless use case currently is not supported by Ignite-3, SQL
> standard allows to create such tables, and many external tests (TCP-H for
> instance) are taking advantage of this.
> To ease of adoption such a tests, let's provide a special mode for Ignite,
> where implicit PK will be created in case of lack explicit one.
> Key points to consider:
> * This mode considered for test purpose only, hence the implementation
> should be as less invasive as possible.
> * An implicit key column should not be returned by {{SELECT *}} queries. It
> may be accessed by its name though.
> * Type of this column doesn't matter, but the range of possible values
> should be big enough to support billiones of unique values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16856) Sql. Ability to create table without specifying PK
[
https://issues.apache.org/jira/browse/IGNITE-16856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-16856:
--
Summary: Sql. Ability to create table without specifying PK (was: Ability
to create table without specifying PK)
> Sql. Ability to create table without specifying PK
> --
>
> Key: IGNITE-16856
> URL: https://issues.apache.org/jira/browse/IGNITE-16856
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
>
> Despite a keyless use case currently is not supported by Ignite-3, SQL
> standard allows to create such tables, and many external tests (TCP-H for
> instance) are taking advantage of this.
> To ease of adoption such a tests, let's provide a special mode for Ignite,
> where implicit PK will be created in case of lack explicit one.
> Key points to consider:
> * This mode considered for test purpose only, hence the implementation
> should be as less invasive as possible.
> * An implicit key column should not be returned by {{SELECT *}} queries. It
> may be accessed by its name though.
> * Type of this column doesn't matter, but the range of possible values
> should be big enough to support billiones of unique values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16856) Sql. Ability to create table without specifying PK
[
https://issues.apache.org/jira/browse/IGNITE-16856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-16856:
--
Labels: ignite-3 (was: )
> Sql. Ability to create table without specifying PK
> --
>
> Key: IGNITE-16856
> URL: https://issues.apache.org/jira/browse/IGNITE-16856
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
>
> Despite a keyless use case currently is not supported by Ignite-3, SQL
> standard allows to create such tables, and many external tests (TCP-H for
> instance) are taking advantage of this.
> To ease of adoption such a tests, let's provide a special mode for Ignite,
> where implicit PK will be created in case of lack explicit one.
> Key points to consider:
> * This mode considered for test purpose only, hence the implementation
> should be as less invasive as possible.
> * An implicit key column should not be returned by {{SELECT *}} queries. It
> may be accessed by its name though.
> * Type of this column doesn't matter, but the range of possible values
> should be big enough to support billiones of unique values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
