[jira] [Commented] (IGNITE-13810) Append additional log and metrics info regarding cache expiration.
[
https://issues.apache.org/jira/browse/IGNITE-13810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424198#comment-17424198
]
Ignite TC Bot commented on IGNITE-13810:
{panel:title=Branch: [pull/9044/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9044/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache (Expiry Policy){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6209454]]
* {color:#013220}IgniteCacheExpiryPolicyTestSuite:
ExpiryPolicyInfoLoggingTest.checkLoggingExpiryInfoForStaticallyCreatedCache -
PASSED{color}
* {color:#013220}IgniteCacheExpiryPolicyTestSuite:
ExpiryPolicyInfoLoggingTest.checkLoggingExpiryInfoForStaticallyCreatedCacheStartedInRecoveryMode
- PASSED{color}
* {color:#013220}IgniteCacheExpiryPolicyTestSuite:
ExpiryPolicyInfoLoggingTest.checkLoggingExpiryInfoForDynamicallyCreatedCache -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6209510buildTypeId=IgniteTests24Java8_RunAll]
> Append additional log and metrics info regarding cache expiration.
> ---
>
> Key: IGNITE-13810
> URL: https://issues.apache.org/jira/browse/IGNITE-13810
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.9
>Reporter: Evgeny Stanilovsky
>Assignee: Konstantin Sirotkin
>Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently we have no any additional information regarding
> _cache.withExpiryPolicy_ execution. Additionally it would be very useful to
> have a corresponding metric.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15484) SQL allows "create index" query with duplicated columns
[ https://issues.apache.org/jira/browse/IGNITE-15484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-15484: Reviewer: (was: Maxim Muzafarov) > SQL allows "create index" query with duplicated columns > --- > > Key: IGNITE-15484 > URL: https://issues.apache.org/jira/browse/IGNITE-15484 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > This query should forbid such queries and raise an exception: > "create index IDX on table (id ASC, id DESC);" > Now it creates index last appearance of the field, in this case (id DESC). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15484) SQL allows "create index" query with duplicated columns
[ https://issues.apache.org/jira/browse/IGNITE-15484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424164#comment-17424164 ] Maksim Timonin commented on IGNITE-15484: - [~jooger] thanks for review! > SQL allows "create index" query with duplicated columns > --- > > Key: IGNITE-15484 > URL: https://issues.apache.org/jira/browse/IGNITE-15484 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > This query should forbid such queries and raise an exception: > "create index IDX on table (id ASC, id DESC);" > Now it creates index last appearance of the field, in this case (id DESC). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15662) It is impossible to add a test-jar dependency to the CLI module
[
https://issues.apache.org/jira/browse/IGNITE-15662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424065#comment-17424065
]
Aleksandr Polovtcev commented on IGNITE-15662:
--
LGTM, thank you!
> It is impossible to add a test-jar dependency to the CLI module
> ---
>
> Key: IGNITE-15662
> URL: https://issues.apache.org/jira/browse/IGNITE-15662
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Petr Ivanov
>Priority: Minor
> Labels: ignite-3
> Time Spent: 3h
> Remaining Estimate: 0h
>
> h2. Steps to reproduce
> 1. Add a {{test-jar}} dependency to the {{pom.xml}} of the {{ignite-cli}}
> module, for example:
> {code:java}
>
> org.apache.ignite
> ignite-core
> test
> test-jar
> {code}
> 2. Run the following command from the repository root:
> {code:java}
> mvn package -Dmaven.test.skip -Dmaven.all-checks.skip
> {code}
> h2. Expected behavior
> The project is built successfully.
> h2. Actual behavior
> The project cannot be built and the following error appears:
> {code:java}
> [ERROR] Failed to execute goal on project ignite-cli: Could not resolve
> dependencies for project org.apache.ignite:ignite-cli:jar:3.0.0-SNAPSHOT:
> Could not find artifact
> org.apache.ignite:ignite-core:jar:tests:3.0.0-SNAPSHOT in apache.snapshots
> (https://repository.apache.org/snapshots) -> [Help 1]
> {code}
> h2. Supposed cause
> {{ignite-cli}} module uses the {{maven-antrun-plugin}} to create a
> self-executing JAR. This plugin requires the test dependencies to be present
> during the {{package}} execution phase (see the [source
> code|https://github.com/apache/maven-antrun-plugin/blob/master/src/main/java/org/apache/maven/plugins/antrun/AntRunMojo.java#L67]),
> which are not created because of the {{maven.test.skip}} flag.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15676) .NET: Fix update-version.sh
[ https://issues.apache.org/jira/browse/IGNITE-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-15676: Component/s: platforms > .NET: Fix update-version.sh > --- > > Key: IGNITE-15676 > URL: https://issues.apache.org/jira/browse/IGNITE-15676 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > update-version.sh doesn't update .Net version after IGNITE-15665 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15676) .NET: Fix update-version.sh
[ https://issues.apache.org/jira/browse/IGNITE-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-15676: Fix Version/s: 2.12 > .NET: Fix update-version.sh > --- > > Key: IGNITE-15676 > URL: https://issues.apache.org/jira/browse/IGNITE-15676 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > update-version.sh doesn't update .Net version after IGNITE-15665 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15676) .NET: Fix update-version.sh
[ https://issues.apache.org/jira/browse/IGNITE-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-15676: Ignite Flags: (was: Docs Required,Release Notes Required) > .NET: Fix update-version.sh > --- > > Key: IGNITE-15676 > URL: https://issues.apache.org/jira/browse/IGNITE-15676 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > update-version.sh doesn't update .Net version after IGNITE-15665 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-15665: Fix Version/s: 2.12 > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15676) .NET: Fix update-version.sh
[ https://issues.apache.org/jira/browse/IGNITE-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-15676: Labels: .NET (was: ) > .NET: Fix update-version.sh > --- > > Key: IGNITE-15676 > URL: https://issues.apache.org/jira/browse/IGNITE-15676 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > update-version.sh doesn't update .Net version after IGNITE-15665 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-15665. - Resolution: Fixed > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-15665: Component/s: platforms > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-15665: Labels: .NET (was: ) > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET > Fix For: 2.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reopened IGNITE-15665: - Ignite Flags: (was: Docs Required,Release Notes Required) > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov resolved IGNITE-15665. -- Resolution: Won't Fix > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15676) .NET: Fix update-version.sh
Nikolay Izhikov created IGNITE-15676: Summary: .NET: Fix update-version.sh Key: IGNITE-15676 URL: https://issues.apache.org/jira/browse/IGNITE-15676 Project: Ignite Issue Type: Bug Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov For now, assembly info duplicated through .Net code. Should use shared assembly info to reduce duplication and diff on version bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15676) .NET: Fix update-version.sh
[ https://issues.apache.org/jira/browse/IGNITE-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-15676: - Description: update-version.sh doesn't update .Net version after IGNITE-15665 (was: For now, assembly info duplicated through .Net code. Should use shared assembly info to reduce duplication and diff on version bump.) > .NET: Fix update-version.sh > --- > > Key: IGNITE-15676 > URL: https://issues.apache.org/jira/browse/IGNITE-15676 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > > update-version.sh doesn't update .Net version after IGNITE-15665 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15675) Ignite CLI commands must fit general logging formatting
[
https://issues.apache.org/jira/browse/IGNITE-15675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15675:
-
Labels: ignite-3 (was: cli ignite-3)
> Ignite CLI commands must fit general logging formatting
>
>
> Key: IGNITE-15675
> URL: https://issues.apache.org/jira/browse/IGNITE-15675
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: ignite-3
>
> When you run, for example,
> {code:bash}
> ./ignite init
> ./ignite node start
> {code}
> output log differs from formatting for ignite, that is described in
> {{config/java.util.logging.properties}}. CLI commands must reuse the common
> config file.
> A possible solution is to pass
> {code:java}
> -Djava.util.logging.config.file=../../config/java.util.logging.properties
> {code}
> in {{modules/cli/ignite.sh}} and in
> {{org.apache.ignite.cli.builtins.node.NodeManager#start}}
>
> Also, this dependency must be added to cli module pom:
> {code:xml}
>
> org.slf4j
> slf4j-jdk14
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15675) Ignite CLI commands must fit general logging formatting
[
https://issues.apache.org/jira/browse/IGNITE-15675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15675:
-
Description:
When you run, for example,
{code:bash}
./ignite init
./ignite node start
{code}
output log differs from formatting for ignite, that is described in
{{config/java.util.logging.properties}}. CLI commands must reuse the common
config file.
A possible solution is to pass
{code:java}
-Djava.util.logging.config.file=../../config/java.util.logging.properties
{code}
in {{modules/cli/ignite.sh}} and in
{{org.apache.ignite.cli.builtins.node.NodeManager#start}}
Also, this dependency must be added to cli module pom:
{code:xml}
org.slf4j
slf4j-jdk14
{code}
was:
When you run, for example,
{code:bash}
./ignite init
./ignite node start
{code}
output log differs from formatting for ignite, that is described in
{{config/java.util.logging.properties}}. CLI commands must reuse the common
config file.
A possible solution is to pass
{code:java}
-Djava.util.logging.config.file=../../config/java.util.logging.properties
{code}
in {{modules/cli/ignite.sh}} and in
{{org.apache.ignite.cli.builtins.node.NodeManager#start}}
Also, this dependency must be added to cli module pom:
{code:xml}
// Some comments here
org.slf4j
slf4j-jdk14
{code}
> Ignite CLI commands must fit general logging formatting
>
>
> Key: IGNITE-15675
> URL: https://issues.apache.org/jira/browse/IGNITE-15675
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: cli, ignite-3
>
> When you run, for example,
> {code:bash}
> ./ignite init
> ./ignite node start
> {code}
> output log differs from formatting for ignite, that is described in
> {{config/java.util.logging.properties}}. CLI commands must reuse the common
> config file.
> A possible solution is to pass
> {code:java}
> -Djava.util.logging.config.file=../../config/java.util.logging.properties
> {code}
> in {{modules/cli/ignite.sh}} and in
> {{org.apache.ignite.cli.builtins.node.NodeManager#start}}
>
> Also, this dependency must be added to cli module pom:
> {code:xml}
>
> org.slf4j
> slf4j-jdk14
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15675) Ignite CLI commands must fit general logging formatting
[
https://issues.apache.org/jira/browse/IGNITE-15675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15675:
-
Description:
When you run, for example,
{code:bash}
./ignite init
./ignite node start
{code}
output log differs from formatting for ignite, that is described in
{{config/java.util.logging.properties}}. CLI commands must reuse the common
config file.
A possible solution is to pass
{code:java}
-Djava.util.logging.config.file=../../config/java.util.logging.properties
{code}
in {{modules/cli/ignite.sh}} and in
{{org.apache.ignite.cli.builtins.node.NodeManager#start}}
Also, this dependency must be added to cli module pom:
{code:xml}
// Some comments here
org.slf4j
slf4j-jdk14
{code}
was:
When you run, for example,
{code:bash}
./ignite init
./ignite node start
{code}
output log differs from formatting for ignite, that is described in
{{config/java.util.logging.properties}}. CLI commands must reuse the common
config file.
A possible solution is to pass
{code:java}
-Djava.util.logging.config.file=../../config/java.util.logging.properties
{code}
in {{modules/cli/ignite.sh}} and in
{{org.apache.ignite.cli.builtins.node.NodeManager#start}}
> Ignite CLI commands must fit general logging formatting
>
>
> Key: IGNITE-15675
> URL: https://issues.apache.org/jira/browse/IGNITE-15675
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: cli, ignite-3
>
> When you run, for example,
> {code:bash}
> ./ignite init
> ./ignite node start
> {code}
> output log differs from formatting for ignite, that is described in
> {{config/java.util.logging.properties}}. CLI commands must reuse the common
> config file.
> A possible solution is to pass
> {code:java}
> -Djava.util.logging.config.file=../../config/java.util.logging.properties
> {code}
> in {{modules/cli/ignite.sh}} and in
> {{org.apache.ignite.cli.builtins.node.NodeManager#start}}
>
> Also, this dependency must be added to cli module pom:
> {code:xml}
> // Some comments here
>
> org.slf4j
> slf4j-jdk14
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15675) Ignite CLI commands must fit general logging formatting
Mirza Aliev created IGNITE-15675:
Summary: Ignite CLI commands must fit general logging formatting
Key: IGNITE-15675
URL: https://issues.apache.org/jira/browse/IGNITE-15675
Project: Ignite
Issue Type: Improvement
Reporter: Mirza Aliev
When you run, for example,
{code:bash}
./ignite init
./ignite node start
{code}
output log differs from formatting for ignite, that is described in
{{config/java.util.logging.properties}}. CLI commands must reuse the common
config file.
A possible solution is to pass
{code:java}
-Djava.util.logging.config.file=../../config/java.util.logging.properties
{code}
in {{modules/cli/ignite.sh}} and in
{{org.apache.ignite.cli.builtins.node.NodeManager#start}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15222) Add test for Metastorage's cursor commands next and hasNext correctly working after Raft leader was changing.
[
https://issues.apache.org/jira/browse/IGNITE-15222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15222:
-
Summary: Add test for Metastorage's cursor commands next and hasNext
correctly working after Raft leader was changing. (was: Metastorage's cursor
commands next and hasNext must work correctly after Raft leader was changing.)
> Add test for Metastorage's cursor commands next and hasNext correctly working
> after Raft leader was changing.
> -
>
> Key: IGNITE-15222
> URL: https://issues.apache.org/jira/browse/IGNITE-15222
> Project: Ignite
> Issue Type: Bug
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> Metastorage's cursor commands next and hasNext are implemented using
> {{CursorNextCommand}} and {{CursorHasNextCommand}} Raft commands, which are
> Raft's Read Commands. Read commands are handled on Raft leader and don't
> replicate to followers. Within the context of cursors, it means that cursor
> position, which is moved by the next command, is stored on leader only and
> might be lost on leader change. It will lead to unexpected side effects on
> the raft client because from the client's point of view, the leader migration
> is seamless and should be invisible. In other words, calling next on leader A
> will only move cursor position on this particular raft node, so that after
> leader migration, the client's next {{next()}} command will be processed on a
> new leader B and will move cursor position again to the same step.
> A possible solution is to change {{CursorNextCommand}} and
> {{CursorHasNextCommand}} to raft's write commands, so they will be replicated
> on the followers and new followers will handle the commands correctly.
> UPD:
> {{CursorNextCommand}} and {{CursorHasNextCommand}} are already raft's write
> commands, so this task contains only test
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15674) Migrates CacheSpringStoreSessionListener to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-15674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-15674: Description: It's proposed to migrate CacheSpringStoreSessionListener to ignite-extensions in ignite-spring-tx module. It helps to take the load off ignite-spring module and to make ignite-spring module responsible only for parsing xml configurations. It also helps to reduce the number of dependencies that ignite-spring relies on. (was: It's proposed t migrate CacheSpringStoreSessionListener to ignite-extensions in ignite-spring-tx module. It helps to take the load off ignite-spring module and to make ignite-spring module responsible only for parsing xml configurations. It also helps to reduce the number of dependencies that ignite-spring relies on.) > Migrates CacheSpringStoreSessionListener to ignite-extensions > - > > Key: IGNITE-15674 > URL: https://issues.apache.org/jira/browse/IGNITE-15674 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > > It's proposed to migrate CacheSpringStoreSessionListener to ignite-extensions > in ignite-spring-tx module. It helps to take the load off ignite-spring > module and to make ignite-spring module responsible only for parsing xml > configurations. It also helps to reduce the number of dependencies that > ignite-spring relies on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15674) Migrates CacheSpringStoreSessionListener to ignite-extensions
Mikhail Petrov created IGNITE-15674: --- Summary: Migrates CacheSpringStoreSessionListener to ignite-extensions Key: IGNITE-15674 URL: https://issues.apache.org/jira/browse/IGNITE-15674 Project: Ignite Issue Type: Improvement Reporter: Mikhail Petrov Assignee: Mikhail Petrov It's proposed t migrate CacheSpringStoreSessionListener to ignite-extensions in ignite-spring-tx module. It helps to take the load off ignite-spring module and to make ignite-spring module responsible only for parsing xml configurations. It also helps to reduce the number of dependencies that ignite-spring relies on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15673) Update Ignite dependency zookeeper
[ https://issues.apache.org/jira/browse/IGNITE-15673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-15673: --- Description: Update Ignite dependency: Zookeeper 3.5.5 to 3.7.0 (was: Update Ignite dependency: Zookeeper) > Update Ignite dependency zookeeper > -- > > Key: IGNITE-15673 > URL: https://issues.apache.org/jira/browse/IGNITE-15673 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update Ignite dependency: Zookeeper 3.5.5 to 3.7.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15673) Update Ignite dependency zookeeper
[ https://issues.apache.org/jira/browse/IGNITE-15673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-15673: --- Labels: newbie (was: ) > Update Ignite dependency zookeeper > -- > > Key: IGNITE-15673 > URL: https://issues.apache.org/jira/browse/IGNITE-15673 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > > Update Ignite dependency: Zookeeper -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15673) Update Ignite dependency zookeeper
Aleksandr created IGNITE-15673: -- Summary: Update Ignite dependency zookeeper Key: IGNITE-15673 URL: https://issues.apache.org/jira/browse/IGNITE-15673 Project: Ignite Issue Type: Improvement Reporter: Aleksandr Assignee: Aleksandr Update Ignite dependency: Zookeeper -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15673) Update Ignite dependency zookeeper
[ https://issues.apache.org/jira/browse/IGNITE-15673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-15673: --- Fix Version/s: 2.12 > Update Ignite dependency zookeeper > -- > > Key: IGNITE-15673 > URL: https://issues.apache.org/jira/browse/IGNITE-15673 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update Ignite dependency: Zookeeper -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15504) .NET: SDK 2.1 is out of support, make sure project can be developed with newer SDKs
[
https://issues.apache.org/jira/browse/IGNITE-15504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15504:
Description:
* our projects target netcoreapp2.0
* .NET SDK 2.x versions are out of support
As a result, developers are required to use an out-of-support version of .NET
SDK.
.NET Framework Support Policy:
https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
.NET Standard Compatibility Table:
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
*Action Items:*
* Switch libraries to netstandard2.0
* Switch legacy libraries to the supported version of the .NET Framework
* Switch csproj files to the new SDK-based format
* Fix examples
* Remove all conditional compilation ('#if')
* Update build script
** "dotnet build" can be used to build everything, including Full Framework
solution
*** [.NET 5 SDK can build net461 projects on any OS without extra
steps|https://stackoverflow.com/questions/57382030/simplest-way-to-build-dotnet-sdk-project-requiring-net461-on-macos]
** "dotnet pack" can pack NuGet packages
*** Get rid of nuspec files
was:
* our projects target netcoreapp2.0
* .NET SDK 2.x versions are out of support
As a result, developers are required to use an out-of-support version of .NET
SDK.
.NET Framework Support Policy:
https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
.NET Standard Compatibility Table:
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
*Action Items:*
* Switch libraries to netstandard2.0
* Switch legacy libraries to the supported version of the .NET Framework
* Switch csproj files to the new SDK-based format
* Fix examples
* Remove all conditional compilation ('#if')
* Update build script
** "dotnet build" can be used to build everything, including Full Framework
solution
*** [.NET 5 SDK can build net461 projects on any OS without extra
steps|https://stackoverflow.com/questions/57382030/simplest-way-to-build-dotnet-sdk-project-requiring-net461-on-macos]
** "dotnet pack" can pack NuGet packages
> .NET: SDK 2.1 is out of support, make sure project can be developed with
> newer SDKs
> ---
>
> Key: IGNITE-15504
> URL: https://issues.apache.org/jira/browse/IGNITE-15504
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.11
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
> Labels: .NET
> Fix For: 2.12
>
>
> * our projects target netcoreapp2.0
> * .NET SDK 2.x versions are out of support
> As a result, developers are required to use an out-of-support version of .NET
> SDK.
> .NET Framework Support Policy:
> https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
> .NET Standard Compatibility Table:
> https://docs.microsoft.com/en-us/dotnet/standard/net-standard
> *Action Items:*
> * Switch libraries to netstandard2.0
> * Switch legacy libraries to the supported version of the .NET Framework
> * Switch csproj files to the new SDK-based format
> * Fix examples
> * Remove all conditional compilation ('#if')
> * Update build script
> ** "dotnet build" can be used to build everything, including Full Framework
> solution
> *** [.NET 5 SDK can build net461 projects on any OS without extra
> steps|https://stackoverflow.com/questions/57382030/simplest-way-to-build-dotnet-sdk-project-requiring-net461-on-macos]
> ** "dotnet pack" can pack NuGet packages
> *** Get rid of nuspec files
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15132) REST API must reuse general netty infrastructure from network module
[ https://issues.apache.org/jira/browse/IGNITE-15132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-15132: - Labels: ignite-3 tech-debt (was: ) > REST API must reuse general netty infrastructure from network module > > > Key: IGNITE-15132 > URL: https://issues.apache.org/jira/browse/IGNITE-15132 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Priority: Major > Labels: ignite-3, tech-debt > > At the moment - RestModule prepares its own Netty infra for handling > requests. But it will be great to have one root Netty pools and etc. configs > and just separate handlers. > Also, maybe we should use the "one port for all operations" concept for REST > API too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15504) .NET: SDK 2.1 is out of support, make sure project can be developed with newer SDKs
[
https://issues.apache.org/jira/browse/IGNITE-15504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15504:
Description:
* our projects target netcoreapp2.0
* .NET SDK 2.x versions are out of support
As a result, developers are required to use an out-of-support version of .NET
SDK.
.NET Framework Support Policy:
https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
.NET Standard Compatibility Table:
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
*Action Items:*
* Switch libraries to netstandard2.0
* Switch legacy libraries to the supported version of the .NET Framework
* Switch csproj files to the new SDK-based format
* Fix examples
* Remove all conditional compilation ('#if')
* Update build script
** "dotnet build" can be used to build everything, including Full Framework
solution
*** [.NET 5 SDK can build net461 projects on any OS without extra
steps|https://stackoverflow.com/questions/57382030/simplest-way-to-build-dotnet-sdk-project-requiring-net461-on-macos]
** "dotnet pack" can pack NuGet packages
was:
* our projects target netcoreapp2.0
* .NET SDK 2.x versions are out of support
As a result, developers are required to use an out-of-support version of .NET
SDK.
.NET Framework Support Policy:
https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
.NET Standard Compatibility Table:
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
*Action Items:*
* Switch libraries to netstandard2.0
* Switch legacy libraries to the supported version of the .NET Framework
* Switch csproj files to the new SDK-based format
* Fix examples
* Remove all conditional compilation ('#if')
* Update build script
** "dotnet build" can be used to build everything, including Full Framework
solution
*** .NET 5 SDK can build net461 projects on any OS without extra steps
** "dotnet pack" can pack NuGet packages
> .NET: SDK 2.1 is out of support, make sure project can be developed with
> newer SDKs
> ---
>
> Key: IGNITE-15504
> URL: https://issues.apache.org/jira/browse/IGNITE-15504
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.11
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
> Labels: .NET
> Fix For: 2.12
>
>
> * our projects target netcoreapp2.0
> * .NET SDK 2.x versions are out of support
> As a result, developers are required to use an out-of-support version of .NET
> SDK.
> .NET Framework Support Policy:
> https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
> .NET Standard Compatibility Table:
> https://docs.microsoft.com/en-us/dotnet/standard/net-standard
> *Action Items:*
> * Switch libraries to netstandard2.0
> * Switch legacy libraries to the supported version of the .NET Framework
> * Switch csproj files to the new SDK-based format
> * Fix examples
> * Remove all conditional compilation ('#if')
> * Update build script
> ** "dotnet build" can be used to build everything, including Full Framework
> solution
> *** [.NET 5 SDK can build net461 projects on any OS without extra
> steps|https://stackoverflow.com/questions/57382030/simplest-way-to-build-dotnet-sdk-project-requiring-net461-on-macos]
> ** "dotnet pack" can pack NuGet packages
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15504) .NET: SDK 2.1 is out of support, make sure project can be developed with newer SDKs
[
https://issues.apache.org/jira/browse/IGNITE-15504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15504:
Description:
* our projects target netcoreapp2.0
* .NET SDK 2.x versions are out of support
As a result, developers are required to use an out-of-support version of .NET
SDK.
.NET Framework Support Policy:
https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
.NET Standard Compatibility Table:
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
*Action Items:*
* Switch libraries to netstandard2.0
* Switch legacy libraries to the supported version of the .NET Framework
* Switch csproj files to the new SDK-based format
* Fix examples
* Remove all conditional compilation ('#if')
* Update build script
** "dotnet build" can be used to build everything, including Full Framework
solution
*** .NET 5 SDK can build net461 projects on any OS without extra steps
** "dotnet pack" can pack NuGet packages
was:
* our projects target netcoreapp2.0
* .NET SDK 2.x versions are out of support
As a result, developers are required to use an out-of-support version of .NET
SDK.
.NET Framework Support Policy:
https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
.NET Standard Compatibility Table:
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
*Action Items:*
* Switch libraries to netstandard2.0
* Switch legacy libraries to the supported version of the .NET Framework
* Switch csproj files to the new SDK-based format
* Fix examples
* Remove all conditional compilation ('#if')
* Update build script
** "dotnet build" can be used to build everything, including Full Framework
solution
** "dotnet pack" can pack NuGet packages
> .NET: SDK 2.1 is out of support, make sure project can be developed with
> newer SDKs
> ---
>
> Key: IGNITE-15504
> URL: https://issues.apache.org/jira/browse/IGNITE-15504
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.11
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
> Labels: .NET
> Fix For: 2.12
>
>
> * our projects target netcoreapp2.0
> * .NET SDK 2.x versions are out of support
> As a result, developers are required to use an out-of-support version of .NET
> SDK.
> .NET Framework Support Policy:
> https://docs.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
> .NET Standard Compatibility Table:
> https://docs.microsoft.com/en-us/dotnet/standard/net-standard
> *Action Items:*
> * Switch libraries to netstandard2.0
> * Switch legacy libraries to the supported version of the .NET Framework
> * Switch csproj files to the new SDK-based format
> * Fix examples
> * Remove all conditional compilation ('#if')
> * Update build script
> ** "dotnet build" can be used to build everything, including Full Framework
> solution
> *** .NET 5 SDK can build net461 projects on any OS without extra steps
> ** "dotnet pack" can pack NuGet packages
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reopened IGNITE-15665: - > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15665) .NET: Use shared assembly info
[ https://issues.apache.org/jira/browse/IGNITE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423879#comment-17423879 ] Pavel Tupitsyn commented on IGNITE-15665: - [~nizhikov] looks like we've broken the version update script which relies on exact "AssemblyInfo.cs" file name: https://github.com/apache/ignite/blob/6cae6afe51b63ae77aa5ec67912ea1c6476fbf0b/pom.xml#L670. Can you please update this as well? > .NET: Use shared assembly info > --- > > Key: IGNITE-15665 > URL: https://issues.apache.org/jira/browse/IGNITE-15665 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > For now, assembly info duplicated through .Net code. > Should use shared assembly info to reduce duplication and diff on version > bump. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14693) Implement MetaStorage exception handling logic.
[ https://issues.apache.org/jira/browse/IGNITE-14693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-14693: - Labels: iep-61 ignite-3 tech-debt (was: iep-61 ignite-3) > Implement MetaStorage exception handling logic. > --- > > Key: IGNITE-14693 > URL: https://issues.apache.org/jira/browse/IGNITE-14693 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: iep-61, ignite-3, tech-debt > > It's required to implement MetaStorage exception handling logic both for > onError() and (CompactedException | OperationTimeoutException) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15663) Set default batch sized to 1 until the striped disruptor is not fixed
[ https://issues.apache.org/jira/browse/IGNITE-15663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15663: - Summary: Set default batch sized to 1 until the striped disruptor is not fixed (was: Set default batch sized to 1 until the striped disruptor does not fixed) > Set default batch sized to 1 until the striped disruptor is not fixed > - > > Key: IGNITE-15663 > URL: https://issues.apache.org/jira/browse/IGNITE-15663 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 40m > Remaining Estimate: 0h > > It is a workaround of root issue, which described in detail in the issue > here: IGNITE-15568. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15371) [Ignite 3] Switch to Google code style
[ https://issues.apache.org/jira/browse/IGNITE-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko reassigned IGNITE-15371: Assignee: Kirill Tkalenko (was: Petr Ivanov) > [Ignite 3] Switch to Google code style > -- > > Key: IGNITE-15371 > URL: https://issues.apache.org/jira/browse/IGNITE-15371 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Attachments: ignite-checks.xml > > > As agreed in [1], we need to switch to the Google code style with two changes: > * 140 column limit instead of 100 > * 4/8 spaces indentation instead of 2/4 > The updated XML file for the Checkstyle Plugin is attached. > Also, > # Create coding guideline wiki page for Ignite 3 > # Update links to CONTRIBUTING.md > [1] > https://lists.apache.org/thread.html/rfa1e775f27b99b1f14c356e25cc52f83eb90c7553db1f1a2aba136c6%40%3Cdev.ignite.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15406) Ignite, Ignition and IgniteManager should be moved to org.apache.ignite package
[ https://issues.apache.org/jira/browse/IGNITE-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15406: - Reviewer: Mirza Aliev > Ignite, Ignition and IgniteManager should be moved to org.apache.ignite > package > --- > > Key: IGNITE-15406 > URL: https://issues.apache.org/jira/browse/IGNITE-15406 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, _Ignite_, _Ignition_, and _IgniteManager_ are placed into > _org.apache.ignite.app_ package. > This does not seem like a correct package, especially _app_ subpackage looks > weird to me. > Looks like we should just move these interfaces to _org.apache.ignite._ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15663) Set default batch sized to 1 until the striped disruptor does not fixed
[ https://issues.apache.org/jira/browse/IGNITE-15663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15663: - Fix Version/s: 3.0.0-alpha3 > Set default batch sized to 1 until the striped disruptor does not fixed > --- > > Key: IGNITE-15663 > URL: https://issues.apache.org/jira/browse/IGNITE-15663 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It is a workaround of root issue, which described in detail in the issue > here: IGNITE-15568. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15191) Ignite 3 CLI 'node list' command: bad wording
[
https://issues.apache.org/jira/browse/IGNITE-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15191:
-
Fix Version/s: 3.0.0-alpha3
> Ignite 3 CLI 'node list' command: bad wording
> -
>
> Key: IGNITE-15191
> URL: https://issues.apache.org/jira/browse/IGNITE-15191
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Valentin Kulichenko
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> The {{node list}} command shows the following output if there is only one
> node running:
> {noformat}
> Currently, there are 1 nodes...
> {noformat}
> The wording is wrong. We can replace it with a more generic option, similar
> to this:
> {noformat}
> Number of running nodes: 1
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14681) Calcite engine. Extend return type of sum() aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14681:
--
Description:
Currently, {{sum()}} aggregate function returns the same type as an argument
and there can be an overflow.
For example, query:
{noformat}
SELECT SUM(i::SMALLINT) FROM (SELECT 32000 as i UNION ALL SELECT
32000){noformat}
Returns {{-1536}}.
or
{noformat}
CREATE TABLE integers(i INTEGER);
INSERT INTO integers SELECT * FROM table(system_range(0, 999, 1));
SELECT SUM(b) FROM bigints
{noformat}
Returns {{499500}} instead of {{4611686018427388403500}}.
Perhaps it would be better to return an extended type as some other vendors do.
For example, PostgreSQL returns {{bigint}} for {{smallint}} or {{int}}
arguments, {{numeric}} for {{bigint}} arguments, {{double precision}} for
floating-point arguments. MySQL returns a {{DECIMAL}} value for exact-value
arguments ({{INTEGER}} or {{DECIMAL}}), and a {{DOUBLE}} value for
approximate-value arguments ({{FLOAT}} or {{DOUBLE}})
Affected tests:
{{modules/calcite/src/test/sql/aggregate/aggregates/test_sum.test_ignore}}
Result type of SUM:
|| Argument type || SUM type ||
| TINYINT
SMALLINT
INTEGER | BIGINT |
| REAL
FLOAT
DOUBLE | DOUBLE |
| BIGINT
DECIMAL | DECIMAL |
| other *type* | the same *type* |
was:
Currently, {{sum()}} aggregate function returns the same type as an argument
and there can be an overflow.
For example, query:
{noformat}
SELECT SUM(i::SMALLINT) FROM (SELECT 32000 as i UNION ALL SELECT
32000){noformat}
Returns {{-1536}}.
or
{noformat}
CREATE TABLE integers(i INTEGER);
INSERT INTO integers SELECT * FROM table(system_range(0, 999, 1));
SELECT SUM(b) FROM bigints
{noformat}
Returns {{499500}} instead of {{4611686018427388403500}}.
Perhaps it would be better to return an extended type as some other vendors do.
For example, PostgreSQL returns {{bigint}} for {{smallint}} or {{int}}
arguments, {{numeric}} for {{bigint}} arguments, {{double precision}} for
floating-point arguments. MySQL returns a {{DECIMAL}} value for exact-value
arguments ({{INTEGER}} or {{DECIMAL}}), and a {{DOUBLE}} value for
approximate-value arguments ({{FLOAT}} or {{DOUBLE}})
Affected tests:
{{modules/calcite/src/test/sql/aggregate/aggregates/test_sum.test_ignore}}
> Calcite engine. Extend return type of sum() aggregate function
> --
>
> Key: IGNITE-14681
> URL: https://issues.apache.org/jira/browse/IGNITE-14681
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Currently, {{sum()}} aggregate function returns the same type as an argument
> and there can be an overflow.
> For example, query:
> {noformat}
> SELECT SUM(i::SMALLINT) FROM (SELECT 32000 as i UNION ALL SELECT
> 32000){noformat}
> Returns {{-1536}}.
> or
> {noformat}
> CREATE TABLE integers(i INTEGER);
> INSERT INTO integers SELECT * FROM table(system_range(0, 999, 1));
> SELECT SUM(b) FROM bigints
> {noformat}
> Returns {{499500}} instead of {{4611686018427388403500}}.
> Perhaps it would be better to return an extended type as some other vendors
> do.
> For example, PostgreSQL returns {{bigint}} for {{smallint}} or {{int}}
> arguments, {{numeric}} for {{bigint}} arguments, {{double precision}} for
> floating-point arguments. MySQL returns a {{DECIMAL}} value for exact-value
> arguments ({{INTEGER}} or {{DECIMAL}}), and a {{DOUBLE}} value for
> approximate-value arguments ({{FLOAT}} or {{DOUBLE}})
> Affected tests:
> {{modules/calcite/src/test/sql/aggregate/aggregates/test_sum.test_ignore}}
> Result type of SUM:
> || Argument type || SUM type ||
> | TINYINT
> SMALLINT
> INTEGER | BIGINT |
> | REAL
> FLOAT
> DOUBLE | DOUBLE |
> | BIGINT
> DECIMAL | DECIMAL |
> | other *type* | the same *type* |
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14681) Calcite engine. Extend return type of sum() aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423846#comment-17423846
]
Evgeny Stanilovsky commented on IGNITE-14681:
-
looks good.
> Calcite engine. Extend return type of sum() aggregate function
> --
>
> Key: IGNITE-14681
> URL: https://issues.apache.org/jira/browse/IGNITE-14681
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Currently, {{sum()}} aggregate function returns the same type as an argument
> and there can be an overflow.
> For example, query:
> {noformat}
> SELECT SUM(i::SMALLINT) FROM (SELECT 32000 as i UNION ALL SELECT
> 32000){noformat}
> Returns {{-1536}}.
> or
> {noformat}
> CREATE TABLE integers(i INTEGER);
> INSERT INTO integers SELECT * FROM table(system_range(0, 999, 1));
> SELECT SUM(b) FROM bigints
> {noformat}
> Returns {{499500}} instead of {{4611686018427388403500}}.
> Perhaps it would be better to return an extended type as some other vendors
> do.
> For example, PostgreSQL returns {{bigint}} for {{smallint}} or {{int}}
> arguments, {{numeric}} for {{bigint}} arguments, {{double precision}} for
> floating-point arguments. MySQL returns a {{DECIMAL}} value for exact-value
> arguments ({{INTEGER}} or {{DECIMAL}}), and a {{DOUBLE}} value for
> approximate-value arguments ({{FLOAT}} or {{DOUBLE}})
> Affected tests:
> {{modules/calcite/src/test/sql/aggregate/aggregates/test_sum.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15484) SQL allows "create index" query with duplicated columns
[ https://issues.apache.org/jira/browse/IGNITE-15484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423832#comment-17423832 ] Yury Gerzhedovich commented on IGNITE-15484: [~timonin.maksim], LGTM > SQL allows "create index" query with duplicated columns > --- > > Key: IGNITE-15484 > URL: https://issues.apache.org/jira/browse/IGNITE-15484 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > This query should forbid such queries and raise an exception: > "create index IDX on table (id ASC, id DESC);" > Now it creates index last appearance of the field, in this case (id DESC). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14681) Calcite engine. Extend return type of sum() aggregate function
[
https://issues.apache.org/jira/browse/IGNITE-14681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423831#comment-17423831
]
Taras Ledkov commented on IGNITE-14681:
---
The ticket to patch calcite is created: CALCITE-4818
> Calcite engine. Extend return type of sum() aggregate function
> --
>
> Key: IGNITE-14681
> URL: https://issues.apache.org/jira/browse/IGNITE-14681
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Currently, {{sum()}} aggregate function returns the same type as an argument
> and there can be an overflow.
> For example, query:
> {noformat}
> SELECT SUM(i::SMALLINT) FROM (SELECT 32000 as i UNION ALL SELECT
> 32000){noformat}
> Returns {{-1536}}.
> or
> {noformat}
> CREATE TABLE integers(i INTEGER);
> INSERT INTO integers SELECT * FROM table(system_range(0, 999, 1));
> SELECT SUM(b) FROM bigints
> {noformat}
> Returns {{499500}} instead of {{4611686018427388403500}}.
> Perhaps it would be better to return an extended type as some other vendors
> do.
> For example, PostgreSQL returns {{bigint}} for {{smallint}} or {{int}}
> arguments, {{numeric}} for {{bigint}} arguments, {{double precision}} for
> floating-point arguments. MySQL returns a {{DECIMAL}} value for exact-value
> arguments ({{INTEGER}} or {{DECIMAL}}), and a {{DOUBLE}} value for
> approximate-value arguments ({{FLOAT}} or {{DOUBLE}})
> Affected tests:
> {{modules/calcite/src/test/sql/aggregate/aggregates/test_sum.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15191) Ignite 3 CLI 'node list' command: bad wording
[
https://issues.apache.org/jira/browse/IGNITE-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15191:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Ignite 3 CLI 'node list' command: bad wording
> -
>
> Key: IGNITE-15191
> URL: https://issues.apache.org/jira/browse/IGNITE-15191
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Valentin Kulichenko
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
>
> The {{node list}} command shows the following output if there is only one
> node running:
> {noformat}
> Currently, there are 1 nodes...
> {noformat}
> The wording is wrong. We can replace it with a more generic option, similar
> to this:
> {noformat}
> Number of running nodes: 1
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15191) Ignite 3 CLI 'node list' command: bad wording
[
https://issues.apache.org/jira/browse/IGNITE-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-15191:
Assignee: Vyacheslav Koptilin
> Ignite 3 CLI 'node list' command: bad wording
> -
>
> Key: IGNITE-15191
> URL: https://issues.apache.org/jira/browse/IGNITE-15191
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Valentin Kulichenko
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
>
> The {{node list}} command shows the following output if there is only one
> node running:
> {noformat}
> Currently, there are 1 nodes...
> {noformat}
> The wording is wrong. We can replace it with a more generic option, similar
> to this:
> {noformat}
> Number of running nodes: 1
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15267) A lot of spam in logs on thick client: "Unable to save statistics obsolescence info on non server node."
[ https://issues.apache.org/jira/browse/IGNITE-15267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-15267: -- Fix Version/s: 2.12 > A lot of spam in logs on thick client: "Unable to save statistics > obsolescence info on non server node." > > > Key: IGNITE-15267 > URL: https://issues.apache.org/jira/browse/IGNITE-15267 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.10 >Reporter: Ilya Kazakov >Assignee: Alexander Belyak >Priority: Major > Fix For: 2.12 > > Time Spent: 1h > Remaining Estimate: 0h > > In logs on thick client there are a lot of such messages: > 2021-08-05 18:28:26,870 17371453 INFO > [grid-timeout-worker-#22%member-checkin-data-s] java.JavaLogger ( > JavaLogger.java: 284) - Unable to save statistics obsolescence info on non > server node. > It looks like unexpected calls to save stat on thick client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15672) Disable pylint for ducktests
[ https://issues.apache.org/jira/browse/IGNITE-15672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15672: - Priority: Minor (was: Major) > Disable pylint for ducktests > > > Key: IGNITE-15672 > URL: https://issues.apache.org/jira/browse/IGNITE-15672 > Project: Ignite > Issue Type: Test >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Pylint is sensitive for different versions of dependencies. It leads to > unpredictable travis builds. Let's remove pylint, as we already have the > flake8 check. > For example reason of this failed is changed version of dependency filelock. > > [https://app.travis-ci.com/github/apache/ignite/jobs/540986717] > > * > ** > *** > > * > ** > *** > > * > ** > *** > > * Module ignitetest.services.utils.ignite_aware > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'WindowsFileLock' with abstract methods instantiated > (abstract-class-instantiated) > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'UnixFileLock' with abstract methods instantiated > (abstract-class-instantiated) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15672) Disable pylint for ducktests
[ https://issues.apache.org/jira/browse/IGNITE-15672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15672: - Issue Type: Test (was: New Feature) > Disable pylint for ducktests > > > Key: IGNITE-15672 > URL: https://issues.apache.org/jira/browse/IGNITE-15672 > Project: Ignite > Issue Type: Test >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Pylint is sensitive for different versions of dependencies. It leads to > unpredictable travis builds. Let's remove pylint, as we already have the > flake8 check. > For example reason of this failed is changed version of dependency filelock. > > [https://app.travis-ci.com/github/apache/ignite/jobs/540986717] > > * > ** > *** > > * > ** > *** > > * > ** > *** > > * Module ignitetest.services.utils.ignite_aware > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'WindowsFileLock' with abstract methods instantiated > (abstract-class-instantiated) > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'UnixFileLock' with abstract methods instantiated > (abstract-class-instantiated) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15668) Commented code without ticket link in ignite-calcite
[ https://issues.apache.org/jira/browse/IGNITE-15668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-15668: -- Fix Version/s: 3.0.0-alpha3 > Commented code without ticket link in ignite-calcite > > > Key: IGNITE-15668 > URL: https://issues.apache.org/jira/browse/IGNITE-15668 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3, tech-debt > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > Let's clean up this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15108) Integrate with actual data layer in Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-15108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-15108: -- Fix Version/s: 3.0.0-alpha3 > Integrate with actual data layer in Ignite 3.0 > -- > > Key: IGNITE-15108 > URL: https://issues.apache.org/jira/browse/IGNITE-15108 > Project: Ignite > Issue Type: Sub-task > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 1h > Remaining Estimate: 0h > > Need to implement TableScan and probably IndexScan nodes that read a real > data from storage as well as rest accompanying code to convert data storage > rows to calcite's rows and vice versa. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15668) Commented code without ticket link in ignite-calcite
[ https://issues.apache.org/jira/browse/IGNITE-15668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423793#comment-17423793 ] Taras Ledkov commented on IGNITE-15668: --- Merged to [main|https://github.com/apache/ignite-3/commit/a9702234d3a535d537f55853e8062d6a833cc5b6] > Commented code without ticket link in ignite-calcite > > > Key: IGNITE-15668 > URL: https://issues.apache.org/jira/browse/IGNITE-15668 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3, tech-debt > Time Spent: 10m > Remaining Estimate: 0h > > Let's clean up this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15672) Disable pylint for ducktests
[ https://issues.apache.org/jira/browse/IGNITE-15672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-15672: Description: Pylint is sensitive for different versions of dependencies. It leads to unpredictable travis builds. Let's remove pylint, as we already have the flake8 check. For example reason of this failed is changed version of dependency filelock. [https://app.travis-ci.com/github/apache/ignite/jobs/540986717] * ** *** * ** *** * ** *** * Module ignitetest.services.utils.ignite_aware ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class 'WindowsFileLock' with abstract methods instantiated (abstract-class-instantiated) ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class 'UnixFileLock' with abstract methods instantiated (abstract-class-instantiated) was: Reason is changed version of dependency filelock. Should be fixed in requirements. [https://app.travis-ci.com/github/apache/ignite/jobs/540986717] * Module ignitetest.services.utils.ignite_aware ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class 'WindowsFileLock' with abstract methods instantiated (abstract-class-instantiated) ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class 'UnixFileLock' with abstract methods instantiated (abstract-class-instantiated) > Disable pylint for ducktests > > > Key: IGNITE-15672 > URL: https://issues.apache.org/jira/browse/IGNITE-15672 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > Pylint is sensitive for different versions of dependencies. It leads to > unpredictable travis builds. Let's remove pylint, as we already have the > flake8 check. > For example reason of this failed is changed version of dependency filelock. > > [https://app.travis-ci.com/github/apache/ignite/jobs/540986717] > > * > ** > *** > > * > ** > *** > > * > ** > *** > > * Module ignitetest.services.utils.ignite_aware > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'WindowsFileLock' with abstract methods instantiated > (abstract-class-instantiated) > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'UnixFileLock' with abstract methods instantiated > (abstract-class-instantiated) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15672) Disable pylint for ducktests
[ https://issues.apache.org/jira/browse/IGNITE-15672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-15672: Summary: Disable pylint for ducktests (was: Travis py38 build failed) > Disable pylint for ducktests > > > Key: IGNITE-15672 > URL: https://issues.apache.org/jira/browse/IGNITE-15672 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > Reason is changed version of dependency filelock. Should be fixed in > requirements. > > [https://app.travis-ci.com/github/apache/ignite/jobs/540986717] > > * Module ignitetest.services.utils.ignite_aware > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'WindowsFileLock' with abstract methods instantiated > (abstract-class-instantiated) > ignitetest/services/utils/ignite_aware.py:205:13: E0110: Abstract class > 'UnixFileLock' with abstract methods instantiated > (abstract-class-instantiated) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14703) Add merge-sort reducer for cache queries.
[
https://issues.apache.org/jira/browse/IGNITE-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423770#comment-17423770
]
Ignite TC Bot commented on IGNITE-14703:
{panel:title=Branch: [pull/9081/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9081/head] Base: [master] : New Tests
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
13|https://ci.ignite.apache.org/viewLog.html?buildId=6208551]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=7] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=8] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=1] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=2] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=5] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=6] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=3] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=4] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryHighLimitedMultiplePages -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryMultiplePagesNoLimit -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryLimitedMultiplePages -
PASSED{color}
... and 2 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6208321buildTypeId=IgniteTests24Java8_RunAll]
> Add merge-sort reducer for cache queries.
> -
>
> Key: IGNITE-14703
> URL: https://issues.apache.org/jira/browse/IGNITE-14703
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maksim Timonin
>Assignee: Maksim Timonin
>Priority: Major
> Labels: IEP-71
> Time Spent: 23h
> Remaining Estimate: 0h
>
> MergeSort reducer is required for TextQueries (and IndexQuery in future) that
> should provide a sorted result for user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
