[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Ignite Flags: (was: Release Notes Required)
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, light-console.jpg,
> log4j2-test.xml, prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for dark test console output (pretty similar to spring boot).
> !prod-propsal.png|width=679,height=337!
> light console output example
> !light-console.jpg|width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Attachment: log4j2-test.xml
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, light-console.jpg,
> log4j2-test.xml, prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for dark test console output (pretty similar to spring boot).
> !prod-propsal.png|width=679,height=337!
> light console output example
> !light-console.jpg|width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Description:
Recently completed Ignite migration to use log4j2. So we can use ["highlight"
conversion
pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
colorize the output.
Initial proposal for dark test console output (pretty similar to spring boot).
!prod-propsal.png|width=679,height=337!
light console output example
!light-console.jpg!width=679,height=337!
Pattern for log4j 2.18+
{code:xml}
{code}
For the test framework, there is a suggestion - to color the output of each
node with its own color. Apparently this can't be done without adding your own
plugin, for example LogEventPatternConverter.
was:
!light-console.jpg! Recently completed Ignite migration to use log4j2. So we
can use ["highlight" conversion
pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
colorize the output.
Initial proposal for dark test console output (pretty similar to spring boot).
!prod-propsal.png|width=679,height=337!
light console output example
Pattern for log4j 2.18+
{code:xml}
{code}
For the test framework, there is a suggestion - to color the output of each
node with its own color. Apparently this can't be done without adding your own
plugin, for example LogEventPatternConverter.
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, light-console.jpg,
> prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for dark test console output (pretty similar to spring boot).
> !prod-propsal.png|width=679,height=337!
> light console output example
> !light-console.jpg!width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Description:
Recently completed Ignite migration to use log4j2. So we can use ["highlight"
conversion
pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
colorize the output.
Initial proposal for dark test console output (pretty similar to spring boot).
!prod-propsal.png|width=679,height=337!
light console output example
!light-console.jpg|width=679,height=337!
Pattern for log4j 2.18+
{code:xml}
{code}
For the test framework, there is a suggestion - to color the output of each
node with its own color. Apparently this can't be done without adding your own
plugin, for example LogEventPatternConverter.
was:
Recently completed Ignite migration to use log4j2. So we can use ["highlight"
conversion
pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
colorize the output.
Initial proposal for dark test console output (pretty similar to spring boot).
!prod-propsal.png|width=679,height=337!
light console output example
!light-console.jpg!width=679,height=337!
Pattern for log4j 2.18+
{code:xml}
{code}
For the test framework, there is a suggestion - to color the output of each
node with its own color. Apparently this can't be done without adding your own
plugin, for example LogEventPatternConverter.
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, light-console.jpg,
> prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for dark test console output (pretty similar to spring boot).
> !prod-propsal.png|width=679,height=337!
> light console output example
> !light-console.jpg|width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Description:
!light-console.jpg! Recently completed Ignite migration to use log4j2. So we
can use ["highlight" conversion
pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
colorize the output.
Initial proposal for dark test console output (pretty similar to spring boot).
!prod-propsal.png|width=679,height=337!
light console output example
Pattern for log4j 2.18+
{code:xml}
{code}
For the test framework, there is a suggestion - to color the output of each
node with its own color. Apparently this can't be done without adding your own
plugin, for example LogEventPatternConverter.
was:
Recently completed Ignite migration to use log4j2. So we can use ["highlight"
conversion
pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
colorize the output.
Initial proposal for production console output (pretty similar to spring boot).
!prod-propsal.png|width=679,height=337!
Pattern for log4j 2.18+
{code:xml}
{code}
For the test framework, there is a suggestion - to color the output of each
node with its own color. Apparently this can't be done without adding your own
plugin, for example LogEventPatternConverter.
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, light-console.jpg,
> prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> !light-console.jpg! Recently completed Ignite migration to use log4j2. So we
> can use ["highlight" conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for dark test console output (pretty similar to spring boot).
> !prod-propsal.png|width=679,height=337!
> light console output example
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Attachment: light-console.jpg
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, light-console.jpg,
> prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for production console output (pretty similar to spring
> boot).
> !prod-propsal.png|width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Attachment: (was: log4j2-test.xml)
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for production console output (pretty similar to spring
> boot).
> !prod-propsal.png|width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Attachment: (was: LayoutConverterDraft.java)
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for production console output (pretty similar to spring
> boot).
> !prod-propsal.png|width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17442) Colorize Ignite test console output
[
https://issues.apache.org/jira/browse/IGNITE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17442:
--
Attachment: IgniteDebugLayoutConverter.java
> Colorize Ignite test console output
> ---
>
> Key: IGNITE-17442
> URL: https://issues.apache.org/jira/browse/IGNITE-17442
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: test-framework
> Attachments: IgniteDebugLayoutConverter.java, prod-propsal.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recently completed Ignite migration to use log4j2. So we can use ["highlight"
> conversion
> pattern|https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns] to
> colorize the output.
> Initial proposal for production console output (pretty similar to spring
> boot).
> !prod-propsal.png|width=679,height=337!
> Pattern for log4j 2.18+
> {code:xml}
> pattern="%style{[%d{ISO8601}]}{#77}%highlight{[%-5p]}{FATAL=red blink,
> ERROR=red, WARN=yellow bold, INFO=green, DEBUG=green bold,
> TRACE=blue}%style{[%t]}{magenta}%style{[%c{1}]}{cyan}%notEmpty{[%markerSimpleName]}
> %m%n"/>
> {code}
> For the test framework, there is a suggestion - to color the output of each
> node with its own color. Apparently this can't be done without adding your
> own plugin, for example LogEventPatternConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17610) Rework snapshot cancel command and simplify syntax in control script.
[
https://issues.apache.org/jira/browse/IGNITE-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17610:
--
Description:
Currently we have confusing snapshot restore command syntax.
For example snapshot creation command:
{noformat}
--snapshot create snapshot_Name
{noformat}
But for snapshot restore we should add confusing "--start" option
{noformat}
--snapshot restore snapshot_Name --start
{noformat}
Cancel snapshot creation:
{noformat}
--snapshot cancel snapshot_Name
{noformat}
But to cancel the snapshot restore you have to type something really weird:
{noformat}
--snapshot restore snapshot_Name --cancel
{noformat}
A new common snapshot "status" command has recently been introduced that
displays an *operation ID* that can be used to cancel any snapshot operation in
progress.
h5. So the proposal - make snapshot-commands syntax simple and universal
{noformat}
--snapshot create snapshotName
--snapshot restore snapshotName
--snapshot status
--snapshot cancel operationId
{noformat}
was:
Currently we have confusing snapshot restore command syntax.
For example snapshot creation command:
{noformat}
--snapshot create snapshot_Name
{noformat}
But for snapshot restore we should add confusing "--start" option
{noformat}
--snapshot restore snapshot_Name --start
{noformat}
And the same goes to the "cancel" command.
Cancel snapshot creation:
{noformat}
--snapshot cancel snapshot_Name
{noformat}
But to cancel the snapshot restore you have to type something really weird:
{noformat}
--snapshot restore snapshot_Name --cancel
{noformat}
A new common snapshot "status" command has recently been introduced that
displays an *operation ID* that can be used to cancel any snapshot operation in
progress.
So the proposal - make snapshot-commands syntax simple and universal
{noformat}
--snapshot create snapshotName
--snapshot restore snapshotName
--snapshot status
--snapshot cancel operationId
{noformat}
> Rework snapshot cancel command and simplify syntax in control script.
> -
>
> Key: IGNITE-17610
> URL: https://issues.apache.org/jira/browse/IGNITE-17610
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we have confusing snapshot restore command syntax.
> For example snapshot creation command:
> {noformat}
> --snapshot create snapshot_Name
> {noformat}
> But for snapshot restore we should add confusing "--start" option
> {noformat}
> --snapshot restore snapshot_Name --start
> {noformat}
> Cancel snapshot creation:
> {noformat}
> --snapshot cancel snapshot_Name
> {noformat}
> But to cancel the snapshot restore you have to type something really weird:
> {noformat}
> --snapshot restore snapshot_Name --cancel
> {noformat}
> A new common snapshot "status" command has recently been introduced that
> displays an *operation ID* that can be used to cancel any snapshot operation
> in progress.
> h5. So the proposal - make snapshot-commands syntax simple and universal
> {noformat}
> --snapshot create snapshotName
> --snapshot restore snapshotName
> --snapshot status
> --snapshot cancel operationId
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17610) Rework snapshot cancel command and simplify syntax in control script.
[
https://issues.apache.org/jira/browse/IGNITE-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600512#comment-17600512
]
Ignite TC Bot commented on IGNITE-17610:
{panel:title=Branch: [pull/10236/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10236/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6595545&buildTypeId=IgniteTests24Java8_RunAll]
> Rework snapshot cancel command and simplify syntax in control script.
> -
>
> Key: IGNITE-17610
> URL: https://issues.apache.org/jira/browse/IGNITE-17610
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we have confusing snapshot restore command syntax.
> For example snapshot creation command:
> {noformat}
> --snapshot create snapshot_Name
> {noformat}
> But for snapshot restore we should add confusing "--start" option
> {noformat}
> --snapshot restore snapshot_Name --start
> {noformat}
> And the same goes to the "cancel" command.
> Cancel snapshot creation:
> {noformat}
> --snapshot cancel snapshot_Name
> {noformat}
> But to cancel the snapshot restore you have to type something really weird:
> {noformat}
> --snapshot restore snapshot_Name --cancel
> {noformat}
> A new common snapshot "status" command has recently been introduced that
> displays an *operation ID* that can be used to cancel any snapshot operation
> in progress.
> So the proposal - make snapshot-commands syntax simple and universal
> {noformat}
> --snapshot create snapshotName
> --snapshot restore snapshotName
> --snapshot status
> --snapshot cancel operationId
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17623) .NET: Thin 3.0: Perf: review exception throw sites
[ https://issues.apache.org/jira/browse/IGNITE-17623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17623: Ignite Flags: (was: Docs Required,Release Notes Required) > .NET: Thin 3.0: Perf: review exception throw sites > -- > > Key: IGNITE-17623 > URL: https://issues.apache.org/jira/browse/IGNITE-17623 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-alpha6 > > > *throw* statement prevents inlining. Review all throw statements: > * Internal sanity checks can be replaced with Debug.Assert > * When *throw* is still necessary, and the method is small (candidate for > inlining) - move throw logic into a separate method. > https://devblogs.microsoft.com/dotnet/performance_improvements_in_net_7/#exceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17623) .NET: Thin 3.0: Perf: review exception throw sites
Pavel Tupitsyn created IGNITE-17623: --- Summary: .NET: Thin 3.0: Perf: review exception throw sites Key: IGNITE-17623 URL: https://issues.apache.org/jira/browse/IGNITE-17623 Project: Ignite Issue Type: Task Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-alpha6 *throw* statement prevents inlining. Review all throw statements: * Internal sanity checks can be replaced with Debug.Assert * When *throw* is still necessary, and the method is small (candidate for inlining) - move throw logic into a separate method. https://devblogs.microsoft.com/dotnet/performance_improvements_in_net_7/#exceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17623) .NET: Thin 3.0: Perf: review exception throw sites
[ https://issues.apache.org/jira/browse/IGNITE-17623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17623: Labels: .NET ignite-3 (was: ) > .NET: Thin 3.0: Perf: review exception throw sites > -- > > Key: IGNITE-17623 > URL: https://issues.apache.org/jira/browse/IGNITE-17623 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-alpha6 > > > *throw* statement prevents inlining. Review all throw statements: > * Internal sanity checks can be replaced with Debug.Assert > * When *throw* is still necessary, and the method is small (candidate for > inlining) - move throw logic into a separate method. > https://devblogs.microsoft.com/dotnet/performance_improvements_in_net_7/#exceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17473) Support transactional scan for RW transaction
[ https://issues.apache.org/jira/browse/IGNITE-17473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-17473: -- Fix Version/s: 3.0.0-alpha6 > Support transactional scan for RW transaction > - > > Key: IGNITE-17473 > URL: https://issues.apache.org/jira/browse/IGNITE-17473 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 1.5h > Remaining Estimate: 0h > > We need to support transactional scan in SQL engine. > At the moment, the transactional protocol has a restriction such that the > scan must be issued on the node that initiated the transaction. This makes > optimisations related to a distributed sql execution barely usable, but we > will deal with this later. As a first step, let's just disable distribution > trait in the planner to get local plans. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17610) Rework snapshot cancel command and simplify syntax in control script.
[
https://issues.apache.org/jira/browse/IGNITE-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17610:
--
Description:
Currently we have confusing snapshot restore command syntax.
For example snapshot creation command:
{noformat}
--snapshot create snapshot_Name
{noformat}
But for snapshot restore we should add confusing "--start" option
{noformat}
--snapshot restore snapshot_Name --start
{noformat}
And the same goes to the "cancel" command.
Cancel snapshot creation:
{noformat}
--snapshot cancel snapshot_Name
{noformat}
But to cancel the snapshot restore you have to type something really weird:
{noformat}
--snapshot restore snapshot_Name --cancel
{noformat}
A new common snapshot "status" command has recently been introduced that
displays an *operation ID* that can be used to cancel any snapshot operation in
progress.
So the proposal - make snapshot-commands syntax simple and universal
{noformat}
--snapshot create snapshotName
--snapshot restore snapshotName
--snapshot status
--snapshot cancel operationId
{noformat}
was:
Currently we have confusing snapshot restore command syntax.
For example snapshot creation command:
{noformat}
--snapshot create snapshot_Name
{noformat}
But for snapshot restore we should add confusing "--start" option
{noformat}
--snapshot restore snapshot_Name --start
{noformat}
And the same goes to the "cancel" command.
Cancel snapshot creation:
{noformat}
--snapshot cancel snapshot_Name
{noformat}
But to cancel the snapshot restore you have to type something really weird:
{noformat}
--snapshot restore snapshot_Name --cancel
{noformat}
A new common snapshot "status" command has recently been introduced that
displays an *operation ID* that can be used to cancel any snapshot operation in
progress.
So the proposal - make snapshot-commands syntax common:
{noformat}
--snapshot create snapshotName
--snapshot restore snapshotName
--snapshot status
--snapshot cancel operationId
{noformat}
> Rework snapshot cancel command and simplify syntax in control script.
> -
>
> Key: IGNITE-17610
> URL: https://issues.apache.org/jira/browse/IGNITE-17610
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we have confusing snapshot restore command syntax.
> For example snapshot creation command:
> {noformat}
> --snapshot create snapshot_Name
> {noformat}
> But for snapshot restore we should add confusing "--start" option
> {noformat}
> --snapshot restore snapshot_Name --start
> {noformat}
> And the same goes to the "cancel" command.
> Cancel snapshot creation:
> {noformat}
> --snapshot cancel snapshot_Name
> {noformat}
> But to cancel the snapshot restore you have to type something really weird:
> {noformat}
> --snapshot restore snapshot_Name --cancel
> {noformat}
> A new common snapshot "status" command has recently been introduced that
> displays an *operation ID* that can be used to cancel any snapshot operation
> in progress.
> So the proposal - make snapshot-commands syntax simple and universal
> {noformat}
> --snapshot create snapshotName
> --snapshot restore snapshotName
> --snapshot status
> --snapshot cancel operationId
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17622) [Ignite Website] Automate extensions documentation build
[ https://issues.apache.org/jira/browse/IGNITE-17622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600459#comment-17600459 ] Vladislav Pyatkov commented on IGNITE-17622: Merged 980199b169ff5cecba28799054796d362a44a4a2 > [Ignite Website] Automate extensions documentation build > > > Key: IGNITE-17622 > URL: https://issues.apache.org/jira/browse/IGNITE-17622 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Alexey Alexandrov >Assignee: Erlan Aytpaev >Priority: Minor > > Extensions part of ignite.apache.org documentation is built from > [https://github.com/apache/ignite-extensions,] we need to automate it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17622) [Ignite Website] Automate extensions documentation build
[ https://issues.apache.org/jira/browse/IGNITE-17622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev reassigned IGNITE-17622: -- Assignee: Erlan Aytpaev > [Ignite Website] Automate extensions documentation build > > > Key: IGNITE-17622 > URL: https://issues.apache.org/jira/browse/IGNITE-17622 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Alexey Alexandrov >Assignee: Erlan Aytpaev >Priority: Minor > > Extensions part of ignite.apache.org documentation is built from > [https://github.com/apache/ignite-extensions,] we need to automate it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17622) [Ignite Website] Automate extensions documentation build
Alexey Alexandrov created IGNITE-17622: -- Summary: [Ignite Website] Automate extensions documentation build Key: IGNITE-17622 URL: https://issues.apache.org/jira/browse/IGNITE-17622 Project: Ignite Issue Type: Task Components: website Reporter: Alexey Alexandrov Extensions part of ignite.apache.org documentation is built from [https://github.com/apache/ignite-extensions,] we need to automate it's build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17622) [Ignite Website] Automate extensions documentation build
[ https://issues.apache.org/jira/browse/IGNITE-17622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Alexandrov updated IGNITE-17622: --- Description: Extensions part of ignite.apache.org documentation is built from [https://github.com/apache/ignite-extensions,] we need to automate it. (was: Extensions part of ignite.apache.org documentation is built from [https://github.com/apache/ignite-extensions,] we need to automate it's build.) > [Ignite Website] Automate extensions documentation build > > > Key: IGNITE-17622 > URL: https://issues.apache.org/jira/browse/IGNITE-17622 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Alexey Alexandrov >Priority: Minor > > Extensions part of ignite.apache.org documentation is built from > [https://github.com/apache/ignite-extensions,] we need to automate it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17473) Support transactional scan for RW transaction
[ https://issues.apache.org/jira/browse/IGNITE-17473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600446#comment-17600446 ] Yury Gerzhedovich commented on IGNITE-17473: [~korlov], LGTM > Support transactional scan for RW transaction > - > > Key: IGNITE-17473 > URL: https://issues.apache.org/jira/browse/IGNITE-17473 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Time Spent: 1h 20m > Remaining Estimate: 0h > > We need to support transactional scan in SQL engine. > At the moment, the transactional protocol has a restriction such that the > scan must be issued on the node that initiated the transaction. This makes > optimisations related to a distributed sql execution barely usable, but we > will deal with this later. As a first step, let's just disable distribution > trait in the planner to get local plans. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600394#comment-17600394
]
David Albrecht commented on IGNITE-16136:
-
[~mmuzaf]
Great that you found the issue.
We already updated to 2.11.1 so no need for 2.7.6.
In general, I doubt that a cherry-pick into an older branch makes sense for us,
since we can't reproduce the problem and not verify if the fix works.
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Assignee: Maxim Muzafarov
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: configuration.zip, image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(Ljava/util/concurrent/ConcurrentMap;ILjava/lang/ClassLoader;Lorg/apache/ignite/marshaller/MarshallerContext;Lorg/apache/ignite/internal/marshaller/optimized/OptimizedMarshallerIdMapper;)Lorg/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor;
> (OptimizedMarshallerUtils.java:264)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:341)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride()Ljava/lang/Object;
> (OptimizedObject
[jira] [Created] (IGNITE-17621) InFlightFutures does not properly register a new future which is already in completed state
Vyacheslav Koptilin created IGNITE-17621:
Summary: InFlightFutures does not properly register a new future
which is already in completed state
Key: IGNITE-17621
URL: https://issues.apache.org/jira/browse/IGNITE-17621
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin
Fix For: 3.0.0-alpha6
The following method does not clean up the internal collection of futures in
case the registered future was completed before calling the _registerFuture_:
{code:java}
/**
* Registers a future in the in-flight futures collection. When it
completes (either normally or exceptionally),
* it will be removed from the collection.
*
* @param future the future to register
*/
public void registerFuture(CompletableFuture future) {
future.whenComplete((result, ex) -> inFlightFutures.remove(future));
inFlightFutures.add(future);
}
{code}
The fix is quite obvious - we just need to re-order these two lines :)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17621) InFlightFutures does not properly register a new future which is already in completed state
[
https://issues.apache.org/jira/browse/IGNITE-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-17621:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> InFlightFutures does not properly register a new future which is already in
> completed state
> ---
>
> Key: IGNITE-17621
> URL: https://issues.apache.org/jira/browse/IGNITE-17621
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Trivial
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> The following method does not clean up the internal collection of futures in
> case the registered future was completed before calling the _registerFuture_:
> {code:java}
> /**
> * Registers a future in the in-flight futures collection. When it
> completes (either normally or exceptionally),
> * it will be removed from the collection.
> *
> * @param future the future to register
> */
> public void registerFuture(CompletableFuture future) {
> future.whenComplete((result, ex) -> inFlightFutures.remove(future));
> inFlightFutures.add(future);
> }
> {code}
> The fix is quite obvious - we just need to re-order these two lines :)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17620) [Ignite Website] Update ignite-extensions header
[
https://issues.apache.org/jira/browse/IGNITE-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600330#comment-17600330
]
Vladislav Pyatkov commented on IGNITE-17620:
Merged eaa36e4ce938d921debdd53eb2a0532413e8dfba
[~hoter] Thank you for contribution.
> [Ignite Website] Update ignite-extensions header
>
>
> Key: IGNITE-17620
> URL: https://issues.apache.org/jira/browse/IGNITE-17620
> Project: Ignite
> Issue Type: Task
> Components: website
>Reporter: Alexey Alexandrov
>Assignee: Erlan Aytpaev
>Priority: Minor
>
> Please replace commented-out header in
> [https://github.com/apache/ignite-extensions/blob/master/docs/_includes/header.html]
> With this:
> {code:xml}
>
>
>
>
> width="18" height="12" alt="menu icon" />
>
>
>
> src="{{'assets/images/apache_ignite_logo.svg'|relative_url}}" alt="Apache
> Ignite logo" width="103" height="36" >
>
>
>
> src='{{"assets/images/cancel.svg"|relative_url}}' alt="close" width="10"
> height="10" />
>
>
> ⋮
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-16916) Make nodes more resilient in case of a job cancellation
[ https://issues.apache.org/jira/browse/IGNITE-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600322#comment-17600322 ] Pavel Pereslegin commented on IGNITE-16916: --- [~ktkale...@gridgain.com], could you please suggest any workaround for system/internal tasks to cancel them immediately without changing 'computeJobWorkerInterruptTimeout' property? > Make nodes more resilient in case of a job cancellation > --- > > Key: IGNITE-16916 > URL: https://issues.apache.org/jira/browse/IGNITE-16916 > Project: Ignite > Issue Type: Task > Components: compute >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.14 > > Attachments: image-2022-05-05-12-46-26-543.png, screenshot-1.png > > Time Spent: 40m > Remaining Estimate: 0h > > In case of a job being cancelled we currently have a really questionable > approach. > We are now setting the interruption flag even before we give a use a chance > to stop the job gracefully. > Proposal for the implementation: > * Adding a distributed property in the metastore that will set a timeout for > interrupting *GridJobWorker* that did not gracefully complete after calling > *GridJobWorker#cancel*; > * On the call of the *GridJobWorker#cancel*, do not *Thread#interrupt* the > thread, but add *GridTimeoutObject*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17620) [Ignite Website] Update ignite-extensions header
[
https://issues.apache.org/jira/browse/IGNITE-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Alexandrov updated IGNITE-17620:
---
Description:
Please replace commented-out header in
[https://github.com/apache/ignite-extensions/blob/master/docs/_includes/header.html]
With this:
{code:xml}
⋮
{code}
was:
Please replace commented-out header in
[https://github.com/apache/ignite-extensions/blob/master/docs/_includes/header.html]
With this:
⋮
> [Ignite Website] Update ignite-extensions header
>
>
> Key: IGNITE-17620
> URL: https://issues.apache.org/jira/browse/IGNITE-17620
> Project: Ignite
> Issue Type: Task
> Components: website
>Reporter: Alexey Alexandrov
>Assignee: Erlan Aytpaev
>Priority: Minor
>
> Please replace commented-out header in
> [https://github.com/apache/ignite-extensions/blob/master/docs/_includes/header.html]
> With this:
> {code:xml}
>
>
>
>
> width="18" height="12" alt="menu icon" />
>
>
>
> src="{{'assets/images/apache_ignite_logo.svg'|relative_url}}" alt="Apache
> Ignite logo" width="103" height="36" >
>
>
>
> src='{{"assets/images/cancel.svg"|relative_url}}' alt="close" width="10"
> height="10" />
>
>
> ⋮
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17620) [Ignite Website] Update ignite-extensions header
[
https://issues.apache.org/jira/browse/IGNITE-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erlan Aytpaev reassigned IGNITE-17620:
--
Assignee: Erlan Aytpaev
> [Ignite Website] Update ignite-extensions header
>
>
> Key: IGNITE-17620
> URL: https://issues.apache.org/jira/browse/IGNITE-17620
> Project: Ignite
> Issue Type: Task
> Components: website
>Reporter: Alexey Alexandrov
>Assignee: Erlan Aytpaev
>Priority: Minor
>
> Please replace commented-out header in
> [https://github.com/apache/ignite-extensions/blob/master/docs/_includes/header.html]
> With this:
>
>
>
>
> width="18" height="12" alt="menu icon" />
>
>
>
> src="\{{'assets/images/apache_ignite_logo.svg'|relative_url}}" alt="Apache
> Ignite logo" width="103" height="36" >
>
>
>
> src='\{{"assets/images/cancel.svg"|relative_url}}' alt="close" width="10"
> height="10" />
>
>
> ⋮
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17620) [Ignite Website] Update ignite-extensions header
Alexey Alexandrov created IGNITE-17620: -- Summary: [Ignite Website] Update ignite-extensions header Key: IGNITE-17620 URL: https://issues.apache.org/jira/browse/IGNITE-17620 Project: Ignite Issue Type: Task Components: website Reporter: Alexey Alexandrov Please replace commented-out header in [https://github.com/apache/ignite-extensions/blob/master/docs/_includes/header.html] With this: ⋮ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-16040) Calcite. Unable to plan query with several correlated sub-queries in select list
[
https://issues.apache.org/jira/browse/IGNITE-16040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600286#comment-17600286
]
Konstantin Orlov commented on IGNITE-16040:
---
[~zstan], I've left a couple of comments. Please check PR
> Calcite. Unable to plan query with several correlated sub-queries in select
> list
>
>
> Key: IGNITE-16040
> URL: https://issues.apache.org/jira/browse/IGNITE-16040
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently the query like below can't be planned by calcite-based sql engine:
> {code:java}
> SELECT a+b*2,
>(a+b+c+d+e)/5,
>(SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d(SELECT count(*) FROM t1 AS x WHERE x.babs(b-c),
>a-b
> FROM t1
> WHERE EXISTS(SELECT 1 FROM t1 AS x WHERE x.bAND c>d
> ORDER BY 6,5,4,1,3,2
> {code}
> Need to figure it out how to fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17565) Update Ignite dependency: jodd-lagarto
[ https://issues.apache.org/jira/browse/IGNITE-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600270#comment-17600270 ] Ivan Daschinsky commented on IGNITE-17565: -- [~tledkov] It seems that this ticket is minor and it relates to building tools. It seems that release notes doesn't have to be added to release notes. > Update Ignite dependency: jodd-lagarto > -- > > Key: IGNITE-17565 > URL: https://issues.apache.org/jira/browse/IGNITE-17565 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update dependency jodd-lagarto 3.4.8 to 6.0.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17565) Update Ignite dependency: jodd-lagarto
[ https://issues.apache.org/jira/browse/IGNITE-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-17565: - Release Note: (was: Update dependency jodd-lagarto to 6.0.6 ) > Update Ignite dependency: jodd-lagarto > -- > > Key: IGNITE-17565 > URL: https://issues.apache.org/jira/browse/IGNITE-17565 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update dependency jodd-lagarto 3.4.8 to 6.0.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17581) Create test TxStateStorage implementation
[ https://issues.apache.org/jira/browse/IGNITE-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov reassigned IGNITE-17581: - Assignee: Denis Chudov > Create test TxStateStorage implementation > - > > Key: IGNITE-17581 > URL: https://issues.apache.org/jira/browse/IGNITE-17581 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Minor > Labels: ignite-3, transaction3_rw > > h3. Motivation > It's an overkill to use RocksDB based implementation of TxStateStorage in > most tests, so let's introduce test ConcurrentHashMap based implementation of > TxStateStorage like it's done with TestConcurrentHashMapMvPartitionStorage > for MvPartitionStorage. > h3. Definition of Done > * New TestConcurrentHashMapTxStateStorage is implemented. > * Aforementioned class is used wherever possible within tests. Some of such > places are marked with corresponding todo, but not all unfortunately. > h3. Implementation Notes > Let's use TestConcurrentHashMapMvPartitionStorage as a reference > implementation. It's pretty simple. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17108) Update Docker deliveries
[ https://issues.apache.org/jira/browse/IGNITE-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600255#comment-17600255 ] Taras Ledkov commented on IGNITE-17108: --- [~vveider], the patch is OK with me. > Update Docker deliveries > > > Key: IGNITE-17108 > URL: https://issues.apache.org/jira/browse/IGNITE-17108 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 2.13 >Reporter: Petr Ivanov >Assignee: Petr Ivanov >Priority: Major > Fix For: 2.14 > > > # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) > # Add JDK11 Dockerfile > # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17565) Update Ignite dependency: jodd-lagarto
[ https://issues.apache.org/jira/browse/IGNITE-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17565: --- Release Note: Update dependency jodd-lagarto to 6.0.6 > Update Ignite dependency: jodd-lagarto > -- > > Key: IGNITE-17565 > URL: https://issues.apache.org/jira/browse/IGNITE-17565 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update dependency jodd-lagarto 3.4.8 to 6.0.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17090) Map sql errors to messages that user see
[
https://issues.apache.org/jira/browse/IGNITE-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-17090:
-
Reviewer: Vyacheslav Koptilin
> Map sql errors to messages that user see
>
>
> Key: IGNITE-17090
> URL: https://issues.apache.org/jira/browse/IGNITE-17090
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Assignee: Aleksandr
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There is a number of errors that user can get during sql command execution.
> Map all types of errors and map them to exit error codes and user messages.
> Also, a user has to understand what is wrong with the query. Now it displays
> jusn an abstract message.
>
> How it works now:
> {code:java}
> sql-cli> create table myta
> SQL query parsing error: Sql query execution failed.
> sql-cli> {code}
> {code:java}
> sql-cli> create table mytable(i int, j int);
> Unrecognized error while process SQL query.
> sql-cli> {code}
> "SQL query parsing error: Sql query execution failed.", "Unrecognized error
> while process SQL query." say nothing about {*}what exactly is wrong{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17618) Update Ignite dependency: Jackson Databind
[ https://issues.apache.org/jira/browse/IGNITE-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17618: --- Release Note: Updated Mesos dependency to 1.11.0. CVE-2020-36518 (was: fix CVE-2020-36518) > Update Ignite dependency: Jackson Databind > --- > > Key: IGNITE-17618 > URL: https://issues.apache.org/jira/browse/IGNITE-17618 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update dependency: jackson 2.12.4 to 2.12.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17618) Update Ignite dependency: Jackson Databind
[ https://issues.apache.org/jira/browse/IGNITE-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17618: --- Release Note: Updated Jackson Databind dependency to 2.12.7 (CVE-2020-36518) (was: Updated Mesos dependency to 1.11.0. CVE-2020-36518) > Update Ignite dependency: Jackson Databind > --- > > Key: IGNITE-17618 > URL: https://issues.apache.org/jira/browse/IGNITE-17618 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update dependency: jackson 2.12.4 to 2.12.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17618) Update Ignite dependency: Jackson Databind
[ https://issues.apache.org/jira/browse/IGNITE-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17618: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: Jackson Databind > --- > > Key: IGNITE-17618 > URL: https://issues.apache.org/jira/browse/IGNITE-17618 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update dependency: jackson 2.12.4 to 2.12.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17618) Update Ignite dependency: Jackson Databind
[ https://issues.apache.org/jira/browse/IGNITE-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17618: --- Release Note: fix CVE-2020-36518 (was: CVE-2020-36518) > Update Ignite dependency: Jackson Databind > --- > > Key: IGNITE-17618 > URL: https://issues.apache.org/jira/browse/IGNITE-17618 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update dependency: jackson 2.12.4 to 2.12.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17618) Update Ignite dependency: Jackson Databind
[ https://issues.apache.org/jira/browse/IGNITE-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17618: --- Release Note: CVE-2020-36518 > Update Ignite dependency: Jackson Databind > --- > > Key: IGNITE-17618 > URL: https://issues.apache.org/jira/browse/IGNITE-17618 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update dependency: jackson 2.12.4 to 2.12.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17593) .NET: Thin 3.0: Implement BinaryTuple serialization
[ https://issues.apache.org/jira/browse/IGNITE-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17593: Ignite Flags: (was: Docs Required,Release Notes Required) > .NET: Thin 3.0: Implement BinaryTuple serialization > --- > > Key: IGNITE-17593 > URL: https://issues.apache.org/jira/browse/IGNITE-17593 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-92, ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17593) .NET: Thin 3.0: Implement BinaryTuple serialization
[ https://issues.apache.org/jira/browse/IGNITE-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600244#comment-17600244 ] Pavel Tupitsyn commented on IGNITE-17593: - Merged to main: https://github.com/apache/ignite-3/commit/3cea078225b107a6b75d4d06973d362d6a973a50 > .NET: Thin 3.0: Implement BinaryTuple serialization > --- > > Key: IGNITE-17593 > URL: https://issues.apache.org/jira/browse/IGNITE-17593 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-92, ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17593) .NET: Thin 3.0: Implement BinaryTuple serialization
[ https://issues.apache.org/jira/browse/IGNITE-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17593: Release Note: (was: Merged to main: https://github.com/apache/ignite-3/commit/3cea078225b107a6b75d4d06973d362d6a973a50) > .NET: Thin 3.0: Implement BinaryTuple serialization > --- > > Key: IGNITE-17593 > URL: https://issues.apache.org/jira/browse/IGNITE-17593 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-92, ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13348) Creating IgniteAtomicLong from the client node may hang.
[
https://issues.apache.org/jira/browse/IGNITE-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-13348:
--
Fix Version/s: (was: 2.14)
> Creating IgniteAtomicLong from the client node may hang.
>
>
> Key: IGNITE-13348
> URL: https://issues.apache.org/jira/browse/IGNITE-13348
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Attachments: DataStructuresInitializationTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like, the data structure processor does not properly initialize when
> a client node connects to a cluster that changes its own state (state
> transition from the inactive state to active).
> reproducer attached.
> *UPDATE*
> It seems to me, the root cause of the issue is that {{joinFut}} is always
> completed with {{false}}.
> {code:java|title=GridClusterStateProcessor.java}
> /** {@inheritDoc} */
> @Override public void onStateFinishMessage(ChangeGlobalStateFinishMessage
> msg) {
> DiscoveryDataClusterState discoClusterState = globalState;
> if (msg.requestId().equals(discoClusterState.transitionRequestId())) {
> ...
> TransitionOnJoinWaitFuture joinFut = this.joinFut;
> if (joinFut != null)
> joinFut.onDone(false);
> ...
> }
> else
> U.warn(log, "Received state finish message with unexpected ID: "
> + msg);
> }
> {code}
> On the other hand, this value is used to determine the state of the cluster
> when a new node joins the cluster
> {code:java|title=IgniteKernal.java}
> public void start(
> DiscoveryLocalJoinData joinData = ctx.discovery().localJoin();
> IgniteInternalFuture transitionWaitFut =
> joinData.transitionWaitFuture();
> ...
> boolean active;
> if (transitionWaitFut != null) {
> if (log.isInfoEnabled()) {
> log.info("Join cluster while cluster state transition is
> in progress, waiting when transition finish.");
> }
> active = transitionWaitFut.get();
> }
> else
> active = joinData.active();
> startTimer.finishGlobalStage("Await transition");
> ...
> }
> {code}
> User list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-node-hangs-while-IgniteAtomicLong-is-created-tp33537.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-9386) control.sh --tx can produce confusing results when limit is set to small value
[ https://issues.apache.org/jira/browse/IGNITE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-9386: - Fix Version/s: 2.15 (was: 2.14) > control.sh --tx can produce confusing results when limit is set to small value > -- > > Key: IGNITE-9386 > URL: https://issues.apache.org/jira/browse/IGNITE-9386 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Affects Versions: 2.10 >Reporter: Alexey Scherbakov >Assignee: Rodion Smolnikov >Priority: Major > Fix For: 2.15 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > This is happening because currently the limit is applied to primary and > backup transactions, which breaks output post-filtering (removal of primary > and backup transactions from output if near is present). > Possible solution: apply limit only to near valid transactions. If some txs > have no near part (broken tx topology), they should be always visible in > output, probably with special "broken" marking. > Best way to achieve this - implement tx paging on client side (using > continuous mapping) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17618) Update Ignite dependency: Jackson Databind
[ https://issues.apache.org/jira/browse/IGNITE-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17618: --- Fix Version/s: 2.14 > Update Ignite dependency: Jackson Databind > --- > > Key: IGNITE-17618 > URL: https://issues.apache.org/jira/browse/IGNITE-17618 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Update dependency: jackson 2.12.4 to 2.12.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17541) Add "set" prefix to ThinClientConfiguration#sendServerExceptionStackTraceToClient()
[
https://issues.apache.org/jira/browse/IGNITE-17541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600241#comment-17600241
]
Julia Bakulina commented on IGNITE-17541:
-
[~alexpl], could you please review my changes?
> Add "set" prefix to
> ThinClientConfiguration#sendServerExceptionStackTraceToClient()
> ---
>
> Key: IGNITE-17541
> URL: https://issues.apache.org/jira/browse/IGNITE-17541
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.13
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: ise, newbie
> Time Spent: 2h 25m
> Remaining Estimate: 0h
>
> IGNITE-13389 introduces
> {{ThinClientConfiguration#sendServerExceptionStackTraceToClient()}}, but name
> of the method does not allow to set up this option in XML configuration,
> because Spring expects "set" prefix for setters.
> As you can see below, there is a workaround, but it would be more convenient
> to set up this property directly.
> Workaround:
> {code:xml|title=Add extra ThinClientConfiguration bean with necessary
> parameters}
> class="org.apache.ignite.configuration.ThinClientConfiguration">
>
>
> {code}
> {code:xml|title=Set up thinClientConfiguration by means of SpEL}
>
> class="org.apache.ignite.configuration.ClientConnectorConfiguration">
>
> value="#{thinClientCfg.sendServerExceptionStackTraceToClient(true)}"/>
>
>
> {code}
> We should add "set" and "get" prefix to setter and getter methods
> respectively or add extra methods with such prefixes from the point of
> possible compatibility issues (see IGNITE-16549).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17541) Add "set" prefix to ThinClientConfiguration#sendServerExceptionStackTraceToClient()
[
https://issues.apache.org/jira/browse/IGNITE-17541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julia Bakulina updated IGNITE-17541:
Reviewer: Alex Plehanov (was: Ivan Daschinsky)
> Add "set" prefix to
> ThinClientConfiguration#sendServerExceptionStackTraceToClient()
> ---
>
> Key: IGNITE-17541
> URL: https://issues.apache.org/jira/browse/IGNITE-17541
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.13
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: ise, newbie
> Time Spent: 2h 25m
> Remaining Estimate: 0h
>
> IGNITE-13389 introduces
> {{ThinClientConfiguration#sendServerExceptionStackTraceToClient()}}, but name
> of the method does not allow to set up this option in XML configuration,
> because Spring expects "set" prefix for setters.
> As you can see below, there is a workaround, but it would be more convenient
> to set up this property directly.
> Workaround:
> {code:xml|title=Add extra ThinClientConfiguration bean with necessary
> parameters}
> class="org.apache.ignite.configuration.ThinClientConfiguration">
>
>
> {code}
> {code:xml|title=Set up thinClientConfiguration by means of SpEL}
>
> class="org.apache.ignite.configuration.ClientConnectorConfiguration">
>
> value="#{thinClientCfg.sendServerExceptionStackTraceToClient(true)}"/>
>
>
> {code}
> We should add "set" and "get" prefix to setter and getter methods
> respectively or add extra methods with such prefixes from the point of
> possible compatibility issues (see IGNITE-16549).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17541) Add "set" prefix to ThinClientConfiguration#sendServerExceptionStackTraceToClient()
[
https://issues.apache.org/jira/browse/IGNITE-17541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600234#comment-17600234
]
Ignite TC Bot commented on IGNITE-17541:
{panel:title=Branch: [pull/10230/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10230/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=6756488&buildTypeId=IgniteTests24Java8_RunAll]
> Add "set" prefix to
> ThinClientConfiguration#sendServerExceptionStackTraceToClient()
> ---
>
> Key: IGNITE-17541
> URL: https://issues.apache.org/jira/browse/IGNITE-17541
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.13
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: ise, newbie
> Time Spent: 2h 25m
> Remaining Estimate: 0h
>
> IGNITE-13389 introduces
> {{ThinClientConfiguration#sendServerExceptionStackTraceToClient()}}, but name
> of the method does not allow to set up this option in XML configuration,
> because Spring expects "set" prefix for setters.
> As you can see below, there is a workaround, but it would be more convenient
> to set up this property directly.
> Workaround:
> {code:xml|title=Add extra ThinClientConfiguration bean with necessary
> parameters}
> class="org.apache.ignite.configuration.ThinClientConfiguration">
>
>
> {code}
> {code:xml|title=Set up thinClientConfiguration by means of SpEL}
>
> class="org.apache.ignite.configuration.ClientConnectorConfiguration">
>
> value="#{thinClientCfg.sendServerExceptionStackTraceToClient(true)}"/>
>
>
> {code}
> We should add "set" and "get" prefix to setter and getter methods
> respectively or add extra methods with such prefixes from the point of
> possible compatibility issues (see IGNITE-16549).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
