[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-09-07 Thread Taras Ledkov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Taras Ledkov updated IGNITE-15424:
--
Labels: ignite-osgi osgi  (was: ignite-osgi important osgi)

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: ignite-osgi, osgi
> Fix For: 2.14
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-09-01 Thread Aleksey Plekhanov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-15424:
---
Labels: ignite-osgi important osgi  (was: calcite2-required ignite-osgi 
important osgi)

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: ignite-osgi, important, osgi
> Fix For: 2.14
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-08-23 Thread Taras Ledkov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Taras Ledkov updated IGNITE-15424:
--
Labels: calcite2-required ignite-osgi important osgi  (was: 
calcite2-required ignite-osgi osgi)

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: calcite2-required, ignite-osgi, important, osgi
> Fix For: 2.14
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-08-18 Thread Aleksey Plekhanov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-15424:
---
Fix Version/s: 2.14

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: calcite2-required, ignite-osgi, osgi
> Fix For: 2.14
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-07-13 Thread Maxim Muzafarov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-15424:
-
Labels: calcite2-required ignite-osgi osgi  (was: calcite2-required osgi)

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: calcite2-required, ignite-osgi, osgi
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-07-13 Thread Maxim Muzafarov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-15424:
-
Labels: calcite2-required osgi  (was: calcite2-required)

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: calcite2-required, osgi
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-06-17 Thread Aleksey Plekhanov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-15424:
---
Ignite Flags:   (was: Docs Required,Release Notes Required)

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: calcite2-required
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-06-17 Thread Aleksey Plekhanov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-15424:
---
Labels: calcite2-required  (was: calcite2-required calcite3-required)

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: calcite2-required
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2022-06-17 Thread Aleksey Plekhanov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-15424:
---
Description: 
Currently, schema management commands initiated in the {{ignite-core}} module, 
but all processing implemented in the {{ignite-indexing}} module. Ignite 
Calciite SQL engine use {{SchemaChangeListener}} to maintain own structures. 
To get rid of {{ignite-indexing}} (and H2) dependency from the 
{{ignite-calcite}} module we should move schema management implementation to 
the core module.

  was:
Currently, schema management commands initiated in the {{ignite-core}} module, 
but all processing implemented in the {{ignite-indexing}} module. Ignite 
Calciite SQL engine use {{SchemaChangeListener}} to maintain own structures. 
To get rid of {{ignite-indexing}} (and H2) dependency from the 
{{ignite-calcite}} module we should move schema management and statistics 
management implementation to the core module.


> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Daschinsky
>Priority: Major
>  Labels: calcite2-required, calcite3-required
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management implementation to 
> the core module.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

2021-09-07 Thread Vyacheslav Koptilin (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Koptilin updated IGNITE-15424:
-
Labels: calcite2-required calcite3-required  (was: )

> Calcite engine. Move schema management infrastructure to the core module 
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Priority: Major
>  Labels: calcite2-required, calcite3-required
>
> Currently, schema management commands initiated in the {{ignite-core}} 
> module, but all processing implemented in the {{ignite-indexing}} module. 
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own 
> structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the 
> {{ignite-calcite}} module we should move schema management and statistics 
> management implementation to the core module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)