[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Fix Version/s: (was: 2.2)
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Issue Type: Task (was: New Feature)
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Fix Version/s: (was: 2.1)
2.2
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.2
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Fix Version/s: (was: 2.0)
2.1
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.1
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Priority: Major (was: Minor)
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Assignee: (was: Alexander Paschenko)
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Priority: Minor
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Priority: Minor (was: Major)
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>Priority: Minor
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Affects Version/s: 1.8
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Component/s: SQL
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
[
https://issues.apache.org/jira/browse/IGNITE-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4268:
Fix Version/s: 2.0
> Allow UPDATEs of the key and its fields in DML statements
> -
>
> Key: IGNITE-4268
> URL: https://issues.apache.org/jira/browse/IGNITE-4268
> Project: Ignite
> Issue Type: New Feature
> Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Initial DML implementation does not allow to UPDATE columns that correspond
> to key or its fields - direct modification would probably damage the index as
> well as hash map integrity, so UPDATE for such cases would need to do first
> {{remove}}, then {{put}}.
> In the course of review, it has been agreed that this feature will be
> implemented in later releases shortly to deliver initial implementation on
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
