[jira] [Updated] (IGNITE-14594) Calcite integration. UnionPlannerTest is not included to any test suite
[ https://issues.apache.org/jira/browse/IGNITE-14594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-14594: --- Priority: Minor (was: Major) > Calcite integration. UnionPlannerTest is not included to any test suite > --- > > Key: IGNITE-14594 > URL: https://issues.apache.org/jira/browse/IGNITE-14594 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Plekhanov >Priority: Minor > > UnionPlannerTest should be included to PlannerTestSuite. > Also, some plan checks should be added to the test, currently it only prints > plan to the output. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12747) Calcite integration. Correlated queries support.
[ https://issues.apache.org/jira/browse/IGNITE-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny reassigned IGNITE-12747: --- Assignee: Stanilovsky Evgeny (was: Andrey Mashenkov) > Calcite integration. Correlated queries support. > > > Key: IGNITE-12747 > URL: https://issues.apache.org/jira/browse/IGNITE-12747 > Project: Ignite > Issue Type: New Feature >Reporter: Igor Seliverstov >Assignee: Stanilovsky Evgeny >Priority: Critical > Time Spent: 3.5h > Remaining Estimate: 0h > > Rewrite correlated subqueries. > Useful links: > [https://zhuanlan.zhihu.com/p/60380557] > [https://zhuanlan.zhihu.com/p/62338250] > [https://zhuanlan.zhihu.com/p/66227661] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14840) Get rid of slf4j in jraft package
[ https://issues.apache.org/jira/browse/IGNITE-14840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14840: --- Description: We should replace slf4j logging with IgniteLogger. (was: We should replace sl4j logging with IgniteLogger.) > Get rid of slf4j in jraft package > - > > Key: IGNITE-14840 > URL: https://issues.apache.org/jira/browse/IGNITE-14840 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > We should replace slf4j logging with IgniteLogger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14841) Use shared distruptor pool for multiple raft group nodes.
[ https://issues.apache.org/jira/browse/IGNITE-14841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14841: --- Summary: Use shared distruptor pool for multiple raft group nodes. (was: Use shared distruptor pool in raft group nodes.) > Use shared distruptor pool for multiple raft group nodes. > - > > Key: IGNITE-14841 > URL: https://issues.apache.org/jira/browse/IGNITE-14841 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently raft uses a thread per raft group per server bound to several > distuptor instances. > It doesn't scale well if the number of groups started on a single server is > significant. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14840) Get rid of slf4j in jraft package
[ https://issues.apache.org/jira/browse/IGNITE-14840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14840: --- Summary: Get rid of slf4j in jraft package (was: Get rid of slfj in jraft package) > Get rid of slf4j in jraft package > - > > Key: IGNITE-14840 > URL: https://issues.apache.org/jira/browse/IGNITE-14840 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > We should replace sl4j logging with IgniteLogger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14838) Fix up messaging in jraft.
[ https://issues.apache.org/jira/browse/IGNITE-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14838: --- Summary: Fix up messaging in jraft. (was: Clean up messages in jraft.) > Fix up messaging in jraft. > -- > > Key: IGNITE-14838 > URL: https://issues.apache.org/jira/browse/IGNITE-14838 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently jraft uses hand coded messages. > This should be cleaned up and switched to generated factories. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14832) Investigate remaining TODOs in org.apache.ignite.raft.jraft package
[ https://issues.apache.org/jira/browse/IGNITE-14832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14832: --- Description: There were several TODOs pushed in IGNITE-13885. They should be investigated and resolved. If necessary, additional tickets must be created and linked to this umbrella ticket. was: There are several TODOs were pushed in IGNITE-13885. They should be investigated and resolved. If necessary, additional tickets must be created and linked to this umbrella ticket. > Investigate remaining TODOs in org.apache.ignite.raft.jraft package > --- > > Key: IGNITE-14832 > URL: https://issues.apache.org/jira/browse/IGNITE-14832 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > There were several TODOs pushed in IGNITE-13885. > They should be investigated and resolved. > If necessary, additional tickets must be created and linked to this umbrella > ticket. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14826) .NET: Thin client fails to compute hash code for string and array keys
[
https://issues.apache.org/jira/browse/IGNITE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358771#comment-17358771
]
Ignite TC Bot commented on IGNITE-14826:
{panel:title=Branch: [pull/9154/head] Base: [master] : Possible Blockers
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}RDD{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6038991]]
{color:#d04437}Cache (Failover) 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6038755]]
{color:#d04437}Activate / Deactivate Cluster{color} [[tests 0 TIMEOUT , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=6038711]]
{color:#d04437}Cache (Full API){color} [[tests 1 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6038758]]
* IgniteCacheFullApiSelfTestSuite:
GridCacheLocalFullApiSelfTest.testEvictExpired - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}Compute (Affinity Run){color} [[tests 1 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6038714]]
* IgniteCacheAffinityRunTestSuite:
IgniteCacheLockPartitionOnAffinityRunTest.testReleasePartitionJobMasterLeave -
Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9154/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Long Running){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6038785]]
* {color:#013220}exe: CacheTest.TestPutGetArrayKey - PASSED{color}
* {color:#013220}exe: CacheTest.TestPutGetArrayKey - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6038808&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Thin client fails to compute hash code for string and array keys
> --
>
> Key: IGNITE-14826
> URL: https://issues.apache.org/jira/browse/IGNITE-14826
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> String keys are not supported in BinaryHashCodeUtils. The following code
> throws "Failed to compute hash code for object" exception:
> {code}
> var server = Ignition.Start();
> var client = Ignition.StartClient(new IgniteClientConfiguration
> {
> Endpoints = new[] {"127.0.0.1"},
> EnablePartitionAwareness = true
> });
> var cache = client.CreateCache("c");
> cache.Put("hello", "world");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14811) .NET: Replace FxCop with Roslyn-based analyzers
[ https://issues.apache.org/jira/browse/IGNITE-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358760#comment-17358760 ] Igor Sapego commented on IGNITE-14811: -- [~ptupitsyn] looks good to me. > .NET: Replace FxCop with Roslyn-based analyzers > --- > > Key: IGNITE-14811 > URL: https://issues.apache.org/jira/browse/IGNITE-14811 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > * FxCop is deprecated long time ago > * It is Windows-only > Remove FxCop and set up build-time Roslyn-based code analysis in DotNetCore > solution: > https://docs.microsoft.com/en-us/visualstudio/code-quality/install-net-analyzers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14811) .NET: Replace FxCop with Roslyn-based analyzers
[ https://issues.apache.org/jira/browse/IGNITE-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358732#comment-17358732 ] Pavel Tupitsyn commented on IGNITE-14811: - [~isapego] please review. > .NET: Replace FxCop with Roslyn-based analyzers > --- > > Key: IGNITE-14811 > URL: https://issues.apache.org/jira/browse/IGNITE-14811 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > * FxCop is deprecated long time ago > * It is Windows-only > Remove FxCop and set up build-time Roslyn-based code analysis in DotNetCore > solution: > https://docs.microsoft.com/en-us/visualstudio/code-quality/install-net-analyzers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14811) .NET: Replace FxCop with Roslyn-based analyzers
[
https://issues.apache.org/jira/browse/IGNITE-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358731#comment-17358731
]
Ignite TC Bot commented on IGNITE-14811:
{panel:title=Branch: [pull/9152/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9152/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=6035599&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Replace FxCop with Roslyn-based analyzers
> ---
>
> Key: IGNITE-14811
> URL: https://issues.apache.org/jira/browse/IGNITE-14811
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * FxCop is deprecated long time ago
> * It is Windows-only
> Remove FxCop and set up build-time Roslyn-based code analysis in DotNetCore
> solution:
> https://docs.microsoft.com/en-us/visualstudio/code-quality/install-net-analyzers
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14811) .NET: Replace FxCop with Roslyn-based analyzers
[
https://issues.apache.org/jira/browse/IGNITE-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14811:
Comment: was deleted
(was: {panel:title=Branch: [pull/9152/head] Base: [master] : Possible Blockers
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility (Zookeeper){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6035592]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=6035639]]
* dll: IgniteStartStopTest.TestStartGetStop - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}Basic 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6035537]]
{color:#d04437}Platform .NET (Long Running){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6035576]]
* exe:
DataStreamerClientTopologyChangeTest.TestStreamerDoesNotLoseDataOnRandomTopologyChanges
- New test duration 73s is more that 1 minute
* exe: DataStreamerClientTopologyChangeTest.TestFlushFailsWhenAllServersStop -
New test duration 222s is more that 1 minute
* exe: DataStreamerClientTopologyChangeTest.TestFlushFailsWhenAllServersStop -
New test duration 222s is more that 1 minute
* exe: CacheAbstractTest.TestCacheConfigurationExpiryPolicy - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6035578]]
* IgniteBinaryCacheQueryTestSuite:
DynamicIndexServerCoordinatorBasicSelfTest.testCreateIndexWithParallelismPartitionedTransactional
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=603]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheInterceptorTransactionalRebalanceTest.testRebalanceRemove - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}AWS{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6035499]]
{panel}
{panel:title=Branch: [pull/9152/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=6035599&buildTypeId=IgniteTests24Java8_RunAll])
> .NET: Replace FxCop with Roslyn-based analyzers
> ---
>
> Key: IGNITE-14811
> URL: https://issues.apache.org/jira/browse/IGNITE-14811
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * FxCop is deprecated long time ago
> * It is Windows-only
> Remove FxCop and set up build-time Roslyn-based code analysis in DotNetCore
> solution:
> https://docs.microsoft.com/en-us/visualstudio/code-quality/install-net-analyzers
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14826) .NET: Thin client fails to compute hash code for string and array keys
[
https://issues.apache.org/jira/browse/IGNITE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358719#comment-17358719
]
Pavel Tupitsyn commented on IGNITE-14826:
-
All .NET suites passed, TC bot does not want to leave a comment for some reason.
Merged to master: 789feff34f78f8544bf7498f22352bc4e22e352a
> .NET: Thin client fails to compute hash code for string and array keys
> --
>
> Key: IGNITE-14826
> URL: https://issues.apache.org/jira/browse/IGNITE-14826
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> String keys are not supported in BinaryHashCodeUtils. The following code
> throws "Failed to compute hash code for object" exception:
> {code}
> var server = Ignition.Start();
> var client = Ignition.StartClient(new IgniteClientConfiguration
> {
> Endpoints = new[] {"127.0.0.1"},
> EnablePartitionAwareness = true
> });
> var cache = client.CreateCache("c");
> cache.Put("hello", "world");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14843) Avoid probing follower if it's dead by discovery
[ https://issues.apache.org/jira/browse/IGNITE-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14843: --- Summary: Avoid probing follower if it's dead by discovery (was: Avoid probing follower if it's dead by discovery in raft protocol) > Avoid probing follower if it's dead by discovery > > > Key: IGNITE-14843 > URL: https://issues.apache.org/jira/browse/IGNITE-14843 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > We can remove some computations (checking for dead nodes) and replace it with > SWIM node alive event - start replicator when the event is received. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14812) SQL statistics
[ https://issues.apache.org/jira/browse/IGNITE-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358716#comment-17358716 ] Yury Gerzhedovich commented on IGNITE-14812: [~Berkov], LGTM. Please provide a Bot Vise. > SQL statistics > -- > > Key: IGNITE-14812 > URL: https://issues.apache.org/jira/browse/IGNITE-14812 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add statistics collection and usage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14843) Avoid probing follower if it's dead by discovery in raft protocol
[ https://issues.apache.org/jira/browse/IGNITE-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14843: --- Summary: Avoid probing follower if it's dead by discovery in raft protocol (was: Avoid probing followers if it's dead by discovery in raft protocol) > Avoid probing follower if it's dead by discovery in raft protocol > - > > Key: IGNITE-14843 > URL: https://issues.apache.org/jira/browse/IGNITE-14843 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > We can remove some computations (checking for dead nodes) and replace it with > SWIM node alive event - start replicator when the event is received. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14834) Move mapping and splitter related code to Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-14834: - Assignee: Konstantin Orlov > Move mapping and splitter related code to Ignite 3.0 > > > Key: IGNITE-14834 > URL: https://issues.apache.org/jira/browse/IGNITE-14834 > Project: Ignite > Issue Type: Sub-task >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14841) Use shared distruptor pool in raft group nodes.
[ https://issues.apache.org/jira/browse/IGNITE-14841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14841: --- Summary: Use shared distruptor pool in raft group nodes. (was: Use shared distruptor pool in raft nodes.) > Use shared distruptor pool in raft group nodes. > --- > > Key: IGNITE-14841 > URL: https://issues.apache.org/jira/browse/IGNITE-14841 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently raft uses a thread per raft group per server bound to several > distuptor instances. > It doesn't scale well if the number of groups is significant. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14841) Use shared distruptor pool in raft group nodes.
[ https://issues.apache.org/jira/browse/IGNITE-14841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14841: --- Description: Currently raft uses a thread per raft group per server bound to several distuptor instances. It doesn't scale well if the number of groups started on a single server is significant. was: Currently raft uses a thread per raft group per server bound to several distuptor instances. It doesn't scale well if the number of groups is significant. > Use shared distruptor pool in raft group nodes. > --- > > Key: IGNITE-14841 > URL: https://issues.apache.org/jira/browse/IGNITE-14841 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently raft uses a thread per raft group per server bound to several > distuptor instances. > It doesn't scale well if the number of groups started on a single server is > significant. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14837) Backport recent changes in jraft master branch
[ https://issues.apache.org/jira/browse/IGNITE-14837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14837: --- Description: Backport recent commits from jraft master branch if it worth. The revision to start is e7b02deea5cb9b281a4bdfb8c0c5e63ba7682870 (1.3.5 release) was:Backport recent commits from jraft master branch, if worth it. > Backport recent changes in jraft master branch > -- > > Key: IGNITE-14837 > URL: https://issues.apache.org/jira/browse/IGNITE-14837 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Backport recent commits from jraft master branch if it worth. > The revision to start is e7b02deea5cb9b281a4bdfb8c0c5e63ba7682870 (1.3.5 > release) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14837) Backport recent changes in jraft master branch
[ https://issues.apache.org/jira/browse/IGNITE-14837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14837: --- Summary: Backport recent changes in jraft master branch (was: Look at recent changes in jraft master branch) > Backport recent changes in jraft master branch > -- > > Key: IGNITE-14837 > URL: https://issues.apache.org/jira/browse/IGNITE-14837 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Backport recent commits from jraft master branch, if worth it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14843) Avoid probing followers if it's dead by discovery in raft protocol
Alexey Scherbakov created IGNITE-14843: -- Summary: Avoid probing followers if it's dead by discovery in raft protocol Key: IGNITE-14843 URL: https://issues.apache.org/jira/browse/IGNITE-14843 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 We can remove some computations (checking for dead nodes) and replace it with SWIM node alive event - start replicator when the event is received. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14842) Calcite engine. Add ability to create tables on existing caches
Aleksey Plekhanov created IGNITE-14842:
--
Summary: Calcite engine. Add ability to create tables on existing
caches
Key: IGNITE-14842
URL: https://issues.apache.org/jira/browse/IGNITE-14842
Project: Ignite
Issue Type: Improvement
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov
We should be able to run \{{CREATE TABLE}} for existing cache (\{{WITH
cache_name="existing_cache"}} parameter)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14841) Use shared distruptor pool in raft nodes.
Alexey Scherbakov created IGNITE-14841: -- Summary: Use shared distruptor pool in raft nodes. Key: IGNITE-14841 URL: https://issues.apache.org/jira/browse/IGNITE-14841 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 Currently raft uses a thread per raft group per server bound to several distuptor instances. It doesn't scale well if the number of groups is significant. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14840) Get rid of slfj in jraft package
Alexey Scherbakov created IGNITE-14840: -- Summary: Get rid of slfj in jraft package Key: IGNITE-14840 URL: https://issues.apache.org/jira/browse/IGNITE-14840 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 We should replace sl4j logging with IgniteLogger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14839) Migrate junit tests to jupiter in jraft package
Alexey Scherbakov created IGNITE-14839: -- Summary: Migrate junit tests to jupiter in jraft package Key: IGNITE-14839 URL: https://issues.apache.org/jira/browse/IGNITE-14839 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 Currently jraft tests use vintage engine. Replace it with junit5 and drop the vintage engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14838) Clean up messages in jraft.
[ https://issues.apache.org/jira/browse/IGNITE-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14838: --- Summary: Clean up messages in jraft. (was: Cleanup messages in jraft.) > Clean up messages in jraft. > --- > > Key: IGNITE-14838 > URL: https://issues.apache.org/jira/browse/IGNITE-14838 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Currently jraft uses hand coded messages. > This should be cleaned up and switched to generated factories. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14838) Cleanup messages in jraft.
Alexey Scherbakov created IGNITE-14838: -- Summary: Cleanup messages in jraft. Key: IGNITE-14838 URL: https://issues.apache.org/jira/browse/IGNITE-14838 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 Currently jraft uses hand coded messages. This should be cleaned up and switched to generated factories. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14837) Look at recent changes in jraft master branch
Alexey Scherbakov created IGNITE-14837: -- Summary: Look at recent changes in jraft master branch Key: IGNITE-14837 URL: https://issues.apache.org/jira/browse/IGNITE-14837 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 Backport recent commits from jraft master branch, if worth it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14836) Integrate all moved part of Caclite engine in Ignite 3.0
Yury Gerzhedovich created IGNITE-14836: -- Summary: Integrate all moved part of Caclite engine in Ignite 3.0 Key: IGNITE-14836 URL: https://issues.apache.org/jira/browse/IGNITE-14836 Project: Ignite Issue Type: Sub-task Reporter: Yury Gerzhedovich -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14835) Move execution related code to Ignite 3.0
Yury Gerzhedovich created IGNITE-14835: -- Summary: Move execution related code to Ignite 3.0 Key: IGNITE-14835 URL: https://issues.apache.org/jira/browse/IGNITE-14835 Project: Ignite Issue Type: Sub-task Reporter: Yury Gerzhedovich -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14834) Move mapping and splitter related code to Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-14834: --- Summary: Move mapping and splitter related code to Ignite 3.0 (was: Move mapping related code to Ignite 3.0) > Move mapping and splitter related code to Ignite 3.0 > > > Key: IGNITE-14834 > URL: https://issues.apache.org/jira/browse/IGNITE-14834 > Project: Ignite > Issue Type: Sub-task >Reporter: Yury Gerzhedovich >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14834) Move mapping related code to Ignite 3.0
Yury Gerzhedovich created IGNITE-14834: -- Summary: Move mapping related code to Ignite 3.0 Key: IGNITE-14834 URL: https://issues.apache.org/jira/browse/IGNITE-14834 Project: Ignite Issue Type: Sub-task Reporter: Yury Gerzhedovich -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14746) Improve row layout. Omit offset for the first varlen.
[ https://issues.apache.org/jira/browse/IGNITE-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358667#comment-17358667 ] Yury Gerzhedovich commented on IGNITE-14746: [~amashenkov], LGTM > Improve row layout. Omit offset for the first varlen. > - > > Key: IGNITE-14746 > URL: https://issues.apache.org/jira/browse/IGNITE-14746 > 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-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > Actually, there is no need to write varlen offset for the very first varlen > column. > Therefore, vartable can be skipped if a single varlen column is defined for > key and/or value. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14833) Bring back checksum support
Alexey Scherbakov created IGNITE-14833: -- Summary: Bring back checksum support Key: IGNITE-14833 URL: https://issues.apache.org/jira/browse/IGNITE-14833 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 Currently checksum support is disabled. It has to be fixed and enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14832) Investigate remaining TODOs in org.apache.ignite.raft.jraft package
Alexey Scherbakov created IGNITE-14832: -- Summary: Investigate remaining TODOs in org.apache.ignite.raft.jraft package Key: IGNITE-14832 URL: https://issues.apache.org/jira/browse/IGNITE-14832 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Fix For: 3.0.0-alpha3 There are several TODOs were pushed in IGNITE-13885. They should be investigated and resolved. If necessary, additional tickets must be created and linked to this umbrella ticket. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14831) [Test failed] GridCommandLineLoaderTest test crashes the process on some environments
[ https://issues.apache.org/jira/browse/IGNITE-14831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luchnikov Alexander updated IGNITE-14831: - Description: If you run this test on macos, then all processes running under the current user will be terminated. If you run this test through jenkins in docker, then jenkins process is interrupted. if you run this test in Linux, then the test passes successfully, but logs contain the message [INFO] [main] [jvm-521bfdd1] Abnormal exit value of 139 for trying to kill the pid -1 was: If you run this test on macos, then all processes running under the current user will be terminated. If you run this test through jenkins in docker, then jenkins process is interrupted. if you run this test in Linux, then the test passes successfully, but logs contain the message [INFO] [main] [jvm-521bfdd1] Abnormal exit value 139 for an attempt to kill pid -1 > [Test failed] GridCommandLineLoaderTest test crashes the process on some > environments > - > > Key: IGNITE-14831 > URL: https://issues.apache.org/jira/browse/IGNITE-14831 > Project: Ignite > Issue Type: Bug >Reporter: Luchnikov Alexander >Assignee: Luchnikov Alexander >Priority: Minor > Labels: newbie > > If you run this test on macos, then all processes running under the current > user will be terminated. > If you run this test through jenkins in docker, then jenkins process is > interrupted. > > if you run this test in Linux, then the test passes successfully, but logs > contain the message [INFO] [main] [jvm-521bfdd1] Abnormal exit value of 139 > for trying to kill the pid -1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14831) [Test failed] GridCommandLineLoaderTest test crashes the process on some environments
Luchnikov Alexander created IGNITE-14831: Summary: [Test failed] GridCommandLineLoaderTest test crashes the process on some environments Key: IGNITE-14831 URL: https://issues.apache.org/jira/browse/IGNITE-14831 Project: Ignite Issue Type: Bug Reporter: Luchnikov Alexander Assignee: Luchnikov Alexander If you run this test on macos, then all processes running under the current user will be terminated. If you run this test through jenkins in docker, then jenkins process is interrupted. if you run this test in Linux, then the test passes successfully, but logs contain the message [INFO] [main] [jvm-521bfdd1] Abnormal exit value 139 for an attempt to kill pid -1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14725) Cluster crashes when the client has a higher byte code version than server
[
https://issues.apache.org/jira/browse/IGNITE-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358624#comment-17358624
]
Surkov Aleksandr commented on IGNITE-14725:
---
[~RyzhovSV] The server does not crash.
Log on the server:
[16:26:56,191][WARNING][disco-event-worker-#61][GridDiscoveryManager] Local
java version is different from remote [loc=8, rmt=11]
Client message:
Caused by: java.lang.UnsupportedClassVersionError:
org/apache/ignite/ThickClient has been compiled by a more recent version of the
Java Runtime (class file version 55.0), this version of the Java Runtime only
recognizes class file versions up to 52.0
> Cluster crashes when the client has a higher byte code version than server
> --
>
> Key: IGNITE-14725
> URL: https://issues.apache.org/jira/browse/IGNITE-14725
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Surkov Aleksandr
>Assignee: Sergei Ryzhov
>Priority: Major
> Attachments: different-java.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the Java version on the server does not support the byte code that the
> client node sends to server, then some operations(Scan Queries) can lead to
> the fall of the cluster.
> Steps to reproduce the situation:
> 1. Start the server using Java 8(org.apache.ignite.SimpleServer#main)
> 2. Start the client using Java 11(target byte code version 11), which will
> run ScanQuery(org.apache.ignite.ThickClient#main)
> Reproducer is attached. Logs from the server and client are located in the
> errors folder.
> {code:java}
> SEVERE: Failed to process message
> [senderId=53c4266d-8b74-480b-bbf5-670bd94c4192, msg=GridCacheQueryRequest
> [id=13, cacheName=cache_scan, type=SCAN, fields=false, clause=null, limit=0,
> clsName=null, keyValFilter=null, rdc=null, trans=null, pageSize=1024,
> incBackups=false, cancel=false, incMeta=false, all=false, keepBinary=false,
> subjId=53c4266d-8b74-480b-bbf5-670bd94c4192, taskHash=0, part=-1,
> topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], mvccSnapshot=null,
> flags=0, super=GridCacheIdMessage [cacheId=29045018, super=GridCacheMessage
> [msgId=14, depInfo=GridDeploymentInfoBean
> [clsLdrId=74845d87971-53c4266d-8b74-480b-bbf5-670bd94c4192, depMode=SHARED,
> userVer=0, locDepOwner=false, participants=null],
> lastAffChangedTopVer=AffinityTopologyVersion [topVer=2, minorTopVer=1],
> err=null, skipPrepare=false
> java.lang.UnsupportedClassVersionError: org/apache/ignite/ThickClient has
> been compiled by a more recent version of the Java Runtime (class file
> version 55.0), this version of the Java Runtime only recognizes class file
> versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:635)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentClassLoader.findClass(GridDeploymentClassLoader.java:543)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentClassLoader.loadClass(GridDeploymentClassLoader.java:461)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9014)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8945)
> at
> org.apache.ignite.internal.managers.deployment.GridDeployment.deployedClass(GridDeployment.java:460)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore.getDeployment(GridDeploymentPerVersionStore.java:441)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentManager.getGlobalDeployment(GridDeploymentManager.java:517)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.tryToloadClassFromCacheDep(GridCacheDeploymentManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.findClass(GridCacheDeploymentManager.java:783)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.loadClass(GridCacheDeploymentManager.java:760)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9012)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8957)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:376)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:693)
> at
> org.a
[jira] [Updated] (IGNITE-14830) Introduce index internal API
[ https://issues.apache.org/jira/browse/IGNITE-14830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-14830: -- Labels: iep-74 ignite-3 (was: ) > Introduce index internal API > > > Key: IGNITE-14830 > URL: https://issues.apache.org/jira/browse/IGNITE-14830 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Labels: iep-74, ignite-3 > Fix For: 3.0.0-alpha3 > > > Introduce internal API for the indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14830) Introduce index internal API
Taras Ledkov created IGNITE-14830: - Summary: Introduce index internal API Key: IGNITE-14830 URL: https://issues.apache.org/jira/browse/IGNITE-14830 Project: Ignite Issue Type: Improvement Components: sql Reporter: Taras Ledkov Assignee: Taras Ledkov Fix For: 3.0.0-alpha3 Introduce internal API for the indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14725) Cluster crashes when the client has a higher byte code version than server
[
https://issues.apache.org/jira/browse/IGNITE-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358606#comment-17358606
]
Sergei Ryzhov commented on IGNITE-14725:
[~surkov] Please check this change and nodes behavior
> Cluster crashes when the client has a higher byte code version than server
> --
>
> Key: IGNITE-14725
> URL: https://issues.apache.org/jira/browse/IGNITE-14725
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Surkov Aleksandr
>Assignee: Sergei Ryzhov
>Priority: Major
> Attachments: different-java.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the Java version on the server does not support the byte code that the
> client node sends to server, then some operations(Scan Queries) can lead to
> the fall of the cluster.
> Steps to reproduce the situation:
> 1. Start the server using Java 8(org.apache.ignite.SimpleServer#main)
> 2. Start the client using Java 11(target byte code version 11), which will
> run ScanQuery(org.apache.ignite.ThickClient#main)
> Reproducer is attached. Logs from the server and client are located in the
> errors folder.
> {code:java}
> SEVERE: Failed to process message
> [senderId=53c4266d-8b74-480b-bbf5-670bd94c4192, msg=GridCacheQueryRequest
> [id=13, cacheName=cache_scan, type=SCAN, fields=false, clause=null, limit=0,
> clsName=null, keyValFilter=null, rdc=null, trans=null, pageSize=1024,
> incBackups=false, cancel=false, incMeta=false, all=false, keepBinary=false,
> subjId=53c4266d-8b74-480b-bbf5-670bd94c4192, taskHash=0, part=-1,
> topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], mvccSnapshot=null,
> flags=0, super=GridCacheIdMessage [cacheId=29045018, super=GridCacheMessage
> [msgId=14, depInfo=GridDeploymentInfoBean
> [clsLdrId=74845d87971-53c4266d-8b74-480b-bbf5-670bd94c4192, depMode=SHARED,
> userVer=0, locDepOwner=false, participants=null],
> lastAffChangedTopVer=AffinityTopologyVersion [topVer=2, minorTopVer=1],
> err=null, skipPrepare=false
> java.lang.UnsupportedClassVersionError: org/apache/ignite/ThickClient has
> been compiled by a more recent version of the Java Runtime (class file
> version 55.0), this version of the Java Runtime only recognizes class file
> versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:635)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentClassLoader.findClass(GridDeploymentClassLoader.java:543)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentClassLoader.loadClass(GridDeploymentClassLoader.java:461)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9014)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8945)
> at
> org.apache.ignite.internal.managers.deployment.GridDeployment.deployedClass(GridDeployment.java:460)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore.getDeployment(GridDeploymentPerVersionStore.java:441)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentManager.getGlobalDeployment(GridDeploymentManager.java:517)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.tryToloadClassFromCacheDep(GridCacheDeploymentManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.findClass(GridCacheDeploymentManager.java:783)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.loadClass(GridCacheDeploymentManager.java:760)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9012)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8957)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:376)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:693)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1641)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1578)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1555)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:383)
> at
> org.apache.ignite.internal
[jira] [Updated] (IGNITE-14474) Improve error message in case rebalance fails
[
https://issues.apache.org/jira/browse/IGNITE-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14474:
-
Fix Version/s: (was: 2.9.2)
2.11
> Improve error message in case rebalance fails
> -
>
> Key: IGNITE-14474
> URL: https://issues.apache.org/jira/browse/IGNITE-14474
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Denis Chudov
>Assignee: Rodion Smolnikov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently we can get a message like this when rebalance fails with an
> exception (examples from ignite 2.5, in newer versions the log messages were
> changed but the problem is still actual):
> {code:java}
> 2019-11-27 13:41:14,504[WARN ][utility-#79%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> 2019-11-27 13:41:14,504[INFO ][utility-#79%xxx%][GridDhtPartitionDemander]
> Cancelled rebalancing [grp=ignite-sys-cache,
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topVer=AffinityTopologyVersion
> [topVer=1932, minorTopVer=1], time=88 ms]
> 2019-11-27 13:41:14,508[WARN ][utility-#76%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=dfa5ee06-48c9-4458-ae55-48cc6ceda998, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> {code}
> In the case above, a marshalling exception leads to rebalance failure which
> will never be resolved - i.e. the cluster enters into a erroneous state.
> We should report issues like this as ERROR. The message should explain that
> the rebalance has failed, data for the cache was not fully copied to the
> node, the backup factor is not recovered and the cluster may not work
> correctly.
>
> After fix:
> New message will looks like this:
> {code:java}
> 2021-06-02 13:52:33,762[ERROR][utility-#79%xxx%][GridDhtPartitionDemander]
> Rebalancing routine has failed, some partitions could be unavailable for
> reading [grp=cache, rebalanceId=1, topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=0], supplier=bf744bda-ba3d-4f48-8172-26d64200,
> unavailablePartitions=[1-256, 768-1024]]
> {code}
> added rebalanceId and unavailablePartitions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14120) select count * returns multiple rows
[ https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-14120: - Assignee: (was: Yury Gerzhedovich) > select count * returns multiple rows > > > Key: IGNITE-14120 > URL: https://issues.apache.org/jira/browse/IGNITE-14120 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8.1 >Reporter: Isaac Zhu >Priority: Major > > I have a partitioned table which has 1 backup, the *queryParallelism* is set > to 4. > The table primary key is column "ID", > If I do this query: > select count( * ) from my_table where ID = 1000; > It will return 4 rows: > 1 > 0 > 0 > 0 > > If I query by other not primary-key columns of this table, the result is > good, like: > select count( *) from my_table where name = 'abcd' > result is: > 0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14413) Start of Ignite node should be supported by ignite-ctl tool
[
https://issues.apache.org/jira/browse/IGNITE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358550#comment-17358550
]
Mirza Aliev commented on IGNITE-14413:
--
Changes look good to me
> Start of Ignite node should be supported by ignite-ctl tool
> ---
>
> Key: IGNITE-14413
> URL: https://issues.apache.org/jira/browse/IGNITE-14413
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Vyacheslav Koptilin
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: iep-73, ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Ignite CLI tool supports the following command now:
> {code:java}
> ignite node start --config path/to/config/file node-name{code}
> but this call starts a naive mock of ignite node.
> We need to implement the actual IgniteCLIRunner, which will be called with:
> * required "nodeName" arg
> * optional "config" arg with json config as a string
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14829) Save DataEntry index inside CDC state
Nikolay Izhikov created IGNITE-14829: Summary: Save DataEntry index inside CDC state Key: IGNITE-14829 URL: https://issues.apache.org/jira/browse/IGNITE-14829 Project: Ignite Issue Type: Bug Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov CDC state should contain an index of DataEntry inside DataRecord to correctly failover. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14828) No fallback to full rebalance after exception on historical
[ https://issues.apache.org/jira/browse/IGNITE-14828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev reassigned IGNITE-14828: Assignee: Mirza Aliev > No fallback to full rebalance after exception on historical > --- > > Key: IGNITE-14828 > URL: https://issues.apache.org/jira/browse/IGNITE-14828 > Project: Ignite > Issue Type: Bug >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Will be filled soon -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13723) Lost & Failed Tests
[ https://issues.apache.org/jira/browse/IGNITE-13723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358503#comment-17358503 ] Maksim Timonin commented on IGNITE-13723: - Hi [~gorchakov]! I've approved your PR. [~ilyak] Could you please have a look and merge this fix [1] to master? How do we should arrange this Jira task for fix of single test only, do we need a separate ticket for that? [1] [https://github.com/apache/ignite/pull/9139] > Lost & Failed Tests > --- > > Key: IGNITE-13723 > URL: https://issues.apache.org/jira/browse/IGNITE-13723 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > This is an umbrella ticket for tests that are lost (weren't take a place in > any suite) and failed& Now they are marked as Ignored with link to this > ticket. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13581) CDC Application
[ https://issues.apache.org/jira/browse/IGNITE-13581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358498#comment-17358498 ] Nikolay Izhikov commented on IGNITE-13581: -- Merged to ignite-cdc. > CDC Application > --- > > Key: IGNITE-13581 > URL: https://issues.apache.org/jira/browse/IGNITE-13581 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59, important > Time Spent: 22h 20m > Remaining Estimate: 0h > > As described in > [IEP-59|https://cwiki.apache.org/confluence/display/IGNITE/IEP-59+CDC+-+Capture+Data+Change] > we need to create IgniteCDC application that can notifies the consumer about > new WAL events. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14828) No fallback to full rebalance after exception on historical
[
https://issues.apache.org/jira/browse/IGNITE-14828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358494#comment-17358494
]
Ignite TC Bot commented on IGNITE-14828:
{panel:title=Branch: [pull/9155/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9155/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=6038394&buildTypeId=IgniteTests24Java8_RunAll]
> No fallback to full rebalance after exception on historical
> ---
>
> Key: IGNITE-14828
> URL: https://issues.apache.org/jira/browse/IGNITE-14828
> Project: Ignite
> Issue Type: Bug
>Reporter: Mirza Aliev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Will be filled soon
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14474) Improve error message in case rebalance fails
[
https://issues.apache.org/jira/browse/IGNITE-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358488#comment-17358488
]
Mirza Aliev commented on IGNITE-14474:
--
[~Smolnikov] Changes look good to me, we should continue with merging
> Improve error message in case rebalance fails
> -
>
> Key: IGNITE-14474
> URL: https://issues.apache.org/jira/browse/IGNITE-14474
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Denis Chudov
>Assignee: Rodion Smolnikov
>Priority: Major
> Fix For: 2.9.2
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently we can get a message like this when rebalance fails with an
> exception (examples from ignite 2.5, in newer versions the log messages were
> changed but the problem is still actual):
> {code:java}
> 2019-11-27 13:41:14,504[WARN ][utility-#79%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> 2019-11-27 13:41:14,504[INFO ][utility-#79%xxx%][GridDhtPartitionDemander]
> Cancelled rebalancing [grp=ignite-sys-cache,
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topVer=AffinityTopologyVersion
> [topVer=1932, minorTopVer=1], time=88 ms]
> 2019-11-27 13:41:14,508[WARN ][utility-#76%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=dfa5ee06-48c9-4458-ae55-48cc6ceda998, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> {code}
> In the case above, a marshalling exception leads to rebalance failure which
> will never be resolved - i.e. the cluster enters into a erroneous state.
> We should report issues like this as ERROR. The message should explain that
> the rebalance has failed, data for the cache was not fully copied to the
> node, the backup factor is not recovered and the cluster may not work
> correctly.
>
> After fix:
> New message will looks like this:
> {code:java}
> 2021-06-02 13:52:33,762[ERROR][utility-#79%xxx%][GridDhtPartitionDemander]
> Rebalancing routine has failed, some partitions could be unavailable for
> reading [grp=cache, rebalanceId=1, topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=0], supplier=bf744bda-ba3d-4f48-8172-26d64200,
> unavailablePartitions=[1-256, 768-1024]]
> {code}
> added rebalanceId and unavailablePartitions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14782) .NET: If bash not installed on pod, ignite fails to start
[
https://issues.apache.org/jira/browse/IGNITE-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14782:
Summary: .NET: If bash not installed on pod, ignite fails to start (was:
.net Thin Client: If bash not installed on pod, ignite fails to start)
> .NET: If bash not installed on pod, ignite fails to start
> -
>
> Key: IGNITE-14782
> URL: https://issues.apache.org/jira/browse/IGNITE-14782
> Project: Ignite
> Issue Type: Bug
> Components: clients, platforms
>Affects Versions: 2.10
>Reporter: Robert May
>Assignee: Pavel Tupitsyn
>Priority: Minor
>
> If bash is not installed, you get the following exception on startup:
> {code:c#}
> System.TypeInitializationException: The type initializer for
> 'Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll' threw an exception.
> ---> System.TypeInitializationException: The type initializer for
> 'Apache.Ignite.Core.Impl.Unmanaged.Os' threw an exception.
> ---> System.ComponentModel.Win32Exception (2): No such file or directory
>at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[]
> argv, String[] envp, String cwd, Boolean redirectStdin, Boolean
> redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32
> userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd,
> Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
>at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
>at System.Diagnostics.Process.Start()
>at Apache.Ignite.Core.Impl.Shell.Execute(String file, String args)
>at Apache.Ignite.Core.Impl.Shell.BashExecute(String args)
>at Apache.Ignite.Core.Impl.Unmanaged.Os..cctor()
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.Os.get_IsWindows()
>at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll..cctor()
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(String
> configJvmDllPath, ILogger log)
>at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14782) .NET: If bash not installed on pod, ignite fails to start
[
https://issues.apache.org/jira/browse/IGNITE-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14782:
Labels: .NET (was: )
> .NET: If bash not installed on pod, ignite fails to start
> -
>
> Key: IGNITE-14782
> URL: https://issues.apache.org/jira/browse/IGNITE-14782
> Project: Ignite
> Issue Type: Bug
> Components: clients, platforms
>Affects Versions: 2.10
>Reporter: Robert May
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
>
> If bash is not installed, you get the following exception on startup:
> {code:c#}
> System.TypeInitializationException: The type initializer for
> 'Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll' threw an exception.
> ---> System.TypeInitializationException: The type initializer for
> 'Apache.Ignite.Core.Impl.Unmanaged.Os' threw an exception.
> ---> System.ComponentModel.Win32Exception (2): No such file or directory
>at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[]
> argv, String[] envp, String cwd, Boolean redirectStdin, Boolean
> redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32
> userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd,
> Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
>at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
>at System.Diagnostics.Process.Start()
>at Apache.Ignite.Core.Impl.Shell.Execute(String file, String args)
>at Apache.Ignite.Core.Impl.Shell.BashExecute(String args)
>at Apache.Ignite.Core.Impl.Unmanaged.Os..cctor()
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.Os.get_IsWindows()
>at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll..cctor()
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(String
> configJvmDllPath, ILogger log)
>at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14782) .net Thin Client: If bash not installed on pod, ignite fails to start
[
https://issues.apache.org/jira/browse/IGNITE-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-14782:
---
Assignee: Pavel Tupitsyn
> .net Thin Client: If bash not installed on pod, ignite fails to start
> -
>
> Key: IGNITE-14782
> URL: https://issues.apache.org/jira/browse/IGNITE-14782
> Project: Ignite
> Issue Type: Bug
> Components: clients, platforms
>Affects Versions: 2.10
>Reporter: Robert May
>Assignee: Pavel Tupitsyn
>Priority: Minor
>
> If bash is not installed, you get the following exception on startup:
> {code:c#}
> System.TypeInitializationException: The type initializer for
> 'Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll' threw an exception.
> ---> System.TypeInitializationException: The type initializer for
> 'Apache.Ignite.Core.Impl.Unmanaged.Os' threw an exception.
> ---> System.ComponentModel.Win32Exception (2): No such file or directory
>at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[]
> argv, String[] envp, String cwd, Boolean redirectStdin, Boolean
> redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32
> userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd,
> Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
>at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
>at System.Diagnostics.Process.Start()
>at Apache.Ignite.Core.Impl.Shell.Execute(String file, String args)
>at Apache.Ignite.Core.Impl.Shell.BashExecute(String args)
>at Apache.Ignite.Core.Impl.Unmanaged.Os..cctor()
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.Os.get_IsWindows()
>at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll..cctor()
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(String
> configJvmDllPath, ILogger log)
>at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14819) ConnectionManager supresses exceptions from the HandshakeManager
[
https://issues.apache.org/jira/browse/IGNITE-14819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358473#comment-17358473
]
Ivan Bessonov commented on IGNITE-14819:
[~apolovtcev] code looks good for me, but I'd wait for [~sdanilov] approval as
well, he knows it better.
> ConnectionManager supresses exceptions from the HandshakeManager
>
>
> Key: IGNITE-14819
> URL: https://issues.apache.org/jira/browse/IGNITE-14819
> Project: Ignite
> Issue Type: Bug
> Components: networking
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 3.0.0-alpha3
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> If an exception is thrown during the handshake, for example, because of a
> missing serialization factory, no errors are logged and no exceptions are
> thrown, \{{ClientManager#connect}} future simply never completes.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14826) .NET: Thin client fails to compute hash code for string and array keys
[
https://issues.apache.org/jira/browse/IGNITE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358467#comment-17358467
]
Igor Sapego commented on IGNITE-14826:
--
[~ptupitsyn] reviewed. Please see my comment in PR
> .NET: Thin client fails to compute hash code for string and array keys
> --
>
> Key: IGNITE-14826
> URL: https://issues.apache.org/jira/browse/IGNITE-14826
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> String keys are not supported in BinaryHashCodeUtils. The following code
> throws "Failed to compute hash code for object" exception:
> {code}
> var server = Ignition.Start();
> var client = Ignition.StartClient(new IgniteClientConfiguration
> {
> Endpoints = new[] {"127.0.0.1"},
> EnablePartitionAwareness = true
> });
> var cache = client.CreateCache("c");
> cache.Put("hello", "world");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14826) .NET: Thin client fails to compute hash code for string and array keys
[
https://issues.apache.org/jira/browse/IGNITE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14826:
Release Note: .NET: Fix string and array cache keys handling when partition
awareness is enabled
> .NET: Thin client fails to compute hash code for string and array keys
> --
>
> Key: IGNITE-14826
> URL: https://issues.apache.org/jira/browse/IGNITE-14826
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> String keys are not supported in BinaryHashCodeUtils. The following code
> throws "Failed to compute hash code for object" exception:
> {code}
> var server = Ignition.Start();
> var client = Ignition.StartClient(new IgniteClientConfiguration
> {
> Endpoints = new[] {"127.0.0.1"},
> EnablePartitionAwareness = true
> });
> var cache = client.CreateCache("c");
> cache.Put("hello", "world");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14826) .NET: Thin client fails to compute hash code for string and array keys
[
https://issues.apache.org/jira/browse/IGNITE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14826:
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> .NET: Thin client fails to compute hash code for string and array keys
> --
>
> Key: IGNITE-14826
> URL: https://issues.apache.org/jira/browse/IGNITE-14826
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> String keys are not supported in BinaryHashCodeUtils. The following code
> throws "Failed to compute hash code for object" exception:
> {code}
> var server = Ignition.Start();
> var client = Ignition.StartClient(new IgniteClientConfiguration
> {
> Endpoints = new[] {"127.0.0.1"},
> EnablePartitionAwareness = true
> });
> var cache = client.CreateCache("c");
> cache.Put("hello", "world");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14826) .NET: Thin client fails to compute hash code for string and array keys
[
https://issues.apache.org/jira/browse/IGNITE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14826:
Description:
String keys are not supported in BinaryHashCodeUtils. The following code throws
"Failed to compute hash code for object" exception:
{code}
var server = Ignition.Start();
var client = Ignition.StartClient(new IgniteClientConfiguration
{
Endpoints = new[] {"127.0.0.1"},
EnablePartitionAwareness = true
});
var cache = client.CreateCache("c");
cache.Put("hello", "world");
{code}
was:
String keys are not supported in BinaryHashCodeUtils:
{code}
var server = Ignition.Start();
var client = Ignition.StartClient(new IgniteClientConfiguration
{
Endpoints = new[] {"127.0.0.1"},
EnablePartitionAwareness = true
});
var cache = client.CreateCache("c");
cache.Put("hello", "world");
{code}
> .NET: Thin client fails to compute hash code for string and array keys
> --
>
> Key: IGNITE-14826
> URL: https://issues.apache.org/jira/browse/IGNITE-14826
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> String keys are not supported in BinaryHashCodeUtils. The following code
> throws "Failed to compute hash code for object" exception:
> {code}
> var server = Ignition.Start();
> var client = Ignition.StartClient(new IgniteClientConfiguration
> {
> Endpoints = new[] {"127.0.0.1"},
> EnablePartitionAwareness = true
> });
> var cache = client.CreateCache("c");
> cache.Put("hello", "world");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14070) Protecting a snapshot from unauthorized changes
[ https://issues.apache.org/jira/browse/IGNITE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-14070: - Assignee: Pavel Pereslegin > Protecting a snapshot from unauthorized changes > --- > > Key: IGNITE-14070 > URL: https://issues.apache.org/jira/browse/IGNITE-14070 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Garus >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-43 > Time Spent: 10m > Remaining Estimate: 0h > > We have to allow Ignite users to check the integrity of snapshot files before > restoring them. > This opportunity can be done through the Ignite plugin mechanism. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11758) Python thin: a lot of documentation files without license header
[ https://issues.apache.org/jira/browse/IGNITE-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-11758: - Fix Version/s: (was: 2.11) python-0.4.0 > Python thin: a lot of documentation files without license header > > > Key: IGNITE-11758 > URL: https://issues.apache.org/jira/browse/IGNITE-11758 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Reporter: Igor Sapego >Assignee: Ivan Daschinsky >Priority: Minor > Fix For: python-0.4.0 > > > There are a lot of .rst documentation files in modules/platforms/python/docs/ > that does not contain license header. We need either delete them if they are > auto generated or add headers to them if they are not. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11758) Python thin: a lot of documentation files without license header
[ https://issues.apache.org/jira/browse/IGNITE-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358432#comment-17358432 ] Ivan Daschinsky commented on IGNITE-11758: -- [~agidaspov] Lesha, there is not python thin client in ignite 2.11. And in 2.10. This ticket is not related to the main ignite release > Python thin: a lot of documentation files without license header > > > Key: IGNITE-11758 > URL: https://issues.apache.org/jira/browse/IGNITE-11758 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Reporter: Igor Sapego >Assignee: Ivan Daschinsky >Priority: Minor > Fix For: 2.11 > > > There are a lot of .rst documentation files in modules/platforms/python/docs/ > that does not contain license header. We need either delete them if they are > auto generated or add headers to them if they are not. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14070) Protecting a snapshot from unauthorized changes
[ https://issues.apache.org/jira/browse/IGNITE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358431#comment-17358431 ] Denis Garus commented on IGNITE-14070: -- Hi, [~xtern]! Ok > Protecting a snapshot from unauthorized changes > --- > > Key: IGNITE-14070 > URL: https://issues.apache.org/jira/browse/IGNITE-14070 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Garus >Priority: Major > Labels: iep-43 > Time Spent: 10m > Remaining Estimate: 0h > > We have to allow Ignite users to check the integrity of snapshot files before > restoring them. > This opportunity can be done through the Ignite plugin mechanism. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14070) Protecting a snapshot from unauthorized changes
[ https://issues.apache.org/jira/browse/IGNITE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus reassigned IGNITE-14070: Assignee: (was: Denis Garus) > Protecting a snapshot from unauthorized changes > --- > > Key: IGNITE-14070 > URL: https://issues.apache.org/jira/browse/IGNITE-14070 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Garus >Priority: Major > Labels: iep-43 > Time Spent: 10m > Remaining Estimate: 0h > > We have to allow Ignite users to check the integrity of snapshot files before > restoring them. > This opportunity can be done through the Ignite plugin mechanism. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11758) Python thin: a lot of documentation files without license header
[ https://issues.apache.org/jira/browse/IGNITE-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Gidaspov updated IGNITE-11758: - Fix Version/s: 2.11 > Python thin: a lot of documentation files without license header > > > Key: IGNITE-11758 > URL: https://issues.apache.org/jira/browse/IGNITE-11758 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Reporter: Igor Sapego >Assignee: Ivan Daschinsky >Priority: Minor > Fix For: 2.11 > > > There are a lot of .rst documentation files in modules/platforms/python/docs/ > that does not contain license header. We need either delete them if they are > auto generated or add headers to them if they are not. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14826) .NET: Thin client fails to compute hash code for string and array keys
[
https://issues.apache.org/jira/browse/IGNITE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14826:
Summary: .NET: Thin client fails to compute hash code for string and array
keys (was: .NET: Thin client fails to compute hash code for string keys)
> .NET: Thin client fails to compute hash code for string and array keys
> --
>
> Key: IGNITE-14826
> URL: https://issues.apache.org/jira/browse/IGNITE-14826
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> String keys are not supported in BinaryHashCodeUtils:
> {code}
> var server = Ignition.Start();
> var client = Ignition.StartClient(new IgniteClientConfiguration
> {
> Endpoints = new[] {"127.0.0.1"},
> EnablePartitionAwareness = true
> });
> var cache = client.CreateCache("c");
> cache.Put("hello", "world");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
