[jira] [Updated] (IGNITE-16083) .NET: Thin client services don't work properly
[
https://issues.apache.org/jira/browse/IGNITE-16083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-16083:
-
Fix Version/s: 2.13
> .NET: Thin client services don't work properly
> --
>
> Key: IGNITE-16083
> URL: https://issues.apache.org/jira/browse/IGNITE-16083
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Even after IGNITE-14742 Thin client serde process on .Net side doesn't work
> properly for array.
> See attached tests added during IGNITE-14299
> {code}
> ///
> /// Tests Java service invocation.
> ///
> [Test]
> [Ignore("https://issues.apache.org/jira/browse/IGNITE-16083;)]
> public void TestCallJavaServiceThinClient()
> {
> var svc =
> _thinClient.GetServices().GetServiceProxy(_javaSvcName);
> var binSvc = _thinClient.GetServices()
> .WithKeepBinary().WithServerKeepBinary()
> .GetServiceProxy(_javaSvcName);
> DoTestService(svc);
> DoTestBinary(svc, binSvc);
> DoTestJavaExceptions(svc, true);
> }
> {code}
> {code}
> ///
> /// Tests .Net service invocation with thin client.
> ///
> [Test]
> [Ignore("https://issues.apache.org/jira/browse/IGNITE-16083;)]
> public void TestPlatformServiceThinClient()
> {
>
> DoTestService(_thinClient.GetServices().GetServiceProxy(PlatformSvcName));
> }
> ///
> /// Tests Java service invocation with thin client.
> /// Types should be resolved implicitly.
> ///
> [Test]
> [Ignore("https://issues.apache.org/jira/browse/IGNITE-16083;)]
> public void TestJavaServiceThinClient()
> {
>
> DoTestService(_thinClient.GetServices().GetServiceProxy(_javaSvcName));
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16121) Thin 3.0: Implement KeyValueView with POJO mapping
[ https://issues.apache.org/jira/browse/IGNITE-16121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463615#comment-17463615 ] Pavel Tupitsyn commented on IGNITE-16121: - Merged to main: 21e9cd89e694877dc1aa26f65dff266478f9d633 > Thin 3.0: Implement KeyValueView with POJO mapping > -- > > Key: IGNITE-16121 > URL: https://issues.apache.org/jira/browse/IGNITE-16121 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Implement KeyValueView for Java thin client. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16185) Improve the interface of UserObjectMarshaller
[ https://issues.apache.org/jira/browse/IGNITE-16185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy updated IGNITE-16185: --- Summary: Improve the interface of UserObjectMarshaller (was: Improve interface of UserObjectMarshaller) > Improve the interface of UserObjectMarshaller > - > > Key: IGNITE-16185 > URL: https://issues.apache.org/jira/browse/IGNITE-16185 > Project: Ignite > Issue Type: Sub-task >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > > There should be 2 'registries' of class descriptors: local one (which is > global and contains descriptors for classes loaded by the local node) and > remote one (which is session-bound and contains only descriptors received > from a remote node). > marshal() method should only work with the local registry in read-write mode > (as it can add descriptors for classes never marshalled before). > unmarshal() method should work with the merge of local and remote registries > (remote registry taking precedence), but only in read-only mode (it should > not modify the registries). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16185) Improve interface of UserObjectMarshaller
Roman Puchkovskiy created IGNITE-16185: -- Summary: Improve interface of UserObjectMarshaller Key: IGNITE-16185 URL: https://issues.apache.org/jira/browse/IGNITE-16185 Project: Ignite Issue Type: Sub-task Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-alpha4 There should be 2 'registries' of class descriptors: local one (which is global and contains descriptors for classes loaded by the local node) and remote one (which is session-bound and contains only descriptors received from a remote node). marshal() method should only work with the local registry in read-write mode (as it can add descriptors for classes never marshalled before). unmarshal() method should work with the merge of local and remote registries (remote registry taking precedence), but only in read-only mode (it should not modify the registries). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16083) .NET: Thin client services don't work properly
[
https://issues.apache.org/jira/browse/IGNITE-16083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463596#comment-17463596
]
Nikolay Izhikov commented on IGNITE-16083:
--
https://ci2.ignite.apache.org/viewLog.html?buildId=6241906=queuedBuildOverviewTab
- tests run
> .NET: Thin client services don't work properly
> --
>
> Key: IGNITE-16083
> URL: https://issues.apache.org/jira/browse/IGNITE-16083
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Even after IGNITE-14742 Thin client serde process on .Net side doesn't work
> properly for array.
> See attached tests added during IGNITE-14299
> {code}
> ///
> /// Tests Java service invocation.
> ///
> [Test]
> [Ignore("https://issues.apache.org/jira/browse/IGNITE-16083;)]
> public void TestCallJavaServiceThinClient()
> {
> var svc =
> _thinClient.GetServices().GetServiceProxy(_javaSvcName);
> var binSvc = _thinClient.GetServices()
> .WithKeepBinary().WithServerKeepBinary()
> .GetServiceProxy(_javaSvcName);
> DoTestService(svc);
> DoTestBinary(svc, binSvc);
> DoTestJavaExceptions(svc, true);
> }
> {code}
> {code}
> ///
> /// Tests .Net service invocation with thin client.
> ///
> [Test]
> [Ignore("https://issues.apache.org/jira/browse/IGNITE-16083;)]
> public void TestPlatformServiceThinClient()
> {
>
> DoTestService(_thinClient.GetServices().GetServiceProxy(PlatformSvcName));
> }
> ///
> /// Tests Java service invocation with thin client.
> /// Types should be resolved implicitly.
> ///
> [Test]
> [Ignore("https://issues.apache.org/jira/browse/IGNITE-16083;)]
> public void TestJavaServiceThinClient()
> {
>
> DoTestService(_thinClient.GetServices().GetServiceProxy(_javaSvcName));
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16182) Move ZookeeperIpFinder to the ignite-extensions
[
https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463424#comment-17463424
]
Ignite TC Bot commented on IGNITE-16182:
{panel:title=Branch: [pull/9682/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6241691]]
{color:#d04437}SPI{color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6241763]]
{color:#d04437}Java Client{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=6241729]]
* IgniteClientTestSuite:
ClientTcpUnreachableMultiNodeSelfTest.testProjectionRun - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteClientTestSuite:
ClientSideCacheCreationDestructionWileTopologyChangeTest.testCreateOnSrvDestroyOnThickClient
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Security{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6241758]]
* SecurityTestSuite:
CacheOperationPermissionCreateDestroyCheckTest.testDestroyCacheWithSystemPermissions[clientMode=false]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Client Nodes{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6241707]]
* IgniteClientReconnectTestSuite:
IgniteClientReconnectFailoverTest.testReconnectStreamerApi - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9682/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=6241779buildTypeId=IgniteTests24Java8_RunAll]
> Move ZookeeperIpFinder to the ignite-extensions
> ---
>
> Key: IGNITE-16182
> URL: https://issues.apache.org/jira/browse/IGNITE-16182
> Project: Ignite
> Issue Type: Task
> Components: extensions
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: ise
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Move TcpDiscoveryZookeeperIpFinder to the ignite-extensions
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16180) Java: GetServiceDescriptors to Thin Client Services
[ https://issues.apache.org/jira/browse/IGNITE-16180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-16180: - Labels: ise (was: ) > Java: GetServiceDescriptors to Thin Client Services > --- > > Key: IGNITE-16180 > URL: https://issues.apache.org/jira/browse/IGNITE-16180 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: ise > Fix For: 2.13 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Add GetServiceDescriptors to java ClientService -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16180) Java: GetServiceDescriptors to Thin Client Services
[ https://issues.apache.org/jira/browse/IGNITE-16180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-16180: - Fix Version/s: 2.13 > Java: GetServiceDescriptors to Thin Client Services > --- > > Key: IGNITE-16180 > URL: https://issues.apache.org/jira/browse/IGNITE-16180 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.13 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Add GetServiceDescriptors to java ClientService -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13359) .NET: Add GetServiceDescriptors to Thin Client Services
[ https://issues.apache.org/jira/browse/IGNITE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-13359: - Fix Version/s: 2.13 > .NET: Add GetServiceDescriptors to Thin Client Services > --- > > Key: IGNITE-13359 > URL: https://issues.apache.org/jira/browse/IGNITE-13359 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET, ise > Fix For: 2.13 > > Time Spent: 50m > Remaining Estimate: 0h > > Add IServicesClient.GetServiceDescriptors - thin clients should be able to > discover available services. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13359) .NET: Add GetServiceDescriptors to Thin Client Services
[ https://issues.apache.org/jira/browse/IGNITE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-13359: - Labels: .NET ise (was: .NET) > .NET: Add GetServiceDescriptors to Thin Client Services > --- > > Key: IGNITE-13359 > URL: https://issues.apache.org/jira/browse/IGNITE-13359 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET, ise > Time Spent: 50m > Remaining Estimate: 0h > > Add IServicesClient.GetServiceDescriptors - thin clients should be able to > discover available services. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-13359) .NET: Add GetServiceDescriptors to Thin Client Services
[ https://issues.apache.org/jira/browse/IGNITE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463407#comment-17463407 ] Nikolay Izhikov commented on IGNITE-13359: -- https://ci2.ignite.apache.org/viewLog.html?buildId=6241887=IgniteTests24Java8_PlatformNetCoreLinux - rerun for flaky > .NET: Add GetServiceDescriptors to Thin Client Services > --- > > Key: IGNITE-13359 > URL: https://issues.apache.org/jira/browse/IGNITE-13359 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET > Time Spent: 50m > Remaining Estimate: 0h > > Add IServicesClient.GetServiceDescriptors - thin clients should be able to > discover available services. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-13359) .NET: Add GetServiceDescriptors to Thin Client Services
[ https://issues.apache.org/jira/browse/IGNITE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463404#comment-17463404 ] Nikolay Izhikov commented on IGNITE-13359: -- https://ci2.ignite.apache.org/viewLog.html?buildId=6241885=queuedBuildOverviewTab - tests run. > .NET: Add GetServiceDescriptors to Thin Client Services > --- > > Key: IGNITE-13359 > URL: https://issues.apache.org/jira/browse/IGNITE-13359 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET > Time Spent: 40m > Remaining Estimate: 0h > > Add IServicesClient.GetServiceDescriptors - thin clients should be able to > discover available services. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-14794) Add JMX command and metrics for automatic snapshot restore operation.
[
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14794:
--
Description:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
||Name||Type||
|start time|long|
|end time|long|
|request ID|string|
|snapshot name|string|
|total partitions|long|
|processed partitions|long|
|error message|string|
was:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
end time
request ID
snapshot name
total partitions
processed partitions
error message (if any)
{noformat}
> Add JMX command and metrics for automatic snapshot restore operation.
> --
>
> Key: IGNITE-14794
> URL: https://issues.apache.org/jira/browse/IGNITE-14794
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43, ise
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add JMX command to restore a cache group from the snapshot.
> Suggested methods
> {code:java}
> @MXBeanDescription("Restore cluster-wide snapshot.")
> public void restoreSnapshot(
> @MXBeanParameter(name = "snpName", description = "Snapshot name.")
> String name,
> @MXBeanParameter(name = "cacheGroupNames", description = "Optional
> comma-separated list of cache group names.") String cacheGroupNames);
> @MXBeanDescription("Cancel previously started snapshot restore
> operation.")
> public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
> description = "Snapshot name.") String name);
> {code}
> Since the automatic snapshot restore operation can take a long time, we must
> be able to track its progress using metrics.
> Suggested metrics:
> ||Name||Type||
> |start time|long|
> |end time|long|
> |request ID|string|
> |snapshot name|string|
> |total partitions|long|
> |processed partitions|long|
> |error message|string|
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14794) Add JMX command and metrics for automatic snapshot restore operation.
[
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14794:
--
Description:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
end time
request ID
snapshot name
total partitions
processed partitions
error message (if any)
{noformat}
was:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
partitions (processed/total)
bytes (processed/total)
end time
{noformat}
Suggested status command output.
[in progress]
{noformat}
Restore operation for snapshot "snapshot_25052021" is still in progress
(requestId=0e2d8c06-d44a-4ade-91bf-2b84b367499a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:47:47.942
Cache groups: default
Node test1: 100% completed (33/33 partitions, 1.9/1.9 MB)
Node test0: 100% completed (33/33 partitions, 1.9/1.9 MB)
{noformat}
[error]
{noformat}
Restore operation for snapshot "snapshot_25052021" failed
(requestId=b9b312f5-ba34-40e9-bb94-35daacd552c0).
Error: Operation has been canceled by the user.
Started: 2021-10-05 15:51:52.255
Finished: 2021-10-05 15:51:52.782
Cache groups: default
Node test1: 100% completed (33/33 partitions, 1.9/1.9 MB)
Node test0: 100% completed (33/33 partitions, 1.9/1.9 MB){noformat}
[finished]
{noformat}
Restore operation for snapshot "snapshot_25052021" completed successfully
(requestId=6adeea86-1ee2-4664-8d7d-3383a484a00a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:53:03.352
Finished: 2021-10-05 15:53:03.443
Cache groups: default
Node test1: 100% completed (33/33 partitions, 1.9/1.9 MB)
Node test0: 100% completed (33/33 partitions, 1.9/1.9 MB){noformat}
[missing snapshot name]
{noformat}
No information about restoring snapshot "snapshot_MISSING" is
available.{noformat}
> Add JMX command and metrics for automatic snapshot restore operation.
> --
>
> Key: IGNITE-14794
> URL: https://issues.apache.org/jira/browse/IGNITE-14794
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43, ise
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add JMX command to restore a cache group from the snapshot.
> Suggested methods
> {code:java}
> @MXBeanDescription("Restore cluster-wide snapshot.")
> public void restoreSnapshot(
> @MXBeanParameter(name = "snpName", description = "Snapshot name.")
> String name,
> @MXBeanParameter(name = "cacheGroupNames", description = "Optional
> comma-separated list of cache group names.") String cacheGroupNames);
> @MXBeanDescription("Cancel previously started snapshot restore
> operation.")
> public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
> description = "Snapshot name.") String name);
> {code}
> Since the automatic snapshot restore operation can take a long time, we must
> be able to track its progress using metrics.
> Suggested metrics:
> {noformat}
> start time
> end time
> request ID
> snapshot name
> total partitions
> processed partitions
> error message (if any)
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16124) deleteAllById has wrong signature
[
https://issues.apache.org/jira/browse/IGNITE-16124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463379#comment-17463379
]
Vladimir Pligin commented on IGNITE-16124:
--
[~mikereiche] thanks for the ticket. At the first glance it really looks like
an issue. We'll have a closer look.
> deleteAllById has wrong signature
> -
>
> Key: IGNITE-16124
> URL: https://issues.apache.org/jira/browse/IGNITE-16124
> Project: Ignite
> Issue Type: Bug
>Reporter: Michael Reiche
>Priority: Major
>
> java: name clash: deleteAllById(java.lang.Iterable) in
> org.apache.ignite.springdata20.repository.IgniteRepository and
> deleteAllById(java.lang.Iterable) in
> org.springframework.data.repository.CrudRepository have the same erasure, yet
> neither overrides the other
>
> 2.6.0-RC1
> 2.9.1
>
>
>
> org.apache.ignite
> ignite-spring-data_2.0
> ${ignite.version}
>
>
> org.apache.ignite
> ignite-core
> ${ignite.version}
>
>
> org.apache.ignite
> ignite-indexing
> ${ignite.version}
>
>
> org.apache.ignite
> ignite-spring
> ${ignite.version}
>
>
> org.springframework.data
> spring-data-commons
> ${spring.data.version}
>
>
> If ignite-spring-data is used instead of ingite-spring-data_2.0, the method
> deleteAll is flagged
> java: name clash: deleteAll(java.lang.Iterable com.example.ignite.EmployeeDTO>) in
> org.springframework.data.repository.CrudRepository and
> deleteAll(java.lang.Iterable) in
> org.apache.ignite.springdata.repository.IgniteRepository have the same
> erasure, yet neither overrides the other
> And 2.2-ext gives the following:
> org.apache.ignite
> ignite-spring-data-2.2-ext
> 1.0.0
> java: name clash: deleteAllById(java.lang.Iterable) in
> org.apache.ignite.springdata22.repository.IgniteRepository and
> deleteAllById(java.lang.Iterable) in
> org.springframework.data.repository.CrudRepository have the same erasure, yet
> neither overrides the other
> package com.example.ignite;
> import org.apache.ignite.springdata.repository.IgniteRepository;
> import org.apache.ignite.springdata.repository.config.RepositoryConfig;
> @RepositoryConfig(cacheName = "myCache")
> public interface EmployeeRepository extends
> IgniteRepository
> { EmployeeDTO getEmployeeDTOById(ID id); }
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16184) testTransferLeader is flaky
[ https://issues.apache.org/jira/browse/IGNITE-16184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16184: - Priority: Critical (was: Major) > testTransferLeader is flaky > --- > > Key: IGNITE-16184 > URL: https://issues.apache.org/jira/browse/IGNITE-16184 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Priority: Critical > Labels: ignite-3 > Attachments: testTransferLeader.log > > > ItCliServiceTest.testTransferLeader is flaky. Need to find out the root cause. > See attached log. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16184) testTransferLeader is flaky
[ https://issues.apache.org/jira/browse/IGNITE-16184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16184: - Attachment: testTransferLeader.log > testTransferLeader is flaky > --- > > Key: IGNITE-16184 > URL: https://issues.apache.org/jira/browse/IGNITE-16184 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Priority: Critical > Labels: ignite-3 > Attachments: testTransferLeader.log > > > ItCliServiceTest.testTransferLeader is flaky. Need to find out the root cause. > See attached log. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16184) testTransferLeader is flaky
Vyacheslav Koptilin created IGNITE-16184: Summary: testTransferLeader is flaky Key: IGNITE-16184 URL: https://issues.apache.org/jira/browse/IGNITE-16184 Project: Ignite Issue Type: Bug Reporter: Vyacheslav Koptilin ItCliServiceTest.testTransferLeader is flaky. Need to find out the root cause. See attached log. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15478) Add access to the IgniteMBeanManager via KernalContext
[ https://issues.apache.org/jira/browse/IGNITE-15478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov reassigned IGNITE-15478: --- Assignee: Mikhail Petrov > Add access to the IgniteMBeanManager via KernalContext > -- > > Key: IGNITE-15478 > URL: https://issues.apache.org/jira/browse/IGNITE-15478 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to add an access to the IgniteMBeanManager via KernalContext. It > helps to access the IgniteMBeanManager in the same way as for other Ignite > components, and allows Ignite components to register needed MBeans from their > own implementations. > It's also proposed to refactor MBeans registration to be performed explicitly > via IgniteMBeanManager. As an example we can eliminate > GridQueryIndexing#registerMxBeans method and registers beans directly. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16183) Multi-raft support
[ https://issues.apache.org/jira/browse/IGNITE-16183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-16183: --- Summary: Multi-raft support (was: Multuraft support) > Multi-raft support > -- > > Key: IGNITE-16183 > URL: https://issues.apache.org/jira/browse/IGNITE-16183 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > > Currently, the dedicated raft group is created for every partition. This > approach leads to creating a huge number of raft groups which is expensive. > It seems that that multiraft can be a good improvement here. The details can > be found here https://tikv.org/deep-dive/scalability/multi-raft/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16183) Multuraft support
Vyacheslav Koptilin created IGNITE-16183: Summary: Multuraft support Key: IGNITE-16183 URL: https://issues.apache.org/jira/browse/IGNITE-16183 Project: Ignite Issue Type: Improvement Reporter: Vyacheslav Koptilin Currently, the dedicated raft group is created for every partition. This approach leads to creating a huge number of raft groups which is expensive. It seems that that multiraft can be a good improvement here. The details can be found here https://tikv.org/deep-dive/scalability/multi-raft/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-13464) Ignite-rest-http modules includes vulnerable dependencies
[
https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463350#comment-17463350
]
Ignite TC Bot commented on IGNITE-13464:
{panel:title=Branch: [pull/9676/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9676/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=6241548buildTypeId=IgniteTests24Java8_RunAll]
> Ignite-rest-http modules includes vulnerable dependencies
> -
>
> Key: IGNITE-13464
> URL: https://issues.apache.org/jira/browse/IGNITE-13464
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.9, 2.8.1
>Reporter: Stephen Darlington
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ignite-rest-http module includes a [vulnerable
> version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j
> library. It also appears to include slf4j. Why does the REST API include its
> own logging libraries?
> This was spotted in 2.8.1 but still appears to be an issue in master and 2.9.
> More here:
> http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16138) Calcite. AssertionError: Input not sorted for some ORDER BY containing requests.
[
https://issues.apache.org/jira/browse/IGNITE-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463341#comment-17463341
]
Evgeny Stanilovsky commented on IGNITE-16138:
-
[~alex_pl] [~tledkov-gridgain] [~korlov] guys make a review plz
> Calcite. AssertionError: Input not sorted for some ORDER BY containing
> requests.
>
>
> Key: IGNITE-16138
> URL: https://issues.apache.org/jira/browse/IGNITE-16138
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> statement ok
> CREATE TABLE tab0(pk INTEGER PRIMARY KEY, col0 INTEGER, col1 FLOAT, col2
> VARCHAR, col3 INTEGER, col4 FLOAT, col5 VARCHAR)
> statement ok
> INSERT INTO tab0 VALUES(0,544,473.59,'lupfg',846,31.38,'crmer')
> statement ok
> INSERT INTO tab0 VALUES(1,551,716.92,'sxtsd',562,145.36,'xxacr')
> statement ok
> INSERT INTO tab0 VALUES(2,481,975.35,'uxrjj',652,750.52,'rdgic')
> statement ok
> INSERT INTO tab0 VALUES(3,345,371.4,'nxyqi',51,199.34,'lekdd')
> statement ok
> INSERT INTO tab0 VALUES(4,908,772.92,'owifa',256,154.36,'xophl')
> statement ok
> INSERT INTO tab0 VALUES(5,309,912.32,'iganw',957,707.84,'tewpl')
> statement ok
> INSERT INTO tab0 VALUES(6,691,521.59,'fstmf',656,504.37,'ptkph')
> statement ok
> INSERT INTO tab0 VALUES(7,823,447.70,'rrwze',294,877.49,'fvoic')
> statement ok
> INSERT INTO tab0 VALUES(8,725,784.91,'iaoqu',878,963.31,'razqy')
> statement ok
> INSERT INTO tab0 VALUES(9,297,993.36,'eoujh',105,829.18,'kvyce')
> statement ok
> CREATE TABLE tab1(pk INTEGER PRIMARY KEY, col0 INTEGER, col1 FLOAT, col2
> VARCHAR, col3 INTEGER, col4 FLOAT, col5 VARCHAR)
> statement ok
> CREATE INDEX idx_tab1_0 on tab1 (col0)
> statement ok
> CREATE INDEX idx_tab1_1 on tab1 (col1)
> statement ok
> CREATE INDEX idx_tab1_3 on tab1 (col3)
> statement ok
> CREATE INDEX idx_tab1_4 on tab1 (col4)
> statement ok
> INSERT INTO tab1 SELECT * FROM tab0
> statement ok
> CREATE TABLE tab2(pk INTEGER PRIMARY KEY, col0 INTEGER, col1 FLOAT, col2
> VARCHAR, col3 INTEGER, col4 FLOAT, col5 VARCHAR)
> statement ok
> CREATE INDEX idx_tab2_0 ON tab2 (col0 DESC,col4 DESC)
> statement ok
> CREATE INDEX idx_tab2_1 ON tab2 (col3,col1)
> statement ok
> CREATE INDEX idx_tab2_3 ON tab2 (col0,col1 DESC)
> statement ok
> CREATE INDEX idx_tab2_5 ON tab2 (col4 DESC)
> statement ok
> INSERT INTO tab2 SELECT * FROM tab0
> statement ok
> CREATE TABLE tab3(pk INTEGER PRIMARY KEY, col0 INTEGER, col1 FLOAT, col2
> VARCHAR, col3 INTEGER, col4 FLOAT, col5 VARCHAR)
> statement ok
> CREATE INDEX idx_tab3_0 ON tab3 (col4)
> statement ok
> CREATE INDEX idx_tab3_2 ON tab3 (col0 DESC,col3)
> statement ok
> CREATE INDEX idx_tab3_3 ON tab3 (col1 DESC)
> statement ok
> INSERT INTO tab3 SELECT * FROM tab0
> statement ok
> CREATE TABLE tab4(pk INTEGER PRIMARY KEY, col0 INTEGER, col1 FLOAT, col2
> VARCHAR, col3 INTEGER, col4 FLOAT, col5 VARCHAR)
> statement ok
> CREATE INDEX idx_tab4_1 ON tab4 (col3)
> statement ok
> CREATE INDEX idx_tab4_2 ON tab4 (col4)
> statement ok
> CREATE INDEX idx_tab4_3 ON tab4 (col1,col0 DESC)
> SELECT pk FROM tab3 WHERE (col3 < 204) AND col3 IN (SELECT col0 FROM tab3
> WHERE col3 >= 218) AND col4 IN (SELECT col1 FROM tab3 WHERE (col3 IN
> (427) OR col3 <= 404 OR ((col0 IS NULL AND (col4 > 802.10 AND col0 =
> 651))) OR col3 BETWEEN 851 AND 573)) ORDER BY 1 DESC
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16107) Calcite engine. Project and filters are not merged into scan node correctly
[
https://issues.apache.org/jira/browse/IGNITE-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-16107:
---
Labels: calcite3-required (was: calcite2-required calcite3-required)
> Calcite engine. Project and filters are not merged into scan node correctly
> ---
>
> Key: IGNITE-16107
> URL: https://issues.apache.org/jira/browse/IGNITE-16107
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite3-required
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> {{ProjectScanMergeRule}} and {{FilterScanMergeRule}} have several issues:
> # {{FilterScanMergeRule}} is not applied on the HEP phase, and due to this
> in most cases {{ProjectScanMergeRule}} can't be correctly applied in the HEP
> phase too. There are several useless transformations that can be avoided if
> {{FilterScanMergeRule}} will be applied (for example, in trivial scan with
> projects and filter, new projects created below filter in
> {{{}trimUnusedFields{}}}, then these projects moved above filter in
> {{FilterProjectTranposeRule}}, then top-level projects and trim-projects
> merged in {{{}ProjectMergeRule{}}}, then project created below filter again
> in {{ProjectFilterTranposeRule}}, then it merged into scan by
> {{ProjectScanMergeRule}} and prevents to merge top-level project later).
> # {{ProjectScanMergeRule.INDEX_SCAN_SKIP_CORRELATED}} is useless since there
> are no index scans on the HEP phase.
> # Traits are created for logical nodes (in some cases, not correct traits),
> but it's redundant (only physical nodes require traits).
> # {{ProjectScanMergeRule}} can't merge projects if another project is
> already merged into a scan.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-16162) StripedDisruptor should clean up its queues on shutdown
[ https://issues.apache.org/jira/browse/IGNITE-16162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-16162: Assignee: Vyacheslav Koptilin > StripedDisruptor should clean up its queues on shutdown > --- > > Key: IGNITE-16162 > URL: https://issues.apache.org/jira/browse/IGNITE-16162 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Minor > Labels: ignite-3 > > StripedDisruptor maintains a collection of ring buffers > (StripedDisruptor.queues) that are not cleared on shutdown. It does not seem > to me that clearing is absolutely required step, but it allows to partially > mitigate the issue IGNITE-16161 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-15694) Document building ODBC driver using cmake, remove Visual Studio building sections
[ https://issues.apache.org/jira/browse/IGNITE-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463303#comment-17463303 ] Ivan Daschinsky edited comment on IGNITE-15694 at 12/21/21, 3:06 PM: - [~nsafonov] [~isapego] Hi, could you please review this docs. I've checked all steps manually on Windows 10, but it can still consist some typos was (Author: ivandasch): [~nsafonov][~isapego] Hi, could you please review this docs. I've checked all steps manually on Windows 10, but it can still consist some typos > Document building ODBC driver using cmake, remove Visual Studio building > sections > - > > Key: IGNITE-15694 > URL: https://issues.apache.org/jira/browse/IGNITE-15694 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15694) Document building ODBC driver using cmake, remove Visual Studio building sections
[ https://issues.apache.org/jira/browse/IGNITE-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463303#comment-17463303 ] Ivan Daschinsky commented on IGNITE-15694: -- [~nsafonov][~isapego] Hi, could you please review this docs. I've checked all steps manually on Windows 10, but it can still consist some typos > Document building ODBC driver using cmake, remove Visual Studio building > sections > - > > Key: IGNITE-15694 > URL: https://issues.apache.org/jira/browse/IGNITE-15694 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16121) Thin 3.0: Implement KeyValueView with POJO mapping
[ https://issues.apache.org/jira/browse/IGNITE-16121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463273#comment-17463273 ] Igor Sapego commented on IGNITE-16121: -- [~ptupitsyn] looks good to me. > Thin 3.0: Implement KeyValueView with POJO mapping > -- > > Key: IGNITE-16121 > URL: https://issues.apache.org/jira/browse/IGNITE-16121 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement KeyValueView for Java thin client. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16107) Calcite engine. Project and filters are not merged into scan node correctly
[
https://issues.apache.org/jira/browse/IGNITE-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463266#comment-17463266
]
Konstantin Orlov commented on IGNITE-16107:
---
[~alex_pl] , LGTM!
> Calcite engine. Project and filters are not merged into scan node correctly
> ---
>
> Key: IGNITE-16107
> URL: https://issues.apache.org/jira/browse/IGNITE-16107
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{ProjectScanMergeRule}} and {{FilterScanMergeRule}} have several issues:
> # {{FilterScanMergeRule}} is not applied on the HEP phase, and due to this
> in most cases {{ProjectScanMergeRule}} can't be correctly applied in the HEP
> phase too. There are several useless transformations that can be avoided if
> {{FilterScanMergeRule}} will be applied (for example, in trivial scan with
> projects and filter, new projects created below filter in
> {{{}trimUnusedFields{}}}, then these projects moved above filter in
> {{FilterProjectTranposeRule}}, then top-level projects and trim-projects
> merged in {{{}ProjectMergeRule{}}}, then project created below filter again
> in {{ProjectFilterTranposeRule}}, then it merged into scan by
> {{ProjectScanMergeRule}} and prevents to merge top-level project later).
> # {{ProjectScanMergeRule.INDEX_SCAN_SKIP_CORRELATED}} is useless since there
> are no index scans on the HEP phase.
> # Traits are created for logical nodes (in some cases, not correct traits),
> but it's redundant (only physical nodes require traits).
> # {{ProjectScanMergeRule}} can't merge projects if another project is
> already merged into a scan.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16123) Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure
[ https://issues.apache.org/jira/browse/IGNITE-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16123: - Labels: IEP-71 (was: ) > Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure > --- > > Key: IGNITE-16123 > URL: https://issues.apache.org/jira/browse/IGNITE-16123 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > LazyOnDmlTest failed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16123) Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure
[ https://issues.apache.org/jira/browse/IGNITE-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16123: - Ignite Flags: (was: Docs Required,Release Notes Required) > Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure > --- > > Key: IGNITE-16123 > URL: https://issues.apache.org/jira/browse/IGNITE-16123 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > LazyOnDmlTest failed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-14945) IndexQuery should use inline IO for internal filtering.
[ https://issues.apache.org/jira/browse/IGNITE-14945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-14945: - Fix Version/s: 2.13 > IndexQuery should use inline IO for internal filtering. > --- > > Key: IGNITE-14945 > URL: https://issues.apache.org/jira/browse/IGNITE-14945 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > For comparison of index keys it's required: > # to init cache data row > # access fields with BinaryObject API > So, it's possible to use inline IO for filtering. It can help: > # speed up comparison (Inline IO access is faster than BinaryObject API). > # to avoid init cache data rows for filtered items (in case there are more > filtered items). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16123) Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure
[ https://issues.apache.org/jira/browse/IGNITE-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-16123: - Fix Version/s: 2.13 > Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure > --- > > Key: IGNITE-16123 > URL: https://issues.apache.org/jira/browse/IGNITE-16123 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > LazyOnDmlTest failed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16123) Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure
[ https://issues.apache.org/jira/browse/IGNITE-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463260#comment-17463260 ] Maksim Timonin commented on IGNITE-16123: - Thanks [~NIzhikov] for the notice. This is an additional commit for [1]. There was a misprint with loosing single symbol in last moment. Fixed ASAP due-to broken master. [1]https://issues.apache.org/jira/browse/IGNITE-14945 > Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure > --- > > Key: IGNITE-16123 > URL: https://issues.apache.org/jira/browse/IGNITE-16123 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > LazyOnDmlTest failed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16182) Move ZookeeperIpFinder to the ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16182: --- Description: Move TcpDiscoveryZookeeperIpFinder to the ignite-extensions (was: Move ZookeeperIpFinder to the ignite-extensions) > Move ZookeeperIpFinder to the ignite-extensions > --- > > Key: IGNITE-16182 > URL: https://issues.apache.org/jira/browse/IGNITE-16182 > Project: Ignite > Issue Type: Task > Components: extensions >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Labels: ise > > Move TcpDiscoveryZookeeperIpFinder to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16182) Move ZookeeperIpFinder to the ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16182: --- Summary: Move ZookeeperIpFinder to the ignite-extensions (was: Move ZookeeperIpFinderTest to the ignite-extensions) > Move ZookeeperIpFinder to the ignite-extensions > --- > > Key: IGNITE-16182 > URL: https://issues.apache.org/jira/browse/IGNITE-16182 > Project: Ignite > Issue Type: Task > Components: extensions >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Labels: ise > > Move ZookeeperIpFinderTest to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16182) Move ZookeeperIpFinder to the ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16182: --- Description: Move ZookeeperIpFinder to the ignite-extensions (was: Move ZookeeperIpFinderTest to the ignite-extensions) > Move ZookeeperIpFinder to the ignite-extensions > --- > > Key: IGNITE-16182 > URL: https://issues.apache.org/jira/browse/IGNITE-16182 > Project: Ignite > Issue Type: Task > Components: extensions >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Labels: ise > > Move ZookeeperIpFinder to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16180) Java: GetServiceDescriptors to Thin Client Services
[
https://issues.apache.org/jira/browse/IGNITE-16180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463253#comment-17463253
]
Ignite TC Bot commented on IGNITE-16180:
{panel:title=Branch: [pull/9677/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9677/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Thin Client: Java{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=6241638]]
* {color:#013220}ClientTestSuite:
ServicesBinaryArraysTests.testServiceDescriptors - PASSED{color}
* {color:#013220}ClientTestSuite: ServicesTest.testServiceDescriptors -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6241649buildTypeId=IgniteTests24Java8_RunAll]
> Java: GetServiceDescriptors to Thin Client Services
> ---
>
> Key: IGNITE-16180
> URL: https://issues.apache.org/jira/browse/IGNITE-16180
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add GetServiceDescriptors to java ClientService
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16182) Move ZookeeperIpFinderTest to the ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16182: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Move ZookeeperIpFinderTest to the ignite-extensions > --- > > Key: IGNITE-16182 > URL: https://issues.apache.org/jira/browse/IGNITE-16182 > Project: Ignite > Issue Type: Task > Components: extensions >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Labels: ise > > Move ZookeeperIpFinderTest to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16182) Move ZookeeperIpFinderTest to the ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16182: --- Labels: ise (was: ) > Move ZookeeperIpFinderTest to the ignite-extensions > --- > > Key: IGNITE-16182 > URL: https://issues.apache.org/jira/browse/IGNITE-16182 > Project: Ignite > Issue Type: Task > Components: extensions >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > Labels: ise > > Move ZookeeperIpFinderTest to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16182) Move ZookeeperIpFinderTest to the ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-16182: --- Component/s: extensions > Move ZookeeperIpFinderTest to the ignite-extensions > --- > > Key: IGNITE-16182 > URL: https://issues.apache.org/jira/browse/IGNITE-16182 > Project: Ignite > Issue Type: Task > Components: extensions >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > > Move ZookeeperIpFinderTest to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16182) Move ZookeeperIpFinderTest to the ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-16182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov reassigned IGNITE-16182: -- Assignee: Sergei Ryzhov > Move ZookeeperIpFinderTest to the ignite-extensions > --- > > Key: IGNITE-16182 > URL: https://issues.apache.org/jira/browse/IGNITE-16182 > Project: Ignite > Issue Type: Task >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Major > > Move ZookeeperIpFinderTest to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16182) Move ZookeeperIpFinderTest to the ignite-extensions
Sergei Ryzhov created IGNITE-16182: -- Summary: Move ZookeeperIpFinderTest to the ignite-extensions Key: IGNITE-16182 URL: https://issues.apache.org/jira/browse/IGNITE-16182 Project: Ignite Issue Type: Task Reporter: Sergei Ryzhov Move ZookeeperIpFinderTest to the ignite-extensions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16164) Implement (un)marshalling of arbitrary objects
[ https://issues.apache.org/jira/browse/IGNITE-16164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16164: - Labels: ignite-3 (was: ) > Implement (un)marshalling of arbitrary objects > -- > > Key: IGNITE-16164 > URL: https://issues.apache.org/jira/browse/IGNITE-16164 > Project: Ignite > Issue Type: Sub-task >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16165) Implement (un)marshalling of Serializable
[ https://issues.apache.org/jira/browse/IGNITE-16165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16165: - Labels: ignite-3 (was: ) > Implement (un)marshalling of Serializable > - > > Key: IGNITE-16165 > URL: https://issues.apache.org/jira/browse/IGNITE-16165 > Project: Ignite > Issue Type: Sub-task >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16140) Cannot find data in index when querying a pojo key in local mode.
[ https://issues.apache.org/jira/browse/IGNITE-16140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16140: - Ignite Flags: (was: Docs Required,Release Notes Required) > Cannot find data in index when querying a pojo key in local mode. > - > > Key: IGNITE-16140 > URL: https://issues.apache.org/jira/browse/IGNITE-16140 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.11 >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > SqlFieldsQuery with POJO parameter leads to index scan won't find data if the > local flag is set. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16121) Thin 3.0: Implement KeyValueView with POJO mapping
[ https://issues.apache.org/jira/browse/IGNITE-16121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16121: - Labels: ignite-3 (was: ) > Thin 3.0: Implement KeyValueView with POJO mapping > -- > > Key: IGNITE-16121 > URL: https://issues.apache.org/jira/browse/IGNITE-16121 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > > Implement KeyValueView for Java thin client. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13464) Ignite-rest-http modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-13464: --- Description: The ignite-rest-http module includes a [vulnerable version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j library. It also appears to include slf4j. Why does the REST API include its own logging libraries? This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. More here: http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html was: The ignite-rest-http, zookeeper module includes a [vulnerable version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j library. It also appears to include slf4j. Why does the REST API include its own logging libraries? This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. More here: http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html > Ignite-rest-http modules includes vulnerable dependencies > - > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13464) Ignite-rest-http modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ryzhov updated IGNITE-13464: --- Summary: Ignite-rest-http modules includes vulnerable dependencies (was: Ignite-rest-http, zookeeper modules includes vulnerable dependencies) > Ignite-rest-http modules includes vulnerable dependencies > - > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http, zookeeper module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16115) Implement getNullable and getOrDefault operations.
[
https://issues.apache.org/jira/browse/IGNITE-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463174#comment-17463174
]
Andrey Mashenkov commented on IGNITE-16115:
---
[~agura] , I've fixed all the comments.
Seems, we've foget {{getAndPut()/getAndRemove()/getAndReplace()/getAll()}}
methods.
Also, AFAIK, {{getAll()}} will return Map after IGNITE-16004, and Map has
{{getOrDefault()}} and {{contains()}} methods.
Should they have adjacents with similar nullable semantic as getNullable? WDYT?
> Implement getNullable and getOrDefault operations.
> --
>
> Key: IGNITE-16115
> URL: https://issues.apache.org/jira/browse/IGNITE-16115
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It is allowed to map an object to a single nullable column, which makes
> 'null' values legal in the KeyValue view.
> Once the 'null' value is possible there is no way to distinguish, if there is
> no row in a table for the given key, or the row exists and the mapped column
> contains the 'null' value.
> Let's introduce {{NullableValue}} class-wrapper for a value and implement
> {{{}getNullable(){}}}, and {{getOrDefault()}} + bulk methods.
> {{getNullable()}} is useful for cases, when it's not possible to use a
> "default", but creates an additional wrapper.
> Also, the KeyValueView.get(key) method behavior should be changed:
> * return {{null}} if the table has no row for the key.
> * return a non-null value for the key.
> * fail with a suggestion to use a getNullable, if a {{null}} value returned
> for the key to avoid ambiguity.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-13464) Ignite-rest-http, zookeeper modules includes vulnerable dependencies
[
https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463152#comment-17463152
]
Ivan Daschinsky edited comment on IGNITE-13464 at 12/21/21, 11:15 AM:
--
Also, if we want to remove all log4j 1.2.17, we should also remove completely
{{ignite-log4j}} module and log4j 1.x support
was (Author: ivandasch):
Also, if we want to remove all log4j 1.2.17, we should also remove completely
Log4J logger.
> Ignite-rest-http, zookeeper modules includes vulnerable dependencies
>
>
> Key: IGNITE-13464
> URL: https://issues.apache.org/jira/browse/IGNITE-13464
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.9, 2.8.1
>Reporter: Stephen Darlington
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ignite-rest-http, zookeeper module includes a [vulnerable
> version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j
> library. It also appears to include slf4j. Why does the REST API include its
> own logging libraries?
> This was spotted in 2.8.1 but still appears to be an issue in master and 2.9.
> More here:
> http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-13464) Ignite-rest-http, zookeeper modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463152#comment-17463152 ] Ivan Daschinsky edited comment on IGNITE-13464 at 12/21/21, 11:14 AM: -- Also, if we want to remove all log4j 1.2.17, we should also remove completely Log4J logger. was (Author: ivandasch): Also, if we want to remove all log4j 1.2.17, we should also remove completely Log4J logger and choose something else for them > Ignite-rest-http, zookeeper modules includes vulnerable dependencies > > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http, zookeeper module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-13464) Ignite-rest-http, zookeeper modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463152#comment-17463152 ] Ivan Daschinsky commented on IGNITE-13464: -- Also, if we want to remove all log4j 1.2.17, we should also remove completely Log4J logger and choose something else for them > Ignite-rest-http, zookeeper modules includes vulnerable dependencies > > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http, zookeeper module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-13464) Ignite-rest-http, zookeeper modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463120#comment-17463120 ] Ivan Daschinsky edited comment on IGNITE-13464 at 12/21/21, 10:45 AM: -- [~RyzhovSV] [~sdarlington] Ignite zookeper depends on curator framework and use good ole log4j 1.2.17. Removing log4j here is not an option. And I don't understand why, because nothing related with log4j 2 hysteria was (Author: ivandasch): [~RyzhovSV] [~sdarlington] Ignite zookeper depends on curator framework and use good ole log4j 1.7. Removing log4j here is not an option. And I don't understand why, because nothing related with log4j 2 hysteria > Ignite-rest-http, zookeeper modules includes vulnerable dependencies > > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http, zookeeper module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16097) Some tests are flaky in ItNodeTest
[ https://issues.apache.org/jira/browse/IGNITE-16097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16097: - Ignite Flags: (was: Docs Required,Release Notes Required) > Some tests are flaky in ItNodeTest > -- > > Key: IGNITE-16097 > URL: https://issues.apache.org/jira/browse/IGNITE-16097 > Project: Ignite > Issue Type: Task >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 1h > Remaining Estimate: 0h > > Some tests are flaky in org.apache.ignite.raft.jraft.core.ItNodeTest: > # testLeaderTransferWithReplicatorStateListener > # testTripleNodesWithReplicatorStateListener > # testResetLearners > # testLeaderTransfer > # testLeaderTransferBeforeLogIsCompleted > # testLeaderTransferResumeOnFailure > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-13464) Ignite-rest-http, zookeeper modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463120#comment-17463120 ] Ivan Daschinsky commented on IGNITE-13464: -- [~RyzhovSV] [~sdarlington] Ignite zookeper depends on curator framework and use good ole log4j 1.7. Removing log4j here is not an option. And I don't understand why, because nothing related with log4j 2 hysteria > Ignite-rest-http, zookeeper modules includes vulnerable dependencies > > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http, zookeeper module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13464) Ignite-rest-http, zookeeper modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-13464: - Summary: Ignite-rest-http, zookeeper modules includes vulnerable dependencies (was: Ignite-rest-http includes vulnerable dependencies) > Ignite-rest-http, zookeeper modules includes vulnerable dependencies > > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13464) Ignite-rest-http, zookeeper modules includes vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-13464: - Description: The ignite-rest-http, zookeeper module includes a [vulnerable version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j library. It also appears to include slf4j. Why does the REST API include its own logging libraries? This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. More here: http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html was: The ignite-rest-http module includes a [vulnerable version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j library. It also appears to include slf4j. Why does the REST API include its own logging libraries? This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. More here: http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html > Ignite-rest-http, zookeeper modules includes vulnerable dependencies > > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.9, 2.8.1 >Reporter: Stephen Darlington >Assignee: Sergei Ryzhov >Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http, zookeeper module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16181) Calcite engine. Handle arithmetic overflows
Aleksey Plekhanov created IGNITE-16181:
--
Summary: Calcite engine. Handle arithmetic overflows
Key: IGNITE-16181
URL: https://issues.apache.org/jira/browse/IGNITE-16181
Project: Ignite
Issue Type: Improvement
Reporter: Aleksey Plekhanov
Currently, we silently ignore arithmetic overflows and return the wrong result,
for example:
{noformat}
SELECT 2147483647 + 2147483647{noformat}
Returns -2. But SQL standard says that exception should be thrown:
{noformat}
5) If the most specific type of the result of an arithmetic operation is exact
numeric, then Case:
a) If the operator is not division and the mathematical result of the operation
is not exactly representable with the precision and scale of the result data
type, then an exception condition is raised: data exception — numeric value out
of range.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-16004) Preserve key order in InternalTableImpl#collectMultiRowsResponses
[ https://issues.apache.org/jira/browse/IGNITE-16004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-16004: - Assignee: (was: Andrey Mashenkov) > Preserve key order in InternalTableImpl#collectMultiRowsResponses > - > > Key: IGNITE-16004 > URL: https://issues.apache.org/jira/browse/IGNITE-16004 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > After the IGNITE-15085 multi key methods return a List of values correponding > to the passed keys order, where each position correponds to the result > operation for a key with the same position in the arguments. > For example, getAll(1, 2, 3) will return A, null, C if a value for 2 doesn't > exists. > collectMultiRowsResponses can break this ordering for multi partition > requests. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16180) Java: GetServiceDescriptors to Thin Client Services
[ https://issues.apache.org/jira/browse/IGNITE-16180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-16180: Assignee: Nikolay Izhikov > Java: GetServiceDescriptors to Thin Client Services > --- > > Key: IGNITE-16180 > URL: https://issues.apache.org/jira/browse/IGNITE-16180 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > > Add GetServiceDescriptors to java ClientService -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16180) Java: GetServiceDescriptors to Thin Client Services
Nikolay Izhikov created IGNITE-16180: Summary: Java: GetServiceDescriptors to Thin Client Services Key: IGNITE-16180 URL: https://issues.apache.org/jira/browse/IGNITE-16180 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov Add GetServiceDescriptors to java ClientService -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16115) Implement getNullable and getOrDefault operations.
[
https://issues.apache.org/jira/browse/IGNITE-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-16115:
--
Description:
It is allowed to map an object to a single nullable column, which makes 'null'
values legal in the KeyValue view.
Once the 'null' value is possible there is no way to distinguish, if there is
no row in a table for the given key, or the row exists and the mapped column
contains the 'null' value.
Let's introduce {{NullableValue}} class-wrapper for a value and implement
{{{}getNullable(){}}}, and {{getOrDefault()}} + bulk methods.
{{getNullable()}} is useful for cases, when it's not possible to use a
"default", but creates an additional wrapper.
Also, the KeyValueView.get(key) method behavior should be changed:
* return {{null}} if the table has no row for the key.
* return a non-null value for the key.
* fail with a suggestion to use a getNullable, if a {{null}} value returned
for the key to avoid ambiguity.
was:
It is allowed to map an object to a single nullable column, which makes 'null'
values legal in the KeyValue view.
Once the 'null' value is possible there is no way to distinguish, if there is
no row in a table for the given key, or the row exists and the mapped column
contains the 'null' value.
Let's introduce NullableValue class-wrapper for a value and implement
getNullable, and getOrDefault methods for that purpose.
The first one is useful for cases, when it's not possible to use a "default",
but creates an additional wrapper.
Also, the KeyValueView.get(key) method behavior should be changed:
* return {{null}} if the table has no row for the key.
* return a non-null value for the key.
* fail with a suggestion to use a getNullable, if a {{null}} value returned for
the key to avoid ambiguity.
> Implement getNullable and getOrDefault operations.
> --
>
> Key: IGNITE-16115
> URL: https://issues.apache.org/jira/browse/IGNITE-16115
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It is allowed to map an object to a single nullable column, which makes
> 'null' values legal in the KeyValue view.
> Once the 'null' value is possible there is no way to distinguish, if there is
> no row in a table for the given key, or the row exists and the mapped column
> contains the 'null' value.
> Let's introduce {{NullableValue}} class-wrapper for a value and implement
> {{{}getNullable(){}}}, and {{getOrDefault()}} + bulk methods.
> {{getNullable()}} is useful for cases, when it's not possible to use a
> "default", but creates an additional wrapper.
> Also, the KeyValueView.get(key) method behavior should be changed:
> * return {{null}} if the table has no row for the key.
> * return a non-null value for the key.
> * fail with a suggestion to use a getNullable, if a {{null}} value returned
> for the key to avoid ambiguity.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-13464) Ignite-rest-http includes vulnerable dependencies
[
https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463072#comment-17463072
]
Ignite TC Bot commented on IGNITE-13464:
{panel:title=Branch: [pull/9676/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9676/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=6240843buildTypeId=IgniteTests24Java8_RunAll]
> Ignite-rest-http includes vulnerable dependencies
> -
>
> Key: IGNITE-13464
> URL: https://issues.apache.org/jira/browse/IGNITE-13464
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.9, 2.8.1
>Reporter: Stephen Darlington
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ignite-rest-http module includes a [vulnerable
> version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j
> library. It also appears to include slf4j. Why does the REST API include its
> own logging libraries?
> This was spotted in 2.8.1 but still appears to be an issue in master and 2.9.
> More here:
> http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16128) Implement bulk table operations for non-binary views
[ https://issues.apache.org/jira/browse/IGNITE-16128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463070#comment-17463070 ] Andrey Mashenkov commented on IGNITE-16128: --- I'll add them within 16115 as this thicket is already closed. > Implement bulk table operations for non-binary views > > > Key: IGNITE-16128 > URL: https://issues.apache.org/jira/browse/IGNITE-16128 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 40m > Remaining Estimate: 0h > > Let's implement getAll, putAll and other operations on KeyValueView and > RecordView. -- This message was sent by Atlassian Jira (v8.20.1#820001)
