[jira] [Assigned] (IGNITE-15883) Remove VariableDeclarationUsageDistance from check-rules/checkstyle-rules.xml
[ https://issues.apache.org/jira/browse/IGNITE-15883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko reassigned IGNITE-15883: Assignee: Kirill Tkalenko > Remove VariableDeclarationUsageDistance from check-rules/checkstyle-rules.xml > - > > Key: IGNITE-15883 > URL: https://issues.apache.org/jira/browse/IGNITE-15883 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0-alpha3 >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > > Remove *VariableDeclarationUsageDistance* from > *check-rules/checkstyle-rules.xml* as it is not strict according to the [code > style|https://google.github.io/styleguide/javaguide.html#s4.8.2-variable-declarations]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15882) Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
[
https://issues.apache.org/jira/browse/IGNITE-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441554#comment-17441554
]
Sergey Chugunov commented on IGNITE-15882:
--
[~ktkale...@gridgain.com] , patch looks good to me, I merged it to master
branch in commit {*}1649eb2a1433f7bdfd01a992b67320e3e76be005{*}.
Thank you for contribution!
> Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
> ---
>
> Key: IGNITE-15882
> URL: https://issues.apache.org/jira/browse/IGNITE-15882
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Need to add check *log.isInfoEnabled()* to the
> *GridCacheDatabaseSharedManager* to avoid log messages like this:
> {noformat}
> [2021-08-09 23:35:37,036][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Starting
> binary memory restore for: [-553318133, -553313514, -553318319, -553317295,
> -553317296, -553317293, -553317294, -628844388, -628844387, -628844386,
> -628844385, -628844392, -628844391, -628844390, -628844389, 1648696228,
> 1648696225, 1648696227, 1648696226, -553318226, -553318412, -2100569601,
> 374280891, 374280890, 374280889, 374280888, 374280887, 374280886, 374280885,
> 374280884, -553313607]
> [2021-08-09 23:35:37,886][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Found last
> checkpoint marker [cpId=dcfe9626-f4f5-4772-930e-73749f55b727,
> pos=FileWALPointer [idx=0, fileOff=3094925, len=135903]]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15882) Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
[
https://issues.apache.org/jira/browse/IGNITE-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-15882:
-
Reviewer: Sergey Chugunov (was: Ivan Bessonov)
> Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
> ---
>
> Key: IGNITE-15882
> URL: https://issues.apache.org/jira/browse/IGNITE-15882
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to add check *log.isInfoEnabled()* to the
> *GridCacheDatabaseSharedManager* to avoid log messages like this:
> {noformat}
> [2021-08-09 23:35:37,036][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Starting
> binary memory restore for: [-553318133, -553313514, -553318319, -553317295,
> -553317296, -553317293, -553317294, -628844388, -628844387, -628844386,
> -628844385, -628844392, -628844391, -628844390, -628844389, 1648696228,
> 1648696225, 1648696227, 1648696226, -553318226, -553318412, -2100569601,
> 374280891, 374280890, 374280889, 374280888, 374280887, 374280886, 374280885,
> 374280884, -553313607]
> [2021-08-09 23:35:37,886][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Found last
> checkpoint marker [cpId=dcfe9626-f4f5-4772-930e-73749f55b727,
> pos=FileWALPointer [idx=0, fileOff=3094925, len=135903]]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-15882) Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
[
https://issues.apache.org/jira/browse/IGNITE-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441062#comment-17441062
]
Kirill Tkalenko edited comment on IGNITE-15882 at 11/10/21, 7:34 AM:
-
[~sergeychugunov] Please make code review.
was (Author: ktkale...@gridgain.com):
[~ibessonov] Please make code review.
> Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
> ---
>
> Key: IGNITE-15882
> URL: https://issues.apache.org/jira/browse/IGNITE-15882
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to add check *log.isInfoEnabled()* to the
> *GridCacheDatabaseSharedManager* to avoid log messages like this:
> {noformat}
> [2021-08-09 23:35:37,036][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Starting
> binary memory restore for: [-553318133, -553313514, -553318319, -553317295,
> -553317296, -553317293, -553317294, -628844388, -628844387, -628844386,
> -628844385, -628844392, -628844391, -628844390, -628844389, 1648696228,
> 1648696225, 1648696227, 1648696226, -553318226, -553318412, -2100569601,
> 374280891, 374280890, 374280889, 374280888, 374280887, 374280886, 374280885,
> 374280884, -553313607]
> [2021-08-09 23:35:37,886][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Found last
> checkpoint marker [cpId=dcfe9626-f4f5-4772-930e-73749f55b727,
> pos=FileWALPointer [idx=0, fileOff=3094925, len=135903]]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15868) Unexpected command: PROBE when authorization is enabled
[
https://issues.apache.org/jira/browse/IGNITE-15868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441503#comment-17441503
]
Andrey Novikov commented on IGNITE-15868:
-
Merged to master.
[Dmitriy
Borunov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmitriy.borunov]
thanks for the contribution.
> Unexpected command: PROBE when authorization is enabled
> ---
>
> Key: IGNITE-15868
> URL: https://issues.apache.org/jira/browse/IGNITE-15868
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Affects Versions: 2.12
>Reporter: Dmitriy Borunov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Rest API Probe is not working when Control Center authorisation is enabled
> {noformat}
> [2021-11-01T13:35:33,550][ERROR][rest-#125%nebula-node%][GridRestProcessor]
> Runtime error caught during grid runnable execution: GridWorker
> [name=rest-proc-work
> er, igniteInstanceName=nebula-node, finished=false,
> heartbeatTs=1635773733544, hashCode=1386655371, interrupted=false,
> runner=rest-#125%nebula-node%]
> java.lang.AssertionError: Unexpected command: PROBE
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:968)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:286)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:108)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:183)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core-8.8.10.jar:8.8.10]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
> at java.lang.Thread.run(Thread.java:829) [?:?]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15868) Unexpected command: PROBE when authorization is enabled
[
https://issues.apache.org/jira/browse/IGNITE-15868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Novikov updated IGNITE-15868:
Summary: Unexpected command: PROBE when authorization is enabled (was:
Unexpected command: PROBE when Control Center authorisation is enabled)
> Unexpected command: PROBE when authorization is enabled
> ---
>
> Key: IGNITE-15868
> URL: https://issues.apache.org/jira/browse/IGNITE-15868
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Affects Versions: 2.12
>Reporter: Dmitriy Borunov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Rest API Probe is not working when Control Center authorisation is enabled
> {noformat}
> [2021-11-01T13:35:33,550][ERROR][rest-#125%nebula-node%][GridRestProcessor]
> Runtime error caught during grid runnable execution: GridWorker
> [name=rest-proc-work
> er, igniteInstanceName=nebula-node, finished=false,
> heartbeatTs=1635773733544, hashCode=1386655371, interrupted=false,
> runner=rest-#125%nebula-node%]
> java.lang.AssertionError: Unexpected command: PROBE
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:968)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:286)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:108)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:183)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core-8.8.10.jar:8.8.10]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
> at java.lang.Thread.run(Thread.java:829) [?:?]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15868) Unexpected command: PROBE when Control Center authorisation is enabled
[
https://issues.apache.org/jira/browse/IGNITE-15868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441502#comment-17441502
]
Andrey Novikov commented on IGNITE-15868:
-
LGTM.
> Unexpected command: PROBE when Control Center authorisation is enabled
> --
>
> Key: IGNITE-15868
> URL: https://issues.apache.org/jira/browse/IGNITE-15868
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Affects Versions: 2.12
>Reporter: Dmitriy Borunov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Rest API Probe is not working when Control Center authorisation is enabled
> {noformat}
> [2021-11-01T13:35:33,550][ERROR][rest-#125%nebula-node%][GridRestProcessor]
> Runtime error caught during grid runnable execution: GridWorker
> [name=rest-proc-work
> er, igniteInstanceName=nebula-node, finished=false,
> heartbeatTs=1635773733544, hashCode=1386655371, interrupted=false,
> runner=rest-#125%nebula-node%]
> java.lang.AssertionError: Unexpected command: PROBE
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:968)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:286)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:108)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:183)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core-8.8.10.jar:8.8.10]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
> at java.lang.Thread.run(Thread.java:829) [?:?]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15892) Calcite tests can be used with a limited list of charsets
[
https://issues.apache.org/jira/browse/IGNITE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441389#comment-17441389
]
Vyacheslav Koptilin commented on IGNITE-15892:
--
Hello [~korlov],
Could you please take a look?
> Calcite tests can be used with a limited list of charsets
> -
>
> Key: IGNITE-15892
> URL: https://issues.apache.org/jira/browse/IGNITE-15892
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> The attempt to run calcite tests on a platform with the default charset
> WINDOWS-1252, for example, results in the following exception:
> {noformat}
> java.nio.charset.UnsupportedCharsetException: WINDOWS-1252
> at org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
> at org.apache.calcite.util.NlsString.(NlsString.java:124)
> at org.apache.calcite.util.NlsString.(NlsString.java:116)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
> at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
> at
> org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
> at
> org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
> {noformat}
> It seems the list of supported charsets can be found here:
> {code:java|title=org.apache.calcite.sql.SqlUtil}
> /**
>* Translates a character set name from a SQL-level name into a Java-level
>* name.
>*
>* @param name SQL-level name
>* @return Java-level name, or null if SQL-level name is unknown
>*/
> public static @Nullable String translateCharacterSetName(String name) {
> switch (name) {
> case "BIG5":
> return "Big5";
> case "LATIN1":
> return "ISO-8859-1";
> case "UTF8":
> return "UTF-8";
> case "UTF16":
> case "UTF-16":
> return ConversionUtil.NATIVE_UTF16_CHARSET_NAME;
> case "GB2312":
> case "GBK":
> case "UTF-16BE":
> case "UTF-16LE":
> case "ISO-8859-1":
> case "UTF-8":
> return name;
> default:
> return null;
> }
> }
> {code}
> On the other hand, IGNITE-14545 proposes getting the default charset from the
> JVM that may contradict the list of supported charsets:
> {code:java|title=IgniteTypeFactory}
> @Override
> public Charset getDefaultCharset() {
> // Use JVM default charset rather then Calcite default charset
> (ISO-8859-1).
> return Charset.defaultCharset();
> }
> {code}
> The obvious and dirty way to work around this issue is to specify the default
> charset explicitly
> {code:java|title=calcite/pom.xml}
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
> -Djava.util.logging.config.file=../../config/java.util.logging.properties
> -Dfile.encoding=UTF-8
>
>
> {code}
> Another option is switching to UTF-8 or UTF-16 in case of the default JVM
> charset is not properly supported:
> {code:java|title=IgniteTypeFactory}
> public Charset getDefaultCharset() {
> // Use JVM default charset rather then Calcite default charset
> (ISO-8859-1).
> Charset jvmDefault = Charset.defaultCharset();
>
> if
> (SqlUtil.translateCharacterSetName(jvmDefault.name().toUpperCase(Locale.ROOT))
> == null)
> jvmDefault = StandardCharsets.UTF_8;
>
> return jvmDefault;
> }
> {code}
> [Calcite charset support
> proposal|https://lists.apache.org/thread/944838cb40a34d19f5d0a50ed1e86e5fbd181cd8a529c3d98ef40f46@%3cdev.calcite.apache.org%3e]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15892) Calcite tests can be used with a limited list of charsets
[
https://issues.apache.org/jira/browse/IGNITE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15892:
-
Description:
The attempt to run calcite tests on a platform with the default charset
WINDOWS-1252, for example, results in the following exception:
{noformat}
java.nio.charset.UnsupportedCharsetException: WINDOWS-1252
at org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
at org.apache.calcite.util.NlsString.(NlsString.java:124)
at org.apache.calcite.util.NlsString.(NlsString.java:116)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
at
org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
at
org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
at
org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
{noformat}
It seems the list of supported charsets can be found here:
{code:java|title=org.apache.calcite.sql.SqlUtil}
/**
* Translates a character set name from a SQL-level name into a Java-level
* name.
*
* @param name SQL-level name
* @return Java-level name, or null if SQL-level name is unknown
*/
public static @Nullable String translateCharacterSetName(String name) {
switch (name) {
case "BIG5":
return "Big5";
case "LATIN1":
return "ISO-8859-1";
case "UTF8":
return "UTF-8";
case "UTF16":
case "UTF-16":
return ConversionUtil.NATIVE_UTF16_CHARSET_NAME;
case "GB2312":
case "GBK":
case "UTF-16BE":
case "UTF-16LE":
case "ISO-8859-1":
case "UTF-8":
return name;
default:
return null;
}
}
{code}
On the other hand, IGNITE-14545 proposes getting the default charset from the
JVM that may contradict the list of supported charsets:
{code:java|title=IgniteTypeFactory}
@Override
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
return Charset.defaultCharset();
}
{code}
The obvious and dirty way to work around this issue is to specify the default
charset explicitly
{code:java|title=calcite/pom.xml}
org.apache.maven.plugins
maven-surefire-plugin
-Djava.util.logging.config.file=../../config/java.util.logging.properties
-Dfile.encoding=UTF-8
{code}
Another option is switching to UTF-8 or UTF-16 in case of the default JVM
charset is not properly supported:
{code:java|title=IgniteTypeFactory}
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
Charset jvmDefault = Charset.defaultCharset();
if
(SqlUtil.translateCharacterSetName(jvmDefault.name().toUpperCase(Locale.ROOT))
== null)
jvmDefault = StandardCharsets.UTF_8;
return jvmDefault;
}
{code}
[Calcite charset support
proposal|https://lists.apache.org/thread/944838cb40a34d19f5d0a50ed1e86e5fbd181cd8a529c3d98ef40f46@%3cdev.calcite.apache.org%3e]
was:
The attempt to run calcite tests on a platform with the default charset
WINDOWS-1252, for example, results in the following exception:
{noformat}
java.nio.charset.UnsupportedCharsetException: WINDOWS-1252
at org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
at org.apache.calcite.util.NlsString.(NlsString.java:124)
at org.apache.calcite.util.NlsString.(NlsString.java:116)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
at
org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
at
org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
at
org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
{noformat}
It seems the list of supported charsets can be found here:
{code:java|title=org.apache.calcite.sql.SqlUtil}
/**
* Translates a character set name from a SQL-level name into a Java-level
* name.
*
* @param name SQL-level name
* @return Java-level name, or null if SQL-level name is unknown
*/
public static @Nullable String translateCharacterSetName(String name) {
switch
[jira] [Updated] (IGNITE-15892) Calcite tests can be used with a limited list of charsets
[
https://issues.apache.org/jira/browse/IGNITE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15892:
-
Description:
The attempt to run calcite tests on a platform with the default charset
WINDOWS-1252, for example, results in the following exception:
{noformat}
java.nio.charset.UnsupportedCharsetException: WINDOWS-1252
at org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
at org.apache.calcite.util.NlsString.(NlsString.java:124)
at org.apache.calcite.util.NlsString.(NlsString.java:116)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
at
org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
at
org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
at
org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
{noformat}
It seems the list of supported charsets can be found here:
{code:java|title=org.apache.calcite.sql.SqlUtil}
/**
* Translates a character set name from a SQL-level name into a Java-level
* name.
*
* @param name SQL-level name
* @return Java-level name, or null if SQL-level name is unknown
*/
public static @Nullable String translateCharacterSetName(String name) {
switch (name) {
case "BIG5":
return "Big5";
case "LATIN1":
return "ISO-8859-1";
case "UTF8":
return "UTF-8";
case "UTF16":
case "UTF-16":
return ConversionUtil.NATIVE_UTF16_CHARSET_NAME;
case "GB2312":
case "GBK":
case "UTF-16BE":
case "UTF-16LE":
case "ISO-8859-1":
case "UTF-8":
return name;
default:
return null;
}
}
{code}
On the other hand, IGNITE-15545 proposes getting the default charset from the
JVM that may contradict the list of supported charsets:
{code:java|title=IgniteTypeFactory}
@Override
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
return Charset.defaultCharset();
}
{code}
The obvious and dirty way to work around this issue is to specify the default
charset explicitly
{code:java|title=calcite/pom.xml}
org.apache.maven.plugins
maven-surefire-plugin
-Djava.util.logging.config.file=../../config/java.util.logging.properties
-Dfile.encoding=UTF-8
{code}
Another option is switching to UTF-8 or UTF-16 in case of the default JVM
charset is not properly supported:
{code:java|title=IgniteTypeFactory}
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
Charset jvmDefault = Charset.defaultCharset();
if
(SqlUtil.translateCharacterSetName(jvmDefault.name().toUpperCase(Locale.ROOT))
== null)
jvmDefault = StandardCharsets.UTF_8;
return jvmDefault;
}
{code}
[Calcite charset support
proposal|https://lists.apache.org/thread/944838cb40a34d19f5d0a50ed1e86e5fbd181cd8a529c3d98ef40f46@%3cdev.calcite.apache.org%3e]
was:
The attempt to run calcite tests on a platform with the default charset
WINDOWS-1252, for example, results in the following exception:
{noformat}
java.nio.charset.UnsupportedCharsetException: WINDOWS-1252
at org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
at org.apache.calcite.util.NlsString.(NlsString.java:124)
at org.apache.calcite.util.NlsString.(NlsString.java:116)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
at
org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
at
org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
at
org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
{noformat}
It seems the list of supported charsets can be found here:
{code:java|title=org.apache.calcite.sql.SqlUtil}
/**
* Translates a character set name from a SQL-level name into a Java-level
* name.
*
* @param name SQL-level name
* @return Java-level name, or null if SQL-level name is unknown
*/
public static @Nullable String translateCharacterSetName(String name) {
switch
[jira] [Updated] (IGNITE-15892) Calcite tests can be used with a limited list of charsets
[
https://issues.apache.org/jira/browse/IGNITE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15892:
-
Description:
The attempt to run calcite tests on a platform with the default charset
WINDOWS-1252, for example, results in the following exception:
{noformat}
java.nio.charset.UnsupportedCharsetException: WINDOWS-1252
at org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
at org.apache.calcite.util.NlsString.(NlsString.java:124)
at org.apache.calcite.util.NlsString.(NlsString.java:116)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
at
org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
at
org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
at
org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
{noformat}
It seems the list of supported charsets can be found here:
{code:java|title=org.apache.calcite.sql.SqlUtil}
/**
* Translates a character set name from a SQL-level name into a Java-level
* name.
*
* @param name SQL-level name
* @return Java-level name, or null if SQL-level name is unknown
*/
public static @Nullable String translateCharacterSetName(String name) {
switch (name) {
case "BIG5":
return "Big5";
case "LATIN1":
return "ISO-8859-1";
case "UTF8":
return "UTF-8";
case "UTF16":
case "UTF-16":
return ConversionUtil.NATIVE_UTF16_CHARSET_NAME;
case "GB2312":
case "GBK":
case "UTF-16BE":
case "UTF-16LE":
case "ISO-8859-1":
case "UTF-8":
return name;
default:
return null;
}
}
{code}
On the other hand, IGNITE-15545 proposes getting the default charset from the
JVM that may contradict the list of supported charsets:
{code:java|title=IgniteTypeFactory}
@Override
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
return Charset.defaultCharset();
}
{code}
The obvious and dirty way to work around this issue is to specify the default
charset explicitly
{code:java|title=calcite/pom.xml}
org.apache.maven.plugins
maven-surefire-plugin
-Djava.util.logging.config.file=../../config/java.util.logging.properties
-Dfile.encoding=UTF-8
{code}
Another option is switching to UTF-8 or UTF-16 in case of the default JVM
charset is not properly supported:
{code:java|title=IgniteTypeFactory}
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
Charset jvmDefault = Charset.defaultCharset();
if
(SqlUtil.translateCharacterSetName(jvmDefault.name().toUpperCase(Locale.ROOT))
== null)
jvmDefault = StandardCharsets.UTF_8;
return jvmDefault;
}
{code}
was:
The attempt to run calcite tests on a platform with the default charset
WINDOWS-1252, for example, results in the following exception:
{noformat}
java.nio.charset.UnsupportedCharsetException: WINDOWS-1252 at
org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
at org.apache.calcite.util.NlsString.(NlsString.java:124)
at org.apache.calcite.util.NlsString.(NlsString.java:116)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
at
org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
at
org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
at
org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
{noformat}
It seems the list of supported charsets can be found here:
{code:java|title=org.apache.calcite.sql.SqlUtil}
/**
* Translates a character set name from a SQL-level name into a Java-level
* name.
*
* @param name SQL-level name
* @return Java-level name, or null if SQL-level name is unknown
*/
public static @Nullable String translateCharacterSetName(String name) {
switch (name) {
case "BIG5":
return "Big5";
case "LATIN1":
return "ISO-8859-1";
case "UTF8":
return "UTF-8";
case "UTF16":
[jira] [Created] (IGNITE-15892) Calcite tests can be used with a limited list of charsets
Vyacheslav Koptilin created IGNITE-15892:
Summary: Calcite tests can be used with a limited list of charsets
Key: IGNITE-15892
URL: https://issues.apache.org/jira/browse/IGNITE-15892
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin
Fix For: 3.0.0-alpha4
The attempt to run calcite tests on a platform with the default charset
WINDOWS-1252, for example, results in the following exception:
{noformat}
java.nio.charset.UnsupportedCharsetException: WINDOWS-1252 at
org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
at org.apache.calcite.util.NlsString.(NlsString.java:124)
at org.apache.calcite.util.NlsString.(NlsString.java:116)
at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
at
org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
at
org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
at
org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
{noformat}
It seems the list of supported charsets can be found here:
{code:java|title=org.apache.calcite.sql.SqlUtil}
/**
* Translates a character set name from a SQL-level name into a Java-level
* name.
*
* @param name SQL-level name
* @return Java-level name, or null if SQL-level name is unknown
*/
public static @Nullable String translateCharacterSetName(String name) {
switch (name) {
case "BIG5":
return "Big5";
case "LATIN1":
return "ISO-8859-1";
case "UTF8":
return "UTF-8";
case "UTF16":
case "UTF-16":
return ConversionUtil.NATIVE_UTF16_CHARSET_NAME;
case "GB2312":
case "GBK":
case "UTF-16BE":
case "UTF-16LE":
case "ISO-8859-1":
case "UTF-8":
return name;
default:
return null;
}
}
{code}
On the other hand, IGNITE-15545 proposes getting the default charset from the
JVM that may contradict the list of supported charsets:
{code:java|title=IgniteTypeFactory}
@Override
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
return Charset.defaultCharset();
}
{code}
The obvious and dirty way to work around this issue is to specify the default
charset explicitly
{code:java|title=calcite/pom.xml}
org.apache.maven.plugins
maven-surefire-plugin
-Djava.util.logging.config.file=../../config/java.util.logging.properties
-Dfile.encoding=UTF-8
{code}
Another option is switching to UTF-8 or UTF-16 in case of the default JVM
charset is not properly supported:
{code:java|title=IgniteTypeFactory}
public Charset getDefaultCharset() {
// Use JVM default charset rather then Calcite default charset
(ISO-8859-1).
Charset jvmDefault = Charset.defaultCharset();
if
(SqlUtil.translateCharacterSetName(jvmDefault.name().toUpperCase(Locale.ROOT))
== null)
jvmDefault = StandardCharsets.UTF_8;
return jvmDefault;
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15892) Calcite tests can be used with a limited list of charsets
[
https://issues.apache.org/jira/browse/IGNITE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15892:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Calcite tests can be used with a limited list of charsets
> -
>
> Key: IGNITE-15892
> URL: https://issues.apache.org/jira/browse/IGNITE-15892
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> The attempt to run calcite tests on a platform with the default charset
> WINDOWS-1252, for example, results in the following exception:
> {noformat}
> java.nio.charset.UnsupportedCharsetException: WINDOWS-1252 at
> org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
> at org.apache.calcite.util.NlsString.(NlsString.java:124)
> at org.apache.calcite.util.NlsString.(NlsString.java:116)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
> at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
> at
> org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
> at
> org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
> {noformat}
> It seems the list of supported charsets can be found here:
> {code:java|title=org.apache.calcite.sql.SqlUtil}
> /**
>* Translates a character set name from a SQL-level name into a Java-level
>* name.
>*
>* @param name SQL-level name
>* @return Java-level name, or null if SQL-level name is unknown
>*/
> public static @Nullable String translateCharacterSetName(String name) {
> switch (name) {
> case "BIG5":
> return "Big5";
> case "LATIN1":
> return "ISO-8859-1";
> case "UTF8":
> return "UTF-8";
> case "UTF16":
> case "UTF-16":
> return ConversionUtil.NATIVE_UTF16_CHARSET_NAME;
> case "GB2312":
> case "GBK":
> case "UTF-16BE":
> case "UTF-16LE":
> case "ISO-8859-1":
> case "UTF-8":
> return name;
> default:
> return null;
> }
> }
> {code}
> On the other hand, IGNITE-15545 proposes getting the default charset from the
> JVM that may contradict the list of supported charsets:
> {code:java|title=IgniteTypeFactory}
> @Override
> public Charset getDefaultCharset() {
> // Use JVM default charset rather then Calcite default charset
> (ISO-8859-1).
> return Charset.defaultCharset();
> }
> {code}
> The obvious and dirty way to work around this issue is to specify the default
> charset explicitly
> {code:java|title=calcite/pom.xml}
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
> -Djava.util.logging.config.file=../../config/java.util.logging.properties
> -Dfile.encoding=UTF-8
>
>
> {code}
> Another option is switching to UTF-8 or UTF-16 in case of the default JVM
> charset is not properly supported:
> {code:java|title=IgniteTypeFactory}
> public Charset getDefaultCharset() {
> // Use JVM default charset rather then Calcite default charset
> (ISO-8859-1).
> Charset jvmDefault = Charset.defaultCharset();
>
> if
> (SqlUtil.translateCharacterSetName(jvmDefault.name().toUpperCase(Locale.ROOT))
> == null)
> jvmDefault = StandardCharsets.UTF_8;
>
> return jvmDefault;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15892) Calcite tests can be used with a limited list of charsets
[
https://issues.apache.org/jira/browse/IGNITE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15892:
-
Labels: ignite-3 (was: )
> Calcite tests can be used with a limited list of charsets
> -
>
> Key: IGNITE-15892
> URL: https://issues.apache.org/jira/browse/IGNITE-15892
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> The attempt to run calcite tests on a platform with the default charset
> WINDOWS-1252, for example, results in the following exception:
> {noformat}
> java.nio.charset.UnsupportedCharsetException: WINDOWS-1252 at
> org.apache.calcite.sql.SqlUtil.getCharset(SqlUtil.java:1008)
> at org.apache.calcite.util.NlsString.(NlsString.java:124)
> at org.apache.calcite.util.NlsString.(NlsString.java:116)
> at org.apache.calcite.rex.RexBuilder.makeLiteral(RexBuilder.java:964)
> at org.apache.calcite.rex.RexBuilder.(RexBuilder.java:132)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.(IgnitePlanner.java:126)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.PlanningContext.planner(PlanningContext.java:163)
> at
> org.apache.ignite.internal.processors.query.calcite.planner.AbstractPlannerTest.physicalPlan(AbstractPlannerTest.java:232)
> at
> org.apache.ignite.internal.processors.query.calcite.planner.TableDmlPlannerTest.insertCachesTableScan(TableDmlPlannerTest.java:57)
> {noformat}
> It seems the list of supported charsets can be found here:
> {code:java|title=org.apache.calcite.sql.SqlUtil}
> /**
>* Translates a character set name from a SQL-level name into a Java-level
>* name.
>*
>* @param name SQL-level name
>* @return Java-level name, or null if SQL-level name is unknown
>*/
> public static @Nullable String translateCharacterSetName(String name) {
> switch (name) {
> case "BIG5":
> return "Big5";
> case "LATIN1":
> return "ISO-8859-1";
> case "UTF8":
> return "UTF-8";
> case "UTF16":
> case "UTF-16":
> return ConversionUtil.NATIVE_UTF16_CHARSET_NAME;
> case "GB2312":
> case "GBK":
> case "UTF-16BE":
> case "UTF-16LE":
> case "ISO-8859-1":
> case "UTF-8":
> return name;
> default:
> return null;
> }
> }
> {code}
> On the other hand, IGNITE-15545 proposes getting the default charset from the
> JVM that may contradict the list of supported charsets:
> {code:java|title=IgniteTypeFactory}
> @Override
> public Charset getDefaultCharset() {
> // Use JVM default charset rather then Calcite default charset
> (ISO-8859-1).
> return Charset.defaultCharset();
> }
> {code}
> The obvious and dirty way to work around this issue is to specify the default
> charset explicitly
> {code:java|title=calcite/pom.xml}
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
> -Djava.util.logging.config.file=../../config/java.util.logging.properties
> -Dfile.encoding=UTF-8
>
>
> {code}
> Another option is switching to UTF-8 or UTF-16 in case of the default JVM
> charset is not properly supported:
> {code:java|title=IgniteTypeFactory}
> public Charset getDefaultCharset() {
> // Use JVM default charset rather then Calcite default charset
> (ISO-8859-1).
> Charset jvmDefault = Charset.defaultCharset();
>
> if
> (SqlUtil.translateCharacterSetName(jvmDefault.name().toUpperCase(Locale.ROOT))
> == null)
> jvmDefault = StandardCharsets.UTF_8;
>
> return jvmDefault;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-15891) Configuration does not concerned global state when handling a consumer
Vladislav Pyatkov created IGNITE-15891: -- Summary: Configuration does not concerned global state when handling a consumer Key: IGNITE-15891 URL: https://issues.apache.org/jira/browse/IGNITE-15891 Project: Ignite Issue Type: Test Reporter: Vladislav Pyatkov A code into Configuration changer: 1) Cannot use a configuration view, because it is just a local cache (the global value may have changed in the past) 2) Can throw an exception (IllegalArgumentException) when cached configuration does not support the change, but global state different (and does not conflict to the change). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15890) [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST
[ https://issues.apache.org/jira/browse/IGNITE-15890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-15890: --- Summary: [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST (was: [ducktests] Added ignite version 2.11.0 to Docker file and set it LATEST ) > [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST > -- > > Key: IGNITE-15890 > URL: https://issues.apache.org/jira/browse/IGNITE-15890 > Project: Ignite > Issue Type: Test >Reporter: Sergei Ryzhov >Priority: Minor > Labels: IEP-56 > > Added ignite version 2.11.0 to Docker file and set it LATEST -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15890) [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST
[ https://issues.apache.org/jira/browse/IGNITE-15890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-15890: --- Description: Add ignite version 2.11.0 to Docker file and set it as LATEST (was: Added ignite version 2.11.0 to Docker file and set it LATEST) > [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST > -- > > Key: IGNITE-15890 > URL: https://issues.apache.org/jira/browse/IGNITE-15890 > Project: Ignite > Issue Type: Test >Reporter: Sergei Ryzhov >Priority: Minor > Labels: IEP-56 > > Add ignite version 2.11.0 to Docker file and set it as LATEST -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15890) [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST
[ https://issues.apache.org/jira/browse/IGNITE-15890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov reassigned IGNITE-15890: -- Assignee: Sergei Ryzhov > [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST > -- > > Key: IGNITE-15890 > URL: https://issues.apache.org/jira/browse/IGNITE-15890 > Project: Ignite > Issue Type: Test >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: IEP-56 > > Add ignite version 2.11.0 to Docker file and set it as LATEST -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15890) [ducktests] Added ignite version 2.11.0 to Docker file and set it LATEST
Sergei Ryzhov created IGNITE-15890: -- Summary: [ducktests] Added ignite version 2.11.0 to Docker file and set it LATEST Key: IGNITE-15890 URL: https://issues.apache.org/jira/browse/IGNITE-15890 Project: Ignite Issue Type: Test Reporter: Sergei Ryzhov Added ignite version 2.11.0 to Docker file and set it LATEST -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15730) Add kafka service to ducktape tests.
[ https://issues.apache.org/jira/browse/IGNITE-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-15730: --- Labels: IEP-56 (was: ) > Add kafka service to ducktape tests. > > > Key: IGNITE-15730 > URL: https://issues.apache.org/jira/browse/IGNITE-15730 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: IEP-56 > Time Spent: 20m > Remaining Estimate: 0h > > Add kafka service to ducktape tests > The results catalog contains the following: > $ tree ducker05/ > ducker05/ > ├── config > │ ├── kafka.properties > │ └── log4j.properties > ├── jfr > └── logs > ├── controller.log > ├── data > │ ├── cleaner-offset-checkpoint > │ ├── log-start-offset-checkpoint > │ ├── meta.properties > │ ├── recovery-point-offset-checkpoint > │ └── replication-offset-checkpoint > ├── kafka-authorizer.log > ├── kafka-request.log > ├── kafka.log > ├── kafkaServer-gc.log.0.current > ├── log-cleaner.log > ├── server.log > └── state-change.log -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15730) [ducktests]Add kafka service to ducktape tests.
[ https://issues.apache.org/jira/browse/IGNITE-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-15730: --- Summary: [ducktests]Add kafka service to ducktape tests. (was: Add kafka service to ducktape tests.) > [ducktests]Add kafka service to ducktape tests. > --- > > Key: IGNITE-15730 > URL: https://issues.apache.org/jira/browse/IGNITE-15730 > Project: Ignite > Issue Type: Improvement >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: IEP-56 > Time Spent: 20m > Remaining Estimate: 0h > > Add kafka service to ducktape tests > The results catalog contains the following: > $ tree ducker05/ > ducker05/ > ├── config > │ ├── kafka.properties > │ └── log4j.properties > ├── jfr > └── logs > ├── controller.log > ├── data > │ ├── cleaner-offset-checkpoint > │ ├── log-start-offset-checkpoint > │ ├── meta.properties > │ ├── recovery-point-offset-checkpoint > │ └── replication-offset-checkpoint > ├── kafka-authorizer.log > ├── kafka-request.log > ├── kafka.log > ├── kafkaServer-gc.log.0.current > ├── log-cleaner.log > ├── server.log > └── state-change.log -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15660) calciteIteratorsCleanWorker threads leakage
[
https://issues.apache.org/jira/browse/IGNITE-15660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15660:
--
Labels: ignite-3 (was: calcite3-required ignite-3)
> calciteIteratorsCleanWorker threads leakage
> ---
>
> Key: IGNITE-15660
> URL: https://issues.apache.org/jira/browse/IGNITE-15660
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Attachments: image-2021-09-30-19-10-13-257.png,
> image-2021-09-30-19-10-39-012.png
>
>
> For example, If you run
> {{ITSchemaChangeKVViewTest#testMergeChangesAddDropAdd}} many times in the
> loop, you can see, that there are a lot of unhandled
> {{calciteIteratorsCleanWorker}} threads. See images from VisualVM
> !image-2021-09-30-19-10-13-257.png!
> !image-2021-09-30-19-10-39-012.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14928) Introduce IndexKey and IndexValue structures
[
https://issues.apache.org/jira/browse/IGNITE-14928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-14928:
-
Issue Type: Task (was: Improvement)
> Introduce IndexKey and IndexValue structures
>
>
> Key: IGNITE-14928
> URL: https://issues.apache.org/jira/browse/IGNITE-14928
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksandr Polovtcev
>Priority: Major
>
> 2.x indexed uses real data row (read by the direct link) to compare indexed
> fields.
> Now we have to create separate IndexKey that will be serialized to bytes.
> It is required by storage engine (now it is RocksDB).
> IndexKey must support all supported native data types.
> {{Comparator}} must be implemented for {{IndexKey}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15885) Create and implement SortedIndexStorage based on RocksDB
[
https://issues.apache.org/jira/browse/IGNITE-15885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-15885:
-
Description:
# Add {{IndexStorage}} interface:
{code:java}
public interface IndexStorage {
/** Index ID. */
IgniteUuid id();
/** Index configuration. */
TableIndexView configuration();
/** Adds the given row to the index */
void put(IndexRow row);
/** Removes the given row from the index. */
void remove(IndexRow row);
/** Replaces the {@code oldRow} with {@code newRow}. */
void replace(IndexRow oldRow, IndexRow newRow);
/** Returns a range of index rows as specified in IEP-74. */
Cursor range(IndexRow lowerBound, IndexRow upperBound, byte
scanBoundMask, BitSet includedColumns);
}
{code}
was:
# Add {{IndexStorage}} interface:
{code:java}
public interface IndexStorage {
IgniteUuid id();
TableIndexView configuration();
void put(IndexRow row);
void remove(IndexRow row);
void replace(IndexRow oldRow, IndexRow newRow);
Cursor scan(IndexRow lowerBound, IndexRow upperBound, byte
scanBoundMask, BitSet includedColumns);
}
{code}
> Create and implement SortedIndexStorage based on RocksDB
>
>
> Key: IGNITE-15885
> URL: https://issues.apache.org/jira/browse/IGNITE-15885
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
>
> # Add {{IndexStorage}} interface:
> {code:java}
> public interface IndexStorage {
> /** Index ID. */
> IgniteUuid id();
>
> /** Index configuration. */
> TableIndexView configuration();
>
> /** Adds the given row to the index */
> void put(IndexRow row);
>
> /** Removes the given row from the index. */
> void remove(IndexRow row);
>
> /** Replaces the {@code oldRow} with {@code newRow}. */
> void replace(IndexRow oldRow, IndexRow newRow);
>
> /** Returns a range of index rows as specified in IEP-74. */
> Cursor range(IndexRow lowerBound, IndexRow upperBound, byte
> scanBoundMask, BitSet includedColumns);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15885) Create and implement SortedIndexStorage based on RocksDB
[
https://issues.apache.org/jira/browse/IGNITE-15885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-15885:
-
Description:
# Add {{IndexStorage}} interface:
{code:java}
// Some comments here
public String getFoo()
{
return foo;
}
{code}
was:TODO
> Create and implement SortedIndexStorage based on RocksDB
>
>
> Key: IGNITE-15885
> URL: https://issues.apache.org/jira/browse/IGNITE-15885
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
>
> # Add {{IndexStorage}} interface:
> {code:java}
> // Some comments here
> public String getFoo()
> {
> return foo;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15885) Create and implement SortedIndexStorage based on RocksDB
[
https://issues.apache.org/jira/browse/IGNITE-15885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-15885:
-
Description:
# Add {{IndexStorage}} interface:
{code:java}
public interface IndexStorage {
IgniteUuid id();
TableIndexView configuration();
void put(IndexRow row);
void remove(IndexRow row);
void replace(IndexRow oldRow, IndexRow newRow);
Cursor scan(IndexRow lowerBound, IndexRow upperBound, byte
scanBoundMask, BitSet includedColumns);
}
{code}
was:
# Add {{IndexStorage}} interface:
{code:java}
// Some comments here
public String getFoo()
{
return foo;
}
{code}
> Create and implement SortedIndexStorage based on RocksDB
>
>
> Key: IGNITE-15885
> URL: https://issues.apache.org/jira/browse/IGNITE-15885
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
>
> # Add {{IndexStorage}} interface:
> {code:java}
> public interface IndexStorage {
> IgniteUuid id();
>
> TableIndexView configuration();
>
> void put(IndexRow row);
>
> void remove(IndexRow row);
>
> void replace(IndexRow oldRow, IndexRow newRow);
>
> Cursor scan(IndexRow lowerBound, IndexRow upperBound, byte
> scanBoundMask, BitSet includedColumns);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15889) Add 'contains' method to Record API
[ https://issues.apache.org/jira/browse/IGNITE-15889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15889: -- Issue Type: Bug (was: Improvement) > Add 'contains' method to Record API > --- > > Key: IGNITE-15889 > URL: https://issues.apache.org/jira/browse/IGNITE-15889 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > There is no method in Record API with the same semantic as the 'contains' > method in KV views. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15889) Add 'contains' method to Record API
Andrey Mashenkov created IGNITE-15889: - Summary: Add 'contains' method to Record API Key: IGNITE-15889 URL: https://issues.apache.org/jira/browse/IGNITE-15889 Project: Ignite Issue Type: Improvement Components: sql Reporter: Andrey Mashenkov There is no method in Record API with the same semantic as the 'contains' method in KV views. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15881) Cleanup after introducing direct properties
[
https://issues.apache.org/jira/browse/IGNITE-15881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441237#comment-17441237
]
Alexander Lapin commented on IGNITE-15881:
--
[~apolovtcev] LGTM
> Cleanup after introducing direct properties
> ---
>
> Key: IGNITE-15881
> URL: https://issues.apache.org/jira/browse/IGNITE-15881
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Minor
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After introducing direct configuration properties in IGNITE-15412, we should
> remove hacks from the {{TableManager}} that were used to overcome previous
> API limitations. These hacks can be found by looking for TODO comments
> mentioning the IGNITE-15412 ticket.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-15888) Add generated POJO marshaller support.
Andrey Mashenkov created IGNITE-15888: - Summary: Add generated POJO marshaller support. Key: IGNITE-15888 URL: https://issues.apache.org/jira/browse/IGNITE-15888 Project: Ignite Issue Type: Improvement Reporter: Andrey Mashenkov Add support of records to generated serialiser. Drop deprecated code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15801) Annotation-based injection of ServiceContext in Ignite services.
[ https://issues.apache.org/jira/browse/IGNITE-15801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441221#comment-17441221 ] Pavel Pereslegin commented on IGNITE-15801: --- [~nizhikov], thanks for the review! > Annotation-based injection of ServiceContext in Ignite services. > > > Key: IGNITE-15801 > URL: https://issues.apache.org/jira/browse/IGNITE-15801 > Project: Ignite > Issue Type: Improvement > Components: managed services >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Inject ServiceContext using special annotation. > Suggested approach for Java services: > _1. Add init/execute/cancel methods without parameters._ > _2. Add default no-op implementations for the new methods (this is required_ > _to preserve compatibility)._ > _3. For old methods that take ServiceContext as a parameter, add default_ > _implementations that delegate to new methods._ > _4. Deprecate the old methods on the API._ > _5. On the implementation level, still use the old methods (again - for_ > _compatibility)._ > _6. Finally, add a @ServiceContextResource annotation to inject_ > _ServiceContext._ > Pros: > 1. The annotation-based injection is a user-friendly approach widely used in > Ignite. > 2. The user does not need to implement all the lifecycle methods every time. > Cons: > 1. Duplication of methods in the Service interface for an indefinite period. > 2. Someday we need to remove the old methods, and this will break all ignite > services that use the old approach. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15887) Improve wording for setCheckpointFrequency method in JavaDoc
[ https://issues.apache.org/jira/browse/IGNITE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441203#comment-17441203 ] Igor Gusev commented on IGNITE-15887: - [~dma...@apache.org] Can you merge the PR? > Improve wording for setCheckpointFrequency method in JavaDoc > - > > Key: IGNITE-15887 > URL: https://issues.apache.org/jira/browse/IGNITE-15887 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > setCheckpointFrequency method states that "If the rate is high, checkpoint > will be triggered more frequently." > This is confusing because high number means low rate, so we should improve > wording. > See: > [https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/DataStorageConfiguration.html] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15887) Improve wording for setCheckpointFrequency method in JavaDoc
[ https://issues.apache.org/jira/browse/IGNITE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Gusev reassigned IGNITE-15887: --- Assignee: Igor Gusev > Improve wording for setCheckpointFrequency method in JavaDoc > - > > Key: IGNITE-15887 > URL: https://issues.apache.org/jira/browse/IGNITE-15887 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Minor > > setCheckpointFrequency method states that "If the rate is high, checkpoint > will be triggered more frequently." > This is confusing because high number means low rate, so we should improve > wording. > See: > [https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/DataStorageConfiguration.html] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15873) Fix constructor argument in jetty config threadPool -> threadpool
[
https://issues.apache.org/jira/browse/IGNITE-15873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-15873:
Assignee: Vyacheslav Koptilin
> Fix constructor argument in jetty config threadPool -> threadpool
> -
>
> Key: IGNITE-15873
> URL: https://issues.apache.org/jira/browse/IGNITE-15873
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.11
>Reporter: Ilya Korol
>Assignee: Vyacheslav Koptilin
>Priority: Major
>
> According to jetty sources:
> {code:java}
> public Server(@Name("threadpool") ThreadPool pool)
> {
> _threadPool = pool != null ? pool : new QueuedThreadPool();
> addBean(_threadPool);
> setServer(this);
> }
> {code}
> When we instantiate Server class via xml we need to use *threadpool* (all
> lowercase) instead of *threadPool*
> {code:java}
>
> ---
> +++
> ...
> {code}
> otherwise we would get an error:
> {code:java}
> Caused by: java.lang.IllegalStateException: No matching constructor class
> org.eclipse.jetty.server.Server in file:///...config/jetty.xml
> at
> org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:454)
> at
> org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:380)
> at
> org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.loadJettyConfiguration(GridJettyRestProtocol.java:318)
> ... 16 more
> {code}
> [SO
> issue|https://stackoverflow.com/questions/69859238/apache-ignite-unable-to-start-2-11-ignite-nodes-in-a-cluster]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-15887) Improve wording for setCheckpointFrequency method in JavaDoc
Igor Gusev created IGNITE-15887: --- Summary: Improve wording for setCheckpointFrequency method in JavaDoc Key: IGNITE-15887 URL: https://issues.apache.org/jira/browse/IGNITE-15887 Project: Ignite Issue Type: Improvement Reporter: Igor Gusev setCheckpointFrequency method states that "If the rate is high, checkpoint will be triggered more frequently." This is confusing because high number means low rate, so we should improve wording. See: [https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/DataStorageConfiguration.html] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15702) Control.sh consistency check command should support status option
[
https://issues.apache.org/jira/browse/IGNITE-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441187#comment-17441187
]
Anton Vinogradov commented on IGNITE-15702:
---
Merged into master.
[~timonin.maksim], thanks for the review!
> Control.sh consistency check command should support status option
> -
>
> Key: IGNITE-15702
> URL: https://issues.apache.org/jira/browse/IGNITE-15702
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {code}consistency status{code} command should return current progress.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15801) Annotation-based injection of ServiceContext in Ignite services.
[ https://issues.apache.org/jira/browse/IGNITE-15801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441181#comment-17441181 ] Nikolay Izhikov commented on IGNITE-15801: -- LGTM. > Annotation-based injection of ServiceContext in Ignite services. > > > Key: IGNITE-15801 > URL: https://issues.apache.org/jira/browse/IGNITE-15801 > Project: Ignite > Issue Type: Improvement > Components: managed services >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Inject ServiceContext using special annotation. > Suggested approach for Java services: > _1. Add init/execute/cancel methods without parameters._ > _2. Add default no-op implementations for the new methods (this is required_ > _to preserve compatibility)._ > _3. For old methods that take ServiceContext as a parameter, add default_ > _implementations that delegate to new methods._ > _4. Deprecate the old methods on the API._ > _5. On the implementation level, still use the old methods (again - for_ > _compatibility)._ > _6. Finally, add a @ServiceContextResource annotation to inject_ > _ServiceContext._ > Pros: > 1. The annotation-based injection is a user-friendly approach widely used in > Ignite. > 2. The user does not need to implement all the lifecycle methods every time. > Cons: > 1. Duplication of methods in the Service interface for an indefinite period. > 2. Someday we need to remove the old methods, and this will break all ignite > services that use the old approach. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15874) Add idea/intellij-java-google-style.xml import instruction to idea into DEVNOTES.md
[
https://issues.apache.org/jira/browse/IGNITE-15874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441174#comment-17441174
]
Vyacheslav Koptilin commented on IGNITE-15874:
--
Hello [~ktkale...@gridgain.com] ,
The patch looks good to me.
> Add idea/intellij-java-google-style.xml import instruction to idea into
> DEVNOTES.md
> ---
>
> Key: IGNITE-15874
> URL: https://issues.apache.org/jira/browse/IGNITE-15874
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Affects Versions: 3.0.0-alpha3
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After implementing ticket IGNITE-15371, I forgot to add instructions for
> importing a *idea/intellij-java-google-style.xml* into an idea into a
> {*}DEVNOTES.md{*}.
> The following steps should be done in order to properly apply a new code
> style script:
> - Open _File_ -> _Settings_ -> _Editor_ -> _Code Style_ -> _Scheme_ ->
> _gear_ (Show Scheme Actions) -> _Import Scheme_ -> _IntelliJ IDEA code style
> XML_
> - Choose: ${igniteProject}/idea/intellij-java-google-style.xml
> - Import the scheme
> - Reboot Intellij IDEA
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15874) Add idea/intellij-java-google-style.xml import instruction to idea into DEVNOTES.md
[
https://issues.apache.org/jira/browse/IGNITE-15874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15874:
-
Description:
After implementing ticket IGNITE-15371, I forgot to add instructions for
importing a *idea/intellij-java-google-style.xml* into an idea into a
{*}DEVNOTES.md{*}.
The following steps should be done in order to properly apply a new code style
script:
- Open _File_ -> _Settings_ -> _Editor_ -> _Code Style_ -> _Scheme_ -> _gear_
(Show Scheme Actions) -> _Import Scheme_ -> _IntelliJ IDEA code style XML_
- Choose: ${igniteProject}/idea/intellij-java-google-style.xml
- Import the scheme
- Reboot Intellij IDEA
was:After implementing ticket IGNITE-15371, I forgot to add instructions for
importing a *idea/intellij-java-google-style.xml* into an idea into a
*DEVNOTES.md*.
> Add idea/intellij-java-google-style.xml import instruction to idea into
> DEVNOTES.md
> ---
>
> Key: IGNITE-15874
> URL: https://issues.apache.org/jira/browse/IGNITE-15874
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Affects Versions: 3.0.0-alpha3
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After implementing ticket IGNITE-15371, I forgot to add instructions for
> importing a *idea/intellij-java-google-style.xml* into an idea into a
> {*}DEVNOTES.md{*}.
> The following steps should be done in order to properly apply a new code
> style script:
> - Open _File_ -> _Settings_ -> _Editor_ -> _Code Style_ -> _Scheme_ ->
> _gear_ (Show Scheme Actions) -> _Import Scheme_ -> _IntelliJ IDEA code style
> XML_
> - Choose: ${igniteProject}/idea/intellij-java-google-style.xml
> - Import the scheme
> - Reboot Intellij IDEA
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (IGNITE-6290) Data loss in case of manual rebalance
[
https://issues.apache.org/jira/browse/IGNITE-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov resolved IGNITE-6290.
---
Resolution: Won't Fix
Method {{rebalance()}} has been deprecated (IGNITE-15764) and will be removed
soon. Closing this ticket.
> Data loss in case of manual rebalance
> -
>
> Key: IGNITE-6290
> URL: https://issues.apache.org/jira/browse/IGNITE-6290
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.1
>Reporter: Andrey N. Gura
>Priority: Major
> Attachments: CacheManualRebalancingDataConsistencyTest.java
>
>
> Data can be lost due to a manual rebalancing.
> See reproducer that always fails when topology consist of two nodes and one
> of them was stopped (except of case when {{NODES_CNT}} was initially 2).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-13428) Ignite Distributed Environment Tests (IEP-56)
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441134#comment-17441134 ] Maxim Muzafarov commented on IGNITE-13428: -- The issue merged to the master branch, however, it is still not resolved. Is it ok? > Ignite Distributed Environment Tests (IEP-56) > - > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: Epic >Reporter: Maksim Timonin >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441117#comment-17441117
]
Gaurav Aggarwal edited comment on IGNITE-15886 at 11/9/21, 12:15 PM:
-
[~PetrovMikhail] cloned this Jira from an existing Jira
https://issues.apache.org/jira/browse/IGNITE-12828 , hence it got assigned to
you, please feel free to un-assign, getting similar exceptions in 2.9 on node
shutdown and it impacts other nodes
was (Author: gaurav.agg83):
[~PetrovMikhail] cloned this Jira from an existing Jira
https://issues.apache.org/jira/browse/IGNITE-12828 , hence it got assigned to
you, please feel free to un-assign, getting similar exceptions in 2.9 on node
shutdown and impacting other nodes
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
>
> {+}*Reproducer*{+}:
> Run a cluster with few nodes, on bringing down one of the nodes, the other
> nodes throw this exception intermittently and eventually come down
> +*Actual result*+
> Intermittent exception in one of the nodes:
> {noformat}
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@3a0d7950,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=a452f5c7-4a27-4a5e-be3e-77ddae5d50a3]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)Nov 03, 2021 12:11:00 PM
> org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@67cc413e,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=c2ce7d01-5c5b-4654-8942-bd7ab6b90351]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
>
[jira] [Commented] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441117#comment-17441117
]
Gaurav Aggarwal commented on IGNITE-15886:
--
[~PetrovMikhail] cloned this Jira from an existing Jira
https://issues.apache.org/jira/browse/IGNITE-12828 , hence it got assigned to
you, please feel free to un-assign, getting similar exceptions in 2.9 on node
shutdown and impacting other nodes
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
>
> {+}*Reproducer*{+}:
> Run a cluster with few nodes, on bringing down one of the nodes, the other
> nodes throw this exception intermittently and eventually come down
> +*Actual result*+
> Intermittent exception in one of the nodes:
> {noformat}
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@3a0d7950,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=a452f5c7-4a27-4a5e-be3e-77ddae5d50a3]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)Nov 03, 2021 12:11:00 PM
> org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@67cc413e,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=c2ce7d01-5c5b-4654-8942-bd7ab6b90351]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
> at
>
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Description:
{+}*Reproducer*{+}:
Run a cluster with few nodes, on bringing down one of the nodes, the other
nodes throw this exception intermittently and eventually come down
+*Actual result*+
Intermittent exception in one of the nodes:
{noformat}
SEVERE: Failed to notify direct custom event listener:
StartRoutineDiscoveryMessage [startReqData=StartRequestData
[prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@3a0d7950,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
[rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=a452f5c7-4a27-4a5e-be3e-77ddae5d50a3]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)Nov 03, 2021 12:11:00 PM
org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to notify direct custom event listener:
StartRoutineDiscoveryMessage [startReqData=StartRequestData
[prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@67cc413e,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
[rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=c2ce7d01-5c5b-4654-8942-bd7ab6b90351]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}
Node terminates after giving a bunch of these exceptions : Failed to send
message to next node
{noformat}
Nov 03, 2021 12:14:40 PM org.apache.ignite.logger.java.JavaLogger warning
WARNING: Failed to send message to next node, try previous
[msg=TcpDiscoveryMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage [...]]
Nov 03, 2021 12:14:40 PM org.apache.ignite.logger.java.JavaLogger warning
WARNING: Unable to connect to next nodes in a ring, it seems local node is
experiencing connectivity issues.
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Description:
{+}*Reproducer*{+}:
Run a cluster with few nodes, on bringing down one of the nodes, the other
nodes throw this exception intermittently and eventually come down
+*Actual result*+
Intermittent exception in one of the nodes:
{noformat}
SEVERE: Failed to notify direct custom event listener:
StartRoutineDiscoveryMessage [startReqData=StartRequestData
[prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@3a0d7950,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
[rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=a452f5c7-4a27-4a5e-be3e-77ddae5d50a3]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)Nov 03, 2021 12:11:00 PM
org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to notify direct custom event listener:
StartRoutineDiscoveryMessage [startReqData=StartRequestData
[prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@67cc413e,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
[rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=c2ce7d01-5c5b-4654-8942-bd7ab6b90351]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}
+*Final Exception*+
Node terminates after giving a bunch of these exceptions : Failed to send
message to next node
{noformat}
Nov 03, 2021 12:14:40 PM org.apache.ignite.logger.java.JavaLogger warning
WARNING: Failed to send message to next node, try previous
[msg=TcpDiscoveryMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage [...]]
Nov 03, 2021 12:14:40 PM org.apache.ignite.logger.java.JavaLogger warning
WARNING: Unable to connect to next nodes in a ring, it seems local node is
experiencing
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Description:
{+}*Reproducer*{+}:
Run a cluster with few nodes, on bringing down one of the nodes, the other
nodes throw this exception intermittently and eventually come down
+*Actual result*+
Intermittent exception in one of the nodes:
{noformat}
SEVERE: Failed to notify direct custom event listener:
StartRoutineDiscoveryMessage [startReqData=StartRequestData
[prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@3a0d7950,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
[rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=a452f5c7-4a27-4a5e-be3e-77ddae5d50a3]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)Nov 03, 2021 12:11:00 PM
org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to notify direct custom event listener:
StartRoutineDiscoveryMessage [startReqData=StartRequestData
[prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@67cc413e,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
[rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=c2ce7d01-5c5b-4654-8942-bd7ab6b90351]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}
was:
{+}*Reproducer*{+}:
Run a cluster with few nodes, on bringing down one of the nodes, the other
nodes throw this exception intermittently and eventually come down
+*Actual result*+
Intermittent exception in one of the nodes:
{noformat}
[16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Description:
{+}*Reproducer*{+}:
Run a cluster with few nodes, on bringing down one of the nodes, the other
nodes throw this exception intermittently and eventually come down
+*Actual result*+
Intermittent exception in one of the nodes:
{noformat}
[16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=true,
routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:745)
[16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
internal=false, notifyExisting=false, oldValRequired=true, sync=false,
ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
at
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Description:
{+}*Reproducer*{+}:
Run a cluster with few nodes, on bringing down one of the nodes, the other
nodes throw this exception intermitently
+*Actual result*+
Intermittent exception in the client node:
{noformat}
[16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=true,
routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:745)
[16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
internal=false, notifyExisting=false, oldValRequired=true, sync=false,
ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
at
[jira] [Assigned] (IGNITE-14484) Implement RecordView API.
[ https://issues.apache.org/jira/browse/IGNITE-14484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-14484: - Assignee: Andrey Mashenkov (was: Alexander Belyak) > Implement RecordView API. > - > > Key: IGNITE-14484 > URL: https://issues.apache.org/jira/browse/IGNITE-14484 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > > Add user-POJO mappers support for key-value view regarding marshallers > initially implemented in IGNITE-13618 and mappers in IGNITE-15782 > #* Mapper is not required to be Serializable as it is intended to be moved to > a remote node. > #* Mapper can be used for schema generation from user classes (annotation > schema configuration IGNITE-13749) and user object validation against the > schema. > #* Mapper might be highly coupled with marshallers\serislizers. > # Implement all RecordView operations (maybe excl. invoke IGNITE-14488). > # Add integration tests. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Labels: (was: sbcf)
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
>
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Fix Version/s: (was: 2.8.1)
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8, 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: sbcf
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
>
[jira] [Created] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
Gaurav Aggarwal created IGNITE-15886:
Summary: Intermittent [Failed to notify direct custom event
listener] exception on node shutdown
Key: IGNITE-15886
URL: https://issues.apache.org/jira/browse/IGNITE-15886
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8
Reporter: Gaurav Aggarwal
Assignee: Mikhail Petrov
Fix For: 2.8.1
+*Reproducer*+:
Run a server node
Run a client node that:
* Creates cache "cache1"
* Deploys a grid service that starts a continuous query against "cache1" in
method init()
* Leaves the cluster
+*Actual result*+
Intermittent exception in the client node:
{noformat}
[16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=true,
routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:745)
[16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
internal=false, notifyExisting=false, oldValRequired=true, sync=false,
ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
at
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Affects Version/s: (was: 2.8)
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: sbcf
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
>
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Affects Version/s: 2.9
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8, 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: sbcf
> Fix For: 2.8.1
>
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
>
[jira] [Updated] (IGNITE-15783) Mapper API and simple implementation.
[ https://issues.apache.org/jira/browse/IGNITE-15783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15783: -- Labels: iep-54 ignite-3 (was: ignite-3) > Mapper API and simple implementation. > - > > Key: IGNITE-15783 > URL: https://issues.apache.org/jira/browse/IGNITE-15783 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Design Mapper API for user POJO classes for use in KvView and RecordView. > NB: Most likely, there is no need to have different interfaces for > Key/Value/Record mappers > and the same implementation can be reused for all cases. > Let's > * Implement an IdentityMapper as a default one that binds the POJO field to > the column with the same name. > * Implement a simple mapper that allows binding the POJO field to the column > with a different name. > Field <--> column mapping expected to be one-to-one function. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15885) Create and implement SortedIndexStorage based on RocksDB
Aleksandr Polovtcev created IGNITE-15885: Summary: Create and implement SortedIndexStorage based on RocksDB Key: IGNITE-15885 URL: https://issues.apache.org/jira/browse/IGNITE-15885 Project: Ignite Issue Type: Task Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev TODO -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15884) Make TableIndexConfigurationSchema polymorphic
Aleksandr Polovtcev created IGNITE-15884:
Summary: Make TableIndexConfigurationSchema polymorphic
Key: IGNITE-15884
URL: https://issues.apache.org/jira/browse/IGNITE-15884
Project: Ignite
Issue Type: Task
Reporter: Aleksandr Polovtcev
Assignee: Aleksandr Polovtcev
After introducing polymorphic configuration, it is now possible to split
{{TableIndexConfigurationSchema}} into different sub-schemas based on the index
type
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15289) Collect global statistics
[ https://issues.apache.org/jira/browse/IGNITE-15289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441101#comment-17441101 ] Alexander Belyak commented on IGNITE-15289: --- [~korlov] please take a look at PR with the last fixes. > Collect global statistics > - > > Key: IGNITE-15289 > URL: https://issues.apache.org/jira/browse/IGNITE-15289 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Major > Time Spent: 5h > Remaining Estimate: 0h > > Collect global statistics by request to use in Calcite cost model. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15134) Add documentation for SQL statistics functionality
[ https://issues.apache.org/jira/browse/IGNITE-15134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441097#comment-17441097 ] Igor Gusev commented on IGNITE-15134: - PR 9556 has minor improvements over 9550. Can close the older one. > Add documentation for SQL statistics functionality > -- > > Key: IGNITE-15134 > URL: https://issues.apache.org/jira/browse/IGNITE-15134 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.12 >Reporter: Nikita Safonov >Assignee: Nikita Safonov >Priority: Major > Labels: docuentation > Fix For: 2.12 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > We need to document the following information on the SQL statistics > functionality: > * New DDL commands: ANALYZE, DROP STATISTICS, REFRESH; > * General information and scenarios of SQL statistics usage; > * An ability to work with statistics via Control script. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15882) Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
[
https://issues.apache.org/jira/browse/IGNITE-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441061#comment-17441061
]
Ignite TC Bot commented on IGNITE-15882:
{panel:title=Branch: [pull/9555/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9555/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=6260422buildTypeId=IgniteTests24Java8_RunAll]
> Add check log.isInfoEnabled() to GridCacheDatabaseSharedManager
> ---
>
> Key: IGNITE-15882
> URL: https://issues.apache.org/jira/browse/IGNITE-15882
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to add check *log.isInfoEnabled()* to the
> *GridCacheDatabaseSharedManager* to avoid log messages like this:
> {noformat}
> [2021-08-09 23:35:37,036][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Starting
> binary memory restore for: [-553318133, -553313514, -553318319, -553317295,
> -553317296, -553317293, -553317294, -628844388, -628844387, -628844386,
> -628844385, -628844392, -628844391, -628844390, -628844389, 1648696228,
> 1648696225, 1648696227, 1648696226, -553318226, -553318412, -2100569601,
> 374280891, 374280890, 374280889, 374280888, 374280887, 374280886, 374280885,
> 374280884, -553313607]
> [2021-08-09 23:35:37,886][WARN ][main][GridCacheDatabaseSharedManager]
> Logging at INFO level without checking if INFO level is enabled: Found last
> checkpoint marker [cpId=dcfe9626-f4f5-4772-930e-73749f55b727,
> pos=FileWALPointer [idx=0, fileOff=3094925, len=135903]]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-15883) Remove VariableDeclarationUsageDistance from check-rules/checkstyle-rules.xml
Kirill Tkalenko created IGNITE-15883: Summary: Remove VariableDeclarationUsageDistance from check-rules/checkstyle-rules.xml Key: IGNITE-15883 URL: https://issues.apache.org/jira/browse/IGNITE-15883 Project: Ignite Issue Type: Improvement Components: build Affects Versions: 3.0.0-alpha3 Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha4 Remove *VariableDeclarationUsageDistance* from *check-rules/checkstyle-rules.xml* as it is not strict according to the [code style|https://google.github.io/styleguide/javaguide.html#s4.8.2-variable-declarations]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-12991) Calcite integration. Introduce running query registry & cancellation refactoring
[
https://issues.apache.org/jira/browse/IGNITE-12991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-12991:
--
Labels: calcite3-required sql (was: calcite2-required calcite3-required
sql)
> Calcite integration. Introduce running query registry & cancellation
> refactoring
>
>
> Key: IGNITE-12991
> URL: https://issues.apache.org/jira/browse/IGNITE-12991
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Igor Seliverstov
>Assignee: Taras Ledkov
>Priority: Minor
> Labels: calcite3-required, sql
> Time Spent: 13h 20m
> Remaining Estimate: 0h
>
> Users should have the ability to cancel a query on planning or execution
> stages.
> Firstly we should have API to retrieve the identifier of the query and API to
> cancel a query by the identifier.
> For cancel planning see {{AbstractRelOptPlanner.java:91}}, here
> {{CancelFlag}} is used to cancel planning loop. We need to pass it into a
> newly created context and bind its state with {{PlanningContext#queryCancel}}
> to break possible infinite planning loop. See also {{PlanningContext#unwrap}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15776) Fix code style issue for sql components
[
https://issues.apache.org/jira/browse/IGNITE-15776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441051#comment-17441051
]
Yury Gerzhedovich commented on IGNITE-15776:
[~Berkov], LGTM, except formating with 120 chars line lengths, however, I think
it's not a criminal and it could be merged.
> Fix code style issue for sql components
> ---
>
> Key: IGNITE-15776
> URL: https://issues.apache.org/jira/browse/IGNITE-15776
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Alexander Belyak
>Priority: Major
> Labels: ignite-3
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For bytecode, calcite, schema modules need to fix all new codystyle issues
> except for "SummaryJavadoc"
> steps to start:
> 1. switch to branch ignite-15371-new
> {{2. uncomment all rules in check-rules/checkstyle-rules.xml}} except
> "SumaryJavadoc"
> 3. run mvn validate -Pcheckstyle -Dmaven.all-checks.skip to see all issues.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-15060) ignitecli must provide work directory path during node start
[ https://issues.apache.org/jira/browse/IGNITE-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-15060: Assignee: Vyacheslav Koptilin (was: Sergey Uttsel) > ignitecli must provide work directory path during node start > > > Key: IGNITE-15060 > URL: https://issues.apache.org/jira/browse/IGNITE-15060 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15492) Check schema availability on local node
[ https://issues.apache.org/jira/browse/IGNITE-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441024#comment-17441024 ] Vladislav Pyatkov commented on IGNITE-15492: [~kgusakov] Please, look at the patch. > Check schema availability on local node > --- > > Key: IGNITE-15492 > URL: https://issues.apache.org/jira/browse/IGNITE-15492 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Koptilin >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, we do not check that a schema that is needed for deserialization > returned tuple (for example, the end-user calls tableKvView.get(key) method) > is available on the local node that performs table operation. > Need to implement a synchronization mechanism that allows overcoming an issue > related to the deserialization of tuples. Looks like it is an actual issue > regardless of rebalancing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15530) IndexQuery has to use MergeSort reducer
[ https://issues.apache.org/jira/browse/IGNITE-15530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441016#comment-17441016 ] Amelchev Nikita commented on IGNITE-15530: -- Cherry-picked to the 2.12. > IndexQuery has to use MergeSort reducer > --- > > Key: IGNITE-15530 > URL: https://issues.apache.org/jira/browse/IGNITE-15530 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Fix For: 2.12 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently IndexQuery doesn't sort result over multiple nodes. But the idea of > index is to return ordered result. So, IndexQuery should use MergeSort for a > result cursor. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15530) IndexQuery has to use MergeSort reducer
[ https://issues.apache.org/jira/browse/IGNITE-15530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-15530: - Fix Version/s: 2.12 (was: 2.13) > IndexQuery has to use MergeSort reducer > --- > > Key: IGNITE-15530 > URL: https://issues.apache.org/jira/browse/IGNITE-15530 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Fix For: 2.12 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently IndexQuery doesn't sort result over multiple nodes. But the idea of > index is to return ordered result. So, IndexQuery should use MergeSort for a > result cursor. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15530) IndexQuery has to use MergeSort reducer
[ https://issues.apache.org/jira/browse/IGNITE-15530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440999#comment-17440999 ] Anton Vinogradov commented on IGNITE-15530: --- Merged into master. Thanks for your contribution! > IndexQuery has to use MergeSort reducer > --- > > Key: IGNITE-15530 > URL: https://issues.apache.org/jira/browse/IGNITE-15530 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Fix For: 2.13 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently IndexQuery doesn't sort result over multiple nodes. But the idea of > index is to return ordered result. So, IndexQuery should use MergeSort for a > result cursor. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15833) Provide interfaces for SQL Extension API
[ https://issues.apache.org/jira/browse/IGNITE-15833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-15833: - Assignee: Konstantin Orlov > Provide interfaces for SQL Extension API > > > Key: IGNITE-15833 > URL: https://issues.apache.org/jira/browse/IGNITE-15833 > Project: Ignite > Issue Type: Sub-task >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > During this task we need to provide minimal yet sufficient interfaces to make > extension possible. Followed aspects should be covered: > # Interface of the plugin (draft could be found in parent ticket) > # Interface to implement by relational nodes. Looks like we have to use > IgniteRel here, but it comes at cost of lost validation: IgniteConvention > uses this interface to validate the convention is set for proper rel. Need to > think about this. > # Interface of the schema. In the prototype the > org.apache.calcite.schema.SchemaPlus is used, but it doesn't look as a good > decision. -- This message was sent by Atlassian Jira (v8.20.1#820001)
