[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747938#comment-16747938 ] Pavel Kuznetsov commented on IGNITE-10784: -- [~vozerov] 1) After sanity testing, I still don't see in what cases name case sensitivity is broken for the {{GridQueryTypeDescriptor}} 2) Ok, I've moved ke/val alias logic to {{GridH2Table}} (because we can't access grid h2 table from row desctiptor's constructor, table is set later) and I use {{columns[keyAliasIdx]}} So, please see my changes committed (https://github.com/apache/ignite/pull/5749/commits/a61d50ede9d8b619962586b76192e31e19583b14) > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745887#comment-16745887 ] Vladimir Ozerov commented on IGNITE-10784: -- [~pkouznet], the only comment to {{GridH2RowDescriptor}} - it is illegal to save key and val field names from {{GridQueryTypeDescriptor}} because it doesn't take in count case. Instead, we should take it from Column with appropriate ID as explained in my previous comment. The rest looks good to me. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745297#comment-16745297 ] Ignite TC Bot commented on IGNITE-10784: {panel:title=-- Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *-- Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2825226buildTypeId=IgniteTests24Java8_RunAll] > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744873#comment-16744873 ] Pavel Kuznetsov commented on IGNITE-10784: -- Added test cases with filter that touches other columns. Also added simple tests for drop/create and custom AffinityMapper. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743015#comment-16743015 ] Pavel Kuznetsov commented on IGNITE-10784: -- About p.1 : In short, I've removed locking. Revisited the code. - Added locking inside getTables() is not correct, because this method is used by H2, which might have already locked the table. - Locking while reading Table#columns was required (select to a View doesn't lock all the tables). BUT, Iteration over columns is removed, and in the view we read only final or effectively final fields. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742255#comment-16742255 ] Pavel Kuznetsov commented on IGNITE-10784: -- [~vozerov] Thank you for the review, 1. If I understad right, we are able to alter columns on the one thread (in this case we use write lock) and still try to read {{org.h2.table.Table#columns}} field inside {{GridH2Table.getColumns}}. Please correct me if I'm wrong. 2,3,4 - Updated. 5,6 - Agree, updated 7, Done 8 - ok, I've added final fields to {{GridH2RowDescriptor}} Working on tests. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740203#comment-16740203 ] Vladimir Ozerov commented on IGNITE-10784: -- Regarding p.8 - even better is to save alias names in descriptor or {{GridH2Table}} in a final field, as they are guaranteed to never change. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738109#comment-16738109 ] Pavel Kuznetsov commented on IGNITE-10784: -- {{TxRollbackAsyncWithPersistenceTest.testSynchronousRollback}} : 1) Can't reproduce the failure locally neither on master nor on {{ignite-10784}} 2) Added VIEWS feature doesn't seem to be related to the scope of the test. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730659#comment-16730659 ] Ignite TC Bot commented on IGNITE-10784: {panel:title=-- Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Cache 7{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=2676528]] * IgniteCacheTestSuite7: TxRollbackAsyncWithPersistenceTest.testSynchronousRollback - 0,0% fails in last 406 master runs. {panel} [TeamCity *-- Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2676560buildTypeId=IgniteTests24Java8_RunAll] > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730616#comment-16730616 ] Pavel Kuznetsov commented on IGNITE-10784: -- I think It's done, [~tledkov-gridgain] would you please do a review? > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728978#comment-16728978 ] Ignite TC Bot commented on IGNITE-10784: {panel:title=- Run :: SQL: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *- Run :: SQL* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2647035buildTypeId=IgniteTests24Java8_RunAllSql] > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728960#comment-16728960 ] Pavel Kuznetsov commented on IGNITE-10784: -- Got comment: we have to use {{Set}} to avoid descriptors duplications in {{GridQueryProcessor#types}}. Let's try to use {{GridH2Table}} instances from indexing instead. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728808#comment-16728808 ] ASF GitHub Bot commented on IGNITE-10784: - GitHub user pavel-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/5749 IGNITE-10784: added TABLES view You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10784 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5749.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5749 commit 8aa0e1a89ad5ccd081aa863b3f68d8b7d768e01c Author: Pavel Kuznetsov Date: 2018-12-24T17:19:25Z ignite-10784: wip commit ea4dd42b4497bd561a308d8ff0c6fba9d5d71f24 Author: Pavel Kuznetsov Date: 2018-12-24T23:33:56Z ignite-10784: Implemented minimal view IGNITE.TABLES. commit a80e224f45d0624217258f23e281f9dc6569fa14 Author: Pavel Kuznetsov Date: 2018-12-25T10:09:33Z ignite-10784: Tests wip. commit 354d0c152952cc039ba7c6a8859c4639d3237826 Author: Pavel Kuznetsov Date: 2018-12-25T12:34:29Z ignite-10784: Fixed bug with filter. Updated code and tests; commit 0bad909b65ccf5cdf8ee38fae9c442d3d8940164 Author: Pavel Kuznetsov Date: 2018-12-25T12:47:50Z ignite-10784: Rename column name; Renamed column name of the view according to ISO standard. commit f367f97215033a7e7f4f7d702bcf6cffd39d93dd Author: Pavel Kuznetsov Date: 2018-12-25T14:11:25Z ignite-10784: added Affinity column. commit 526cb3eb98623bbe50c694859a9ea898dbc4401a Author: Pavel Kuznetsov Date: 2018-12-25T15:00:27Z ignite-10784: reverted affinity mode info in the view. AffinityMapper should be handled during IGNITE-10310 commit ca14ca844c484e437aef323082839143daa52bf7 Author: Pavel Kuznetsov Date: 2018-12-25T18:52:31Z ignite-10784: Added key and field alias columns. commit 3af040ba1d439228b5e00a615bdb8a97c6aee053 Author: Pavel Kuznetsov Date: 2018-12-25T19:19:18Z ignite-10784: fixed duplicates. commit 795486fea87b762f58bbde11f0ec6e242217000c Author: Pavel Kuznetsov Date: 2018-12-25T19:23:17Z ignite-10784: Got rid of unnecessary arrays allocations. commit 6512c06e6bab6bbdcc3162d5a2be02a485806d2a Author: Pavel Kuznetsov Date: 2018-12-25T19:40:27Z ignite-10784: Added key/value type name columns to the TABLES view. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728712#comment-16728712 ] Vladimir Ozerov commented on IGNITE-10784: -- [~pkouznet], please note that info about MVCC mode is already available in {{CACHES.ATOMICITY_MODE}}. I doubt that we need constant fields as we are implementing our own custom view, not {{INFORMATIONAL_SCHEMA}}. Table size approximation is not available at the moment in Ignite. We will have it in future [1]. [1] IGNITE-6079 > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728698#comment-16728698 ] Pavel Kuznetsov commented on IGNITE-10784: -- Important note: many vendors give "INFORMATION_SCHEMA" to the schema of the view because it's a part of the SQL ISO standard. Maybe we should change the name? > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728692#comment-16728692 ] Pavel Kuznetsov commented on IGNITE-10784: -- Lets add also "constant" fields : CATALOG_NAME ("IGNITE"), TABLE_TYPE ("TABLE") It is also good to have TABLE_ROWS field, should think, if we can do without scan (size of pk index?). > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728651#comment-16728651 ] Pavel Kuznetsov commented on IGNITE-10784: -- maybe we should duplicate atomic mode or introduce new column "mvcc enabled". > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[ https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728522#comment-16728522 ] Pavel Kuznetsov commented on IGNITE-10784: -- MySQL has approximate table table size. > SQL: Create a view with list of existing tables > --- > > Key: IGNITE-10784 > URL: https://issues.apache.org/jira/browse/IGNITE-10784 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > > We need to create a system view of currently available SQL tables. > Minimal required information: > 1) Schema name > 2) Table name > 3) Owning cache name > 4) Owning cache ID > Other info to consider: > 1) Affinity column name > 2) Key/value aliases > 3) Key/value type names > 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful > information could be exposed (taking in count that a lot of engine properties > are already exposed through {{CACHES}} view) > Starting point: {{SqlSystemView}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)