[jira] [Commented] (IGNITE-17063) .NET: Failed to load libjvm.so in some environments
[ https://issues.apache.org/jira/browse/IGNITE-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550836#comment-17550836 ] Pavel Tupitsyn commented on IGNITE-17063: - Merged to master: 5c9a8c7a95be59a5299a2ae05a61611a3a45129b > .NET: Failed to load libjvm.so in some environments > --- > > Key: IGNITE-17063 > URL: https://issues.apache.org/jira/browse/IGNITE-17063 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.11 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Trivial > Labels: .NET > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > We rely on "readlink -f /usr/bin/java" to locate the JVM on Linux. > However, in some cases "readlink" is not in PATH and this fails. > # Try full path "/usr/bin/readlink" as well as short path > # Capture stderr when running commands -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17115) Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager
[
https://issues.apache.org/jira/browse/IGNITE-17115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17115:
-
Description:
During SchemaManager extraction from TableManager to explicit component
latestSchemeVersion() losts its ability to use local configuration property
instead of direct one if IGNITE_GET_METADATA_LOCALLY_ONLY is set to true.
I've just copy-pasted IGNITE_GET_METADATA_LOCALLY_ONLY-aware direct proxy
method from TableManager to SchemaManager
{code:java}
private > T directProxy(T property) {
return getMetadataLocallyOnly ? property :
ConfigurationUtil.directProxy(property);
}{code}
because, on the one hand IGNITE_GET_METADATA_LOCALLY_ONLY is itself temporary
and thus directProxy doesn't worth the effort of moving to some additional
level of abstraction, and on the other hand ConfigurationUtil.directProxy() is
too common place to inline metadataLocallyOnly flag inside.
> Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager
> -
>
> Key: IGNITE-17115
> URL: https://issues.apache.org/jira/browse/IGNITE-17115
> Project: Ignite
> Issue Type: Task
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During SchemaManager extraction from TableManager to explicit component
> latestSchemeVersion() losts its ability to use local configuration property
> instead of direct one if IGNITE_GET_METADATA_LOCALLY_ONLY is set to true.
> I've just copy-pasted IGNITE_GET_METADATA_LOCALLY_ONLY-aware direct proxy
> method from TableManager to SchemaManager
> {code:java}
> private > T directProxy(T property) {
> return getMetadataLocallyOnly ? property :
> ConfigurationUtil.directProxy(property);
> }{code}
> because, on the one hand IGNITE_GET_METADATA_LOCALLY_ONLY is itself temporary
> and thus directProxy doesn't worth the effort of moving to some additional
> level of abstraction, and on the other hand ConfigurationUtil.directProxy()
> is too common place to inline metadataLocallyOnly flag inside.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17063) .NET: Failed to load libjvm.so in some environments
[ https://issues.apache.org/jira/browse/IGNITE-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17063: Release Note: .NET: Improved Java detection on Linux. (was: IGNITE-17063 .NET: Improved Java detection on Linux.) > .NET: Failed to load libjvm.so in some environments > --- > > Key: IGNITE-17063 > URL: https://issues.apache.org/jira/browse/IGNITE-17063 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.11 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Trivial > Labels: .NET > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > We rely on "readlink -f /usr/bin/java" to locate the JVM on Linux. > However, in some cases "readlink" is not in PATH and this fails. > # Try full path "/usr/bin/readlink" as well as short path > # Capture stderr when running commands -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17118) Use CompletableFuture instead of CompletionStage in all public APIs
Pavel Tupitsyn created IGNITE-17118: --- Summary: Use CompletableFuture instead of CompletionStage in all public APIs Key: IGNITE-17118 URL: https://issues.apache.org/jira/browse/IGNITE-17118 Project: Ignite Issue Type: Improvement Affects Versions: 3.0.0-alpha5 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-alpha6 The majority of async public APIs return *CompletableFuture*, however there are some occurrences of *CompletionStage* too. As discussed on the [dev list|https://lists.apache.org/thread/tx15hpbddnq4tfkwyvjlgfyvnbb7xzwx], we should use *CompletableFuture*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17119) DiscoveryClientSocketTest.sslSocketTest fails regularly on TC and locally
Roman Puchkovskiy created IGNITE-17119: -- Summary: DiscoveryClientSocketTest.sslSocketTest fails regularly on TC and locally Key: IGNITE-17119 URL: https://issues.apache.org/jira/browse/IGNITE-17119 Project: Ignite Issue Type: Bug Components: networking Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 2.14 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1051723478826841368&tab=testDetails -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17120) Move ignite-yarn to the Ignite Extensions project
Maxim Muzafarov created IGNITE-17120: Summary: Move ignite-yarn to the Ignite Extensions project Key: IGNITE-17120 URL: https://issues.apache.org/jira/browse/IGNITE-17120 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.14 Move ignite-yarn to the Ignite Extensions project. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17053) Incorrect configuration of spring-data example
[
https://issues.apache.org/jira/browse/IGNITE-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-17053:
---
Labels: ise newbie (was: newbie)
> Incorrect configuration of spring-data example
> --
>
> Key: IGNITE-17053
> URL: https://issues.apache.org/jira/browse/IGNITE-17053
> Project: Ignite
> Issue Type: Bug
> Components: springdata
>Reporter: Ilya Shishkov
>Priority: Minor
> Labels: ise, newbie
> Attachments: SpringDataExamples.patch
>
>
> After removing of spring-data-2.2-ext, {{SpringDataExample}} will fail to
> start because of incorrect path to XML-configuration [1], and incorrect FQDN
> of Person class in XML-configuration [2].
> Fix is simple (see, [^SpringDataExamples.patch]) but it would be perfect to
> add tests for examples similarly to tests of examples in Ignite.
> *Links:*
> #
> [https://github.com/apache/ignite-extensions/blob/master/modules/spring-data-ext/examples/src/main/java/org/apache/ignite/springdata/examples/SpringApplicationConfiguration.java#L51]
> #
> [https://github.com/apache/ignite-extensions/blob/master/modules/spring-data-ext/examples/config/example-spring-data.xml#L57]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17121) Expand sql WITH syntax with abitliy of resetting specific values to deault
Alexander Lapin created IGNITE-17121: Summary: Expand sql WITH syntax with abitliy of resetting specific values to deault Key: IGNITE-17121 URL: https://issues.apache.org/jira/browse/IGNITE-17121 Project: Ignite Issue Type: Task Reporter: Alexander Lapin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17121) Expand sql WITH syntax with abitliy of resetting specific values to deault
[ https://issues.apache.org/jira/browse/IGNITE-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-17121: - Labels: ignite-3 (was: ) > Expand sql WITH syntax with abitliy of resetting specific values to deault > -- > > Key: IGNITE-17121 > URL: https://issues.apache.org/jira/browse/IGNITE-17121 > Project: Ignite > Issue Type: Task >Reporter: Alexander Lapin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17121) Expand sql WITH syntax with abitliy of resetting specific values to deault
[
https://issues.apache.org/jira/browse/IGNITE-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17121:
-
Description:
Let's say there's a table created with
{code:java}
CREATE TABLE t ... WITH A=X, B=Y;{code}
It's suggested to introduce predefined DEFAULT key word as a specific
with-property value in order to reset such property to default. PostgeSQL use
same [approach|https://www.postgresql.org/docs/current/sql-altersystem.html]
So in order to reset B in example above following should be used:
{code:java}
ALTER TABLE t WITH B=DEFAULT;{code}
> Expand sql WITH syntax with abitliy of resetting specific values to deault
> --
>
> Key: IGNITE-17121
> URL: https://issues.apache.org/jira/browse/IGNITE-17121
> Project: Ignite
> Issue Type: Task
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
>
> Let's say there's a table created with
> {code:java}
> CREATE TABLE t ... WITH A=X, B=Y;{code}
> It's suggested to introduce predefined DEFAULT key word as a specific
> with-property value in order to reset such property to default. PostgeSQL use
> same [approach|https://www.postgresql.org/docs/current/sql-altersystem.html]
> So in order to reset B in example above following should be used:
> {code:java}
> ALTER TABLE t WITH B=DEFAULT;{code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17122) Failed to release WAL segments even after reaching DataStorageConfiguration#maxWalArchiveSize
Marcus Lo created IGNITE-17122: -- Summary: Failed to release WAL segments even after reaching DataStorageConfiguration#maxWalArchiveSize Key: IGNITE-17122 URL: https://issues.apache.org/jira/browse/IGNITE-17122 Project: Ignite Issue Type: Bug Components: persistence Affects Versions: 2.13 Reporter: Marcus Lo Attachments: 1654590690_34713_920D9DE6-1C3F-4E8B-8181-446CB340ACF3.txt When maxWalArchiveSize is reached, Ignite is able to detect that and tries to release WAL segments (and prints out "maximum size of the WAL archive exceeded, the segments will be forcibly released"). However the WAL archive deletion doesn't happens immediately, and sometimes it happens almost 1 hour after the first detection, and the actual WAL archive size is much larger than the maxWalArchiveSize. See the (trimmed) attached log for an example. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[ https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-16038: --- Assignee: Pavel Tupitsyn > Java Thin Client: Retrieve binary configuration from server > --- > > Key: IGNITE-16038 > URL: https://issues.apache.org/jira/browse/IGNITE-16038 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.11 >Reporter: Alexandr Shapkin >Assignee: Pavel Tupitsyn >Priority: Major > > Thin clients require manual binary configuration currently. Settings like > compact footer and simple/full name mapper should be set to match the cluster > settings. Extend the protocol to retrieve those settings automatically on > start. > > I.e. it's impossible to read a value inserted by a thick client with java > thin client without specifying compactFooter=true -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17055) Ignite JDBC Driver don't support contract
[
https://issues.apache.org/jira/browse/IGNITE-17055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin resolved IGNITE-17055.
Resolution: Duplicate
https://issues.apache.org/jira/browse/IGNITE-16971
> Ignite JDBC Driver don't support contract
> --
>
> Key: IGNITE-17055
> URL: https://issues.apache.org/jira/browse/IGNITE-17055
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Pochatkin
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3, jdbc
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently in org.apache.ignite.internal.jdbc.JdbcStatement#execute0 exist
> async call to org.apache.ignite.internal.jdbc.proto.JdbcQueryEventHandler
>
> {code:java}
> protected void execute0(JdbcStatementType stmtType, String sql, List
> args) throws SQLException {
> ...
>
> res = conn.handler().queryAsync(req).join();
>
> ...
> } {code}
> Main problem with this part of code is that in case when the handler cannot
> parse SQL qeury will throw
> {code:java}
> java.util.concurrent.CompletionException: class
> org.apache.ignite.client.IgniteClientException: Failed to parse query{code}
> without any catching. This is doesn't match with Jdbc contract in the
> section of possible exeptions and looks like unpredictable behavior.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (IGNITE-16976) Replace ignite-cli with a new one
[ https://issues.apache.org/jira/browse/IGNITE-16976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-16976. Resolution: Won't Fix Done in https://issues.apache.org/jira/browse/IGNITE-16971 > Replace ignite-cli with a new one > - > > Key: IGNITE-16976 > URL: https://issues.apache.org/jira/browse/IGNITE-16976 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3 > > Drop existing ignite-cli module. > Change the documentation (installation process and commands description). > Provide the developer documentation (readme.md), so ignite developer can > understand how to add new commands and how to install the tool locally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-16972) Implement CLI default config
[ https://issues.apache.org/jira/browse/IGNITE-16972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-16972. Resolution: Won't Fix Done in https://issues.apache.org/jira/browse/IGNITE-16971 > Implement CLI default config > > > Key: IGNITE-16972 > URL: https://issues.apache.org/jira/browse/IGNITE-16972 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > The default config is the property file with configured defaults for Ignite > CLI parameters. List of parameters: > * ignite.cluster-url > * ignite.jdbc-url > * etc > Also, configs could be configured with defaults set/get command. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-15550) Calcite engine. Support collections constuction from the query
[
https://issues.apache.org/jira/browse/IGNITE-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550901#comment-17550901
]
Ignite TC Bot commented on IGNITE-15550:
{panel:title=Branch: [pull/10059/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2 (lazy=true){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6612847]]
* IgniteBinaryCacheQueryLazyTestSuite2:
DynamicIndexReplicatedAtomicConcurrentSelfTest.testQueryConsistencyMultithreaded
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10059/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6613155]]
* {color:#013220}IgniteCalciteTestSuite: map.test - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: array.test - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: array_agg.test - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: array_agg.test_slow - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6612851&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Support collections constuction from the query
> --
>
> Key: IGNITE-15550
> URL: https://issues.apache.org/jira/browse/IGNITE-15550
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Daschinsky
>Priority: Minor
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, queries like:
>
> {noformat}
> SELECT MAP(SELECT 'a', 1)
> SELECT ARRAY(SELECT 1){noformat}
> Can't be executed, since logical plan contains \{{Collect}} relational
> operator and there is no rule and no physical operator to convert this
> logical operator.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15550) Calcite engine. Support collections constuction from the query
[
https://issues.apache.org/jira/browse/IGNITE-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-15550:
-
Fix Version/s: 2.14
> Calcite engine. Support collections constuction from the query
> --
>
> Key: IGNITE-15550
> URL: https://issues.apache.org/jira/browse/IGNITE-15550
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Daschinsky
>Priority: Minor
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
> Fix For: 2.14
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently, queries like:
>
> {noformat}
> SELECT MAP(SELECT 'a', 1)
> SELECT ARRAY(SELECT 1){noformat}
> Can't be executed, since logical plan contains \{{Collect}} relational
> operator and there is no rule and no physical operator to convert this
> logical operator.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15550) Calcite engine. Support collections constuction from the query
[
https://issues.apache.org/jira/browse/IGNITE-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-15550:
-
Release Note: SQL Calcite: implemented ARRAY, ARRAY_AGG, ARRAY_CONCAT_AGG
and MAP support
> Calcite engine. Support collections constuction from the query
> --
>
> Key: IGNITE-15550
> URL: https://issues.apache.org/jira/browse/IGNITE-15550
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Daschinsky
>Priority: Minor
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
> Fix For: 2.14
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently, queries like:
>
> {noformat}
> SELECT MAP(SELECT 'a', 1)
> SELECT ARRAY(SELECT 1){noformat}
> Can't be executed, since logical plan contains \{{Collect}} relational
> operator and there is no rule and no physical operator to convert this
> logical operator.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17115) Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager
[
https://issues.apache.org/jira/browse/IGNITE-17115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550904#comment-17550904
]
Denis Chudov commented on IGNITE-17115:
---
[~alapin] LGTM.
> Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager
> -
>
> Key: IGNITE-17115
> URL: https://issues.apache.org/jira/browse/IGNITE-17115
> Project: Ignite
> Issue Type: Task
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During SchemaManager extraction from TableManager to explicit component
> latestSchemeVersion() losts its ability to use local configuration property
> instead of direct one if IGNITE_GET_METADATA_LOCALLY_ONLY is set to true.
> I've just copy-pasted IGNITE_GET_METADATA_LOCALLY_ONLY-aware direct proxy
> method from TableManager to SchemaManager
> {code:java}
> private > T directProxy(T property) {
> return getMetadataLocallyOnly ? property :
> ConfigurationUtil.directProxy(property);
> }{code}
> because, on the one hand IGNITE_GET_METADATA_LOCALLY_ONLY is itself temporary
> and thus directProxy doesn't worth the effort of moving to some additional
> level of abstraction, and on the other hand ConfigurationUtil.directProxy()
> is too common place to inline metadataLocallyOnly flag inside.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-17053) Incorrect configuration of spring-data example
[
https://issues.apache.org/jira/browse/IGNITE-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov reassigned IGNITE-17053:
--
Assignee: Ilya Shishkov
> Incorrect configuration of spring-data example
> --
>
> Key: IGNITE-17053
> URL: https://issues.apache.org/jira/browse/IGNITE-17053
> Project: Ignite
> Issue Type: Bug
> Components: springdata
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise, newbie
> Attachments: SpringDataExamples.patch
>
>
> After removing of spring-data-2.2-ext, {{SpringDataExample}} will fail to
> start because of incorrect path to XML-configuration [1], and incorrect FQDN
> of Person class in XML-configuration [2].
> Fix is simple (see, [^SpringDataExamples.patch]) but it would be perfect to
> add tests for examples similarly to tests of examples in Ignite.
> *Links:*
> #
> [https://github.com/apache/ignite-extensions/blob/master/modules/spring-data-ext/examples/src/main/java/org/apache/ignite/springdata/examples/SpringApplicationConfiguration.java#L51]
> #
> [https://github.com/apache/ignite-extensions/blob/master/modules/spring-data-ext/examples/config/example-spring-data.xml#L57]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17123) Fix partition counter reservation.
Andrey Mashenkov created IGNITE-17123: - Summary: Fix partition counter reservation. Key: IGNITE-17123 URL: https://issues.apache.org/jira/browse/IGNITE-17123 Project: Ignite Issue Type: Bug Components: cache Reporter: Andrey Mashenkov Transaction reserves partition counters on primary. On the backup side, TxEntries must be commited with counters from the reserved range. However, a range of update counters, which were reserved on primary, is NOT validated on backup. Thus means NOOP invoke operation may cause partition counter difference on the primary and backup nodes. 1. Let's pass NOOP result of invoke operation to the backup and avoid incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote node (for the WAL purposes) instead of allocate+iterate over new collection (GridDistributedTxRemoteAdapter.commitIfLocked). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17124) Storage API tests can't be used for storages with specific binary format
Timur Magomedov created IGNITE-17124: Summary: Storage API tests can't be used for storages with specific binary format Key: IGNITE-17124 URL: https://issues.apache.org/jira/browse/IGNITE-17124 Project: Ignite Issue Type: Improvement Reporter: Timur Magomedov Assignee: Timur Magomedov Storages that need to get table UUID or rely on some specific binary format of DataRow can't be tested using AbstractPartitionStorageTest. This works for key-value storages that don't decode key and value of DataRow/SearchRow and don't use table UUID but will fail once such storages are implemented or existing ones will decode data binaries. Two main issues here are the following: 1. searchRow() and dataRow() methods in AbstractPartitionStorageTest can't be overridden since they are static methods. 2. Table UUID is always null in Storage API tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17123) Fix partition counter reservation.
[ https://issues.apache.org/jira/browse/IGNITE-17123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-17123: - Assignee: Andrey Mashenkov > Fix partition counter reservation. > -- > > Key: IGNITE-17123 > URL: https://issues.apache.org/jira/browse/IGNITE-17123 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > > Transaction reserves partition counters on primary. > On the backup side, TxEntries must be commited with counters from the > reserved range. > However, a range of update counters, which were reserved on primary, is NOT > validated on backup. Thus means NOOP invoke operation may cause partition > counter difference on the primary and backup nodes. > 1. Let's pass NOOP result of invoke operation to the backup and avoid > incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). > 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote > node (for the WAL purposes) instead of allocate+iterate over > new collection (GridDistributedTxRemoteAdapter.commitIfLocked). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17043) Performance degradation in Marshaller
[
https://issues.apache.org/jira/browse/IGNITE-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550909#comment-17550909
]
Sergey Kosarev commented on IGNITE-17043:
-
[~sdanilov], thank you for contribution!
> Performance degradation in Marshaller
> -
>
> Key: IGNITE-17043
> URL: https://issues.apache.org/jira/browse/IGNITE-17043
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.13, 2.14
>Reporter: Sergey Kosarev
>Assignee: Semyon Danilov
>Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> There is a problem in ignite-core code in GridHandleTable used inside
> OptimizedMarshaller where the internal buffers grow in size and does not
> shrink back.
> What problematic is in GridHandleTable? This is its reset() method that fills
> arrays in memory. Done once, it's not a big deal. Done a million times for a
> long buffer, it becomes really long and CPU-consuming.
> Here is simple reproducer (omitting imports for brevity):
> Marshalling of the same object at first takes about 50ms, and then after
> degradation more than 100 seconds.
> {code:title=DegradationReproducer.java|borderStyle=solid}
> public class DegradationReproducer extends BinaryMarshallerSelfTest {
> @Test
> public void reproduce() throws Exception {
> List> obj = IntStream.range(0,
> 10).mapToObj(Collections::singletonList).collect(Collectors.toList());
> for (int i = 0; i < 50; i++) {
> Assert.assertThat(measureMarshal(obj), Matchers.lessThan(1000L));
> }
> binaryMarshaller().marshal(
> Collections.singletonList(IntStream.range(0,
> 1000_000).mapToObj(String::valueOf).collect(Collectors.toList()))
> );
> Assert.assertThat(measureMarshal(obj), Matchers.lessThan(1000L));
> }
> private long measureMarshal(List> obj) throws
> IgniteCheckedException {
> info("marshalling started ");
> long millis = System.currentTimeMillis();
> binaryMarshaller().marshal(obj);
> millis = System.currentTimeMillis() - millis;
> info("marshalling finished in " + millis + " ms");
> return millis;
> }
> }
> {code}
> on my machine reslust is:
> {quote}
> .
> [2022-05-26 20:58:27,178][INFO
> ][test-runner-#1%binary.DegradationReproducer%][root] marshalling finished in
> 39 ms
> [2022-05-26 20:58:27,769][INFO
> ][test-runner-#1%binary.DegradationReproducer%][root] marshalling started
> [2022-05-26 21:02:03,588][INFO
> ][test-runner-#1%binary.DegradationReproducer%][root] marshalling finished in
> 215819 ms
> [2022-05-26 21:02:03,593][ERROR][main][root] Test failed
> [test=DegradationReproducer#reproduce[useBinaryArrays = true],
> duration=218641]
> java.lang.AssertionError:
> Expected: a value less than <1000L>
> but: <*215819L*> was greater than <1000L>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at
> org.apache.ignite.internal.binary.DegradationReproducer.reproduce(DegradationReproducer.java:27)
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17123) Fix partition counter reservation on backup.
[ https://issues.apache.org/jira/browse/IGNITE-17123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-17123: -- Summary: Fix partition counter reservation on backup. (was: Fix partition counter reservation.) > Fix partition counter reservation on backup. > > > Key: IGNITE-17123 > URL: https://issues.apache.org/jira/browse/IGNITE-17123 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > > Transaction reserves partition counters on primary. > On the backup side, TxEntries must be commited with counters from the > reserved range. > However, a range of update counters, which were reserved on primary, is NOT > validated on backup. Thus means NOOP invoke operation may cause partition > counter difference on the primary and backup nodes. > 1. Let's pass NOOP result of invoke operation to the backup and avoid > incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). > 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote > node (for the WAL purposes) instead of allocate+iterate over > new collection (GridDistributedTxRemoteAdapter.commitIfLocked). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17105) Maven unused dependencies check false positive
[ https://issues.apache.org/jira/browse/IGNITE-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev reassigned IGNITE-17105: - Assignee: Vadim Pakhnushev > Maven unused dependencies check false positive > -- > > Key: IGNITE-17105 > URL: https://issues.apache.org/jira/browse/IGNITE-17105 > Project: Ignite > Issue Type: Bug >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > CheckUnusedDependenciesAndPluginsInParent.sh greps dependencies without whole > words only switch, so for example unused dependency "jline" is falsely found > to be used in "picocli-shell-jline3" -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17105) Maven unused dependencies check false positive
[ https://issues.apache.org/jira/browse/IGNITE-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev updated IGNITE-17105: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Maven unused dependencies check false positive > -- > > Key: IGNITE-17105 > URL: https://issues.apache.org/jira/browse/IGNITE-17105 > Project: Ignite > Issue Type: Bug >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > CheckUnusedDependenciesAndPluginsInParent.sh greps dependencies without whole > words only switch, so for example unused dependency "jline" is falsely found > to be used in "picocli-shell-jline3" -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17105) Maven unused dependencies check false positive
[ https://issues.apache.org/jira/browse/IGNITE-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev updated IGNITE-17105: -- Ignite Flags: (was: Release Notes Required) > Maven unused dependencies check false positive > -- > > Key: IGNITE-17105 > URL: https://issues.apache.org/jira/browse/IGNITE-17105 > Project: Ignite > Issue Type: Bug >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > CheckUnusedDependenciesAndPluginsInParent.sh greps dependencies without whole > words only switch, so for example unused dependency "jline" is falsely found > to be used in "picocli-shell-jline3" -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17123) Fix update counter assignment on backup nodes.
[ https://issues.apache.org/jira/browse/IGNITE-17123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-17123: -- Summary: Fix update counter assignment on backup nodes. (was: Fix partition counter reservation on backup.) > Fix update counter assignment on backup nodes. > -- > > Key: IGNITE-17123 > URL: https://issues.apache.org/jira/browse/IGNITE-17123 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > > Transaction reserves partition counters on primary. > On the backup side, TxEntries must be commited with counters from the > reserved range. > However, a range of update counters, which were reserved on primary, is NOT > validated on backup. Thus means NOOP invoke operation may cause partition > counter difference on the primary and backup nodes. > 1. Let's pass NOOP result of invoke operation to the backup and avoid > incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). > 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote > node (for the WAL purposes) instead of allocate+iterate over > new collection (GridDistributedTxRemoteAdapter.commitIfLocked). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17123) Fix update counter assignment on backup nodes.
[ https://issues.apache.org/jira/browse/IGNITE-17123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-17123: -- Description: Transaction reserves partition counters on primary. On the backup side, TxEntries must be commited with counters from the reserved range. However, a range of update counters, which were reserved on primary, is NOT validated on backup. Thus means NOOP invoke operation may cause partition counter difference on the primary and backup nodes. 1. Let's pass NOOP result of invoke operation to the backup and avoid incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote node (for the WAL purposes) instead of allocating+iterating over a new collection (see GridDistributedTxRemoteAdapter.commitIfLocked). was: Transaction reserves partition counters on primary. On the backup side, TxEntries must be commited with counters from the reserved range. However, a range of update counters, which were reserved on primary, is NOT validated on backup. Thus means NOOP invoke operation may cause partition counter difference on the primary and backup nodes. 1. Let's pass NOOP result of invoke operation to the backup and avoid incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote node (for the WAL purposes) instead of allocate+iterate over new collection (GridDistributedTxRemoteAdapter.commitIfLocked). > Fix update counter assignment on backup nodes. > -- > > Key: IGNITE-17123 > URL: https://issues.apache.org/jira/browse/IGNITE-17123 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Transaction reserves partition counters on primary. > On the backup side, TxEntries must be commited with counters from the > reserved range. > However, a range of update counters, which were reserved on primary, is NOT > validated on backup. Thus means NOOP invoke operation may cause partition > counter difference on the primary and backup nodes. > 1. Let's pass NOOP result of invoke operation to the backup and avoid > incorrect partition counter change on backup nodes (see DhtTxPrepareFuture). > 2. Update counter can be assigned to TxEntry instantly on tx commit on Remote > node (for the WAL purposes) instead of allocating+iterating over a new > collection (see GridDistributedTxRemoteAdapter.commitIfLocked). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17125) Advanced completion for option values
Mikhail Pochatkin created IGNITE-17125: -- Summary: Advanced completion for option values Key: IGNITE-17125 URL: https://issues.apache.org/jira/browse/IGNITE-17125 Project: Ignite Issue Type: Improvement Reporter: Mikhail Pochatkin Currently cli completer has possibility to complete only commands names and options. It would be helpful and user friendly to add possibility to complete options value. To more understandable, currently cli has command "config show --selector 'key'", where key is property name in ignite configuration. This is possible to complete this key by "cached representation" of Ignite configuration. The solution should be customazable to use it in all commands which require option value completion. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-15620) Calcite. Support for ARRAY_AGG function.
[
https://issues.apache.org/jira/browse/IGNITE-15620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky resolved IGNITE-15620.
--
Fix Version/s: 2.14
Resolution: Fixed
> Calcite. Support for ARRAY_AGG function.
>
>
> Key: IGNITE-15620
> URL: https://issues.apache.org/jira/browse/IGNITE-15620
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
> Fix For: 2.14
>
>
> This function already implemented in
> [CALCITE-4335|https://issues.apache.org/jira/browse/CALCITE-4335]. Need
> support it locally.
> Affected tests:
> {{src/test/sql/types/list/array_agg.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17113) Document distributed computing in AI alpha 5
[ https://issues.apache.org/jira/browse/IGNITE-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550933#comment-17550933 ] Pavel Tupitsyn commented on IGNITE-17113: - [~igusev] looks good to me. > Document distributed computing in AI alpha 5 > > > Key: IGNITE-17113 > URL: https://issues.apache.org/jira/browse/IGNITE-17113 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17073) Document new CLI commands
[ https://issues.apache.org/jira/browse/IGNITE-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17073: Fix Version/s: 3.0.0-alpha5 > Document new CLI commands > -- > > Key: IGNITE-17073 > URL: https://issues.apache.org/jira/browse/IGNITE-17073 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksandr >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 20m > Remaining Estimate: 0h > > Document commands that are introdused in > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17126) Update README.md to reflect changes in CLI
Aleksandr created IGNITE-17126:
--
Summary: Update README.md to reflect changes in CLI
Key: IGNITE-17126
URL: https://issues.apache.org/jira/browse/IGNITE-17126
Project: Ignite
Issue Type: Task
Reporter: Aleksandr
Fix For: 3.0.0-alpha5
It still says alpha3 inside and {{ignite init }}was changed to {{ignite
bootstrap }}in current version. I would suggest to also add a few steps on
{{node start }}and {{cluster init }}with a few examples.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17098) Create documentation for pluggable storage engines
[ https://issues.apache.org/jira/browse/IGNITE-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17098: Fix Version/s: 3.0.0-alpha5 > Create documentation for pluggable storage engines > -- > > Key: IGNITE-17098 > URL: https://issues.apache.org/jira/browse/IGNITE-17098 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr Polovtcev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1h > Remaining Estimate: 0h > > We need to document the following aspects regarding the pluggable storage > engines feature: > 1. SQL API for defining a storage engine for a table. > 2. Configuration of data regions using Ignite CLI. > 3. Configuration of the default engine using Ignite CLU. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17113) Document distributed computing in AI alpha 5
[ https://issues.apache.org/jira/browse/IGNITE-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17113: Fix Version/s: 3.0.0-alpha5 > Document distributed computing in AI alpha 5 > > > Key: IGNITE-17113 > URL: https://issues.apache.org/jira/browse/IGNITE-17113 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17126) Update README.md to reflect changes in CLI
[
https://issues.apache.org/jira/browse/IGNITE-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17126:
---
Description: It still says alpha3 inside and \{{ignite init }} was changed
to \{{ignite bootstrap }} in current version. I would suggest to also add a few
steps on \{{node start }} and \{{cluster init }} with a few examples. (was: It
still says alpha3 inside and {{ignite init }}was changed to {{ignite bootstrap
}}in current version. I would suggest to also add a few steps on {{node start
}}and {{cluster init }}with a few examples.)
> Update README.md to reflect changes in CLI
> --
>
> Key: IGNITE-17126
> URL: https://issues.apache.org/jira/browse/IGNITE-17126
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Critical
> Labels: ignite-3-cli-tool
> Fix For: 3.0.0-alpha5
>
>
> It still says alpha3 inside and \{{ignite init }} was changed to \{{ignite
> bootstrap }} in current version. I would suggest to also add a few steps on
> \{{node start }} and \{{cluster init }} with a few examples.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-16038) Java Thin Client: Retrieve binary configuration from server
[ https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550953#comment-17550953 ] Pavel Tupitsyn commented on IGNITE-16038: - [~alex_pl] [~ashapkin] I propose to do the following: * Apply server-side binary configuration by default. * Add *ClientConfiguration#autoBinaryConfigurationEnabled*, default *true* - as a way to fall back to the old behavior when required. * List this as a potentially breaking change in the release notes. Here is a draft PR: https://github.com/apache/ignite/pull/10076 Please have a look and let me know your thoughts. If there are no objections, I'll finalize the changes next week. > Java Thin Client: Retrieve binary configuration from server > --- > > Key: IGNITE-16038 > URL: https://issues.apache.org/jira/browse/IGNITE-16038 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.11 >Reporter: Alexandr Shapkin >Assignee: Pavel Tupitsyn >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Thin clients require manual binary configuration currently. Settings like > compact footer and simple/full name mapper should be set to match the cluster > settings. Extend the protocol to retrieve those settings automatically on > start. > > I.e. it's impossible to read a value inserted by a thick client with java > thin client without specifying compactFooter=true -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17115) Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager
[
https://issues.apache.org/jira/browse/IGNITE-17115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17115:
-
Fix Version/s: 3.0.0-alpha6
> Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager
> -
>
> Key: IGNITE-17115
> URL: https://issues.apache.org/jira/browse/IGNITE-17115
> Project: Ignite
> Issue Type: Task
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During SchemaManager extraction from TableManager to explicit component
> latestSchemeVersion() losts its ability to use local configuration property
> instead of direct one if IGNITE_GET_METADATA_LOCALLY_ONLY is set to true.
> I've just copy-pasted IGNITE_GET_METADATA_LOCALLY_ONLY-aware direct proxy
> method from TableManager to SchemaManager
> {code:java}
> private > T directProxy(T property) {
> return getMetadataLocallyOnly ? property :
> ConfigurationUtil.directProxy(property);
> }{code}
> because, on the one hand IGNITE_GET_METADATA_LOCALLY_ONLY is itself temporary
> and thus directProxy doesn't worth the effort of moving to some additional
> level of abstraction, and on the other hand ConfigurationUtil.directProxy()
> is too common place to inline metadataLocallyOnly flag inside.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17120) Move ignite-yarn to the Ignite Extensions project
[ https://issues.apache.org/jira/browse/IGNITE-17120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550954#comment-17550954 ] Maxim Muzafarov commented on IGNITE-17120: -- Yarn Tests suite created: https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Yarn&branch_IgniteExtensions_Tests=%3Cdefault%3E&tab=buildTypeStatusDiv > Move ignite-yarn to the Ignite Extensions project > - > > Key: IGNITE-17120 > URL: https://issues.apache.org/jira/browse/IGNITE-17120 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Move ignite-yarn to the Ignite Extensions project. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17126) Update README.md to reflect changes in CLI
[
https://issues.apache.org/jira/browse/IGNITE-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17126:
---
Description:
It still says alpha3 inside and `ignite init` was changed to `ignite bootstrap`
in the current version. I would suggest also adding a few steps on `node start`
and `cluster init` with a few examples.
All examples in the `examples` folder have to be adjusted too.
was:It still says alpha3 inside and \{{ignite init }} was changed to
\{{ignite bootstrap }} in current version. I would suggest to also add a few
steps on \{{node start }} and \{{cluster init }} with a few examples.
> Update README.md to reflect changes in CLI
> --
>
> Key: IGNITE-17126
> URL: https://issues.apache.org/jira/browse/IGNITE-17126
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Critical
> Labels: ignite-3-cli-tool
> Fix For: 3.0.0-alpha5
>
>
> It still says alpha3 inside and `ignite init` was changed to `ignite
> bootstrap` in the current version. I would suggest also adding a few steps on
> `node start` and `cluster init` with a few examples.
> All examples in the `examples` folder have to be adjusted too.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17073) Document new CLI commands
[ https://issues.apache.org/jira/browse/IGNITE-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550958#comment-17550958 ] Andrey N. Gura commented on IGNITE-17073: - [~igusev] [~igusev] Please, notice, that checks are failed. > Document new CLI commands > -- > > Key: IGNITE-17073 > URL: https://issues.apache.org/jira/browse/IGNITE-17073 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksandr >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 20m > Remaining Estimate: 0h > > Document commands that are introdused in > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17105) Maven unused dependencies check false positive
[ https://issues.apache.org/jira/browse/IGNITE-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17105: - Labels: ignite-3 (was: ) > Maven unused dependencies check false positive > -- > > Key: IGNITE-17105 > URL: https://issues.apache.org/jira/browse/IGNITE-17105 > Project: Ignite > Issue Type: Bug >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Minor > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > CheckUnusedDependenciesAndPluginsInParent.sh greps dependencies without whole > words only switch, so for example unused dependency "jline" is falsely found > to be used in "picocli-shell-jline3" -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17109) Error handling for invalid url passed to any command
[
https://issues.apache.org/jira/browse/IGNITE-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-17109:
-
Labels: ignite-3 (was: )
> Error handling for invalid url passed to any command
>
>
> Key: IGNITE-17109
> URL: https://issues.apache.org/jira/browse/IGNITE-17109
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3
>
> h2. Description
> Different commands given the wrong URL display different messages. For example
>
> {code:java}
> disconnected]> connect lkhjasdflkjhhasdf
> 2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled
> exception
> java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but
> no colon was found
> at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
> at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
> at okhttp3.Request$Builder.url(Request.kt:184)
> ...
> Internal error! {code}
>
> {code:java}
> [disconnected]> connect http://kjhasdflkjhhasdf:10300/
> Api error: null
> {code}
>
> {code:java}
> [disconnected]> sql -u=hdbkljghhgasdflkjhasdf
> Connection failed. {code}
> h2. To-Do
> * Test all possible variations of incorrect URLs with integration/interface
> tests
> * Define a single error handler for the wrong URL, port, etc.
> As a result, all variations of wrong data passed should be handled on a
> consistent way. The user has to see the same messages for the same mistakes
> regardless of the command is used.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17110) Auto-connect on the REPL start
[
https://issues.apache.org/jira/browse/IGNITE-17110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-17110:
-
Labels: ignite-3 ignite-3-cli-tool (was: ignite-3-cli-tool)
> Auto-connect on the REPL start
> --
>
> Key: IGNITE-17110
> URL: https://issues.apache.org/jira/browse/IGNITE-17110
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> h2. Description
> When a user starts REPL by the {{ignite}} command they get
> {{{}[disconnected]{}}}> prompt by default. Even if the user already connected
> to the cluster node in the previous session.
> h2. To-Do
> Implement the auto-connect logic for the case described below. The URL for
> the connect command can be taken from the defaults. If the user previously
> connected to the URL that differs from the default one then suggest using the
> last URL as a default.
> {code:bash}
> $ ignite
> > connect to http://host.from.previous.session:10300 ? # this is asked only
> > if the default url is not possible to connect
> > yes
> [http://host.from.previous.session:10300]> would you like to use
> http://host.from.previous.session:10300 as the default URL?
> [http://host.from.previous.session:10300]> no
> [http://host.from.previous.session:10300]> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17116) Add architecture documentation for CLI module.
[ https://issues.apache.org/jira/browse/IGNITE-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17116: - Labels: ignite-3 (was: ) > Add architecture documentation for CLI module. > -- > > Key: IGNITE-17116 > URL: https://issues.apache.org/jira/browse/IGNITE-17116 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3 > > A developer should read the documentation and: > * how to create an executable command > * how to test an executable command (unit and integration) > * how to create an interactive command > * how to test an interactive command > Also, the ExecutionPepiline concept and the extention mechanismshould be > described. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17126) Update README.md to reflect changes in CLI
[ https://issues.apache.org/jira/browse/IGNITE-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17126: - Labels: ignite-3 ignite-3-cli-tool (was: ignite-3-cli-tool) > Update README.md to reflect changes in CLI > -- > > Key: IGNITE-17126 > URL: https://issues.apache.org/jira/browse/IGNITE-17126 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > > It still says alpha3 inside and `ignite init` was changed to `ignite > bootstrap` in the current version. I would suggest also adding a few steps on > `node start` and `cluster init` with a few examples. > All examples in the `examples` folder have to be adjusted too. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17125) Advanced completion for option values
[ https://issues.apache.org/jira/browse/IGNITE-17125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17125: - Labels: ignite-3 ignite-3-cli-tool (was: ignite-3-cli-tool) > Advanced completion for option values > - > > Key: IGNITE-17125 > URL: https://issues.apache.org/jira/browse/IGNITE-17125 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Currently cli completer has possibility to complete only commands names and > options. It would be helpful and user friendly to add possibility to complete > options value. To more understandable, currently cli has command "config show > --selector 'key'", where key is property name in ignite configuration. This > is possible to complete this key by "cached representation" of Ignite > configuration. > The solution should be customazable to use it in all commands which require > option value completion. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17098) Create documentation for pluggable storage engines
[ https://issues.apache.org/jira/browse/IGNITE-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550973#comment-17550973 ] Yury Gerzhedovich commented on IGNITE-17098: [~igusev] , LGTM > Create documentation for pluggable storage engines > -- > > Key: IGNITE-17098 > URL: https://issues.apache.org/jira/browse/IGNITE-17098 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr Polovtcev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1h > Remaining Estimate: 0h > > We need to document the following aspects regarding the pluggable storage > engines feature: > 1. SQL API for defining a storage engine for a table. > 2. Configuration of data regions using Ignite CLI. > 3. Configuration of the default engine using Ignite CLU. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17121) Expand sql WITH syntax with abitliy of resetting specific values to deault
[
https://issues.apache.org/jira/browse/IGNITE-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-17121:
---
Component/s: sql
> Expand sql WITH syntax with abitliy of resetting specific values to deault
> --
>
> Key: IGNITE-17121
> URL: https://issues.apache.org/jira/browse/IGNITE-17121
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
>
> Let's say there's a table created with
> {code:java}
> CREATE TABLE t ... WITH A=X, B=Y;{code}
> It's suggested to introduce predefined DEFAULT key word as a specific
> with-property value in order to reset such property to default. PostgeSQL use
> same [approach|https://www.postgresql.org/docs/current/sql-altersystem.html]
> So in order to reset B in example above following should be used:
> {code:java}
> ALTER TABLE t WITH B=DEFAULT;{code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17088) SQL API: Add examples.
[ https://issues.apache.org/jira/browse/IGNITE-17088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550974#comment-17550974 ] Yury Gerzhedovich commented on IGNITE-17088: [~amashenkov] , LGTM. Please cherypick it to alpha 5 branch after merge to main one. > SQL API: Add examples. > -- > > Key: IGNITE-17088 > URL: https://issues.apache.org/jira/browse/IGNITE-17088 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Add examples of using SQL API. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-17124) Storage API tests can't be used for storages with specific binary format
[ https://issues.apache.org/jira/browse/IGNITE-17124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550975#comment-17550975 ] Timur Magomedov edited comment on IGNITE-17124 at 6/7/22 12:42 PM: --- PR: [https://github.com/apache/ignite-3/pull/861] [~ktkale...@gridgain.com] could you please review the fix? was (Author: JIRAUSER290398): PR: [https://github.com/apache/ignite-3/pull/861] [~ibessonov] could you please review the fix? > Storage API tests can't be used for storages with specific binary format > > > Key: IGNITE-17124 > URL: https://issues.apache.org/jira/browse/IGNITE-17124 > Project: Ignite > Issue Type: Improvement >Reporter: Timur Magomedov >Assignee: Timur Magomedov >Priority: Major > Labels: ignite-3 > > Storages that need to get table UUID or rely on some specific binary format > of DataRow can't be tested using AbstractPartitionStorageTest. This works for > key-value storages that don't decode key and value of DataRow/SearchRow and > don't use table UUID but will fail once such storages are implemented or > existing ones will decode data binaries. > Two main issues here are the following: > 1. searchRow() and dataRow() methods in AbstractPartitionStorageTest can't be > overridden since they are static methods. > 2. Table UUID is always null in Storage API tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16903) Stop redundant raft groups on a node when the node receives update about partition stable assignments
[ https://issues.apache.org/jira/browse/IGNITE-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16903: - Epic Link: IGNITE-14209 > Stop redundant raft groups on a node when the node receives update about > partition stable assignments > - > > Key: IGNITE-16903 > URL: https://issues.apache.org/jira/browse/IGNITE-16903 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > > According to the rebalance algorithm from > https://issues.apache.org/jira/browse/IGNITE-16020, we need to stop redundant > raft groups on a node when the node receives update about partition stable > assignments. More details about the rebalance algorithm can be found in > https://github.com/apache/ignite-3/blob/main/modules/table/tech-notes/rebalance.md > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16109) Add listeners to raft module
[
https://issues.apache.org/jira/browse/IGNITE-16109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16109:
-
Fix Version/s: 3.0.0-alpha5
> Add listeners to raft module
>
>
> Key: IGNITE-16109
> URL: https://issues.apache.org/jira/browse/IGNITE-16109
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> For handle rebalance feature safe and correct we need to add the following
> listeners on the start of new Raft node:
> - {{onLeaderElected()}} - must be executed from the new leader when raft
> group changes the leader.
> - {{onNewPeersConfigurationApplied(peers)}} - must be executed with the list
> of new peers when changePeers has successfully done.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16379) Extend raft configuration changes' listener with onReconfigurationError
[
https://issues.apache.org/jira/browse/IGNITE-16379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16379:
-
Fix Version/s: 3.0.0-alpha5
> Extend raft configuration changes' listener with onReconfigurationError
> ---
>
> Key: IGNITE-16379
> URL: https://issues.apache.org/jira/browse/IGNITE-16379
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to extend raft change configurations listener with
> {{onReconfigurationError(errorContext)}} event.
> It must be invoked on any issues, which will be occurred when
> ChangePeersRequest has already been processed and provide the context of
> error: RaftError and message.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16010) setBaseline method must write new baseline to metastore
[ https://issues.apache.org/jira/browse/IGNITE-16010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16010: - Fix Version/s: 3.0.0-alpha5 > setBaseline method must write new baseline to metastore > --- > > Key: IGNITE-16010 > URL: https://issues.apache.org/jira/browse/IGNITE-16010 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Current org.apache.ignite.Ignite#setBaseline method updates assignments > directly and does not save baseline as a separate source of truth anywhere. > Instead, it should store new baseline configuration to metastore (in future > it can be baseline per table). This metastore key update will be a trigger > for listeners to update appropriate assignments. > This approach provides the generalized way of baseline changing and further > processing of this event by rebalancing the algorithm, for example. > UPD: > It was decided to move baseline to the cluster conguration > > (Phase1) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16801) Implement error handling for rebalance onReconfigurationError callback
[
https://issues.apache.org/jira/browse/IGNITE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16801:
-
Fix Version/s: 3.0.0-alpha5
> Implement error handling for rebalance onReconfigurationError callback
> --
>
> Key: IGNITE-16801
> URL: https://issues.apache.org/jira/browse/IGNITE-16801
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> We have the listener {{onReconfigurationError}} for handling errors during
> the rebalance, but not implementation yet.
> At the moment, it looks like, that we can receive only 1 kind of errors -
> {{RaftError.ECATCHUP}}
> UPD:
> Retry logic of changePeersAsync was implemented.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15554) Add logic for assignment recalculation in case of replicas changes
[ https://issues.apache.org/jira/browse/IGNITE-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15554: - Fix Version/s: 3.0.0-alpha5 > Add logic for assignment recalculation in case of replicas changes > -- > > Key: IGNITE-15554 > URL: https://issues.apache.org/jira/browse/IGNITE-15554 > Project: Ignite > Issue Type: Task >Reporter: Alexander Lapin >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > We need to provide the trigger when the number of partition replicas changes. > At the moment, replicas is a table configuration. But at the same time, > rebalance trigger mechanism assumes that changes triggered by metastore’s key > change (IGNITE-16063). So, we need provide the bridge between configuration > changes and metastore key, it can be: > separate metastore key, which duplicate the field from configuration and > mirror all configuration changes > any better ways here… -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16011) Start new rebalance round, when partition assignments updated
[
https://issues.apache.org/jira/browse/IGNITE-16011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16011:
-
Fix Version/s: 3.0.0-alpha5
> Start new rebalance round, when partition assignments updated
> -
>
> Key: IGNITE-16011
> URL: https://issues.apache.org/jira/browse/IGNITE-16011
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 8h
> Remaining Estimate: 0h
>
> When partition assignments are updated, we need to start raft changePeers and
> handle failover scenarios.
> When metastore event about partition assignments updates received we need to:
> - Start all needed nodes
> {code:java}
> partition.assignments.pending / partition.assignments.stable{code}
> - After successful starts - check if current node is the leader of raft
> group (leader response must be updated by current term) and
> changePeers(leaderTerm, peers). changePeers from old terms must be skipped.
> Also, we need the propagation of some new events from the raft side:
> * {{onLeaderElected(boolean configurationChangeInProgress)}} - must be
> executed from the new leader when raft group changes the leader. Maybe we
> actually need to also check if a new lease is received - we need to
> investigate.
> * {{onChangePeersError(errorContext)}} - must be executed when any errors
> during changePeers occurred
> * {{onChangePeersCommitted(peers)}} - must be executed with the list of new
> peers when changePeers has successfully done.
> and handle them by appropriate way:
> * {{{}onLeaderElected({}}}{{{}configurationChangeInProgress{}}}{{{}){}}} -
> we need to:
> ** if {{configurationChangeInProgress}} == false and pending/planned
> assignments not empty - run new changePeers. If true, do nothing.}}
> * {{onChangePeersError(errorContext)}} - run failover logic
> * {{onChangePeersCommitted(peers)}} - check if planned assignments is not
> empty and move it to pending.
> *
> -- Update pending and stable partitions assignments:
> {code:java}
> metastoreInvoke: \\ atomic
> // Here we can check invariant that pending is empty, but planned is not
> is impossible
> partition.assignments.stable = appliedPeers
> if empty(partition.assignments.planned):
> partition.assignments.pending = empty
> else:
> partition.assignments.pending = partition.assignments.planned {code}
> When {{partition.assignments.stable}} updated, we need to:
> * Replace current raft client with new one, with appropriate peers
> * Stop unneeded raft node
>
> (Phase 1)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16012) Raft changePeers behavior must be updated to async version
[
https://issues.apache.org/jira/browse/IGNITE-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16012:
-
Fix Version/s: 3.0.0-alpha5
> Raft changePeers behavior must be updated to async version
> --
>
> Key: IGNITE-16012
> URL: https://issues.apache.org/jira/browse/IGNITE-16012
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We need to update the current {{changePeers}} behavior with the following:
> - it must be asynchronous and returns ASAP when the request processed
> (without waiting for data catchup)
> - it must be updated with {{term}} argument for skipping the updates from
> old terms
>
> (Phase 1)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16800) Support leader changing during rebalance
[ https://issues.apache.org/jira/browse/IGNITE-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16800: - Fix Version/s: 3.0.0-alpha5 > Support leader changing during rebalance > > > Key: IGNITE-16800 > URL: https://issues.apache.org/jira/browse/IGNITE-16800 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > We need to start new rebalance, if leader changes during the current (when it > was in the catching up phase) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16063) Update partition pending/planned assignments on rebalance triggers
[
https://issues.apache.org/jira/browse/IGNITE-16063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16063:
-
Fix Version/s: 3.0.0-alpha5
> Update partition pending/planned assignments on rebalance triggers
> --
>
> Key: IGNITE-16063
> URL: https://issues.apache.org/jira/browse/IGNITE-16063
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> According to an algorithm from
> https://issues.apache.org/jira/browse/IGNITE-16020, we need to support
> partition assignments updates when:
> - baseline changed
> - number of partition replicas changed
> This update needs metastore multi-invoke feature and can be described as:
> {code}
> onBaselineEvent:
> for table in tableCfg.tables():
> for partition in table.partitions:
>
>
> onReplicaNumberChange:
> with table as event.table:
> for partitoin in table.partitions:
>
> metastoreInvoke: // atomic metastore call through multi-invoke api
> if empty(partition.change.trigger.revision) ||
> partition.change.trigger.revision < event.revision:
> if empty(partition.assignments.pending) &&
> partition.assignments.stable != calcPartAssighments():
> partition.assignments.pending = calcPartAssignments()
> partition.change.trigger.revision = event.revision
> else:
> if partition.assignments.pending != calcPartAssignments
> partition.assignments.planned = calcPartAssignments()
> partition.change.trigger.revision = event.revision
> else
> remove(partition.assignments.planned)
> else:
> skip
> {code}
> (Phase 1)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17111) Remove the ability to set the lazy flag in SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550985#comment-17550985 ] Yury Gerzhedovich commented on IGNITE-17111: [~AldoRaine] , your proposal relate to change public API. Such changes must be discussed at dev list firstly. > Remove the ability to set the lazy flag in SqlFieldsQuery > - > > Key: IGNITE-17111 > URL: https://issues.apache.org/jira/browse/IGNITE-17111 > Project: Ignite > Issue Type: Improvement >Reporter: Luchnikov Alexander >Priority: Minor > Labels: ise > > Remove the ability to set the lazy flag in SqlFieldsQuery. SqlFieldsQuery > must always be executed as lazy=true. > This property > (org.apache.igniteIgniteSystemProperties#IGNITE_SQL_FORCE_LAZY_RESULT_SET) > refers to the same functionality, but is not used in the code. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16903) Stop redundant raft groups on a node when the node receives update about partition stable assignments
[ https://issues.apache.org/jira/browse/IGNITE-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16903: - Fix Version/s: 3.0.0-alpha5 > Stop redundant raft groups on a node when the node receives update about > partition stable assignments > - > > Key: IGNITE-16903 > URL: https://issues.apache.org/jira/browse/IGNITE-16903 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > According to the rebalance algorithm from > https://issues.apache.org/jira/browse/IGNITE-16020, we need to stop redundant > raft groups on a node when the node receives update about partition stable > assignments. More details about the rebalance algorithm can be found in > https://github.com/apache/ignite-3/blob/main/modules/table/tech-notes/rebalance.md > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17124) Storage API tests can't be used for storages with specific binary format
[ https://issues.apache.org/jira/browse/IGNITE-17124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timur Magomedov updated IGNITE-17124: - Fix Version/s: 3.0 > Storage API tests can't be used for storages with specific binary format > > > Key: IGNITE-17124 > URL: https://issues.apache.org/jira/browse/IGNITE-17124 > Project: Ignite > Issue Type: Improvement >Reporter: Timur Magomedov >Assignee: Timur Magomedov >Priority: Major > Labels: ignite-3 > Fix For: 3.0 > > > Storages that need to get table UUID or rely on some specific binary format > of DataRow can't be tested using AbstractPartitionStorageTest. This works for > key-value storages that don't decode key and value of DataRow/SearchRow and > don't use table UUID but will fail once such storages are implemented or > existing ones will decode data binaries. > Two main issues here are the following: > 1. searchRow() and dataRow() methods in AbstractPartitionStorageTest can't be > overridden since they are static methods. > 2. Table UUID is always null in Storage API tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17124) Storage API tests can't be used for storages with specific binary format
[ https://issues.apache.org/jira/browse/IGNITE-17124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timur Magomedov updated IGNITE-17124: - Fix Version/s: 3.0.0-alpha6 (was: 3.0) > Storage API tests can't be used for storages with specific binary format > > > Key: IGNITE-17124 > URL: https://issues.apache.org/jira/browse/IGNITE-17124 > Project: Ignite > Issue Type: Improvement >Reporter: Timur Magomedov >Assignee: Timur Magomedov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > Storages that need to get table UUID or rely on some specific binary format > of DataRow can't be tested using AbstractPartitionStorageTest. This works for > key-value storages that don't decode key and value of DataRow/SearchRow and > don't use table UUID but will fail once such storages are implemented or > existing ones will decode data binaries. > Two main issues here are the following: > 1. searchRow() and dataRow() methods in AbstractPartitionStorageTest can't be > overridden since they are static methods. > 2. Table UUID is always null in Storage API tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17127) Update version number in Ignite 3 Alpha docs for alpha 5 release
Igor Gusev created IGNITE-17127: --- Summary: Update version number in Ignite 3 Alpha docs for alpha 5 release Key: IGNITE-17127 URL: https://issues.apache.org/jira/browse/IGNITE-17127 Project: Ignite Issue Type: Task Components: documentation Reporter: Igor Gusev We need to update version numbers and download links for AI3 alpha docs -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17127) Update version number in Ignite 3 Alpha docs for alpha 5 release
[ https://issues.apache.org/jira/browse/IGNITE-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Gusev reassigned IGNITE-17127: --- Assignee: Igor Gusev > Update version number in Ignite 3 Alpha docs for alpha 5 release > > > Key: IGNITE-17127 > URL: https://issues.apache.org/jira/browse/IGNITE-17127 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > > We need to update version numbers and download links for AI3 alpha docs -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17124) Storage API tests can't be used for storages with specific binary format
[ https://issues.apache.org/jira/browse/IGNITE-17124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timur Magomedov updated IGNITE-17124: - Epic Link: IGNITE-16851 > Storage API tests can't be used for storages with specific binary format > > > Key: IGNITE-17124 > URL: https://issues.apache.org/jira/browse/IGNITE-17124 > Project: Ignite > Issue Type: Improvement >Reporter: Timur Magomedov >Assignee: Timur Magomedov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > Storages that need to get table UUID or rely on some specific binary format > of DataRow can't be tested using AbstractPartitionStorageTest. This works for > key-value storages that don't decode key and value of DataRow/SearchRow and > don't use table UUID but will fail once such storages are implemented or > existing ones will decode data binaries. > Two main issues here are the following: > 1. searchRow() and dataRow() methods in AbstractPartitionStorageTest can't be > overridden since they are static methods. > 2. Table UUID is always null in Storage API tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17065) CorruptedTreeException: B+Tree is corrupted(Duplicate row in index)
[ https://issues.apache.org/jira/browse/IGNITE-17065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551097#comment-17551097 ] Yury Gerzhedovich commented on IGNITE-17065: [~liyuj] , is itpossible to reproduce the issue on last 2.13 version of Ignite? Since 2.10 were fixed many B+tree corrupt issues and probably the issue is not actual. Also to have ability to analyze such type of issue requires WAL and PDS files. Could you please attache WAL and PDS? List (not full) of possible root cause fixed issues : https://issues.apache.org/jira/browse/IGNITE-16494 https://issues.apache.org/jira/browse/IGNITE-15943 https://issues.apache.org/jira/browse/IGNITE-12911 https://issues.apache.org/jira/browse/IGNITE-15990 https://issues.apache.org/jira/browse/IGNITE-16661 > CorruptedTreeException: B+Tree is corrupted(Duplicate row in index) > --- > > Key: IGNITE-17065 > URL: https://issues.apache.org/jira/browse/IGNITE-17065 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.10 >Reporter: YuJue Li >Priority: Major > Attachments: 2021-12-21_13-59-27.574.log > > > In a pure memory cluster, the B+Tree is corrupted during node restart. > See the attachment log for details. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17117) Analyze Table SQL Statement not working with Ignite 2.13.0
[
https://issues.apache.org/jira/browse/IGNITE-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551109#comment-17551109
]
Yury Gerzhedovich commented on IGNITE-17117:
[~SachinJanani] , could you please attach a reproducer? I can't reproduce the
issue.
> Analyze Table SQL Statement not working with Ignite 2.13.0
> --
>
> Key: IGNITE-17117
> URL: https://issues.apache.org/jira/browse/IGNITE-17117
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Sachin Janani
>Priority: Critical
> Fix For: 2.14
>
>
> Running ANALYZE table SQL statement is failing with following exception:
> {code:java}
> 0: jdbc:ignite:thin://127.0.0.1/> ANALYZE PRODUCT_TABLE; Error: Failed to
> parse query. Syntax error in SQL statement "ANALYZE PRODUCT_TABLE[*]"; SQL
> statement: ANALYZE PRODUCT_TABLE [42000-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "ANALYZE PRODUCT_TABLE[*]"; SQL statement: ANALYZE PRODUCT_TABLE [42000-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054) at
> sqlline.Commands.execute(Commands.java:1003) at
> sqlline.Commands.sql(Commands.java:967) at
> sqlline.SqlLine.dispatch(SqlLine.java:734) at
> sqlline.SqlLine.begin(SqlLine.java:541) at
> sqlline.SqlLine.start(SqlLine.java:267) at
> sqlline.SqlLine.main(SqlLine.java:206) 0: jdbc:ignite:thin://127.0.0.1/>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17128) PersistentPageMemoryStorageExample cannot be run twice
Andrey Khitrin created IGNITE-17128:
---
Summary: PersistentPageMemoryStorageExample cannot be run twice
Key: IGNITE-17128
URL: https://issues.apache.org/jira/browse/IGNITE-17128
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 3.0.0-alpha5
Reporter: Andrey Khitrin
{*}Issue{*}: example PersistentPageMemoryStorageExample cannot be run twice. At
the first attempt it runs fine. But at the second attempt, it fails with the
following exception:
{code:java}
Exception in thread "main" java.sql.SQLException: Exception while executing
query INSERT INTO ACCOUNTS (ACCOUNT_ID, FIRST_NAME, LAST_NAME, BALANCE) values
(?, ?, ?, ?). Error message: java.util.concurrent.CompletionException: class
org.apache.ignite.lang.IgniteException: Failed to INSERT some keys because they
are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
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.uniHandle(CompletableFuture.java:932)
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.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:194)
at
java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
at
java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
at
org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:194)
at
org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:149)
at
org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
at
org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
at
org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
at
org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:298)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: class org.apache.ignite.lang.IgniteException: Failed to INSERT some
keys because they are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
at
org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
at
java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
... 16 more
Caused by: class org.apache.ignite.lang.IgniteInternalException: Failed to
INSERT some keys because they are already in cache. [rows=[Row[1, John, Doe,
1000.0]]]
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.conflictKeysException(ModifyNode.java:256)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:233)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:175)
at
org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:148)
at
org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.end(ProjectNode.java:81)
at
org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:132)
at
org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:295)
... 4 more at
org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
at
org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:147)
at
org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeWithArguments(JdbcPreparedStatement.java:657)
at
org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:136)
at
org.apache.ignite.example.storage.PersistentPageMemoryStorageExample.main(PersistentPageMemoryStorageExample.java:105)Process
finished with exit code 1
{code}
This could be mitigated by re-creation of ignite working environment, but I'm
not sure whether this behavior is desired.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17128) PersistentPageMemoryStorageExample cannot be run twice
[
https://issues.apache.org/jira/browse/IGNITE-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17128:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> PersistentPageMemoryStorageExample cannot be run twice
> --
>
> Key: IGNITE-17128
> URL: https://issues.apache.org/jira/browse/IGNITE-17128
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 3.0.0-alpha5
>Reporter: Andrey Khitrin
>Priority: Major
>
> {*}Issue{*}: example PersistentPageMemoryStorageExample cannot be run twice.
> At the first attempt it runs fine. But at the second attempt, it fails with
> the following exception:
> {code:java}
> Exception in thread "main" java.sql.SQLException: Exception while executing
> query INSERT INTO ACCOUNTS (ACCOUNT_ID, FIRST_NAME, LAST_NAME, BALANCE)
> values (?, ?, ?, ?). Error message: java.util.concurrent.CompletionException:
> class org.apache.ignite.lang.IgniteException: Failed to INSERT some keys
> because they are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
> 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.uniHandle(CompletableFuture.java:932)
> 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.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:194)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:194)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:149)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:298)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: class org.apache.ignite.lang.IgniteException: Failed to INSERT
> some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> ... 16 more
> Caused by: class org.apache.ignite.lang.IgniteInternalException: Failed to
> INSERT some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.conflictKeysException(ModifyNode.java:256)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:233)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:175)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.end(ProjectNode.java:81)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:132)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:295)
> ... 4 more at
> org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:147)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeWithArguments(JdbcPreparedStatement.java:657)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:136)
[jira] [Assigned] (IGNITE-17128) PersistentPageMemoryStorageExample cannot be run twice
[
https://issues.apache.org/jira/browse/IGNITE-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko reassigned IGNITE-17128:
Assignee: Kirill Tkalenko
> PersistentPageMemoryStorageExample cannot be run twice
> --
>
> Key: IGNITE-17128
> URL: https://issues.apache.org/jira/browse/IGNITE-17128
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 3.0.0-alpha5
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Major
>
> {*}Issue{*}: example PersistentPageMemoryStorageExample cannot be run twice.
> At the first attempt it runs fine. But at the second attempt, it fails with
> the following exception:
> {code:java}
> Exception in thread "main" java.sql.SQLException: Exception while executing
> query INSERT INTO ACCOUNTS (ACCOUNT_ID, FIRST_NAME, LAST_NAME, BALANCE)
> values (?, ?, ?, ?). Error message: java.util.concurrent.CompletionException:
> class org.apache.ignite.lang.IgniteException: Failed to INSERT some keys
> because they are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
> 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.uniHandle(CompletableFuture.java:932)
> 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.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:194)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:194)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:149)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:298)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: class org.apache.ignite.lang.IgniteException: Failed to INSERT
> some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> ... 16 more
> Caused by: class org.apache.ignite.lang.IgniteInternalException: Failed to
> INSERT some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.conflictKeysException(ModifyNode.java:256)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:233)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:175)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.end(ProjectNode.java:81)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:132)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:295)
> ... 4 more at
> org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:147)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeWithArguments(JdbcPreparedStatement.java:657)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStateme
[jira] [Commented] (IGNITE-17088) SQL API: Add examples.
[
https://issues.apache.org/jira/browse/IGNITE-17088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551125#comment-17551125
]
Andrey Khitrin commented on IGNITE-17088:
-
Hi! I've tried to run this example and found it failing with
{{UnsupportedOperationException}} (due to IGNITE-17057 probably). Is it OK to
have a failing example in Alpha release?
> SQL API: Add examples.
> --
>
> Key: IGNITE-17088
> URL: https://issues.apache.org/jira/browse/IGNITE-17088
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add examples of using SQL API.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17129) cli tool dosn’t expand tilde in a config path
Andrey Khitrin created IGNITE-17129:
---
Summary: cli tool dosn’t expand tilde in a config path
Key: IGNITE-17129
URL: https://issues.apache.org/jira/browse/IGNITE-17129
Project: Ignite
Issue Type: Bug
Affects Versions: 3.0.0-alpha5
Reporter: Andrey Khitrin
Many Linux users use tilde ({{{}~{}}}) as a shortcut for a user's home
directory. CLI tool could expand environment variables (like {{{}$HOME{}}}) in
config path, but fails to expand tilde.
An example:
{code:java}
$ ./ignite node start
--config=~/work/apache/ignite-3/examples/config/ignite-config.json my-first-node
Starting a new Ignite node...
Can't start the node. Read logs for details:
/home/zloddey/opt/ai3/ignite-log/my-first-node.log
$ cat /home/zloddey/opt/ai3/ignite-log/my-first-node.log
Exception in thread "main" class org.apache.ignite.lang.IgniteException: Unable
to read user specific configuration.
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:97)
at org.apache.ignite.IgnitionManager.start(IgnitionManager.java:105)
at org.apache.ignite.app.IgniteCliRunner.start(IgniteCliRunner.java:109)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:44)
Caused by: java.nio.file.NoSuchFileException:
/home/zloddey/opt/ai3/~/work/apache/ignite-3/examples/config/ignite-config.json
at
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
at
java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:219)
at java.base/java.nio.file.Files.newByteChannel(Files.java:371)
at java.base/java.nio.file.Files.newByteChannel(Files.java:422)
at java.base/java.nio.file.Files.readAllBytes(Files.java:3206)
at java.base/java.nio.file.Files.readString(Files.java:3284)
at java.base/java.nio.file.Files.readString(Files.java:3243)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:92)
... 3 more
{code}
When I use {{/home/zloddey}} or {{$HOME}} instead of tilde, it works fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17128) PersistentPageMemoryStorageExample cannot be run twice
[
https://issues.apache.org/jira/browse/IGNITE-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17128:
-
Fix Version/s: 3.0.0-alpha5
> PersistentPageMemoryStorageExample cannot be run twice
> --
>
> Key: IGNITE-17128
> URL: https://issues.apache.org/jira/browse/IGNITE-17128
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 3.0.0-alpha5
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 3.0.0-alpha5
>
>
> {*}Issue{*}: example PersistentPageMemoryStorageExample cannot be run twice.
> At the first attempt it runs fine. But at the second attempt, it fails with
> the following exception:
> {code:java}
> Exception in thread "main" java.sql.SQLException: Exception while executing
> query INSERT INTO ACCOUNTS (ACCOUNT_ID, FIRST_NAME, LAST_NAME, BALANCE)
> values (?, ?, ?, ?). Error message: java.util.concurrent.CompletionException:
> class org.apache.ignite.lang.IgniteException: Failed to INSERT some keys
> because they are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
> 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.uniHandle(CompletableFuture.java:932)
> 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.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:194)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:194)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:149)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:298)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: class org.apache.ignite.lang.IgniteException: Failed to INSERT
> some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> ... 16 more
> Caused by: class org.apache.ignite.lang.IgniteInternalException: Failed to
> INSERT some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.conflictKeysException(ModifyNode.java:256)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:233)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:175)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.end(ProjectNode.java:81)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:132)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:295)
> ... 4 more at
> org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:147)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeWithArguments(JdbcPreparedStatement.java:657)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.
[jira] [Updated] (IGNITE-17128) PersistentPageMemoryStorageExample cannot be run twice
[
https://issues.apache.org/jira/browse/IGNITE-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17128:
-
Fix Version/s: (was: 3.0.0-alpha5)
> PersistentPageMemoryStorageExample cannot be run twice
> --
>
> Key: IGNITE-17128
> URL: https://issues.apache.org/jira/browse/IGNITE-17128
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 3.0.0-alpha5
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Major
>
> {*}Issue{*}: example PersistentPageMemoryStorageExample cannot be run twice.
> At the first attempt it runs fine. But at the second attempt, it fails with
> the following exception:
> {code:java}
> Exception in thread "main" java.sql.SQLException: Exception while executing
> query INSERT INTO ACCOUNTS (ACCOUNT_ID, FIRST_NAME, LAST_NAME, BALANCE)
> values (?, ?, ?, ?). Error message: java.util.concurrent.CompletionException:
> class org.apache.ignite.lang.IgniteException: Failed to INSERT some keys
> because they are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
> 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.uniHandle(CompletableFuture.java:932)
> 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.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:194)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:194)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:149)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:298)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: class org.apache.ignite.lang.IgniteException: Failed to INSERT
> some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> ... 16 more
> Caused by: class org.apache.ignite.lang.IgniteInternalException: Failed to
> INSERT some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.conflictKeysException(ModifyNode.java:256)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:233)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:175)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.end(ProjectNode.java:81)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:132)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:295)
> ... 4 more at
> org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:147)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeWithArguments(JdbcPreparedStatement.java:657)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedS
[jira] [Assigned] (IGNITE-17126) Update README.md to reflect changes in CLI
[ https://issues.apache.org/jira/browse/IGNITE-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-17126: -- Assignee: Aleksandr > Update README.md to reflect changes in CLI > -- > > Key: IGNITE-17126 > URL: https://issues.apache.org/jira/browse/IGNITE-17126 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 20m > Remaining Estimate: 0h > > It still says alpha3 inside and `ignite init` was changed to `ignite > bootstrap` in the current version. I would suggest also adding a few steps on > `node start` and `cluster init` with a few examples. > All examples in the `examples` folder have to be adjusted too. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17128) PersistentPageMemoryStorageExample cannot be run twice
[
https://issues.apache.org/jira/browse/IGNITE-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17128:
-
Labels: ignite-3 (was: )
> PersistentPageMemoryStorageExample cannot be run twice
> --
>
> Key: IGNITE-17128
> URL: https://issues.apache.org/jira/browse/IGNITE-17128
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 3.0.0-alpha5
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
>
> {*}Issue{*}: example PersistentPageMemoryStorageExample cannot be run twice.
> At the first attempt it runs fine. But at the second attempt, it fails with
> the following exception:
> {code:java}
> Exception in thread "main" java.sql.SQLException: Exception while executing
> query INSERT INTO ACCOUNTS (ACCOUNT_ID, FIRST_NAME, LAST_NAME, BALANCE)
> values (?, ?, ?, ?). Error message: java.util.concurrent.CompletionException:
> class org.apache.ignite.lang.IgniteException: Failed to INSERT some keys
> because they are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
> 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.uniHandle(CompletableFuture.java:932)
> 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.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:194)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:194)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:149)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:298)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: class org.apache.ignite.lang.IgniteException: Failed to INSERT
> some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> ... 16 more
> Caused by: class org.apache.ignite.lang.IgniteInternalException: Failed to
> INSERT some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.conflictKeysException(ModifyNode.java:256)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:233)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:175)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.end(ProjectNode.java:81)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:132)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:295)
> ... 4 more at
> org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:147)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeWithArguments(JdbcPreparedStatement.java:657)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeU
[jira] [Updated] (IGNITE-17129) cli tool dosn’t expand tilde in a config path
[
https://issues.apache.org/jira/browse/IGNITE-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin updated IGNITE-17129:
Labels: ignite-3 (was: )
> cli tool dosn’t expand tilde in a config path
> --
>
> Key: IGNITE-17129
> URL: https://issues.apache.org/jira/browse/IGNITE-17129
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha5
>Reporter: Andrey Khitrin
>Priority: Major
> Labels: ignite-3
>
> Many Linux users use tilde ({{{}~{}}}) as a shortcut for a user's home
> directory. CLI tool could expand environment variables (like {{{}$HOME{}}})
> in config path, but fails to expand tilde.
> An example:
> {code:java}
> $ ./ignite node start
> --config=~/work/apache/ignite-3/examples/config/ignite-config.json
> my-first-node
> Starting a new Ignite node...
> Can't start the node. Read logs for details:
> /home/zloddey/opt/ai3/ignite-log/my-first-node.log
> $ cat /home/zloddey/opt/ai3/ignite-log/my-first-node.log
> Exception in thread "main" class org.apache.ignite.lang.IgniteException:
> Unable to read user specific configuration.
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:97)
> at org.apache.ignite.IgnitionManager.start(IgnitionManager.java:105)
> at
> org.apache.ignite.app.IgniteCliRunner.start(IgniteCliRunner.java:109)
> at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:44)
> Caused by: java.nio.file.NoSuchFileException:
> /home/zloddey/opt/ai3/~/work/apache/ignite-3/examples/config/ignite-config.json
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:219)
> at java.base/java.nio.file.Files.newByteChannel(Files.java:371)
> at java.base/java.nio.file.Files.newByteChannel(Files.java:422)
> at java.base/java.nio.file.Files.readAllBytes(Files.java:3206)
> at java.base/java.nio.file.Files.readString(Files.java:3284)
> at java.base/java.nio.file.Files.readString(Files.java:3243)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:92)
> ... 3 more
> {code}
> When I use {{/home/zloddey}} or {{$HOME}} instead of tilde, it works fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17128) PersistentPageMemoryStorageExample cannot be run twice
[
https://issues.apache.org/jira/browse/IGNITE-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-17128:
Fix Version/s: 3.0.0-alpha5
> PersistentPageMemoryStorageExample cannot be run twice
> --
>
> Key: IGNITE-17128
> URL: https://issues.apache.org/jira/browse/IGNITE-17128
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 3.0.0-alpha5
>Reporter: Andrey Khitrin
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> {*}Issue{*}: example PersistentPageMemoryStorageExample cannot be run twice.
> At the first attempt it runs fine. But at the second attempt, it fails with
> the following exception:
> {code:java}
> Exception in thread "main" java.sql.SQLException: Exception while executing
> query INSERT INTO ACCOUNTS (ACCOUNT_ID, FIRST_NAME, LAST_NAME, BALANCE)
> values (?, ?, ?, ?). Error message: java.util.concurrent.CompletionException:
> class org.apache.ignite.lang.IgniteException: Failed to INSERT some keys
> because they are already in cache. [rows=[Row[1, John, Doe, 1000.0]]]
> 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.uniHandle(CompletableFuture.java:932)
> 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.sql.engine.exec.rel.AsyncRootNode.lambda$closeAsync$0(AsyncRootNode.java:194)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEachFrom(LinkedBlockingQueue.java:1010)
> at
> java.base/java.util.concurrent.LinkedBlockingQueue.forEach(LinkedBlockingQueue.java:979)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.closeAsync(AsyncRootNode.java:194)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AsyncRootNode.onError(AsyncRootNode.java:149)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.AbstractNode.onError(AbstractNode.java:157)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:298)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:78)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: class org.apache.ignite.lang.IgniteException: Failed to INSERT
> some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> ... 16 more
> Caused by: class org.apache.ignite.lang.IgniteInternalException: Failed to
> INSERT some keys because they are already in cache. [rows=[Row[1, John, Doe,
> 1000.0]]]
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.conflictKeysException(ModifyNode.java:256)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.flushTuples(ModifyNode.java:233)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.tryEnd(ModifyNode.java:175)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ModifyNode.end(ModifyNode.java:148)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ProjectNode.end(ProjectNode.java:81)
> at
> org.apache.ignite.internal.sql.engine.exec.rel.ScanNode.push(ScanNode.java:132)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:295)
> ... 4 more at
> org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
> at
> org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:147)
> at
> org.apache.ignite.internal.jdbc.JdbcPreparedStatement.executeWithArguments(JdbcPreparedStatement.java:657)
> at
> org.apache.ignite.intern
[jira] [Commented] (IGNITE-17117) Analyze Table SQL Statement not working with Ignite 2.13.0
[
https://issues.apache.org/jira/browse/IGNITE-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551147#comment-17551147
]
Sachin Janani commented on IGNITE-17117:
[~jooger] Here are the steps of how i reproduced it:
1. Download apache ignite 2.13 from this link:
https://dlcdn.apache.org/ignite/2.13.0/apache-ignite-2.13.0-bin.zip
2. Start ignite with the default config using following command
{code:java}
./ignite.sh ../config/default-config.xml{code}
3. Start sqlline and create table with using the following sql:
{code:java}
create table test2(a int, b int, c int, primary key(a,b)) with "affinity_key=a
, template=PARTITIONED";{code}
4. Run analyze command:
{code:java}
ANALYZE test2;{code}
The above command throws the following error:
{code:java}
0: jdbc:ignite:thin://127.0.0.1/> ANALYZE test2;
Error: Failed to parse query. Syntax error in SQL statement "ANALYZE TEST2[*]
"; SQL statement:
ANALYZE test2 [42000-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
"ANALYZE TEST2[*] "; SQL statement:
ANALYZE test2 [42000-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
at sqlline.Commands.executeSingleQuery(Commands.java:1054)
at sqlline.Commands.execute(Commands.java:1003)
at sqlline.Commands.sql(Commands.java:967)
at sqlline.SqlLine.dispatch(SqlLine.java:734)
at sqlline.SqlLine.begin(SqlLine.java:541)
at sqlline.SqlLine.start(SqlLine.java:267)
at sqlline.SqlLine.main(SqlLine.java:206) {code}
> Analyze Table SQL Statement not working with Ignite 2.13.0
> --
>
> Key: IGNITE-17117
> URL: https://issues.apache.org/jira/browse/IGNITE-17117
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Sachin Janani
>Priority: Critical
> Fix For: 2.14
>
>
> Running ANALYZE table SQL statement is failing with following exception:
> {code:java}
> 0: jdbc:ignite:thin://127.0.0.1/> ANALYZE PRODUCT_TABLE; Error: Failed to
> parse query. Syntax error in SQL statement "ANALYZE PRODUCT_TABLE[*]"; SQL
> statement: ANALYZE PRODUCT_TABLE [42000-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "ANALYZE PRODUCT_TABLE[*]"; SQL statement: ANALYZE PRODUCT_TABLE [42000-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054) at
> sqlline.Commands.execute(Commands.java:1003) at
> sqlline.Commands.sql(Commands.java:967) at
> sqlline.SqlLine.dispatch(SqlLine.java:734) at
> sqlline.SqlLine.begin(SqlLine.java:541) at
> sqlline.SqlLine.start(SqlLine.java:267) at
> sqlline.SqlLine.main(SqlLine.java:206) 0: jdbc:ignite:thin://127.0.0.1/>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17127) Update version number in Ignite 3 Alpha docs for alpha 5 release
[ https://issues.apache.org/jira/browse/IGNITE-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551150#comment-17551150 ] Pavel Tupitsyn commented on IGNITE-17127: - [~igusev] LGTM > Update version number in Ignite 3 Alpha docs for alpha 5 release > > > Key: IGNITE-17127 > URL: https://issues.apache.org/jira/browse/IGNITE-17127 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > > We need to update version numbers and download links for AI3 alpha docs -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17130) Profilies support for CLI configuration
Mikhail Pochatkin created IGNITE-17130: -- Summary: Profilies support for CLI configuration Key: IGNITE-17130 URL: https://issues.apache.org/jira/browse/IGNITE-17130 Project: Ignite Issue Type: New Feature Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17130) Profilies support for CLI configuration
[ https://issues.apache.org/jira/browse/IGNITE-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17130: --- Epic Link: IGNITE-16970 Labels: ignite-3 ignite-3-cli-tool (was: ) > Profilies support for CLI configuration > --- > > Key: IGNITE-17130 > URL: https://issues.apache.org/jira/browse/IGNITE-17130 > Project: Ignite > Issue Type: New Feature >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17106) Create documentation for Java SQL API
[ https://issues.apache.org/jira/browse/IGNITE-17106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17106: Fix Version/s: 3.0.0-alpha5 > Create documentation for Java SQL API > - > > Key: IGNITE-17106 > URL: https://issues.apache.org/jira/browse/IGNITE-17106 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17127) Update version number in Ignite 3 Alpha docs for alpha 5 release
[ https://issues.apache.org/jira/browse/IGNITE-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17127: Fix Version/s: 3.0.0-alpha5 > Update version number in Ignite 3 Alpha docs for alpha 5 release > > > Key: IGNITE-17127 > URL: https://issues.apache.org/jira/browse/IGNITE-17127 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > We need to update version numbers and download links for AI3 alpha docs -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17093) Map error codes for cli commands
[ https://issues.apache.org/jira/browse/IGNITE-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-17093: -- Assignee: Vadim Pakhnushev > Map error codes for cli commands > > > Key: IGNITE-17093 > URL: https://issues.apache.org/jira/browse/IGNITE-17093 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > There should be a mapping between the error and the exit code. > * list types of errors that user can get during commands execution > * return exit codes from all commands -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17088) SQL API: Add examples.
[ https://issues.apache.org/jira/browse/IGNITE-17088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551162#comment-17551162 ] Andrey Mashenkov commented on IGNITE-17088: --- [~akhitrin], SQL API is partially supported on the client side. You are right, this will be fixed in IGNITE-17057. > SQL API: Add examples. > -- > > Key: IGNITE-17088 > URL: https://issues.apache.org/jira/browse/IGNITE-17088 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > Add examples of using SQL API. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17119) DiscoveryClientSocketTest.sslSocketTest fails regularly on TC and locally
[
https://issues.apache.org/jira/browse/IGNITE-17119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551165#comment-17551165
]
Ignite TC Bot commented on IGNITE-17119:
{panel:title=Branch: [pull/10073/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10073/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6614945&buildTypeId=IgniteTests24Java8_RunAll]
> DiscoveryClientSocketTest.sslSocketTest fails regularly on TC and locally
> -
>
> Key: IGNITE-17119
> URL: https://issues.apache.org/jira/browse/IGNITE-17119
> Project: Ignite
> Issue Type: Bug
> Components: networking
>Reporter: Roman Puchkovskiy
>Assignee: Roman Puchkovskiy
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1051723478826841368&tab=testDetails
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17073) Document new CLI commands
[ https://issues.apache.org/jira/browse/IGNITE-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551175#comment-17551175 ] Andrey N. Gura commented on IGNITE-17073: - [~igusev] [~aleksandr.pakhomov] Thanks for contribution! Merged to main and ignite-3.0.0-alpha5 branches. > Document new CLI commands > -- > > Key: IGNITE-17073 > URL: https://issues.apache.org/jira/browse/IGNITE-17073 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksandr >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 20m > Remaining Estimate: 0h > > Document commands that are introdused in > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17090) Map sql errors to messages that user see
[
https://issues.apache.org/jira/browse/IGNITE-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-17090:
--
Assignee: Mikhail Pochatkin
> Map sql errors to messages that user see
>
>
> Key: IGNITE-17090
> URL: https://issues.apache.org/jira/browse/IGNITE-17090
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> There is a number of errors that user can get during sql command execution.
> Map all types of errors and map them to exit error codes and user messages.
> Also, a user has to understand what is wrong with the query. Now it displays
> jusn an abstract message.
>
> How it works now:
> {code:java}
> sql-cli> create table myta
> SQL query parsing error: Sql query execution failed.
> sql-cli> {code}
> {code:java}
> sql-cli> create table mytable(i int, j int);
> Unrecognized error while process SQL query.
> sql-cli> {code}
> "SQL query parsing error: Sql query execution failed.", "Unrecognized error
> while process SQL query." say nothing about {*}what exactly is wrong{*}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-16974) Map ignite errors to the command line exit codes
[ https://issues.apache.org/jira/browse/IGNITE-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-16974: -- Assignee: Aleksandr > Map ignite errors to the command line exit codes > > > Key: IGNITE-16974 > URL: https://issues.apache.org/jira/browse/IGNITE-16974 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Provide the list of errors that can be produced by REST, for example: > * VALIDATION_EXCEPTION > * CONFIG_PATH_UNRECOGNIZED > * INVALID_CONFIG_FORMAT > And map them to CLI exit codes. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17098) Create documentation for pluggable storage engines
[ https://issues.apache.org/jira/browse/IGNITE-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551194#comment-17551194 ] Andrey N. Gura commented on IGNITE-17098: - [~igusev] [~apolovtcev] Thanks for contribution! Merged to main and ignite-3.0.0-alpha5 branches. > Create documentation for pluggable storage engines > -- > > Key: IGNITE-17098 > URL: https://issues.apache.org/jira/browse/IGNITE-17098 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr Polovtcev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1h > Remaining Estimate: 0h > > We need to document the following aspects regarding the pluggable storage > engines feature: > 1. SQL API for defining a storage engine for a table. > 2. Configuration of data regions using Ignite CLI. > 3. Configuration of the default engine using Ignite CLU. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17130) Profilies support for CLI configuration
[
https://issues.apache.org/jira/browse/IGNITE-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-17130:
---
Description:
h3. Config file site:
The Ignite CLI currently only has one set of properties. Need to support
multiple profiles, this means that the config must have multiple sections for
each user profile. INI format completely covers everything we need, so need
migrate config file format from properties to ini.
Default profile name [default].
h3. CLI command site:
Create profile command
{code:java}
ignite cli config create-profile
--name profile_name (REQUIRED)
--copy-from profile-name (OPTIONAL)
--activate true\false (OPTIONAL, DEFAULT VALUE = true){code}
Activate profile command as default profile
{code:java}
ignite cli config --profile profile_name {code}
Read\write property with profile
{code:java}
ignite cli config --profile profile_name get\set propertyKey=propertyValue
{code}
> Profilies support for CLI configuration
> ---
>
> Key: IGNITE-17130
> URL: https://issues.apache.org/jira/browse/IGNITE-17130
> Project: Ignite
> Issue Type: New Feature
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> h3. Config file site:
> The Ignite CLI currently only has one set of properties. Need to support
> multiple profiles, this means that the config must have multiple sections for
> each user profile. INI format completely covers everything we need, so need
> migrate config file format from properties to ini.
> Default profile name [default].
> h3. CLI command site:
> Create profile command
> {code:java}
> ignite cli config create-profile
> --name profile_name (REQUIRED)
> --copy-from profile-name (OPTIONAL)
> --activate true\false (OPTIONAL, DEFAULT VALUE = true){code}
> Activate profile command as default profile
> {code:java}
> ignite cli config --profile profile_name {code}
> Read\write property with profile
> {code:java}
> ignite cli config --profile profile_name get\set propertyKey=propertyValue
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17113) Document distributed computing in AI alpha 5
[ https://issues.apache.org/jira/browse/IGNITE-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551201#comment-17551201 ] Andrey N. Gura commented on IGNITE-17113: - [~igusev] Thanks for contribution! Merged to main and ignite-3.0.0-alpha5 branches. > Document distributed computing in AI alpha 5 > > > Key: IGNITE-17113 > URL: https://issues.apache.org/jira/browse/IGNITE-17113 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17127) Update version number in Ignite 3 Alpha docs for alpha 5 release
[ https://issues.apache.org/jira/browse/IGNITE-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551203#comment-17551203 ] Andrey N. Gura commented on IGNITE-17127: - [~igusev] Thanks for contribution! Merged to main and ignite-3.0.0-alpha5 branches. > Update version number in Ignite 3 Alpha docs for alpha 5 release > > > Key: IGNITE-17127 > URL: https://issues.apache.org/jira/browse/IGNITE-17127 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > We need to update version numbers and download links for AI3 alpha docs -- This message was sent by Atlassian Jira (v8.20.7#820007)
