[jira] [Updated] (IGNITE-14937) Introduce index management
[ https://issues.apache.org/jira/browse/IGNITE-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14937: -- Fix Version/s: 3.0.0-alpha6 > Introduce index management > -- > > Key: IGNITE-14937 > URL: https://issues.apache.org/jira/browse/IGNITE-14937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > We need to introduce component to handle index-related manipulation commands > (like CREATE or DROP) as well as manage indices' lifecycle. > As a first phase let's introduce index manager with functionality reduced to > the following duties: > * accepting CREATE|DROP command and changing the schema > * --handling the event from configuration and creating reduced set of > index-related structures (index description only for now) on all necessary > nodes-- -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14937) Introduce index management
[ https://issues.apache.org/jira/browse/IGNITE-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14937: -- Description: We need to introduce component to handle index-related manipulation commands (like CREATE or DROP) as well as manage indices' lifecycle. As a first phase let's introduce index manager with functionality reduced to the following duties: * accepting CREATE|DROP command and changing the schema * --handling the event from configuration and creating reduced set of index-related structures (index description only for now) on all necessary nodes-- was: We need to introduce component to handle index-related manipulation commands (like CREATE or DROP) as well as manage indices' lifecycle. As a first phase let's introduce index manager with functionality reduced to the following duties: * accepting CREATE|DROP command and changing the schema * -handling the event from configuration and creating reduced set of index-related structures (index description only for now) on all necessary nodes - > Introduce index management > -- > > Key: IGNITE-14937 > URL: https://issues.apache.org/jira/browse/IGNITE-14937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > We need to introduce component to handle index-related manipulation commands > (like CREATE or DROP) as well as manage indices' lifecycle. > As a first phase let's introduce index manager with functionality reduced to > the following duties: > * accepting CREATE|DROP command and changing the schema > * --handling the event from configuration and creating reduced set of > index-related structures (index description only for now) on all necessary > nodes-- -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14937) Introduce index management
[ https://issues.apache.org/jira/browse/IGNITE-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14937: -- Description: We need to introduce component to handle index-related manipulation commands (like CREATE or DROP) as well as manage indices' lifecycle. As a first phase let's introduce index manager with functionality reduced to the following duties: * accepting CREATE|DROP command and changing the schema * -handling the event from configuration and creating reduced set of index-related structures (index description only for now) on all necessary nodes - was: We need to introduce component to handle index-related manipulation commands (like CREATE or DROP) as well as manage indices' lifecycle. As a first phase let's introduce index manager with functionality reduced to the following duties: * accepting CREATE|DROP command and changing the schema * handling the event from configuration and creating reduced set of index-related structures (index description only for now) on all necessary nodes > Introduce index management > -- > > Key: IGNITE-14937 > URL: https://issues.apache.org/jira/browse/IGNITE-14937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > We need to introduce component to handle index-related manipulation commands > (like CREATE or DROP) as well as manage indices' lifecycle. > As a first phase let's introduce index manager with functionality reduced to > the following duties: > * accepting CREATE|DROP command and changing the schema > * -handling the event from configuration and creating reduced set of > index-related structures (index description only for now) on all necessary > nodes - -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14937) Introduce index management
[ https://issues.apache.org/jira/browse/IGNITE-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14937: -- Description: We need to introduce component to handle index-related manipulation commands (like CREATE or DROP) as well as manage indices' lifecycle. As a first phase let's introduce index manager with functionality reduced to the following duties: * accepting CREATE|DROP command and changing the schema * handling the event from configuration and creating reduced set of index-related structures (index description only for now) on all necessary nodes was: Public index schema (required indexes) and current indexes state on the cluster are different. We have to track it, store it and provide actual indexes schema state for any components: select query, DDL query etc.. > Introduce index management > -- > > Key: IGNITE-14937 > URL: https://issues.apache.org/jira/browse/IGNITE-14937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > We need to introduce component to handle index-related manipulation commands > (like CREATE or DROP) as well as manage indices' lifecycle. > As a first phase let's introduce index manager with functionality reduced to > the following duties: > * accepting CREATE|DROP command and changing the schema > * handling the event from configuration and creating reduced set of > index-related structures (index description only for now) on all necessary > nodes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14937) Introduce index management
[ https://issues.apache.org/jira/browse/IGNITE-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14937: -- Summary: Introduce index management (was: Index schema & Index management integration) > Introduce index management > -- > > Key: IGNITE-14937 > URL: https://issues.apache.org/jira/browse/IGNITE-14937 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Public index schema (required indexes) and current indexes state on the > cluster are different. > We have to track it, store it and provide actual indexes schema state for any > components: select query, DDL query etc.. -- This message was sent by Atlassian Jira (v8.20.10#820010)
