[jira] [Comment Edited] (IGNITE-22181) BigDecimal scale is lost during create table
[
https://issues.apache.org/jira/browse/IGNITE-22181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850638#comment-17850638
]
Vadim Kolodin edited comment on IGNITE-22181 at 5/30/24 8:52 AM:
-
To specify precision and scale in POJO, use
{code:java}
@Column(precision = 5, scale = 2){code}
or
{code:java}
@Column(columnDefinition = "decimal(5,2)"){code}
With TableDefinition builders this is also possible with
{code:java}
.addColumn("col1", decimal(5,2)){code}
was (Author: JIRAUSER303000):
To specify precision and scale in POJO, use
`@Column(precision = 5, scale = 2)`
or
`@Column(columnDefinition = "decimal(5,2)")`
With TableDefinition builders this is also possible with
`.addColumn("col1", decimal(5,2))`
> BigDecimal scale is lost during create table
>
>
> Key: IGNITE-22181
> URL: https://issues.apache.org/jira/browse/IGNITE-22181
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3
>
> Given a pojo
> {code:java}
> @Table
> public static class PojoClass {
> @Id
> private Integer i;
> private BigDecimal b;
> public Integer getI() {
> return i;
> }
> public void setI(int i) {
> this.i = i;
> }
> public BigDecimal getB() {
> return b;
> }
> public void setB(BigDecimal b) {
> this.b = b;
> }
> {code}
> I create a table from it with this call:
> {code:java}
> client.catalog().create(PojoClass.class).execute();
> {code}
> Then I insert one record and read it:
> {code:java}
> var table = client.tables().table(PojoClass.class.getSimpleName());
> var pojo = new PojoClass();
> pojo.setI(44);
> pojo.setB(new BigDecimal("123.45")); // <-- NOTE
> var pojoRecordView = table.recordView(PojoClass.class);
> pojoRecordView.insert(null, pojo);
> var keyPojo = new PojoClass();
> keyPojo.setI(44);
> assertThat(pojoRecordView.get(null, keyPojo), equalTo(pojo)); <-- THIS FAILS
> {code}
> The assertion is failed due the scale (2) is lost for the BigDecimal field
> during the table creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22181) BigDecimal scale is lost during create table
[
https://issues.apache.org/jira/browse/IGNITE-22181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850638#comment-17850638
]
Vadim Kolodin commented on IGNITE-22181:
To specify precision and scale in POJO, use
`@Column(precision = 5, scale = 2)`
or
`@Column(columnDefinition = "decimal(5,2)")`
With TableDefinition builders this is also possible with
`.addColumn("col1", decimal(5,2))`
> BigDecimal scale is lost during create table
>
>
> Key: IGNITE-22181
> URL: https://issues.apache.org/jira/browse/IGNITE-22181
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3
>
> Given a pojo
> {code:java}
> @Table
> public static class PojoClass {
> @Id
> private Integer i;
> private BigDecimal b;
> public Integer getI() {
> return i;
> }
> public void setI(int i) {
> this.i = i;
> }
> public BigDecimal getB() {
> return b;
> }
> public void setB(BigDecimal b) {
> this.b = b;
> }
> {code}
> I create a table from it with this call:
> {code:java}
> client.catalog().create(PojoClass.class).execute();
> {code}
> Then I insert one record and read it:
> {code:java}
> var table = client.tables().table(PojoClass.class.getSimpleName());
> var pojo = new PojoClass();
> pojo.setI(44);
> pojo.setB(new BigDecimal("123.45")); // <-- NOTE
> var pojoRecordView = table.recordView(PojoClass.class);
> pojoRecordView.insert(null, pojo);
> var keyPojo = new PojoClass();
> keyPojo.setI(44);
> assertThat(pojoRecordView.get(null, keyPojo), equalTo(pojo)); <-- THIS FAILS
> {code}
> The assertion is failed due the scale (2) is lost for the BigDecimal field
> during the table creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22272) Rework Catalog API
[
https://issues.apache.org/jira/browse/IGNITE-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Kolodin updated IGNITE-22272:
---
Description:
* Do not return a Query that has to be executed, run it immediately. For
example: *Table table = catalog.createTable(Pojo.class)*
* All methods should be async-first
* Rename *create* to *createTable* (recordClass and KV methods)
* all *createTable* methods should return a {*}Table{*}. Especially important
for record and KV cases, where the resulting name is not obvious
* add option to specify column/index order in builders, annotations - explicit
order or implicit "default" (in case of composite index, colocation columns)
was:
* Do not return a Query that has to be executed, run it immediately. For
example: *Table table = catalog.createTable(Pojo.class)*
* All methods should be async-first
* Rename *create* to *createTable* (recordClass and KV methods)
* all *createTable* methods should return a {*}Table{*}. Especially important
for record and KV cases, where the resulting name is not obvious
* add option to specify column/index order in builders, annotations (in case
of composite index, colocation columns)
> Rework Catalog API
> --
>
> Key: IGNITE-22272
> URL: https://issues.apache.org/jira/browse/IGNITE-22272
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> * Do not return a Query that has to be executed, run it immediately. For
> example: *Table table = catalog.createTable(Pojo.class)*
> * All methods should be async-first
> * Rename *create* to *createTable* (recordClass and KV methods)
> * all *createTable* methods should return a {*}Table{*}. Especially
> important for record and KV cases, where the resulting name is not obvious
> * add option to specify column/index order in builders, annotations -
> explicit order or implicit "default" (in case of composite index, colocation
> columns)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22272) Rework Catalog API
[
https://issues.apache.org/jira/browse/IGNITE-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Kolodin updated IGNITE-22272:
---
Description:
* Do not return a Query that has to be executed, run it immediately. For
example: *Table table = catalog.createTable(Pojo.class)*
* All methods should be async-first
* Rename *create* to *createTable* (recordClass and KV methods)
* all *createTable* methods should return a {*}Table{*}. Especially important
for record and KV cases, where the resulting name is not obvious
* add option to specify column/index order in builders, annotations (in case
of composite index, colocation columns)
was:
* Do not return a Query that has to be executed, run it immediately. For
example: *Table table = catalog.createTable(Pojo.class)*
* All methods should be async-first
* Rename *create* to *createTable* (recordClass and KV methods)
* all *createTable* methods should return a {*}Table{*}. Especially important
for record and KV cases, where the resulting name is not obvious
* add option to specify column/index order (in case of composite index,
colocation columns)
> Rework Catalog API
> --
>
> Key: IGNITE-22272
> URL: https://issues.apache.org/jira/browse/IGNITE-22272
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> * Do not return a Query that has to be executed, run it immediately. For
> example: *Table table = catalog.createTable(Pojo.class)*
> * All methods should be async-first
> * Rename *create* to *createTable* (recordClass and KV methods)
> * all *createTable* methods should return a {*}Table{*}. Especially
> important for record and KV cases, where the resulting name is not obvious
> * add option to specify column/index order in builders, annotations (in case
> of composite index, colocation columns)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22272) Rework Catalog API
[
https://issues.apache.org/jira/browse/IGNITE-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Kolodin updated IGNITE-22272:
---
Description:
* Do not return a Query that has to be executed, run it immediately. For
example: *Table table = catalog.createTable(Pojo.class)*
* All methods should be async-first
* Rename *create* to *createTable* (recordClass and KV methods)
* all *createTable* methods should return a {*}Table{*}. Especially important
for record and KV cases, where the resulting name is not obvious
* add option to specify column/index order (in case of composite index,
colocation columns)
was:
* Do not return a Query that has to be executed, run it immediately. For
example: *Table table = catalog.createTable(Pojo.class)*
* All methods should be async-first
* Rename *create* to *createTable* (recordClass and KV methods)
* all *createTable* methods should return a *Table*. Especially important for
record and KV cases, where the resulting name is not obvious
> Rework Catalog API
> --
>
> Key: IGNITE-22272
> URL: https://issues.apache.org/jira/browse/IGNITE-22272
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> * Do not return a Query that has to be executed, run it immediately. For
> example: *Table table = catalog.createTable(Pojo.class)*
> * All methods should be async-first
> * Rename *create* to *createTable* (recordClass and KV methods)
> * all *createTable* methods should return a {*}Table{*}. Especially
> important for record and KV cases, where the resulting name is not obvious
> * add option to specify column/index order (in case of composite index,
> colocation columns)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22124) Java Thin 3.0: Implement MapReduce API
[
https://issues.apache.org/jira/browse/IGNITE-22124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Kolodin reassigned IGNITE-22124:
--
Assignee: Vadim Kolodin
> Java Thin 3.0: Implement MapReduce API
> --
>
> Key: IGNITE-22124
> URL: https://issues.apache.org/jira/browse/IGNITE-22124
> Project: Ignite
> Issue Type: Improvement
> Components: compute, thin client
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Kolodin
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implement {{ClientTaskExecution}} in Java client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22124) Java Thin 3.0: Implement MapReduce API
[
https://issues.apache.org/jira/browse/IGNITE-22124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Kolodin updated IGNITE-22124:
---
Summary: Java Thin 3.0: Implement MapReduce API (was: Thin 3.0: Implement
MapReduce API)
> Java Thin 3.0: Implement MapReduce API
> --
>
> Key: IGNITE-22124
> URL: https://issues.apache.org/jira/browse/IGNITE-22124
> Project: Ignite
> Issue Type: Improvement
> Components: compute, thin client
>Reporter: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
>
> Implement {{ClientTaskExecution}} in Java client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-19962) Actualize list of 3rd party dependencies for AI 3.0
[ https://issues.apache.org/jira/browse/IGNITE-19962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin resolved IGNITE-19962. Resolution: Resolved devlist thread [AI3 3rd party dependencies-Apache Mail Archives|https://lists.apache.org/thread/3d18s2cjyyqktp0573n8qkjk4265dr5q] > Actualize list of 3rd party dependencies for AI 3.0 > --- > > Key: IGNITE-19962 > URL: https://issues.apache.org/jira/browse/IGNITE-19962 > Project: Ignite > Issue Type: Improvement >Reporter: Iurii Gerzhedovich >Assignee: Vadim Kolodin >Priority: Blocker > Labels: ignite-3 > > AI3 codestyle guide contains part about using 3rd party libraries. Right now > the document present just 5 such libraries, however we already use > signifignetely more. > Let's do two steps: > # analizy which dependencies could be get rid, even in tests. We must have > minimum dependency for whole project. > # Actualize list of 3rd party libraries in > [codestyle|https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide#JavaCodeStyleGuide-2Using3rdpartylibraries]]. > The first step should be discussed at developers mailing list and have strong > explanation of necessety for each of dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) catalog-dsl. Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Description: In catalog-dsl, rename index type after IGNITE-21353 in sql engine. (was: In catalog-dsl, rename index type after IGNITE-21353 in sql engine. Aslo need to get rid keyword TREE from [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f]) > catalog-dsl. Rename IndexType.TREE to SORTED > > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) catalog-dsl. Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Summary: catalog-dsl. Rename IndexType.TREE to SORTED (was: catalog-dsl Rename IndexType.TREE to SORTED) > catalog-dsl. Rename IndexType.TREE to SORTED > > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Description: In catalog-dsl, rename index type after IGNITE-21353 in sql engine. Aslo need to get rid keyword TREE from [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] was: Rename index type after IGNITE-21353 in sql engine. Aslo need to get rid keyword TREE from [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] > Rename IndexType.TREE to SORTED > --- > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) catalog-dsl Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Summary: catalog-dsl Rename IndexType.TREE to SORTED (was: Rename IndexType.TREE to SORTED) > catalog-dsl Rename IndexType.TREE to SORTED > --- > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In catalog-dsl, rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21426) Create tables from Java classes basic implementation
[ https://issues.apache.org/jira/browse/IGNITE-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21426: --- Description: * add a new module * public interfaces, entry point is ignite.catalog() * ignite annotations - table, id, index, colocateBy, zone * table/zone definition builders * basic sql generation implementation * update existing MapperBuilder to support Column annotation * some tests was: * add a new module * public interfaces * ignite annotations - table, id, index, colocateBy, zone * table/zone definition builders * basic sql generation implementation * update existing MapperBuilder to support Column annotation * some tests > Create tables from Java classes basic implementation > > > Key: IGNITE-21426 > URL: https://issues.apache.org/jira/browse/IGNITE-21426 > Project: Ignite > Issue Type: New Feature >Reporter: Vadim Kolodin >Priority: Major > > * add a new module > * public interfaces, entry point is ignite.catalog() > * ignite annotations - table, id, index, colocateBy, zone > * table/zone definition builders > * basic sql generation implementation > * update existing MapperBuilder to support Column annotation > * some tests -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21427) Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21427: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Rename IndexType.TREE to SORTED > --- > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement >Reporter: Vadim Kolodin >Priority: Major > > Rename index type after IGNITE-21353 in sql engine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21428) Additional WITH params for zone, table
Vadim Kolodin created IGNITE-21428: -- Summary: Additional WITH params for zone, table Key: IGNITE-21428 URL: https://issues.apache.org/jira/browse/IGNITE-21428 Project: Ignite Issue Type: Improvement Reporter: Vadim Kolodin Implement currently supported WITH params for zone, table - adjust, filter, dataregion, affinityFunction etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21426) Create tables from Java classes basic implementation
[ https://issues.apache.org/jira/browse/IGNITE-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21426: --- Description: * add a new module * public interfaces * ignite annotations - table, id, index, colocateBy, zone * table/zone definition builders * basic sql generation implementation * update existing MapperBuilder to support Column annotation * some tests was:Add new module, public interfaces, annotations, table/zone definition builders, basic sql generation implementation, some tests. > Create tables from Java classes basic implementation > > > Key: IGNITE-21426 > URL: https://issues.apache.org/jira/browse/IGNITE-21426 > Project: Ignite > Issue Type: New Feature >Reporter: Vadim Kolodin >Priority: Major > > * add a new module > * public interfaces > * ignite annotations - table, id, index, colocateBy, zone > * table/zone definition builders > * basic sql generation implementation > * update existing MapperBuilder to support Column annotation > * some tests -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21427) Rename IndexType.TREE to SORTED
Vadim Kolodin created IGNITE-21427: -- Summary: Rename IndexType.TREE to SORTED Key: IGNITE-21427 URL: https://issues.apache.org/jira/browse/IGNITE-21427 Project: Ignite Issue Type: Improvement Reporter: Vadim Kolodin Rename index type after IGNITE-21353 in sql engine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21426) Create tables from Java classes basic implementation
Vadim Kolodin created IGNITE-21426: -- Summary: Create tables from Java classes basic implementation Key: IGNITE-21426 URL: https://issues.apache.org/jira/browse/IGNITE-21426 Project: Ignite Issue Type: New Feature Reporter: Vadim Kolodin Add new module, public interfaces, annotations, table/zone definition builders, basic sql generation implementation, some tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21410) Ignite 3.0: Create tables from Java classes
[ https://issues.apache.org/jira/browse/IGNITE-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21410: --- Summary: Ignite 3.0: Create tables from Java classes (was: Ignite 3.0: Java API for tables generation) > Ignite 3.0: Create tables from Java classes > --- > > Key: IGNITE-21410 > URL: https://issues.apache.org/jira/browse/IGNITE-21410 > Project: Ignite > Issue Type: Epic >Reporter: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In addition to SQL DDL commands, provide a simple Java API for initial tables > generation from POJO. Support custom annotations and simple builders. This > feature should work seamlessly with existing Mapper interface (keyValueView > and recordView). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21410) Ignite 3.0: Java API for tables generation
[ https://issues.apache.org/jira/browse/IGNITE-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Kolodin updated IGNITE-21410: --- Summary: Ignite 3.0: Java API for tables generation (was: Java API for tables generation) > Ignite 3.0: Java API for tables generation > -- > > Key: IGNITE-21410 > URL: https://issues.apache.org/jira/browse/IGNITE-21410 > Project: Ignite > Issue Type: Epic >Reporter: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > In addition to SQL DDL commands, provide a simple Java API for initial tables > generation from POJO. Support custom annotations and simple builders. This > feature should work seamlessly with existing Mapper interface (keyValueView > and recordView). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21410) Java API for tables generation
Vadim Kolodin created IGNITE-21410: -- Summary: Java API for tables generation Key: IGNITE-21410 URL: https://issues.apache.org/jira/browse/IGNITE-21410 Project: Ignite Issue Type: Epic Reporter: Vadim Kolodin In addition to SQL DDL commands, provide a simple Java API for initial tables generation from POJO. Support custom annotations and simple builders. This feature should work seamlessly with existing Mapper interface (keyValueView and recordView). -- This message was sent by Atlassian Jira (v8.20.10#820010)
