[jira] [Commented] (IGNITE-16427) Broken code formatting in 3.0.0-alpha4 documentation
[ https://issues.apache.org/jira/browse/IGNITE-16427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486007#comment-17486007 ] Valentin Kulichenko commented on IGNITE-16427: -- Igor, I will merge the PR next week, unless someone else picks it up. Thanks! > Broken code formatting in 3.0.0-alpha4 documentation > > > Key: IGNITE-16427 > URL: https://issues.apache.org/jira/browse/IGNITE-16427 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > > There are formatting issues on these two pages: > * > [https://ignite.apache.org/docs/3.0.0-alpha/transactions/performing-transactions] > * https://ignite.apache.org/docs/3.0.0-alpha/table-views -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (IGNITE-16343) Update hash and sig links on the Downloads page
[ https://issues.apache.org/jira/browse/IGNITE-16343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-16343. > Update hash and sig links on the Downloads page > --- > > Key: IGNITE-16343 > URL: https://issues.apache.org/jira/browse/IGNITE-16343 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3 > > See dev list thread: > https://lists.apache.org/thread/b693db4rpll8fnwoc01xpspcvjjggsp6 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-16343) Update hash and sig links on the Downloads page
[ https://issues.apache.org/jira/browse/IGNITE-16343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-16343. -- Resolution: Fixed > Update hash and sig links on the Downloads page > --- > > Key: IGNITE-16343 > URL: https://issues.apache.org/jira/browse/IGNITE-16343 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3 > > See dev list thread: > https://lists.apache.org/thread/b693db4rpll8fnwoc01xpspcvjjggsp6 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16343) Update hash and sig links on the Downloads page
[ https://issues.apache.org/jira/browse/IGNITE-16343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16343: - Fix Version/s: (was: 3.0.0-alpha4) > Update hash and sig links on the Downloads page > --- > > Key: IGNITE-16343 > URL: https://issues.apache.org/jira/browse/IGNITE-16343 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3 > > See dev list thread: > https://lists.apache.org/thread/b693db4rpll8fnwoc01xpspcvjjggsp6 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16427) Broken code formatting in 3.0.0-alpha4 documentation
Valentin Kulichenko created IGNITE-16427: Summary: Broken code formatting in 3.0.0-alpha4 documentation Key: IGNITE-16427 URL: https://issues.apache.org/jira/browse/IGNITE-16427 Project: Ignite Issue Type: Bug Components: documentation Reporter: Valentin Kulichenko Fix For: 3.0.0-alpha4 There are formatting issues on these two pages: * [https://ignite.apache.org/docs/3.0.0-alpha/transactions/performing-transactions] * https://ignite.apache.org/docs/3.0.0-alpha/table-views -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16427) Broken code formatting in 3.0.0-alpha4 documentation
[ https://issues.apache.org/jira/browse/IGNITE-16427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16427: - Labels: ignite-3 (was: ) > Broken code formatting in 3.0.0-alpha4 documentation > > > Key: IGNITE-16427 > URL: https://issues.apache.org/jira/browse/IGNITE-16427 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Valentin Kulichenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > > There are formatting issues on these two pages: > * > [https://ignite.apache.org/docs/3.0.0-alpha/transactions/performing-transactions] > * https://ignite.apache.org/docs/3.0.0-alpha/table-views -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16357) Add documentation for DB names format used by API calls
[
https://issues.apache.org/jira/browse/IGNITE-16357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483253#comment-17483253
]
Valentin Kulichenko commented on IGNITE-16357:
--
Cherry-picked to {{alpha4}}
> Add documentation for DB names format used by API calls
> ---
>
> Key: IGNITE-16357
> URL: https://issues.apache.org/jira/browse/IGNITE-16357
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Reporter: Taras Ledkov
>Assignee: Nikita A. Safonov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The patch IGNITE-16322 changes behavior of the public API.
> Need to document.
> API: tuples (java, java client, .net client), IgniteTables, Mapper-s
> ,
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (IGNITE-16357) Add documentation for DB names format used by API calls
[ https://issues.apache.org/jira/browse/IGNITE-16357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-16357. > Add documentation for DB names format used by API calls > --- > > Key: IGNITE-16357 > URL: https://issues.apache.org/jira/browse/IGNITE-16357 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Taras Ledkov >Assignee: Nikita A. Safonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > > The patch IGNITE-16322 changes behavior of the public API. > Need to document. > API: tuples (java, java client, .net client), IgniteTables, Mapper-s > , -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16357) Add documentation for DB names format used by API calls
[
https://issues.apache.org/jira/browse/IGNITE-16357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483252#comment-17483252
]
Valentin Kulichenko commented on IGNITE-16357:
--
LGTM, merged to {{main}}
> Add documentation for DB names format used by API calls
> ---
>
> Key: IGNITE-16357
> URL: https://issues.apache.org/jira/browse/IGNITE-16357
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Reporter: Taras Ledkov
>Assignee: Nikita A. Safonov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The patch IGNITE-16322 changes behavior of the public API.
> Need to document.
> API: tuples (java, java client, .net client), IgniteTables, Mapper-s
> ,
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15804) [IGNITE 3] Remove Ignition and IgnitionManager from the public API
[
https://issues.apache.org/jira/browse/IGNITE-15804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17482558#comment-17482558
]
Valentin Kulichenko commented on IGNITE-15804:
--
{{RebalanceExample}} still starts an embedded server node because
{{Ignite#setBaseline}} is not implemented for thin clients.
Looks like we need to complete IGNITE-16410 before we can merge this.
> [IGNITE 3] Remove Ignition and IgnitionManager from the public API
> --
>
> Key: IGNITE-15804
> URL: https://issues.apache.org/jira/browse/IGNITE-15804
> Project: Ignite
> Issue Type: Improvement
>Reporter: Valentin Kulichenko
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> There are currently no plans to support embedded mode in Ignite 3. Thus, we
> should remove {{Ignition}} and {{IgnitionManager}} classes from the public
> API.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-16410) Implement Ignite#setBaseline method in thin client
Valentin Kulichenko created IGNITE-16410:
Summary: Implement Ignite#setBaseline method in thin client
Key: IGNITE-16410
URL: https://issues.apache.org/jira/browse/IGNITE-16410
Project: Ignite
Issue Type: Task
Components: thin client
Affects Versions: 3.0.0-alpha4
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha5
Currently, this method is available only on server side - thin client throws
{{{}UnsupportedOperationException{}}}. Because of that, {{RebalanceExample}}
still starts an embedded server node.
Need to implement the method in the thin client and update the example.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16244) Update examples for Ignite 3
[
https://issues.apache.org/jira/browse/IGNITE-16244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481576#comment-17481576
]
Valentin Kulichenko commented on IGNITE-16244:
--
Merged to {{main}} and {{alpha4}}
> Update examples for Ignite 3
>
>
> Key: IGNITE-16244
> URL: https://issues.apache.org/jira/browse/IGNITE-16244
> Project: Ignite
> Issue Type: Improvement
> Components: examples
>Affects Versions: 3.0.0-alpha3
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the current advancements in Ignite 3 functionality, examples look
> outdated and should be updated.
> The following changes should be made:
> # Use DDL instead of the convoluted {{createTable}} API to create tables.
> # Add examples for POJO-based views (we can use the existing
> {{RecordViewExample}} and {{KeyValueViewExample}} as a basis).
> # Add transactional API example(s).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16322) Database object names case inconsisten between SQL and KV API
[
https://issues.apache.org/jira/browse/IGNITE-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481467#comment-17481467
]
Valentin Kulichenko commented on IGNITE-16322:
--
Cherry-picked to {{ignite-3.0.0-alpha4}}
> Database object names case inconsisten between SQL and KV API
> -
>
> Key: IGNITE-16322
> URL: https://issues.apache.org/jira/browse/IGNITE-16322
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current naming of the database object is not clear for everyone.
> *Current behavior*
> {{CREATE TABLE mytable(id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID, VAL)
> {{ignite.tables().table("public.mytable");}} -> fails with table not found
> {{ignite.tables().table("PUBLIC.MYTABLE ");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable(ID,
> VAL)
> {{ignite.tables().table("PUBLIC.MyTable");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> fails with error: column not found
> {{tbl.get().value("ID")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns Id column's value
> *Proposed Fixes*
> *1. Use case insensitive collation to compare and lookup database object*
> e.g.
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID,
> VAL)
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> fails with error:
> PUBLIC.MYTABLE already exists,
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> fails with error:
> duplicate column name: ID
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> *2. Case sensitive collation for DB object names and parse string argument of
> the name passed through API*
> Use quotation for string values by API
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable
> {{ignite.tables().table("public.\"MyTable\"");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> {{tbl.get().value("\"Id\"")}} -> returns Id column's value
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16161) Memory leak in BaseQueryContext
[ https://issues.apache.org/jira/browse/IGNITE-16161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480196#comment-17480196 ] Valentin Kulichenko commented on IGNITE-16161: -- Looks like a serious issue - I've included the fix in the alpha4. > Memory leak in BaseQueryContext > --- > > Key: IGNITE-16161 > URL: https://issues.apache.org/jira/browse/IGNITE-16161 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 3.0.0-alpha3 >Reporter: Vyacheslav Koptilin >Assignee: Andrey Mashenkov >Priority: Blocker > Labels: calcite2-required, calcite3-required, ignite-3 > Fix For: 3.0.0-alpha4 > > Attachments: image-2021-12-20-14-37-02-163.png, image.png > > Time Spent: 40m > Remaining Estimate: 0h > > BaseQueryContext contains a number of static fields that are used in order to > store references to internal classes. For example, BaseQueryContext.CLUSTER > which indirectly refers to ignite tables (TableImpl instances). > Unfortunately, these references are not cleared even though the corresponding > ignite node is stopped. > The following trace based on a heap dump illustrates the issue: > !image-2021-12-20-14-37-02-163.png! > This issue can be partially mitigated by clearing ring buffers in > StripedDisruptor, but the right way to fix the issue is a proper approach to > handle static collections in BaseQueryContext. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16161) Memory leak in BaseQueryContext
[ https://issues.apache.org/jira/browse/IGNITE-16161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16161: - Fix Version/s: 3.0.0-alpha4 (was: 3.0.0-alpha5) > Memory leak in BaseQueryContext > --- > > Key: IGNITE-16161 > URL: https://issues.apache.org/jira/browse/IGNITE-16161 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 3.0.0-alpha3 >Reporter: Vyacheslav Koptilin >Assignee: Andrey Mashenkov >Priority: Blocker > Labels: calcite2-required, calcite3-required, ignite-3 > Fix For: 3.0.0-alpha4 > > Attachments: image-2021-12-20-14-37-02-163.png, image.png > > Time Spent: 40m > Remaining Estimate: 0h > > BaseQueryContext contains a number of static fields that are used in order to > store references to internal classes. For example, BaseQueryContext.CLUSTER > which indirectly refers to ignite tables (TableImpl instances). > Unfortunately, these references are not cleared even though the corresponding > ignite node is stopped. > The following trace based on a heap dump illustrates the issue: > !image-2021-12-20-14-37-02-163.png! > This issue can be partially mitigated by clearing ring buffers in > StripedDisruptor, but the right way to fix the issue is a proper approach to > handle static collections in BaseQueryContext. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16343) Update hash and sig links on the Downloads page
Valentin Kulichenko created IGNITE-16343: Summary: Update hash and sig links on the Downloads page Key: IGNITE-16343 URL: https://issues.apache.org/jira/browse/IGNITE-16343 Project: Ignite Issue Type: Task Components: website Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko Fix For: 3.0.0-alpha4 See dev list thread: https://lists.apache.org/thread/b693db4rpll8fnwoc01xpspcvjjggsp6 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (IGNITE-16326) Prepare Documentation for the AI Alpha 4 Release
[ https://issues.apache.org/jira/browse/IGNITE-16326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-16326. > Prepare Documentation for the AI Alpha 4 Release > > > Key: IGNITE-16326 > URL: https://issues.apache.org/jira/browse/IGNITE-16326 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0-alpha4 >Reporter: Nikita A. Safonov >Assignee: Nikita A. Safonov >Priority: Major > Labels: documentation > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > > We need to document the following functionality of the upcoming release: > - DDL commands > - Transactions functionality > - Table views: KeyValueView, RecordView, and RecordBinaryView -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16326) Prepare Documentation for the AI Alpha 4 Release
[
https://issues.apache.org/jira/browse/IGNITE-16326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479728#comment-17479728
]
Valentin Kulichenko commented on IGNITE-16326:
--
Also, cherry-picked to {{ignite-3.0.0-alpha4}}
> Prepare Documentation for the AI Alpha 4 Release
>
>
> Key: IGNITE-16326
> URL: https://issues.apache.org/jira/browse/IGNITE-16326
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 3.0.0-alpha4
>Reporter: Nikita A. Safonov
>Assignee: Nikita A. Safonov
>Priority: Major
> Labels: documentation
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to document the following functionality of the upcoming release:
> - DDL commands
> - Transactions functionality
> - Table views: KeyValueView, RecordView, and RecordBinaryView
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16326) Prepare Documentation for the AI Alpha 4 Release
[ https://issues.apache.org/jira/browse/IGNITE-16326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479726#comment-17479726 ] Valentin Kulichenko commented on IGNITE-16326: -- [~nsafonov] I've merged the PR, thanks! I think I will want to make some minor changes before the release, but we can do this separately. Overall, looks really good. > Prepare Documentation for the AI Alpha 4 Release > > > Key: IGNITE-16326 > URL: https://issues.apache.org/jira/browse/IGNITE-16326 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0-alpha4 >Reporter: Nikita A. Safonov >Assignee: Nikita A. Safonov >Priority: Major > Labels: documentation > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > > We need to document the following functionality of the upcoming release: > - DDL commands > - Transactions functionality > - Table views: KeyValueView, RecordView, and RecordBinaryView -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16322) Database object names case inconsisten between SQL and KV API
[
https://issues.apache.org/jira/browse/IGNITE-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-16322:
-
Fix Version/s: 3.0.0-alpha4
(was: 3.0.0-alpha5)
> Database object names case inconsisten between SQL and KV API
> -
>
> Key: IGNITE-16322
> URL: https://issues.apache.org/jira/browse/IGNITE-16322
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Examples fail with NPE because table with the specified name does not exist.
> The actual table name is PUBLIC.ACCOUNTS (all uppercase), same for column
> names - ACCOUNTNUMBER and so on.
> *Current behavior*
> {{CREATE TABLE mytable(id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID, VAL)
> {{ignite.tables().table("public.mytable");}} -> fails with table not found
> {{ignite.tables().table("PUBLIC.MYTABLE ");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable(ID,
> VAL)
> {{ignite.tables().table("PUBLIC.MyTable");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> fails with error: column not found
> {{tbl.get().value("ID")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns Id column's value
> *Proposed Fixes*
> *1. Use case insensitive collation to compare and lookup database object*
> e.g.
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID,
> VAL)
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> fails with error:
> PUBLIC.MYTABLE already exists,
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> fails with error:
> duplicate column name: ID
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> *2. Case sensitive collation for DB object names and parse string argument of
> the name passed through API*
> Use quotation for string values by API
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable
> {{ignite.tables().table("public.\"MyTable\"");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> {{tbl.get().value("\"Id\"")}} -> returns Id column's value
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16322) Database object names case inconsisten between SQL and KV API
[
https://issues.apache.org/jira/browse/IGNITE-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479720#comment-17479720
]
Valentin Kulichenko commented on IGNITE-16322:
--
I also believe that what Andrey describes is actually equivalent to option #2
of the original proposal. The only difference is that Postgres uses lowercase,
while Ignite currently uses uppercase. As I've mentioned in the previous
comment, I don't think there is any difference, so we can keep uppercase.
> Database object names case inconsisten between SQL and KV API
> -
>
> Key: IGNITE-16322
> URL: https://issues.apache.org/jira/browse/IGNITE-16322
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Examples fail with NPE because table with the specified name does not exist.
> The actual table name is PUBLIC.ACCOUNTS (all uppercase), same for column
> names - ACCOUNTNUMBER and so on.
> *Current behavior*
> {{CREATE TABLE mytable(id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID, VAL)
> {{ignite.tables().table("public.mytable");}} -> fails with table not found
> {{ignite.tables().table("PUBLIC.MYTABLE ");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable(ID,
> VAL)
> {{ignite.tables().table("PUBLIC.MyTable");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> fails with error: column not found
> {{tbl.get().value("ID")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns Id column's value
> *Proposed Fixes*
> *1. Use case insensitive collation to compare and lookup database object*
> e.g.
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID,
> VAL)
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> fails with error:
> PUBLIC.MYTABLE already exists,
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> fails with error:
> duplicate column name: ID
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> *2. Case sensitive collation for DB object names and parse string argument of
> the name passed through API*
> Use quotation for string values by API
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable
> {{ignite.tables().table("public.\"MyTable\"");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> {{tbl.get().value("\"Id\"")}} -> returns Id column's value
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16322) Database object names case inconsisten between SQL and KV API
[
https://issues.apache.org/jira/browse/IGNITE-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479710#comment-17479710
]
Valentin Kulichenko commented on IGNITE-16322:
--
Andrey's proposal seems reasonable. We can use lowercase or uppercase though,
doesn't matter. Whatever is easier.
There are some corner cases like supporting clash names (e.g. {{user_name}} and
{{{}"USER_NAME"{}}}) in POJOs, but those are going to be rare and can be
addressed with custom mappers.
> Database object names case inconsisten between SQL and KV API
> -
>
> Key: IGNITE-16322
> URL: https://issues.apache.org/jira/browse/IGNITE-16322
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Examples fail with NPE because table with the specified name does not exist.
> The actual table name is PUBLIC.ACCOUNTS (all uppercase), same for column
> names - ACCOUNTNUMBER and so on.
> *Current behavior*
> {{CREATE TABLE mytable(id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID, VAL)
> {{ignite.tables().table("public.mytable");}} -> fails with table not found
> {{ignite.tables().table("PUBLIC.MYTABLE ");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable(ID,
> VAL)
> {{ignite.tables().table("PUBLIC.MyTable");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> fails with error: column not found
> {{tbl.get().value("ID")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns Id column's value
> *Proposed Fixes*
> *1. Use case insensitive collation to compare and lookup database object*
> e.g.
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE (ID,
> VAL)
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> fails with error:
> PUBLIC.MYTABLE already exists,
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> fails with error:
> duplicate column name: ID
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> *2. Case sensitive collation for DB object names and parse string argument of
> the name passed through API*
> Use quotation for string values by API
> {{CREATE TABLE MyTable (id INT, val INT)}}; -> creates PUBLIC.MYTABLE
> {{ignite.tables().table("public.mytable");}} -> returns PUBLIC.MYTABLE
> {{CREATE TABLE \"MyTable\" (id INT, val INT)}}; -> creates PUBLIC.MyTable
> {{ignite.tables().table("public.\"MyTable\"");}} -> returns PUBLIC.MyTable
> Tuple / column behavior:
> {{CREATE TABLE MyTable (id INT, \"Id\" INT, val INT)}}; -> creates
> PUBLIC.MYTABLE (ID, Id, VAL)
> {{tbl.get().value("id")}} -> returns ID column's value
> {{tbl.get().value("Id")}} -> returns ID column's value
> {{tbl.get().value("\"Id\"")}} -> returns Id column's value
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16303) Thin 3.0: ClientTables.table throws MessageTypeException when table does not exist
[
https://issues.apache.org/jira/browse/IGNITE-16303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477373#comment-17477373
]
Valentin Kulichenko commented on IGNITE-16303:
--
Cherry-picked to {{{}ignite-3.0.0-alpha4{}}}.
> Thin 3.0: ClientTables.table throws MessageTypeException when table does not
> exist
> --
>
> Key: IGNITE-16303
> URL: https://issues.apache.org/jira/browse/IGNITE-16303
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 3.0.0-alpha4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ClientTables.table throws MessageTypeException when table does not exist:
> {code:java}
> @Test
> public void testTableReturnsNullWhenDoesNotExist() {
> Table table = client.tables().table("non-existent-table");
> assertNull(table);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16258) Support Serializable lambdas marshalling in User Object Serialization
[ https://issues.apache.org/jira/browse/IGNITE-16258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16258: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Support Serializable lambdas marshalling in User Object Serialization > - > > Key: IGNITE-16258 > URL: https://issues.apache.org/jira/browse/IGNITE-16258 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > There is a disabled test > DefaultUserObjectMarshallerWithArbitraryObjectsTest#supportsNonCapturingSerializableLambdas > The goal of this task is to make it pass. The test creates a serializable > lambda instance and tries to marshal and then unmarshal it back. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16234) Implement injection of Ignite resources on unmarshalling
[ https://issues.apache.org/jira/browse/IGNITE-16234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16234: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Implement injection of Ignite resources on unmarshalling > > > Key: IGNITE-16234 > URL: https://issues.apache.org/jira/browse/IGNITE-16234 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > User Object Serialization (IGNITE-15944) might be used to serialize compute > tasks and other components supplied by a user, sent via network, unmarshalled > and executed on Ignite nodes. > Such serialized components may need access to Ignite resources. It makes > sense to inject them to fields annotated with a special-purpose annotation > (like it was it Ignite 2). > An example of such annotation in Ignite 2 is @TaskSessionResource. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16115) Implement getNullable and getOrDefault operations.
[
https://issues.apache.org/jira/browse/IGNITE-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-16115:
-
Fix Version/s: 3.0.0-alpha5
(was: 3.0.0-alpha4)
> Implement getNullable and getOrDefault operations.
> --
>
> Key: IGNITE-16115
> URL: https://issues.apache.org/jira/browse/IGNITE-16115
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> It is allowed to map an object to a single nullable column, which makes
> 'null' values legal in the KeyValue view.
> Once the 'null' value is possible there is no way to distinguish, if there is
> no row in a table for the given key, or the row exists and the mapped column
> contains the 'null' value.
> Let's introduce {{NullableValue}} class-wrapper for a value and implement
> {{{}getNullable(){}}}, and {{getOrDefault()}} + bulk methods.
> {{getNullable()}} is useful for cases, when it's not possible to use a
> "default", but creates an additional wrapper.
> Also, the KeyValueView.get(key) method behavior should be changed:
> * return {{null}} if the table has no row for the key.
> * return a non-null value for the key.
> * fail with a suggestion to use a getNullable, if a {{null}} value returned
> for the key to avoid ambiguity.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16094) Mapper and Marshaller caching
[ https://issues.apache.org/jira/browse/IGNITE-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16094: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Mapper and Marshaller caching > - > > Key: IGNITE-16094 > URL: https://issues.apache.org/jira/browse/IGNITE-16094 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > *Mapper* and *Marshaller* implementations use reflection to retrieve > object fields. We should cache results when possible. > For example: > * *IdentityMapper* instances can be cached by Class > * *Marshaller* instances can be cached by Class + Schema when using > IdentityMapper > See TODOs in code with "IGNITE-16094". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15945) Class inheritance and effectively final fields
[ https://issues.apache.org/jira/browse/IGNITE-15945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15945: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Class inheritance and effectively final fields > -- > > Key: IGNITE-15945 > URL: https://issues.apache.org/jira/browse/IGNITE-15945 > Project: Ignite > Issue Type: Task >Reporter: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Support inheritance of user objects and polymorphic fields. > During the class instance (de)serialization, the (de)serializer traverses the > fields from the descriptor and writes: > * Field's value class descriptor ID and field data if the declared field's > class is non-final. This allows supporting polymorphic fields. > * Field data without field value class descriptor if declared field's class > is final. In this case, the actual field's value object is guaranteed to be > equal to the declared field class. > See > https://github.com/gridgain/gridgain-9-ce/blob/iep-67/modules/network/README.md -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16250) Use direct marshaller and user object serialization instead of JDK serialization for networking
[ https://issues.apache.org/jira/browse/IGNITE-16250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16250: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Use direct marshaller and user object serialization instead of JDK > serialization for networking > --- > > Key: IGNITE-16250 > URL: https://issues.apache.org/jira/browse/IGNITE-16250 > Project: Ignite > Issue Type: Task >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 3h > Remaining Estimate: 0h > > ScaleCube transport currently uses JDK serialization instead of direct > marshalling which can cause performance and compatibility issues. > All of the NetworkMessages should use generated serializers and for all of > the types that are not supported by direct marshaller, user object > serialization should be used. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16082) Thin 3.0: Avoid array allocation when serializing tuples on client
[ https://issues.apache.org/jira/browse/IGNITE-16082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16082: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Thin 3.0: Avoid array allocation when serializing tuples on client > -- > > Key: IGNITE-16082 > URL: https://issues.apache.org/jira/browse/IGNITE-16082 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Minor > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Optimize *writeTuple* overloads in *ClientTable*. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15780) ITDistributedConfigurationPropertiesTest#testFallingBehindDistributedStorageValue is flaky
[ https://issues.apache.org/jira/browse/IGNITE-15780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15780: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > ITDistributedConfigurationPropertiesTest#testFallingBehindDistributedStorageValue > is flaky > -- > > Key: IGNITE-15780 > URL: https://issues.apache.org/jira/browse/IGNITE-15780 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Attachments: ITDistributedConfigurationPropertiesTest.log > > > Test fails locally after a few runs. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16257) Implement readUnshared()/writeUnshared() for User Object Serialization
[ https://issues.apache.org/jira/browse/IGNITE-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16257: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Implement readUnshared()/writeUnshared() for User Object Serialization > -- > > Key: IGNITE-16257 > URL: https://issues.apache.org/jira/browse/IGNITE-16257 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > ObjectOutputStream has writeUnshared() and ObjectInputStream has > readUnshared() methods that differ from writeObject() and readObject() > methods in some aspects (see their javadocs). > We probably need to support this difference. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16152) Thin 3.0: Optimize server-side Tuple handling using known schema version
[ https://issues.apache.org/jira/browse/IGNITE-16152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16152: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Thin 3.0: Optimize server-side Tuple handling using known schema version > > > Key: IGNITE-16152 > URL: https://issues.apache.org/jira/browse/IGNITE-16152 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Thin client protocol is schema-aware, but the known schema is thrown away on > the server after deserialization, and Table API has to match it against > schemas again. > *SchemaAware* interface can be used to preserve known schema when passing > tuples to the Table API (see how TupleMarshallerImpl checks for SchemaAware). > *Example: table.Upsert(Tuple t)* > # Client: match user tuple to schema, serialize with schema version, send to > server > # Server: read schema version, read tuple data, create Tuple, throw away > schema version, pass to Table API > # Server: match tuple to schema -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16196) Supports index rename
[ https://issues.apache.org/jira/browse/IGNITE-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16196: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Supports index rename > - > > Key: IGNITE-16196 > URL: https://issues.apache.org/jira/browse/IGNITE-16196 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 3.0.0-alpha3 >Reporter: Taras Ledkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Need to supports index rename. > ALTER INDEX [ IF EXISTS ] RENAME TO -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15782) User POJO mapping.
[
https://issues.apache.org/jira/browse/IGNITE-15782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15782:
-
Fix Version/s: 3.0.0-alpha5
(was: 3.0.0-alpha4)
> User POJO mapping.
> --
>
> Key: IGNITE-15782
> URL: https://issues.apache.org/jira/browse/IGNITE-15782
> Project: Ignite
> Issue Type: New Feature
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: iep-54, ignite-3
> Fix For: 3.0.0-alpha5
>
>
> Umbrella ticket
> Please, refer to {{org.apache.ignite.internal.table.Example}} for details.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15913) Merge SQL calcite running query registry to 3.0
[ https://issues.apache.org/jira/browse/IGNITE-15913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15913: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Merge SQL calcite running query registry to 3.0 > --- > > Key: IGNITE-15913 > URL: https://issues.apache.org/jira/browse/IGNITE-15913 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Adopt the query registry patch (IGNITE-12991) for the Ignite 3.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16282) Support (un)marshalling of Proxies in User Object Serialization
[ https://issues.apache.org/jira/browse/IGNITE-16282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16282: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Support (un)marshalling of Proxies in User Object Serialization > --- > > Key: IGNITE-16282 > URL: https://issues.apache.org/jira/browse/IGNITE-16282 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15400) Raft bulk update command uses Set for collection of BinaryRow
[ https://issues.apache.org/jira/browse/IGNITE-15400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15400: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Raft bulk update command uses Set for collection of BinaryRow > - > > Key: IGNITE-15400 > URL: https://issues.apache.org/jira/browse/IGNITE-15400 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > InsertAllCommand and UpsertAllCommand uses Set structures for BinaryRow > collection. > BinaryRow object doen't override hashcode/equals methods, so HashSet can't be > used here. > Comparing rows on equality by only their key parts is incorrect in general > case. > So, an external Comparator must be used for that purpose. > Let's use List implementation here as an uniqueness task should be resolved > before a Command object creation or even before the Row serialization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15390) Info on free-lists omitted from Memory Architecture section of current ignite docs
[ https://issues.apache.org/jira/browse/IGNITE-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15390: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Info on free-lists omitted from Memory Architecture section of current ignite > docs > -- > > Key: IGNITE-15390 > URL: https://issues.apache.org/jira/browse/IGNITE-15390 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikolay Shubin >Priority: Minor > Labels: documentation > Fix For: 3.0.0-alpha5 > > > Info concerning Free-lists described in old doc: > [https://apacheignite.readme.io/docs/memory-architecture#free-lists] > was omitted in new doc version: > [https://www.gridgain.com/docs/latest/developers-guide/memory-centric-storage] > Note that old doc treats the subject of free lists in terms of caches > belonging to memory regions. In fact, caches can be united in cache groups, > and then the choice of free space in a data region is made based on the cache > group the cache in question belongs to. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16254) Optimize (un)marshalling of primitives in object fields
[ https://issues.apache.org/jira/browse/IGNITE-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16254: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Optimize (un)marshalling of primitives in object fields > --- > > Key: IGNITE-16254 > URL: https://issues.apache.org/jira/browse/IGNITE-16254 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 40m > Remaining Estimate: 0h > > Currently, during both marshalling and unmarshalling of primitives from/to > fields an intermediary boxed object might be allocated on the heap. > We can use Unsafe to avoid this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16226) .NET: Thin 3.0: Add KeyValueBinaryView
[ https://issues.apache.org/jira/browse/IGNITE-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16226: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > .NET: Thin 3.0: Add KeyValueBinaryView > -- > > Key: IGNITE-16226 > URL: https://issues.apache.org/jira/browse/IGNITE-16226 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-alpha5 > > > Implement *IKeyValueView*. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15804) [IGNITE 3] Remove Ignition and IgnitionManager from the public API
[
https://issues.apache.org/jira/browse/IGNITE-15804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15804:
-
Fix Version/s: 3.0.0-alpha5
(was: 3.0.0-alpha4)
> [IGNITE 3] Remove Ignition and IgnitionManager from the public API
> --
>
> Key: IGNITE-15804
> URL: https://issues.apache.org/jira/browse/IGNITE-15804
> Project: Ignite
> Issue Type: Improvement
>Reporter: Valentin Kulichenko
>Assignee: Sergey Uttsel
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> There are currently no plans to support embedded mode in Ignite 3. Thus, we
> should remove {{Ignition}} and {{IgnitionManager}} classes from the public
> API.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16259) Improve detection of objects that cannot participate in object graph cycles
[ https://issues.apache.org/jira/browse/IGNITE-16259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16259: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Improve detection of objects that cannot participate in object graph cycles > --- > > Key: IGNITE-16259 > URL: https://issues.apache.org/jira/browse/IGNITE-16259 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Currently, only built-ins are considered to be immune to participating in > object graph cycles. But more classes are immune: for example, a class that > only contains primitive fields cannot participate in cycles. > Representation of a non-cycleable object is a bit more compact (as we do not > need to store object ID for it), so we can save a bit of space here. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15948) Implement class structure change handling
[ https://issues.apache.org/jira/browse/IGNITE-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15948: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Implement class structure change handling > - > > Key: IGNITE-15948 > URL: https://issues.apache.org/jira/browse/IGNITE-15948 > Project: Ignite > Issue Type: Task >Reporter: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > User objects may change their class definition (e.g. class can lose its final > modifier, can become private, or in other means inaccessible). Ignite should > make the best effort at merging different versions of descriptors and parsing > objects. > See > https://github.com/gridgain/gridgain-9-ce/blob/iep-67/modules/network/README.md#handling-class-structure-changes -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16199) Implements index build/rebuild
[ https://issues.apache.org/jira/browse/IGNITE-16199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16199: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Implements index build/rebuild > --- > > Key: IGNITE-16199 > URL: https://issues.apache.org/jira/browse/IGNITE-16199 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 3.0.0-alpha3 >Reporter: Taras Ledkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Index must be built on exists table data: scan table's data and build an > index. > Now only update index by table updates is implemented. > May be build and rebuild tasks may be split. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16022) Thin 3.0: Optimize multi-row responses using guaranteed order
[ https://issues.apache.org/jira/browse/IGNITE-16022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16022: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Thin 3.0: Optimize multi-row responses using guaranteed order > - > > Key: IGNITE-16022 > URL: https://issues.apache.org/jira/browse/IGNITE-16022 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > IGNITE-16004 introduces guaranteed row order for multi-row operations, like > *GetAll*, *InsertAll*, *DeleteAll*. We can leverage this fact to optimize the > thin client protocol: > * *GetAll* can return values without keys (keys are known on the client), and > without size (it is the same as input collection size) > * *InsertAll* and *DeleteAll* can return a bit set to indicate which items > were skipped. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16227) .NET: Thin 3.0: Add RecordView with POCO mapping
[ https://issues.apache.org/jira/browse/IGNITE-16227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16227: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > .NET: Thin 3.0: Add RecordView with POCO mapping > > > Key: IGNITE-16227 > URL: https://issues.apache.org/jira/browse/IGNITE-16227 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-alpha5 > > > * Investigate schema-based user object serialization with MessagePack > * Add *IRecordView* with user object mapping. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16298) Object identity distinction must be preserved after marshalling+unmarshalling
[ https://issues.apache.org/jira/browse/IGNITE-16298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16298: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Object identity distinction must be preserved after marshalling+unmarshalling > - > > Key: IGNITE-16298 > URL: https://issues.apache.org/jira/browse/IGNITE-16298 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > If we marshal an object graph containing N distinct objects that are all > equal, then after unmarshalling we must get N distinct objects and not N > references all pointing to just 1 object. It's easy to miss this requirement > for primitive wrapper types (like Integer). > Also, when we marshal a graph containing N references to the same object, > after the unmarshalling this property must be maintained. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-14830) Introduce index internal API
[ https://issues.apache.org/jira/browse/IGNITE-14830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-14830: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Introduce index internal API > > > Key: IGNITE-14830 > URL: https://issues.apache.org/jira/browse/IGNITE-14830 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Labels: iep-74, ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 2h > Remaining Estimate: 0h > > Introduce internal API for the indexes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16240) Support putFields()+writeFields() and readFields() in User Object Serialization
[ https://issues.apache.org/jira/browse/IGNITE-16240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16240: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Support putFields()+writeFields() and readFields() in User Object > Serialization > --- > > Key: IGNITE-16240 > URL: https://issues.apache.org/jira/browse/IGNITE-16240 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > It's about ObjectOutputStream#putFields(), ObjectOutputStream#writeFields() > and ObjectInputStream#readFields(). We probably need to support them to fully > support writeObject()/readObject() inside Serializables. > There is one problem: readFields() returns ObjectInputStream.GetField which > in turn has a method returning ObjectStreamClass which is more or less an > equivalent of our ClassDescriptor. It might happen that we would have to > reconstruct it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15944) [Networking] User object serialization
[
https://issues.apache.org/jira/browse/IGNITE-15944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15944:
-
Fix Version/s: 3.0.0-alpha5
(was: 3.0.0-alpha4)
> [Networking] User object serialization
> --
>
> Key: IGNITE-15944
> URL: https://issues.apache.org/jira/browse/IGNITE-15944
> Project: Ignite
> Issue Type: Epic
>Reporter: Semyon Danilov
>Priority: Major
> Labels: iep-67, ignite-3
> Fix For: 3.0.0-alpha5
>
>
> Arbitrary objects serialization must be provided by Apache Ignite. Unlike
> {{NetworkMessage}} descendants, user objects are not known to the system in
> advance, and serialization layout must be resolved at runtime.
> For more information look at the
> https://github.com/gridgain/gridgain-9-ce/blob/iep-67/modules/network/README.md
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16229) Improve unmarshalling of immutable containers in the User Object Serialization component
[ https://issues.apache.org/jira/browse/IGNITE-16229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16229: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Improve unmarshalling of immutable containers in the User Object > Serialization component > > > Key: IGNITE-16229 > URL: https://issues.apache.org/jira/browse/IGNITE-16229 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > At the moment, we support just one type of immutable containers > (singletonList), but we'll probably want to support other types like > List.of(), Set.of() and so on. > Immutable built-in containers pose a challenge: on the one hand, they can > participate in cycles and hence need to be read in two phases (instantiate, > store reference, fill), but on the other hand, they cannot be modified after > instantiation. > Right now, we implemented a hack: we still read immutable containers in two > phases, but for filling them we have a custom code that breaks their > 'immutability' invariant and pushes the values by force via reflection to > fill such containers. It seems to work, but it's ugly and potentially > dangerous (as we are violating the immutability invariant). > There is another possibility. > # Handle all the values that are not built-in immutable containers in the > same way they are handled now > # For immutable containers, during instantiation phase, create mutable > placeholders instead of the immutable container instances themselves > # Such placeholders need to track the slots of other objects in the graph > that reference them > # They are filled normally on the 'fill' phase > # After the graph is read into memory, it consists of (mainly) normal > objects and placeholders; the placeholders need to be resolved and replaced > with proper immutable container values > # It is impossible to create a cycle of immutable containers (without using > hacks like Reflection), so we can find connectivity components of the graph > (each of such component will be a tree) and then instantiate immutable > containers from placeholders in the leaf-to-root order > # Placeholders need to be replaced with the instantiated immutable > containers in the graph; here, the knowledge about the set of slots which > reference a placeholder (mentioned in item 3) will be useful > # If we encounter a cycle comprised completely of immutable containers (such > cycle can only be creafted using some sort of a hack), we can either fail > with an exception or use a hack (reflection) to forge just one connection of > the cycle. > This is a hybrid approach of > * always having 'real' objects in the graph - which is not realistic when we > have immutable containers > * and always constructing a graph of placeholders first and then turning > them into real objects (this is what Spring does with Bean Definitions and > then Beans) - which seems to incur too much overhead, especially having in > mind that most of the objects are not immutable containers and hence do not > need placeholders to represent them in the intermediate graph -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16295) Listeners "any()" do not get specific instances of the polymorphic configuration, but the general one
[
https://issues.apache.org/jira/browse/IGNITE-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-16295:
-
Fix Version/s: 3.0.0-alpha5
(was: 3.0.0-alpha4)
> Listeners "any()" do not get specific instances of the polymorphic
> configuration, but the general one
> -
>
> Key: IGNITE-16295
> URL: https://issues.apache.org/jira/browse/IGNITE-16295
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha3
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment, listeners *any()* for a polymorphic configuration do not get
> specific instances, but general ones.
> The following example will clearly show the problem:
> {code:java}
> @Config
> public class TableConfigurationSchema {
> @NamedConfigValue
> public BaseIndexConfigurationSchema indexes;
> }
> @PolymorphicConfig
> public class BaseIndexConfigurationSchema {
> @PolymorphicId
> public String type;
> }
> @PolymorphicConfigInstance("hash")
> public class HashIndexConfigurationSchema extends
> BaseIndexConfigurationSchema {
> @Value
> public String column;
> }
> @PolymorphicConfigInstance("sorted")
> public class SortedIndexConfigurationSchema extends
> BaseIndexConfigurationSchema {
> @Value
> public String column;
> }
> ...
> rootConfig.tables().any().listen(ctx->{
> // It's falling here.
> assert ctx.newValue() instanceof HashIndexView;
> return CompletableFuture.completedFuture(null);
> });
> rootConfig.tables()
>
> .change(c->c.create("0",c1->c1.convert(HashIndexChange.class).changeColumn("idx")))
> .get(1,SECONDS);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16198) Use raft state machine to start index scan
[
https://issues.apache.org/jira/browse/IGNITE-16198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-16198:
-
Fix Version/s: 3.0.0-alpha5
(was: 3.0.0-alpha4)
> Use raft state machine to start index scan
> ---
>
> Key: IGNITE-16198
> URL: https://issues.apache.org/jira/browse/IGNITE-16198
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Taras Ledkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> The index must use the same scan approach based on the Raft as the table.
> See: {{InternalTableImpl#scan}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16088) Reuse Marshaller code in marshaller-common module
[ https://issues.apache.org/jira/browse/IGNITE-16088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16088: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > Reuse Marshaller code in marshaller-common module > - > > Key: IGNITE-16088 > URL: https://issues.apache.org/jira/browse/IGNITE-16088 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha4 >Reporter: Pavel Tupitsyn >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-14971 added *ignite-marshaller-common* module to reuse serialization > logic between the server and client parts. > This module duplicates some logic from *ignite-schema* module. > * Remove duplicated code from *ignite-schema* and reuse the logic from common > module. > * Extract other common bits where applicable (e.g. *AsmSerializerGenerator*) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16230) .NET: Thin 3.0: Implement transaction timeouts
[ https://issues.apache.org/jira/browse/IGNITE-16230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-16230: - Fix Version/s: 3.0.0-alpha5 (was: 3.0.0-alpha4) > .NET: Thin 3.0: Implement transaction timeouts > -- > > Key: IGNITE-16230 > URL: https://issues.apache.org/jira/browse/IGNITE-16230 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-alpha5 > > > Add a way to specify timeout for transactions. > Java uses *withTimeout*, in .NET we should probably add a parameter to > *BeginAsync*. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16244) Update examples for Ignite 3
[
https://issues.apache.org/jira/browse/IGNITE-16244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476906#comment-17476906
]
Valentin Kulichenko commented on IGNITE-16244:
--
[~isapego] [~ptupitsyn] Folks, could you take a look at the issue? I believe it
might be related to the client protocol (although it seems to be reproducible
only if tables are created using DDL).
> Update examples for Ignite 3
>
>
> Key: IGNITE-16244
> URL: https://issues.apache.org/jira/browse/IGNITE-16244
> Project: Ignite
> Issue Type: Improvement
> Components: examples
>Affects Versions: 3.0.0-alpha3
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> With the current advancements in Ignite 3 functionality, examples look
> outdated and should be updated.
> The following changes should be made:
> # Use DDL instead of the convoluted {{createTable}} API to create tables.
> # Add examples for POJO-based views (we can use the existing
> {{RecordViewExample}} and {{KeyValueViewExample}} as a basis).
> # Add transactional API example(s).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16244) Update examples for Ignite 3
[
https://issues.apache.org/jira/browse/IGNITE-16244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476904#comment-17476904
]
Valentin Kulichenko commented on IGNITE-16244:
--
After updates, examples fail with a deserialization error in the client
protocol. To reproduce:
# Build from branch {{{}ignite-16244{}}}: {{mvn clean install -DskipTests
-Dcheckstyle.skip}}
# Unzip {{target/apache-ignite-3.0.0-SNAPSHOT.zip}} and switch to the folder.
# Run {{./ignite init}}
# Start a node: {{./ignite node start
--config=examples/config/ignite-config.json my-first-node}}
# Open the {{target/apache-ignite-3.0.0-SNAPSHOT/examples}} project in an IDE.
# Run any of the examples under {{table}} or {{tx}} package.
# Observe the exception shown below.
{noformat}
Exception in thread "main" class
org.apache.ignite.client.IgniteClientException: class
org.apache.ignite.lang.IgniteException: Failed to deserialize server response:
Expected Ext, but got Nil (c0)
at
org.apache.ignite.internal.client.ReliableChannel.lambda$handleServiceAsync$3(ReliableChannel.java:229)
at
java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
at
java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
at
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
Caused by: java.util.concurrent.CompletionException: class
org.apache.ignite.lang.IgniteException: Failed to deserialize server response:
Expected Ext, but got Nil (c0)
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645)
... 6 more
Caused by: class org.apache.ignite.lang.IgniteException: Failed to deserialize
server response: Expected Ext, but got Nil (c0)
at
org.apache.ignite.internal.client.TcpClientChannel.lambda$receiveAsync$1(TcpClientChannel.java:215)
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
... 6 more
Caused by: org.msgpack.core.MessageTypeException: Expected Ext, but got Nil (c0)
at
org.apache.ignite.internal.client.proto.ClientMessageUnpacker.unexpected(ClientMessageUnpacker.java:108)
at
org.apache.ignite.internal.client.proto.ClientMessageUnpacker.unpackExtensionTypeHeader(ClientMessageUnpacker.java:498)
at
org.apache.ignite.internal.client.proto.ClientMessageUnpacker.unpackIgniteUuid(ClientMessageUnpacker.java:753)
at
org.apache.ignite.internal.client.table.ClientTables.lambda$tableAsync$3(ClientTables.java:126)
at
org.apache.ignite.internal.client.TcpClientChannel.lambda$receiveAsync$1(TcpClientChannel.java:213)
... 7 more {noformat}
> Update examples for Ignite 3
>
>
> Key: IGNITE-16244
> URL: https://issues.apache.org/jira/browse/IGNITE-16244
> Project: Ignite
> Issue Type: Improvement
> Components: examples
>Affects Versions: 3.0.0-alpha3
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> With the current advancements in Ignite 3 functionality, examples look
> outdated and should be updated.
> The following changes should be made:
> # Use DDL instead of the convoluted {{createTable}} API to create tables.
> # Add examples for POJO-based views (we can use the existing
> {{RecordViewExample}} and {{KeyValueViewExample}} as a basis).
> # Add transactional API example(s).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-16244) Update examples for Ignite 3
Valentin Kulichenko created IGNITE-16244:
Summary: Update examples for Ignite 3
Key: IGNITE-16244
URL: https://issues.apache.org/jira/browse/IGNITE-16244
Project: Ignite
Issue Type: Improvement
Components: examples
Affects Versions: 3.0.0-alpha3
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Fix For: 3.0.0-alpha4
With the current advancements in Ignite 3 functionality, examples look outdated
and should be updated.
The following changes should be made:
# Use DDL instead of the convoluted {{createTable}} API to create tables.
# Add examples for POJO-based views (we can use the existing
{{RecordViewExample}} and {{KeyValueViewExample}} as a basis).
# Add transactional API example(s).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16151) Introduce timeout for calcite planner
[ https://issues.apache.org/jira/browse/IGNITE-16151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466956#comment-17466956 ] Valentin Kulichenko commented on IGNITE-16151: -- [~ivandasch] Do we know the exact scenarios when this happens (at least some of them)? It seems to me that just having a timeout is not enough. We need to help users as much as possible. > Introduce timeout for calcite planner > - > > Key: IGNITE-16151 > URL: https://issues.apache.org/jira/browse/IGNITE-16151 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Ivan Daschinsky >Priority: Major > Labels: calcite, calcite2-required, calcite3-required > > Since it is quite common case that calcite planner can produce too many plans > and can planning infinitely, it is of crucial > importance to be able to cancel this process on timeout. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16151) Introduce timeout for calcite planner
[ https://issues.apache.org/jira/browse/IGNITE-16151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465847#comment-17465847 ] Valentin Kulichenko commented on IGNITE-16151: -- [~ivandasch] That makes sense, but I still don't understand how a user will have to deal with this. What should they do if the planner goes into the loop and fails after the timeout? Will retry help? Or such scenarios require query changes? > Introduce timeout for calcite planner > - > > Key: IGNITE-16151 > URL: https://issues.apache.org/jira/browse/IGNITE-16151 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Ivan Daschinsky >Priority: Major > Labels: calcite, calcite2-required, calcite3-required > > Since it is quite common case that calcite planner can produce too many plans > and can planning infinitely, it is of crucial > importance to be able to cancel this process on timeout. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16151) Introduce timeout for calcite planner
[ https://issues.apache.org/jira/browse/IGNITE-16151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464724#comment-17464724 ] Valentin Kulichenko commented on IGNITE-16151: -- [~ivandasch] Can you elaborate a little more on the issue? What exactly causes Calcite to go into such a state? What a user is expected to do if the corresponding exception is thrown? > Introduce timeout for calcite planner > - > > Key: IGNITE-16151 > URL: https://issues.apache.org/jira/browse/IGNITE-16151 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Ivan Daschinsky >Priority: Major > Labels: calcite, calcite2-required, calcite3-required > > Since it is quite common case that calcite planner can produce too many plans > and can planning infinitely, it is of crucial > importance to be able to cancel this process on timeout. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-13616) IEP-54 Live schema for tables
[ https://issues.apache.org/jira/browse/IGNITE-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464012#comment-17464012 ] Valentin Kulichenko commented on IGNITE-13616: -- [~amashenkov] Is this parent ticket for IEP-54 as a whole, or specifically for the live schema? > IEP-54 Live schema for tables > - > > Key: IGNITE-13616 > URL: https://issues.apache.org/jira/browse/IGNITE-13616 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Major > Labels: ignite-3 > Fix For: 3.0 > > > Umbrella ticket for > [IEP-54|https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16151) Introduce timeout for calcite planner
[ https://issues.apache.org/jira/browse/IGNITE-16151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464011#comment-17464011 ] Valentin Kulichenko commented on IGNITE-16151: -- [~ivandasch] I would suggest to have a single timeout for the query execution as a whole. >From the user's perspective, planning is a part of execution. There is no good >way for a user to decide how long the planning should take. > Introduce timeout for calcite planner > - > > Key: IGNITE-16151 > URL: https://issues.apache.org/jira/browse/IGNITE-16151 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Ivan Daschinsky >Priority: Major > Labels: calcite, calcite2-required, calcite3-required > > Since it is quite common case that calcite planner can produce too many plans > and can planning infinitely, it is of crucial > importance to be able to cancel this process on timeout. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15957) [IGNITE 3] Create DEB packages
Valentin Kulichenko created IGNITE-15957: Summary: [IGNITE 3] Create DEB packages Key: IGNITE-15957 URL: https://issues.apache.org/jira/browse/IGNITE-15957 Project: Ignite Issue Type: Improvement Components: build Affects Versions: 3.0.0-alpha3 Reporter: Valentin Kulichenko Need to create DEB packages based on ZIP packages describe in IGNITE-15955. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15956) [IGNITE 3] Create RPM packages
Valentin Kulichenko created IGNITE-15956: Summary: [IGNITE 3] Create RPM packages Key: IGNITE-15956 URL: https://issues.apache.org/jira/browse/IGNITE-15956 Project: Ignite Issue Type: Improvement Components: build Affects Versions: 3.0.0-alpha3 Reporter: Valentin Kulichenko Need to create RPM packages based on ZIP packages described in IGNITE-15955. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15955) [IGNITE 3] Packaging improvements
[
https://issues.apache.org/jira/browse/IGNITE-15955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15955:
-
Description:
One of the ideas discussed in the scope of Ignite 3 was to provide a
lightweight download with the CLI tool, which will then allow to install core
artifacts and manage local node if needed. This however, seems to provide
significant complications with a little value, mainly for the following reasons:
* Core artifacts installation is a separate step that user has to perform.
* This approach poorly integrates with OS-specific packaging systems (RPM,
DEB.etc.) and with Linux services.
* CLI tool becomes cumbersome because it manages both local nodes and remote
cluster.
* For external dependencies we will have a separate deployment mechanism, no
need to have another one in the CLI tool.
Proposing to create three separate downloadable ZIP packages:
* {{ignite-cli}} - contains only CLI tool, can be used to connect to a remote
cluster.
* {{ignite-core}} - contains Ignite core artifacts required to start local
nodes, and scripts to manage those nodes ({{{}ignite-start{}}},
{{{}ignite-stop{}}}, {{{}ignite-restart{}}}).
* {{ignite}} - meta package combining {{ignite-cli}} and {{{}ignite-core{}}}.
With these changes, we also need to get rid of CLI tool commands responsible
for local node management and artifact installation.
was:
One of the ideas discussed in the scope of Ignite 3 was to provide a
lightweight download with the CLI tool, which will then allow to install core
artifacts and manage local node if needed. This however, seems to provide
significant complications with a little value, mainly for the following reasons:
* Core artifacts installation is a separate step that user has to perform.
* This approach poorly integrates with OS-specific packaging systems (RPM,
DEB.etc.) and with Linux services.
* CLI tool becomes cumbersome because it manages both local nodes and remote
cluster.
Proposing to create three separate downloadable ZIP packages:
* {{ignite-cli}} - contains only CLI tool, can be used to connect to a remote
cluster.
* {{ignite-core}} - contains Ignite core artifacts required to start local
nodes, and scripts to manage those nodes ({{{}ignite-start{}}},
{{{}ignite-stop{}}}, {{{}ignite-restart{}}}).
* {{ignite}} - meta package combining {{ignite-cli}} and {{{}ignite-core{}}}.
> [IGNITE 3] Packaging improvements
> -
>
> Key: IGNITE-15955
> URL: https://issues.apache.org/jira/browse/IGNITE-15955
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Affects Versions: 3.0.0-alpha3
>Reporter: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3
>
> One of the ideas discussed in the scope of Ignite 3 was to provide a
> lightweight download with the CLI tool, which will then allow to install core
> artifacts and manage local node if needed. This however, seems to provide
> significant complications with a little value, mainly for the following
> reasons:
> * Core artifacts installation is a separate step that user has to perform.
> * This approach poorly integrates with OS-specific packaging systems (RPM,
> DEB.etc.) and with Linux services.
> * CLI tool becomes cumbersome because it manages both local nodes and remote
> cluster.
> * For external dependencies we will have a separate deployment mechanism, no
> need to have another one in the CLI tool.
> Proposing to create three separate downloadable ZIP packages:
> * {{ignite-cli}} - contains only CLI tool, can be used to connect to a
> remote cluster.
> * {{ignite-core}} - contains Ignite core artifacts required to start local
> nodes, and scripts to manage those nodes ({{{}ignite-start{}}},
> {{{}ignite-stop{}}}, {{{}ignite-restart{}}}).
> * {{ignite}} - meta package combining {{ignite-cli}} and {{{}ignite-core{}}}.
> With these changes, we also need to get rid of CLI tool commands responsible
> for local node management and artifact installation.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-15955) [IGNITE 3] Packaging improvements
Valentin Kulichenko created IGNITE-15955:
Summary: [IGNITE 3] Packaging improvements
Key: IGNITE-15955
URL: https://issues.apache.org/jira/browse/IGNITE-15955
Project: Ignite
Issue Type: Improvement
Components: build
Affects Versions: 3.0.0-alpha3
Reporter: Valentin Kulichenko
One of the ideas discussed in the scope of Ignite 3 was to provide a
lightweight download with the CLI tool, which will then allow to install core
artifacts and manage local node if needed. This however, seems to provide
significant complications with a little value, mainly for the following reasons:
* Core artifacts installation is a separate step that user has to perform.
* This approach poorly integrates with OS-specific packaging systems (RPM,
DEB.etc.) and with Linux services.
* CLI tool becomes cumbersome because it manages both local nodes and remote
cluster.
Proposing to create three separate downloadable ZIP packages:
* {{ignite-cli}} - contains only CLI tool, can be used to connect to a remote
cluster.
* {{ignite-core}} - contains Ignite core artifacts required to start local
nodes, and scripts to manage those nodes ({{{}ignite-start{}}},
{{{}ignite-stop{}}}, {{{}ignite-restart{}}}).
* {{ignite}} - meta package combining {{ignite-cli}} and {{{}ignite-core{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15437) .NET: Thin 3.0: NuGet Multitargeting
[ https://issues.apache.org/jira/browse/IGNITE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15437: - Priority: Major (was: Blocker) > .NET: Thin 3.0: NuGet Multitargeting > > > Key: IGNITE-15437 > URL: https://issues.apache.org/jira/browse/IGNITE-15437 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Priority: Major > Labels: .NET, iep-78, ignite-3 > Fix For: 3.0 > > > Make a decision on supported .NET versions before the *final release of > Ignite 3.0*, and set up NuGet multitargeting accordingly. > Per IEP-78, we target only netstandard2.1 while in pre-release stage, and > this should be reviewed. > https://cwiki.apache.org/confluence/display/IGNITE/IEP-78+.NET+Thin+Client -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15804) [IGNITE 3] Remove Ignition and IgnitionManager from the public API
[
https://issues.apache.org/jira/browse/IGNITE-15804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15804:
-
Labels: ignite-3 (was: )
> [IGNITE 3] Remove Ignition and IgnitionManager from the public API
> --
>
> Key: IGNITE-15804
> URL: https://issues.apache.org/jira/browse/IGNITE-15804
> Project: Ignite
> Issue Type: Improvement
>Reporter: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> There are currently no plans to support embedded mode in Ignite 3. Thus, we
> should remove {{Ignition}} and {{IgnitionManager}} classes from the public
> API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15804) [IGNITE 3] Remove Ignition and IgnitionManager from the public API
Valentin Kulichenko created IGNITE-15804:
Summary: [IGNITE 3] Remove Ignition and IgnitionManager from the
public API
Key: IGNITE-15804
URL: https://issues.apache.org/jira/browse/IGNITE-15804
Project: Ignite
Issue Type: Improvement
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha4
There are currently no plans to support embedded mode in Ignite 3. Thus, we
should remove {{Ignition}} and {{IgnitionManager}} classes from the public API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15775) Provide documentation for Alpha 3 release
[ https://issues.apache.org/jira/browse/IGNITE-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432592#comment-17432592 ] Valentin Kulichenko commented on IGNITE-15775: -- Merged the PR. Thanks, [~nsafonov]! > Provide documentation for Alpha 3 release > - > > Key: IGNITE-15775 > URL: https://issues.apache.org/jira/browse/IGNITE-15775 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0-alpha3 >Reporter: Nikita Safonov >Assignee: Nikita Safonov >Priority: Critical > Labels: docuentation > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > We need to prepare a full set of documentation for the Apache Ignite Alpha 3 > release, which includes: > - New SQL engine based on Apache Calcite + JDBC driver > - Persistence implementation based on RocksDB > - New binary client protocol with an implementation in Java > - Data rebalancing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15775) Provide documentation for Alpha 3 release
[
https://issues.apache.org/jira/browse/IGNITE-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432129#comment-17432129
]
Valentin Kulichenko commented on IGNITE-15775:
--
[~nsafonov], several comments regarding your PR:
# Please replace {{node-1}} with {{my-first-node}} for start and stop node
steps in the getting started guide.
# Built-in Examples section of the getting started guide doesn't list all the
examples. You can grab the correct list from here:
[https://github.com/apache/ignite-3/blob/main/examples/README.md]
# Ignite CLI Tool page still claims the {{config}} commands do not work, which
is not the case - they've been fixed. Please remove the callout and add the
commands to the list.
# Same goes for the Known Issues section on the index page. Let's remove the
section.
# I've noticed that if there is an {{.ignitecfg}} file in the home folder left
from a previous installation (alpha 1 or alpha 2), the installation can fail.
Let's add the "zero" step to the installation procedure - smth like "If you've
installed one of the Ignite 3 Alpha releases before, please remove the
{{~/.ignitecfg}} file before proceeding. Add a note that this is temporary and
the procedure will be improved in the future releases.
> Provide documentation for Alpha 3 release
> -
>
> Key: IGNITE-15775
> URL: https://issues.apache.org/jira/browse/IGNITE-15775
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 3.0.0-alpha3
>Reporter: Nikita Safonov
>Assignee: Nikita Safonov
>Priority: Critical
> Labels: docuentation
> Fix For: 3.0.0-alpha3
>
>
> We need to prepare a full set of documentation for the Apache Ignite Alpha 3
> release, which includes:
> - New SQL engine based on Apache Calcite + JDBC driver
> - Persistence implementation based on RocksDB
> - New binary client protocol with an implementation in Java
> - Data rebalancing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15741) Deploy .NET client NuGet package for 3.0.0-alpha3
[ https://issues.apache.org/jira/browse/IGNITE-15741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429624#comment-17429624 ] Valentin Kulichenko commented on IGNITE-15741: -- [~ptupitsyn] [~vveider] Pavel, Petr, the release has been accepted: [https://lists.apache.org/thread.html/r555fe366b60c064801a403b78895b3d76ee5fd34d8631b96d1a2fb1d%40%3Cdev.ignite.apache.org%3E] Can one of you please deploy the NuGet package? > Deploy .NET client NuGet package for 3.0.0-alpha3 > - > > Key: IGNITE-15741 > URL: https://issues.apache.org/jira/browse/IGNITE-15741 > Project: Ignite > Issue Type: Task > Components: build, thin client >Reporter: Valentin Kulichenko >Assignee: Petr Ivanov >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Need to build the NuGet package for 3.0.0-alpha3 and deploy it to the > repository. > Release branch to build from: > [https://github.com/apache/ignite-3/tree/ignite-3.0.0-alpha3] > TC task for building binaries: > https://ci.ignite.apache.org/buildConfiguration/ignite3_Release_Build_DotnetBinaries?branch=ignite-3.0.0-alpha3=builds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15741) Deploy .NET client NuGet package for 3.0.0-alpha3
[ https://issues.apache.org/jira/browse/IGNITE-15741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15741: - Description: Need to build the NuGet package for 3.0.0-alpha3 and deploy it to the repository. Release branch to build from: https://github.com/apache/ignite-3/tree/ignite-3.0.0-alpha3 > Deploy .NET client NuGet package for 3.0.0-alpha3 > - > > Key: IGNITE-15741 > URL: https://issues.apache.org/jira/browse/IGNITE-15741 > Project: Ignite > Issue Type: Task > Components: build, thin client >Reporter: Valentin Kulichenko >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Need to build the NuGet package for 3.0.0-alpha3 and deploy it to the > repository. > Release branch to build from: > https://github.com/apache/ignite-3/tree/ignite-3.0.0-alpha3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15741) Deploy .NET client NuGet package for 3.0.0-alpha3
Valentin Kulichenko created IGNITE-15741: Summary: Deploy .NET client NuGet package for 3.0.0-alpha3 Key: IGNITE-15741 URL: https://issues.apache.org/jira/browse/IGNITE-15741 Project: Ignite Issue Type: Task Components: build, thin client Reporter: Valentin Kulichenko Fix For: 3.0.0-alpha3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15729) RecordViewExample fails with two remote nodes
Valentin Kulichenko created IGNITE-15729:
Summary: RecordViewExample fails with two remote nodes
Key: IGNITE-15729
URL: https://issues.apache.org/jira/browse/IGNITE-15729
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 3.0.0-alpha3
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha4
To reproduce:
# Start *two* nodes using the CLI tool.
# Run the {{RecordViewExample}} (need to check other examples as well).
# Observe the exception shown below.
{noformat}
Exception in thread "main" java.util.concurrent.CompletionException: class
org.apache.ignite.client.IgniteClientException: class
org.apache.ignite.client.IgniteClientException: class
org.apache.ignite.raft.jraft.rpc.impl.RaftException: ENOENT:No nodes in group
1-40f121ca-81e4-4929-8ad3-24f5742c81af_part_6
at
java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:367)
at
java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:376)
at
java.base/java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:1019)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
at
org.apache.ignite.internal.client.ReliableChannel.lambda$handleServiceAsync$3(ReliableChannel.java:213)
at
java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
at
java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
at
org.apache.ignite.internal.client.TcpClientChannel.processNextMessage(TcpClientChannel.java:260)
at
org.apache.ignite.internal.client.TcpClientChannel.onMessage(TcpClientChannel.java:109)
at
org.apache.ignite.internal.client.io.netty.NettyClientConnection.onMessage(NettyClientConnection.java:85)
at
org.apache.ignite.internal.client.io.netty.NettyClientMessageHandler.channelRead(NettyClientMessageHandler.java:33)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:324)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:296)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: class org.apache.ignite.client.IgniteClientException: class
org.apache.ignite.client.IgniteClientException: class
org.apache.ignite.raft.jraft.rpc.impl.RaftException: ENOENT:No nodes in group
1-40f121ca-81e4-4929-8ad3-24f5742c81af_part_6
at
org.apache.ignite.internal.client.ReliableChannel.lambda$handleServiceAsync$3(ReliableChannel.java:215)
...
[jira] [Assigned] (IGNITE-15720) Examples fail to run with a remote node started from CLI
[
https://issues.apache.org/jira/browse/IGNITE-15720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-15720:
Assignee: Valentin Kulichenko
> Examples fail to run with a remote node started from CLI
>
>
> Key: IGNITE-15720
> URL: https://issues.apache.org/jira/browse/IGNITE-15720
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> To reproduce:
> # Download the pre-release build from here:
> [https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha3-test/apache-ignite-3.0.0-alpha3.zip]
> # Unzip and go to the created folder.
> # Install Ignite core from staging: {{./ignite init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1530}}
> # Start a node: {{./ignite node start
> --config=examples/config/ignite-config.json node-1}}
> # Open the {{examples}} project and run any example (e.g.
> {{RecordViewExample}}).
> # Example either fails with the exception below, or hangs on the table
> creation step.
> {noformat}
> Exception in thread "main" class org.apache.ignite.lang.IgniteException:
> Unable to start node=[node-0].
> at
> org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:147)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:88)
> at org.apache.ignite.IgnitionManager.start(IgnitionManager.java:79)
> at
> org.apache.ignite.example.table.KeyValueViewExample.main(KeyValueViewExample.java:54)
> Caused by: class org.apache.ignite.lang.IgniteException: Unable to start
> node=[node-0].
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:298)
> at
> org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
> ... 3 more
> Caused by: java.util.concurrent.CompletionException:
> java.util.concurrent.TimeoutException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2152)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:487)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl$1.lambda$accept$1(RaftGroupServiceImpl.java:518)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
> at java.base/java.lang.Thread.run(Thread.java:832)
> Caused by: java.util.concurrent.TimeoutException
> ... 7 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15719) Several issues with 'examples' module
[
https://issues.apache.org/jira/browse/IGNITE-15719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426717#comment-17426717
]
Valentin Kulichenko commented on IGNITE-15719:
--
TC passed - merged to {{main}} and {{alpha3}}
> Several issues with 'examples' module
> -
>
> Key: IGNITE-15719
> URL: https://issues.apache.org/jira/browse/IGNITE-15719
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are several issues with the {{examples}} module in Ignite 3:
> * {{README}} file is not updated (doesn't list newly added examples).
> * Tests are included in packaging.
> * SQL example should use try-with-resources for the server node, similar to
> other examples.
> * Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
> removed and replaced with the versions that use the new client implementation
> ( {{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
> * Example JavaDocs and outputs don't look complete and might require a
> review.
> * If a table is created for an example, it should be dropped at the end.
> Otherwise, subsequent executions can fail.
> * Logging is not formatted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15720) Examples fail to run with a remote node started from CLI
Valentin Kulichenko created IGNITE-15720:
Summary: Examples fail to run with a remote node started from CLI
Key: IGNITE-15720
URL: https://issues.apache.org/jira/browse/IGNITE-15720
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha3
To reproduce:
# Download the pre-release build from here:
[https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha3-test/apache-ignite-3.0.0-alpha3.zip]
# Unzip and go to the created folder.
# Install Ignite core from staging: {{./ignite init
--repo=https://repository.apache.org/content/repositories/orgapacheignite-1530}}
# Start a node: {{./ignite node start
--config=examples/config/ignite-config.json node-1}}
# Open the {{examples}} project and run any example (e.g.
{{RecordViewExample}}).
# Example either fails with the exception below, or hangs on the table
creation step.
{noformat}
Exception in thread "main" class org.apache.ignite.lang.IgniteException: Unable
to start node=[node-0].
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:147)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:88)
at org.apache.ignite.IgnitionManager.start(IgnitionManager.java:79)
at
org.apache.ignite.example.table.KeyValueViewExample.main(KeyValueViewExample.java:54)
Caused by: class org.apache.ignite.lang.IgniteException: Unable to start
node=[node-0].
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:298)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
... 3 more
Caused by: java.util.concurrent.CompletionException:
java.util.concurrent.TimeoutException
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2152)
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:487)
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl$1.lambda$accept$1(RaftGroupServiceImpl.java:518)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: java.util.concurrent.TimeoutException
... 7 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15719) Several issues with 'examples' module
[
https://issues.apache.org/jira/browse/IGNITE-15719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15719:
-
Description:
There are several issues with the {{examples}} module in Ignite 3:
* {{README}} file is not updated (doesn't list newly added examples).
* Tests are included in packaging.
* SQL example should use try-with-resources for the server node, similar to
other examples.
* Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
removed and replaced with the versions that use the new client implementation (
{{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
* Example JavaDocs and outputs don't look complete and might require a review.
* If a table is created for an example, it should be dropped at the end.
Otherwise, subsequent executions can fail.
* Logging is not formatted.
was:
There are several issues with the {{examples}} module in Ignite 3:
* {{README}} file is not updated (doesn't list newly added examples).
* Tests are included in packaging.
* SQL example should use try-with-resources for the server node, similar to
other examples.
* Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
removed and replaced with the versions that use the new client implementation (
{{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
* Example JavaDocs don't look complete and might require a review.
* If a table is created for an example, it should be dropped at the end.
Otherwise, subsequent executions can fail.
* Logging is not formatted.
> Several issues with 'examples' module
> -
>
> Key: IGNITE-15719
> URL: https://issues.apache.org/jira/browse/IGNITE-15719
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> There are several issues with the {{examples}} module in Ignite 3:
> * {{README}} file is not updated (doesn't list newly added examples).
> * Tests are included in packaging.
> * SQL example should use try-with-resources for the server node, similar to
> other examples.
> * Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
> removed and replaced with the versions that use the new client implementation
> ( {{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
> * Example JavaDocs and outputs don't look complete and might require a
> review.
> * If a table is created for an example, it should be dropped at the end.
> Otherwise, subsequent executions can fail.
> * Logging is not formatted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15719) Several issues with 'examples' module
[
https://issues.apache.org/jira/browse/IGNITE-15719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15719:
-
Description:
There are several issues with the {{examples}} module in Ignite 3:
* {{README}} file is not updated (doesn't list newly added examples).
* Tests are included in packaging.
* SQL example should use try-with-resources for the server node, similar to
other examples.
* Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
removed and replaced with the versions that use the new client implementation (
{{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
* Example JavaDocs don't look complete and might require a review.
* If a table is created for an example, it should be dropped at the end.
Otherwise, subsequent executions can fail.
* Logging is not formatted.
was:
There are several issues with the {{examples}} module in Ignite 3:
* {{README}} file is not updated (doesn't list newly added examples).
* Tests are included in packaging.
* SQL example should use try-with-resources for the server node, similar to
other examples.
* Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
removed and replaced with the versions that use the new client implementation (
{{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
* Example JavaDocs don't look complete and might require a review.
> Several issues with 'examples' module
> -
>
> Key: IGNITE-15719
> URL: https://issues.apache.org/jira/browse/IGNITE-15719
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> There are several issues with the {{examples}} module in Ignite 3:
> * {{README}} file is not updated (doesn't list newly added examples).
> * Tests are included in packaging.
> * SQL example should use try-with-resources for the server node, similar to
> other examples.
> * Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
> removed and replaced with the versions that use the new client implementation
> ( {{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
> * Example JavaDocs don't look complete and might require a review.
> * If a table is created for an example, it should be dropped at the end.
> Otherwise, subsequent executions can fail.
> * Logging is not formatted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15719) Several issues with 'examples' module
Valentin Kulichenko created IGNITE-15719:
Summary: Several issues with 'examples' module
Key: IGNITE-15719
URL: https://issues.apache.org/jira/browse/IGNITE-15719
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Fix For: 3.0.0-alpha3
There are several issues with the {{examples}} module in Ignite 3:
* {{README}} file is not updated (doesn't list newly added examples).
* Tests are included in packaging.
* SQL example should use try-with-resources for the server node, similar to
other examples.
* Older {{RecordViewExample}} and {{KeyValueBinaryView}} examples should be
removed and replaced with the versions that use the new client implementation (
{{ClientRecordViewExample}} and {{ClientKeyValueViewExample}} respectively).
* Example JavaDocs don't look complete and might require a review.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15708) Fix DEB/RPM repository redirect and docs
[
https://issues.apache.org/jira/browse/IGNITE-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426281#comment-17426281
]
Valentin Kulichenko commented on IGNITE-15708:
--
[~vveider], I've updated the {{.htaccess}} files:
* [https://dist.apache.org/repos/dist/release/ignite/deb/.htaccess]
* [https://dist.apache.org/repos/dist/release/ignite/rpm/.htaccess]
Let me know if any other help is needed!
> Fix DEB/RPM repository redirect and docs
>
>
> Key: IGNITE-15708
> URL: https://issues.apache.org/jira/browse/IGNITE-15708
> Project: Ignite
> Issue Type: Bug
>Reporter: Petr Ivanov
>Assignee: Valentin Kulichenko
>Priority: Critical
>
> * Current redirect for DEB/RPM package seems to be wrong, tested and working
> one is
> {code:bash}
> https://apache.jfrog.io/artifactory/ignite-{deb|rpm}
> {code}
> * Documentation should be changed too
> (https://ignite.apache.org/docs/latest/installation/deb-rpm#installing-deb-package):
> {code:bash}
> sudo apt update
> sudo apt install gnupg ca-certificates --no-install-recommends -y
> sudo bash -c 'cat < /etc/apt/sources.list.d/ignite.list
> deb https://apache.jfrog.io/artifactory/ignite-deb/ apache-ignite main
> EOF'
> sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys
> 0EE62FB37A00258D
> sudo apt update
> sudo apt install apache-ignite --no-install-recommends
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15708) Fix DEB/RPM repository redirect and docs
[
https://issues.apache.org/jira/browse/IGNITE-15708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-15708:
Assignee: Petr Ivanov (was: Valentin Kulichenko)
> Fix DEB/RPM repository redirect and docs
>
>
> Key: IGNITE-15708
> URL: https://issues.apache.org/jira/browse/IGNITE-15708
> Project: Ignite
> Issue Type: Bug
>Reporter: Petr Ivanov
>Assignee: Petr Ivanov
>Priority: Critical
>
> * Current redirect for DEB/RPM package seems to be wrong, tested and working
> one is
> {code:bash}
> https://apache.jfrog.io/artifactory/ignite-{deb|rpm}
> {code}
> * Documentation should be changed too
> (https://ignite.apache.org/docs/latest/installation/deb-rpm#installing-deb-package):
> {code:bash}
> sudo apt update
> sudo apt install gnupg ca-certificates --no-install-recommends -y
> sudo bash -c 'cat < /etc/apt/sources.list.d/ignite.list
> deb https://apache.jfrog.io/artifactory/ignite-deb/ apache-ignite main
> EOF'
> sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys
> 0EE62FB37A00258D
> sudo apt update
> sudo apt install apache-ignite --no-install-recommends
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15491) Introduce IgniteCluster interface to manipulate baseline nodes
[ https://issues.apache.org/jira/browse/IGNITE-15491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15491: - Fix Version/s: 3.0.0-alpha3 > Introduce IgniteCluster interface to manipulate baseline nodes > --- > > Key: IGNITE-15491 > URL: https://issues.apache.org/jira/browse/IGNITE-15491 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 8h 50m > Remaining Estimate: 0h > > Introduce IgniteCluster API as a temporary solution in order to trigger > rebalance in a manual way. Perhaps it will be easier to take the approach > introduced by IGNITE-15125 (this approach is based on events and changes > topology baseline in an automatic way) > Need to choose the most appropriate for the first phase (IGNITE-14209) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15125) Implement naive partitions reassignment
[ https://issues.apache.org/jira/browse/IGNITE-15125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15125: - Fix Version/s: (was: 3.0.0-alpha3) 3.0.0-alpha4 > Implement naive partitions reassignment > --- > > Key: IGNITE-15125 > URL: https://issues.apache.org/jira/browse/IGNITE-15125 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexander Lapin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Original Estimate: 96h > Time Spent: 0.5h > Remaining Estimate: 95.5h > > TBD -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15490) Create an example(s) that can allow to demonstrate rebalancing from the end-user point of view
[ https://issues.apache.org/jira/browse/IGNITE-15490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15490: - Fix Version/s: 3.0.0-alpha3 > Create an example(s) that can allow to demonstrate rebalancing from the > end-user point of view > -- > > Key: IGNITE-15490 > URL: https://issues.apache.org/jira/browse/IGNITE-15490 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Need to implement examples that show joining new nodes to the cluster and > rebalancing data across all the cluster nodes. The case with nodes moved > offline should be covered as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15060) ignitecli must provide work directory path during node start
[ https://issues.apache.org/jira/browse/IGNITE-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15060: - Fix Version/s: (was: 3.0.0-alpha3) 3.0.0-alpha4 > ignitecli must provide work directory path during node start > > > Key: IGNITE-15060 > URL: https://issues.apache.org/jira/browse/IGNITE-15060 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15700) Rename 'Table#tableName' method to 'name'
Valentin Kulichenko created IGNITE-15700:
Summary: Rename 'Table#tableName' method to 'name'
Key: IGNITE-15700
URL: https://issues.apache.org/jira/browse/IGNITE-15700
Project: Ignite
Issue Type: Bug
Reporter: Valentin Kulichenko
The {{table}} prefix seems redundant here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15699) Incorrect class name: TableSchemaBuilder
Valentin Kulichenko created IGNITE-15699:
Summary: Incorrect class name: TableSchemaBuilder
Key: IGNITE-15699
URL: https://issues.apache.org/jira/browse/IGNITE-15699
Project: Ignite
Issue Type: Bug
Reporter: Valentin Kulichenko
Looks like {{TableSchemaBuilder}} was left untouched during renamings in the
{{org.apache.ignite.schema}} package.
The correct name should be {{TableDefinitionBuilder}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15675) Ignite CLI commands must fit general logging formatting
[
https://issues.apache.org/jira/browse/IGNITE-15675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15675:
-
Fix Version/s: 3.0.0-alpha3
> Ignite CLI commands must fit general logging formatting
>
>
> Key: IGNITE-15675
> URL: https://issues.apache.org/jira/browse/IGNITE-15675
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> When you run, for example,
> {code:bash}
> ./ignite init
> ./ignite node start
> {code}
> output log differs from formatting for ignite, that is described in
> {{config/java.util.logging.properties}}. CLI commands must reuse the common
> config file.
> A possible solution is to pass
> {code:java}
> -Djava.util.logging.config.file=../../config/java.util.logging.properties
> {code}
> in {{modules/cli/ignite.sh}} and in
> {{org.apache.ignite.cli.builtins.node.NodeManager#start}}
>
> Also, this dependency must be added to cli module pom:
> {code:xml}
>
> org.slf4j
> slf4j-jdk14
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15125) Implement naive partitions reassignment
[ https://issues.apache.org/jira/browse/IGNITE-15125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15125: - Fix Version/s: 3.0.0-alpha3 > Implement naive partitions reassignment > --- > > Key: IGNITE-15125 > URL: https://issues.apache.org/jira/browse/IGNITE-15125 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexander Lapin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Original Estimate: 96h > Time Spent: 0.5h > Remaining Estimate: 95.5h > > TBD -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15060) ignitecli must provide work directory path during node start
[ https://issues.apache.org/jira/browse/IGNITE-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15060: - Fix Version/s: 3.0.0-alpha3 > ignitecli must provide work directory path during node start > > > Key: IGNITE-15060 > URL: https://issues.apache.org/jira/browse/IGNITE-15060 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15681) SLF4J header is printed out in CLI
[
https://issues.apache.org/jira/browse/IGNITE-15681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15681:
-
Fix Version/s: 3.0.0-alpha3
> SLF4J header is printed out in CLI
> --
>
> Key: IGNITE-15681
> URL: https://issues.apache.org/jira/browse/IGNITE-15681
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> Currently, every CLI command has the following output at the very beginning:
> {noformat}
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> {noformat}
> This output is unnecessary and should be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15687) Unable to start more than one node on a single server
Valentin Kulichenko created IGNITE-15687:
Summary: Unable to start more than one node on a single server
Key: IGNITE-15687
URL: https://issues.apache.org/jira/browse/IGNITE-15687
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha3
If I try to start two server nodes on my laptop from the CLI tool, the second
fails to start with the following error:
{noformat}
Oct 05, 2021 5:13:06 PM org.apache.ignite.lang.IgniteLogger error
SEVERE: Unable to start node=[node-2].
class org.apache.ignite.lang.IgniteInternalException: While lock file:
work/vault/LOCK: Resource temporarily unavailable
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:103)
at
org.apache.ignite.internal.vault.VaultManager.start(VaultManager.java:50)
at
org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:385)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:238)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Caused by: org.rocksdb.RocksDBException: While lock file: work/vault/LOCK:
Resource temporarily unavailable
at org.rocksdb.RocksDB.open(Native Method)
at org.rocksdb.RocksDB.open(RocksDB.java:251)
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:100)
... 6 more
Oct 05, 2021 5:13:06 PM org.apache.ignite.lang.IgniteLogger error
SEVERE: Unable to stop
component=[org.apache.ignite.internal.vault.VaultManager@1a1da881] within
node=[node-2]
java.lang.NullPointerException
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.close(PersistentVaultService.java:121)
at
org.apache.ignite.internal.vault.VaultManager.stop(VaultManager.java:56)
at
org.apache.ignite.internal.app.IgniteImpl.doStopNode(IgniteImpl.java:418)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:292)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Exception in thread "main" class org.apache.ignite.lang.IgniteException: Unable
to start node=[node-2].
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:147)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Caused by: class org.apache.ignite.lang.IgniteException: Unable to start
node=[node-2].
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:294)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
... 2 more
Caused by: class org.apache.ignite.lang.IgniteInternalException: While lock
file: work/vault/LOCK: Resource temporarily unavailable
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:103)
at
org.apache.ignite.internal.vault.VaultManager.start(VaultManager.java:50)
at
org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:385)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:238)
... 3 more
Caused by: org.rocksdb.RocksDBException: While lock file: work/vault/LOCK:
Resource temporarily unavailable
at org.rocksdb.RocksDB.open(Native Method)
at org.rocksdb.RocksDB.open(RocksDB.java:251)
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:100)
... 6 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15686) TableExample and KeyValueBinaryViewExample fail with NPE
Valentin Kulichenko created IGNITE-15686:
Summary: TableExample and KeyValueBinaryViewExample fail with NPE
Key: IGNITE-15686
URL: https://issues.apache.org/jira/browse/IGNITE-15686
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha3
{noformat}
Exception in thread "main" java.util.concurrent.CompletionException: class
org.apache.ignite.internal.manager.ListenerRemovedException:
java.lang.NullPointerException
at
java.base/java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:412)
at
java.base/java.util.concurrent.CompletableFuture.join(CompletableFuture.java:2108)
at
org.apache.ignite.internal.table.distributed.TableManager.createTable(TableManager.java:382)
at
org.apache.ignite.example.table.TableExample.main(TableExample.java:65)
Caused by: class org.apache.ignite.internal.manager.ListenerRemovedException:
java.lang.NullPointerException
at
org.apache.ignite.internal.manager.Producer.removeListener(Producer.java:65)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$10(TableManager.java:489)
at
java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
at
java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1769)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1756)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016)
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
Caused by: class org.apache.ignite.lang.IgniteInternalCheckedException:
java.lang.NullPointerException
... 11 more
Caused by: java.util.concurrent.CompletionException:
java.lang.NullPointerException
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1766)
... 6 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.configuration.schemas.table.TableNode.partitions(Unknown
Source)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$8(TableManager.java:464)
at
org.apache.ignite.internal.configuration.tree.NamedListNode.create(NamedListNode.java:131)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$9(TableManager.java:452)
at
org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:88)
at
org.apache.ignite.configuration.schemas.table.TablesNode.construct(Unknown
Source)
at
org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:90)
at
org.apache.ignite.internal.configuration.SuperRoot.construct(SuperRoot.java:137)
at
org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:90)
at
org.apache.ignite.internal.configuration.ConfigurationChanger.lambda$changeInternally$1(ConfigurationChanger.java:376)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1764)
... 6 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15685) Examples should be renamed
Valentin Kulichenko created IGNITE-15685:
Summary: Examples should be renamed
Key: IGNITE-15685
URL: https://issues.apache.org/jira/browse/IGNITE-15685
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Fix For: 3.0.0-alpha3
The Ignite 3 Table API changed, so current example names look inconsistent.
Need to rename:
* {{TableExample}} to {{RecordViewExample}}.
* {{KeyValueBinaryViewExample}} to {{KeyValueViewExample}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15685) Examples should be renamed
[
https://issues.apache.org/jira/browse/IGNITE-15685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15685:
-
Priority: Blocker (was: Major)
> Examples should be renamed
> --
>
> Key: IGNITE-15685
> URL: https://issues.apache.org/jira/browse/IGNITE-15685
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> The Ignite 3 Table API changed, so current example names look inconsistent.
> Need to rename:
> * {{TableExample}} to {{RecordViewExample}}.
> * {{KeyValueBinaryViewExample}} to {{KeyValueViewExample}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15683) CLI tool says 'Can't start the node' even though the node is successfully started
[
https://issues.apache.org/jira/browse/IGNITE-15683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-15683:
Assignee: Valentin Kulichenko
> CLI tool says 'Can't start the node' even though the node is successfully
> started
> -
>
> Key: IGNITE-15683
> URL: https://issues.apache.org/jira/browse/IGNITE-15683
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite node start}} command fails with the following message even though
> the node actually starts:
> {code}
> Starting a new Ignite node...
> Can't start the node. Read logs for details:
> /Users/vkulichenko/GridGain/ignite-3/target/apache-ignite-3.0.0-alpha3/ignite-log/node-1.log
> {code}
> Looks like this happens because there is the following line in the log:
> {noformat}
> Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger
> logInternalExceptional
> {noformat}
> The tool treats it as a failure because of this condition (see
> {{NodeManager}} class):
> {code}
> else if (content.contains("Exception"))
> throw new IgniteCLIException("Can't start the node. Read logs for
> details: " + file);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
