[jira] [Commented] (IGNITE-15911) Move IGNITE_THROTTLE_INLINE_SIZE_CALCULATION to IgniteSystemProperties
[
https://issues.apache.org/jira/browse/IGNITE-15911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444350#comment-17444350
]
Ignite TC Bot commented on IGNITE-15911:
{panel:title=Branch: [pull/9562/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9562/head] Base: [master] : New Tests
(30)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 2{color} [[tests
30|https://ci.ignite.apache.org/viewLog.html?buildId=6269697]]
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=false, walMode=LOG_ONLY,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=true, walMode=FSYNC,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=true,
walMode=FSYNC,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=true,
walMode=FSYNC,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadAllKeys[specificConsistentId=false, walMode=LOG_ONLY,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReadBeforeGracefulShutdown[specificConsistentId=false,
walMode=LOG_ONLY,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=false,
walMode=LOG_ONLY,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=false,
walMode=LOG_ONLY,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testReReadWhenStateWasNotStored[specificConsistentId=false,
walMode=FSYNC,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testMultiNodeConsumption[specificConsistentId=false, walMode=FSYNC,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite2:
CdcSelfTest.testCdcSingleton[specificConsistentId=false, walMode=FSYNC,
metricExporter=org.apache.ignite.cdc.CdcSelfTest$$Lambda$17/1457157255@10f7c76]
- PASSED{color}
... and 19 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6269719&buildTypeId=IgniteTests24Java8_RunAll]
> Move IGNITE_THROTTLE_INLINE_SIZE_CALCULATION to IgniteSystemProperties
> --
>
> Key: IGNITE-15911
> URL: https://issues.apache.org/jira/browse/IGNITE-15911
> Project: Ignite
> Issue Type: Task
>Reporter: Maksim Timonin
>Assignee: Maksim Timonin
>Priority: Major
>
> All IgniteSystem properties should be specified in single place -
> IgniteSystemProperties, to be correctly write down when running help with
> 'ignite.sh'
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15794) Request attributes for a java service.
[
https://issues.apache.org/jira/browse/IGNITE-15794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444352#comment-17444352
]
Ivan Daschinsky commented on IGNITE-15794:
--
[~xtern] Looks good to me. Lets' wait for the bot's visa.
> Request attributes for a java service.
> ---
>
> Key: IGNITE-15794
> URL: https://issues.apache.org/jira/browse/IGNITE-15794
> Project: Ignite
> Issue Type: Sub-task
> Components: managed services
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-79, ise
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Implement support for passing implicit "request" attributes from the proxy to
> the Java service.
> *Implementation notes*.
> # If no caller attributes are passed - there should be no performance
> overhead when executing service methods.
> # Attributes allow only {{string}} and {{byte[]}} values and does not permit
> nulls in key/values.
> # Currently, the context should be immutable, but in the future, it should
> be possible to change it through the interceptor.
> # {{ServiceResource}} annotation allows to inject service/proxy, we must
> provide the ability to transparently pass the context to the injected service.
> *Public API changes:*
> New methods in {{IgniteServices}} to pass caller context to service proxy.
> {code:java}
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx)
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx, long timeout)
> {code}
> New method in {{ServiceContext}} for getting caller context inside the
> service method.
> {code:java}
> /**
> * Gets context of the current service call.
> *
> * @return Context of the current service call, possibly {@code null}.
> * @see ServiceCallContext
> */
> @Nullable public ServiceCallContext currentCallContext();
> {code}
> New interface {{ServiceCallContext}}
> {code:java}
> public interface ServiceCallContext {
> public String attribute(String name);
> public byte[] binaryAttribute(String name);
> }
> {code}
> And the builder {{ServiceCallContextBuilder}} for creating
> {{ServiceCallContext}}.
> New property in {{ServiceResource annotation}}.
> {code:java}
> /**
> * Flag indicating that the service call context should be passed to the
> injected service.
> *
> * @return {@code True} if the service call context should be passed to the
> injected service.
> */
> public boolean forwardCallerContext() default false;
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15845) .NET: CreateCache fails - Invalid array specification
[
https://issues.apache.org/jira/browse/IGNITE-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444355#comment-17444355
]
Pavel Tupitsyn commented on IGNITE-15845:
-
Merged to master: d110e5f5b7eeb0e7591a21d69a31cee79c42a8df
> .NET: CreateCache fails - Invalid array specification
> -
>
> Key: IGNITE-15845
> URL: https://issues.apache.org/jira/browse/IGNITE-15845
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ignition.Start fails with an exception:
> {code}
> Failure in Java callback Apache.Ignite.Core.Common.IgniteException: Invalid
> array specification:
> MassTransit.Initializers.PropertyConverters.MessageDataPropertyConverter+\,MassTransit-MessageData>-Convert>d__4`1
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.ParseArrayDefinition()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser..ctor(String typeName,
> Int32& pos)
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse(String typeName)
>at Apache.Ignite.Core.Binary.BinaryBasicNameMapper.GetTypeName(String name)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass8_0.b__0(Type
> x)
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.FindType(Assembly asm,
> String typeName, IBinaryNameMapper mapper)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass4_0.b__1(Assembly
> a)
>at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveNonGenericType(String
> assemblyName, String typeName, ICollection`1 assemblies, IBinaryNameMapper
> nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> assemblyName, TypeNameParser typeName, ICollection`1 assemblies,
> IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> typeName, String assemblyName, IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.ResolveType(String typeName)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Boolean
> userType, Int32 typeId, Boolean requiresType, String typeName, Type knownType)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(String
> typeName, Boolean requiresType)
>at
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.<>c__DisplayClass98_0.b__0()
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.SafeCall[T](Func`1
> func, Boolean allowUnitialized)
> {code}
> 1. ResolveNonGenericType should skip all generic types when scanning
> assemblies
> 2. ParseArrayDefinition should be fixed
> *Workaround*
> Register SQL key and value types manually before starting the cache:
> {code}
> ignite.GetBinary().GetBinaryType(typeof(TKey));
> ignite.GetBinary().GetBinaryType(typeof(TValue));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15845) .NET: CreateCache fails - Invalid array specification
[
https://issues.apache.org/jira/browse/IGNITE-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15845:
Fix Version/s: 2.12
> .NET: CreateCache fails - Invalid array specification
> -
>
> Key: IGNITE-15845
> URL: https://issues.apache.org/jira/browse/IGNITE-15845
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.12, 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignition.Start fails with an exception:
> {code}
> Failure in Java callback Apache.Ignite.Core.Common.IgniteException: Invalid
> array specification:
> MassTransit.Initializers.PropertyConverters.MessageDataPropertyConverter+\,MassTransit-MessageData>-Convert>d__4`1
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.ParseArrayDefinition()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser..ctor(String typeName,
> Int32& pos)
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse(String typeName)
>at Apache.Ignite.Core.Binary.BinaryBasicNameMapper.GetTypeName(String name)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass8_0.b__0(Type
> x)
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.FindType(Assembly asm,
> String typeName, IBinaryNameMapper mapper)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass4_0.b__1(Assembly
> a)
>at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveNonGenericType(String
> assemblyName, String typeName, ICollection`1 assemblies, IBinaryNameMapper
> nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> assemblyName, TypeNameParser typeName, ICollection`1 assemblies,
> IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> typeName, String assemblyName, IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.ResolveType(String typeName)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Boolean
> userType, Int32 typeId, Boolean requiresType, String typeName, Type knownType)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(String
> typeName, Boolean requiresType)
>at
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.<>c__DisplayClass98_0.b__0()
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.SafeCall[T](Func`1
> func, Boolean allowUnitialized)
> {code}
> 1. ResolveNonGenericType should skip all generic types when scanning
> assemblies
> 2. ParseArrayDefinition should be fixed
> *Workaround*
> Register SQL key and value types manually before starting the cache:
> {code}
> ignite.GetBinary().GetBinaryType(typeof(TKey));
> ignite.GetBinary().GetBinaryType(typeof(TValue));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15845) .NET: CreateCache fails - Invalid array specification
[
https://issues.apache.org/jira/browse/IGNITE-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15845:
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> .NET: CreateCache fails - Invalid array specification
> -
>
> Key: IGNITE-15845
> URL: https://issues.apache.org/jira/browse/IGNITE-15845
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.12, 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignition.Start fails with an exception:
> {code}
> Failure in Java callback Apache.Ignite.Core.Common.IgniteException: Invalid
> array specification:
> MassTransit.Initializers.PropertyConverters.MessageDataPropertyConverter+\,MassTransit-MessageData>-Convert>d__4`1
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.ParseArrayDefinition()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser..ctor(String typeName,
> Int32& pos)
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse(String typeName)
>at Apache.Ignite.Core.Binary.BinaryBasicNameMapper.GetTypeName(String name)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass8_0.b__0(Type
> x)
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.FindType(Assembly asm,
> String typeName, IBinaryNameMapper mapper)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass4_0.b__1(Assembly
> a)
>at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveNonGenericType(String
> assemblyName, String typeName, ICollection`1 assemblies, IBinaryNameMapper
> nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> assemblyName, TypeNameParser typeName, ICollection`1 assemblies,
> IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> typeName, String assemblyName, IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.ResolveType(String typeName)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Boolean
> userType, Int32 typeId, Boolean requiresType, String typeName, Type knownType)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(String
> typeName, Boolean requiresType)
>at
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.<>c__DisplayClass98_0.b__0()
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.SafeCall[T](Func`1
> func, Boolean allowUnitialized)
> {code}
> 1. ResolveNonGenericType should skip all generic types when scanning
> assemblies
> 2. ParseArrayDefinition should be fixed
> *Workaround*
> Register SQL key and value types manually before starting the cache:
> {code}
> ignite.GetBinary().GetBinaryType(typeof(TKey));
> ignite.GetBinary().GetBinaryType(typeof(TValue));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15845) .NET: CreateCache fails - Invalid array specification
[
https://issues.apache.org/jira/browse/IGNITE-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444356#comment-17444356
]
Pavel Tupitsyn commented on IGNITE-15845:
-
Cherry-picked to ignite-2.12: 5db72544629249cf285479e5df8018341a0d2c5b
> .NET: CreateCache fails - Invalid array specification
> -
>
> Key: IGNITE-15845
> URL: https://issues.apache.org/jira/browse/IGNITE-15845
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.12, 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignition.Start fails with an exception:
> {code}
> Failure in Java callback Apache.Ignite.Core.Common.IgniteException: Invalid
> array specification:
> MassTransit.Initializers.PropertyConverters.MessageDataPropertyConverter+\,MassTransit-MessageData>-Convert>d__4`1
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.ParseArrayDefinition()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser..ctor(String typeName,
> Int32& pos)
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse(String typeName)
>at Apache.Ignite.Core.Binary.BinaryBasicNameMapper.GetTypeName(String name)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass8_0.b__0(Type
> x)
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.FindType(Assembly asm,
> String typeName, IBinaryNameMapper mapper)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass4_0.b__1(Assembly
> a)
>at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveNonGenericType(String
> assemblyName, String typeName, ICollection`1 assemblies, IBinaryNameMapper
> nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> assemblyName, TypeNameParser typeName, ICollection`1 assemblies,
> IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> typeName, String assemblyName, IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.ResolveType(String typeName)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Boolean
> userType, Int32 typeId, Boolean requiresType, String typeName, Type knownType)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(String
> typeName, Boolean requiresType)
>at
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.<>c__DisplayClass98_0.b__0()
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.SafeCall[T](Func`1
> func, Boolean allowUnitialized)
> {code}
> 1. ResolveNonGenericType should skip all generic types when scanning
> assemblies
> 2. ParseArrayDefinition should be fixed
> *Workaround*
> Register SQL key and value types manually before starting the cache:
> {code}
> ignite.GetBinary().GetBinaryType(typeof(TKey));
> ignite.GetBinary().GetBinaryType(typeof(TValue));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15845) .NET: CreateCache fails - Invalid array specification
[
https://issues.apache.org/jira/browse/IGNITE-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15845:
Affects Version/s: 2.6
> .NET: CreateCache fails - Invalid array specification
> -
>
> Key: IGNITE-15845
> URL: https://issues.apache.org/jira/browse/IGNITE-15845
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.12, 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignition.Start fails with an exception:
> {code}
> Failure in Java callback Apache.Ignite.Core.Common.IgniteException: Invalid
> array specification:
> MassTransit.Initializers.PropertyConverters.MessageDataPropertyConverter+\,MassTransit-MessageData>-Convert>d__4`1
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.ParseArrayDefinition()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse()
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser..ctor(String typeName,
> Int32& pos)
>at Apache.Ignite.Core.Impl.Binary.TypeNameParser.Parse(String typeName)
>at Apache.Ignite.Core.Binary.BinaryBasicNameMapper.GetTypeName(String name)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass8_0.b__0(Type
> x)
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.FindType(Assembly asm,
> String typeName, IBinaryNameMapper mapper)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.<>c__DisplayClass4_0.b__1(Assembly
> a)
>at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
>at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source,
> Func`2 predicate, Boolean& found)
>at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source,
> Func`2 predicate)
>at
> Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveNonGenericType(String
> assemblyName, String typeName, ICollection`1 assemblies, IBinaryNameMapper
> nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> assemblyName, TypeNameParser typeName, ICollection`1 assemblies,
> IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.TypeResolver.ResolveType(String
> typeName, String assemblyName, IBinaryNameMapper nameMapper)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.ResolveType(String typeName)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Boolean
> userType, Int32 typeId, Boolean requiresType, String typeName, Type knownType)
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(String
> typeName, Boolean requiresType)
>at
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.<>c__DisplayClass98_0.b__0()
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.SafeCall[T](Func`1
> func, Boolean allowUnitialized)
> {code}
> 1. ResolveNonGenericType should skip all generic types when scanning
> assemblies
> 2. ParseArrayDefinition should be fixed
> *Workaround*
> Register SQL key and value types manually before starting the cache:
> {code}
> ignite.GetBinary().GetBinaryType(typeof(TKey));
> ignite.GetBinary().GetBinaryType(typeof(TValue));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15348) Checkstyle should check whitespace after cast token.
[
https://issues.apache.org/jira/browse/IGNITE-15348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444361#comment-17444361
]
Maksim Timonin commented on IGNITE-15348:
-
[~andydem] , hi!
There is a separated block related to whitespaces and symbols like \{, }, (, )
[1]. According to it there should not be space after ")":
> Blanks space (1 space character) should be used before opening *(* or
>{*}{{*}. *{* and *}* should always be the last tokens in the line (except for
>the possible comments). However, blank space should not be used between the
>method name and opening {*}({*}.
Also, it's historical practice, some of Ignite commiters require to avoid
spaces after cast operations.
[1]https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines
> Checkstyle should check whitespace after cast token.
> -
>
> Key: IGNITE-15348
> URL: https://issues.apache.org/jira/browse/IGNITE-15348
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maksim Timonin
>Assignee: Andrei Demidov
>Priority: Major
> Labels: newbie
>
> According to Ignite code style [1] there shouldn't a whitespace after the
> ")" token. Let's add check for that.
>
> Solution is add the TYPECAST token to the NoWhitespaceAfter module
>
>
>
>
> Also it is required to fix all issues within repo.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15348) Checkstyle should check whitespace after cast token.
[ https://issues.apache.org/jira/browse/IGNITE-15348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444364#comment-17444364 ] Andrei Demidov commented on IGNITE-15348: - [~timonin.maksim], ok, thanks! > Checkstyle should check whitespace after cast token. > - > > Key: IGNITE-15348 > URL: https://issues.apache.org/jira/browse/IGNITE-15348 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Andrei Demidov >Priority: Major > Labels: newbie > > According to Ignite code style [1] there shouldn't a whitespace after the > ")" token. Let's add check for that. > > Solution is add the TYPECAST token to the NoWhitespaceAfter module > > > > > Also it is required to fix all issues within repo. > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-13558) GridCacheProcessor should implement better parallelization when restoring partition states on startup
[ https://issues.apache.org/jira/browse/IGNITE-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444381#comment-17444381 ] Denis Chudov commented on IGNITE-13558: --- Thank you! I'm going to get a new visa and then we will be ready to merge. > GridCacheProcessor should implement better parallelization when restoring > partition states on startup > - > > Key: IGNITE-13558 > URL: https://issues.apache.org/jira/browse/IGNITE-13558 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Sergey Chugunov >Assignee: Denis Chudov >Priority: Major > Time Spent: 4h > Remaining Estimate: 0h > > GridCacheProcessor#restorePartitionStates method tries to employ striped pool > to restore partition states in parallel but level of parallelization is down > only to cache group per thread. > It is not enough and not utilizes resources effectively in case of one cache > group much bigger than the others. > We need to parallel restore process down to individual partitions to get the > most from the available resources and speed up node startup. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15922) Create numa-aware allocator for data regions.
Ivan Daschinsky created IGNITE-15922:
Summary: Create numa-aware allocator for data regions.
Key: IGNITE-15922
URL: https://issues.apache.org/jira/browse/IGNITE-15922
Project: Ignite
Issue Type: Improvement
Reporter: Ivan Daschinsky
Assignee: Ivan Daschinsky
Sometimes it is worth to allocate data region on specific numa node or on
interleaved node (i.e. Intel Optane can be set up as a little bit slower, but
cheaper than and have more capacity, than DDR, and unified as NUMA nodes).
Need to write C++ wrapper around {{libnuma}} and extract common allocator
interface and add as a configuration parameter to {{DataRegionConfiguration}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15085) Implement tx coordination
[
https://issues.apache.org/jira/browse/IGNITE-15085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15085:
-
Reviewer: Alexander Lapin
> Implement tx coordination
> -
>
> Key: IGNITE-15085
> URL: https://issues.apache.org/jira/browse/IGNITE-15085
> Project: Ignite
> Issue Type: Task
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Labels: iep-61, ignite-3
> Time Spent: 7h 40m
> Remaining Estimate: 0h
>
> This ticket implies the implementation of tx coordination, as described in
> [1].
> This includes:
> * TxManager - top-level manager for tx state and coordination
> * pre-writes - each tx write is pre-written to partition store in special
> format
> * replicated tx state - tx state is stored in the partition's raft group
> * integration with lock manager (see *precaution* chapter in [1])
> The example of single key tx:
> {noformat}
> Tx client TxCoordinator
> Partition leaseholder.
> tx.start
> ->
> assign timestamp (id)
> txstate = PENDING
> <-
> table.put(k,v)
> ->
> enlist(partition(k));
> lh = getLeaseholder(partition(k))
> send UpsertCommand(k) to lh
>
> >
>
>replicate txstate = PENDING
>
>lockManager.tryAcquire(k,timestamp);
>
>wait for completion async
>
>prewrite(k, v) -- replicate to all replicas
> repeat for each enlisted partition...
> <-
> tx.finish - commit or rollback
> ->
> send finish request to all remote enlisted nodes
>
> >
>
>replicate txstate = COMMITTED/ABORTED
> txState = COMMITTED/ABORTED
>lockManager.tryRelease(k, timestamp)
>
> <
>
> when all leasholders are replied,
> reply to initiator
> <
> {noformat}
> [1] [https://github.com/apache/ignite-3/tree/main/modules/transactions]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15085) Implement tx coordination
[
https://issues.apache.org/jira/browse/IGNITE-15085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1719#comment-1719
]
Vyacheslav Koptilin commented on IGNITE-15085:
--
Hello [~alapin],
Could you please take a look at this pull request?
> Implement tx coordination
> -
>
> Key: IGNITE-15085
> URL: https://issues.apache.org/jira/browse/IGNITE-15085
> Project: Ignite
> Issue Type: Task
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Labels: iep-61, ignite-3
> Time Spent: 7h 40m
> Remaining Estimate: 0h
>
> This ticket implies the implementation of tx coordination, as described in
> [1].
> This includes:
> * TxManager - top-level manager for tx state and coordination
> * pre-writes - each tx write is pre-written to partition store in special
> format
> * replicated tx state - tx state is stored in the partition's raft group
> * integration with lock manager (see *precaution* chapter in [1])
> The example of single key tx:
> {noformat}
> Tx client TxCoordinator
> Partition leaseholder.
> tx.start
> ->
> assign timestamp (id)
> txstate = PENDING
> <-
> table.put(k,v)
> ->
> enlist(partition(k));
> lh = getLeaseholder(partition(k))
> send UpsertCommand(k) to lh
>
> >
>
>replicate txstate = PENDING
>
>lockManager.tryAcquire(k,timestamp);
>
>wait for completion async
>
>prewrite(k, v) -- replicate to all replicas
> repeat for each enlisted partition...
> <-
> tx.finish - commit or rollback
> ->
> send finish request to all remote enlisted nodes
>
> >
>
>replicate txstate = COMMITTED/ABORTED
> txState = COMMITTED/ABORTED
>lockManager.tryRelease(k, timestamp)
>
> <
>
> when all leasholders are replied,
> reply to initiator
> <
> {noformat}
> [1] [https://github.com/apache/ignite-3/tree/main/modules/transactions]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15794) Request attributes for a java service.
[
https://issues.apache.org/jira/browse/IGNITE-15794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1741#comment-1741
]
Ignite TC Bot commented on IGNITE-15794:
{panel:title=Branch: [pull/9510/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9510/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid (Legacy Mode){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=6270615]]
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttributeMultithreaded[clusterSingleton=false,
sticky=true] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttribute[clusterSingleton=false,
sticky=false] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttributeMultithreaded[clusterSingleton=false,
sticky=false] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttribute[clusterSingleton=true,
sticky=true] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttributeMultithreaded[clusterSingleton=true,
sticky=true] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttribute[clusterSingleton=false,
sticky=true] - PASSED{color}
{color:#8b}Service Grid{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=6270594]]
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttributeMultithreaded[clusterSingleton=false,
sticky=true] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttribute[clusterSingleton=false,
sticky=false] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttributeMultithreaded[clusterSingleton=false,
sticky=false] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttribute[clusterSingleton=true,
sticky=true] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttributeMultithreaded[clusterSingleton=true,
sticky=true] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
IgniteServiceCallContextTest.testContextAttribute[clusterSingleton=false,
sticky=true] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6270620&buildTypeId=IgniteTests24Java8_RunAll]
> Request attributes for a java service.
> ---
>
> Key: IGNITE-15794
> URL: https://issues.apache.org/jira/browse/IGNITE-15794
> Project: Ignite
> Issue Type: Sub-task
> Components: managed services
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-79, ise
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Implement support for passing implicit "request" attributes from the proxy to
> the Java service.
> *Implementation notes*.
> # If no caller attributes are passed - there should be no performance
> overhead when executing service methods.
> # Attributes allow only {{string}} and {{byte[]}} values and does not permit
> nulls in key/values.
> # Currently, the context should be immutable, but in the future, it should
> be possible to change it through the interceptor.
> # {{ServiceResource}} annotation allows to inject service/proxy, we must
> provide the ability to transparently pass the context to the injected service.
> *Public API changes:*
> New methods in {{IgniteServices}} to pass caller context to service proxy.
> {code:java}
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx)
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx, long timeout)
> {code}
> New method in {{ServiceContext}} for getting caller context inside the
> service method.
> {code:java}
> /**
> * Gets context of the current service call.
> *
> * @return Context of the current service call, possibly {@code null}.
> * @see ServiceCallContext
> */
> @Nullable public ServiceCallContext currentCallContext();
> {code}
> New interface {{ServiceCallContext}}
> {code:java}
> public interface ServiceCallContext {
> public String attribute(String name);
> public byte[] binaryAttribute(String name);
> }
> {code}
> And the builder {{ServiceCallContextBuilder}} for creating
> {{ServiceCallContext}}.
> New property in {{ServiceResource annotation}}.
> {code:java}
> /**
> * Flag indicating that the service call conte
[jira] [Commented] (IGNITE-15794) Request attributes for a java service.
[
https://issues.apache.org/jira/browse/IGNITE-15794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1742#comment-1742
]
Pavel Pereslegin commented on IGNITE-15794:
---
[~ivandasch].
Thank you for the review!
Иot's visa is ready.
> Request attributes for a java service.
> ---
>
> Key: IGNITE-15794
> URL: https://issues.apache.org/jira/browse/IGNITE-15794
> Project: Ignite
> Issue Type: Sub-task
> Components: managed services
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-79, ise
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Implement support for passing implicit "request" attributes from the proxy to
> the Java service.
> *Implementation notes*.
> # If no caller attributes are passed - there should be no performance
> overhead when executing service methods.
> # Attributes allow only {{string}} and {{byte[]}} values and does not permit
> nulls in key/values.
> # Currently, the context should be immutable, but in the future, it should
> be possible to change it through the interceptor.
> # {{ServiceResource}} annotation allows to inject service/proxy, we must
> provide the ability to transparently pass the context to the injected service.
> *Public API changes:*
> New methods in {{IgniteServices}} to pass caller context to service proxy.
> {code:java}
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx)
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx, long timeout)
> {code}
> New method in {{ServiceContext}} for getting caller context inside the
> service method.
> {code:java}
> /**
> * Gets context of the current service call.
> *
> * @return Context of the current service call, possibly {@code null}.
> * @see ServiceCallContext
> */
> @Nullable public ServiceCallContext currentCallContext();
> {code}
> New interface {{ServiceCallContext}}
> {code:java}
> public interface ServiceCallContext {
> public String attribute(String name);
> public byte[] binaryAttribute(String name);
> }
> {code}
> And the builder {{ServiceCallContextBuilder}} for creating
> {{ServiceCallContext}}.
> New property in {{ServiceResource annotation}}.
> {code:java}
> /**
> * Flag indicating that the service call context should be passed to the
> injected service.
> *
> * @return {@code True} if the service call context should be passed to the
> injected service.
> */
> public boolean forwardCallerContext() default false;
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-15794) Request attributes for a java service.
[
https://issues.apache.org/jira/browse/IGNITE-15794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1742#comment-1742
]
Pavel Pereslegin edited comment on IGNITE-15794 at 11/16/21, 10:43 AM:
---
[~ivandasch].
Thank you for the review!
Bot's visa is ready.
was (Author: xtern):
[~ivandasch].
Thank you for the review!
Иot's visa is ready.
> Request attributes for a java service.
> ---
>
> Key: IGNITE-15794
> URL: https://issues.apache.org/jira/browse/IGNITE-15794
> Project: Ignite
> Issue Type: Sub-task
> Components: managed services
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-79, ise
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Implement support for passing implicit "request" attributes from the proxy to
> the Java service.
> *Implementation notes*.
> # If no caller attributes are passed - there should be no performance
> overhead when executing service methods.
> # Attributes allow only {{string}} and {{byte[]}} values and does not permit
> nulls in key/values.
> # Currently, the context should be immutable, but in the future, it should
> be possible to change it through the interceptor.
> # {{ServiceResource}} annotation allows to inject service/proxy, we must
> provide the ability to transparently pass the context to the injected service.
> *Public API changes:*
> New methods in {{IgniteServices}} to pass caller context to service proxy.
> {code:java}
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx)
> public T serviceProxy(String name, Class svcItf, boolean
> sticky, ServiceCallContext callCtx, long timeout)
> {code}
> New method in {{ServiceContext}} for getting caller context inside the
> service method.
> {code:java}
> /**
> * Gets context of the current service call.
> *
> * @return Context of the current service call, possibly {@code null}.
> * @see ServiceCallContext
> */
> @Nullable public ServiceCallContext currentCallContext();
> {code}
> New interface {{ServiceCallContext}}
> {code:java}
> public interface ServiceCallContext {
> public String attribute(String name);
> public byte[] binaryAttribute(String name);
> }
> {code}
> And the builder {{ServiceCallContextBuilder}} for creating
> {{ServiceCallContext}}.
> New property in {{ServiceResource annotation}}.
> {code:java}
> /**
> * Flag indicating that the service call context should be passed to the
> injected service.
> *
> * @return {@code True} if the service call context should be passed to the
> injected service.
> */
> public boolean forwardCallerContext() default false;
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15915) .NET thin: SSL keystore shouldn't be a mandatory parameter
[
https://issues.apache.org/jira/browse/IGNITE-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1773#comment-1773
]
Igor Sapego commented on IGNITE-15915:
--
[~ptupitsyn] looks good to me.
> .NET thin: SSL keystore shouldn't be a mandatory parameter
> --
>
> Key: IGNITE-15915
> URL: https://issues.apache.org/jira/browse/IGNITE-15915
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, SslStreamFactory can't be configured without specifying
> client-side certificates.
> This shouldn't be the case - SSL can be used without any certificates on the
> client.
> Workaround:
> {code}
> class SimpleSslStreamFactory : ISslStreamFactory {
> public SslStream Create(Stream stream, string targetHost)
> {
> var sslStream = new SslStream(stream, false, null, null);
> sslStream.AuthenticateAsClient(targetHost);
> return sslStream;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15896) Update extensions docs: the downloads page, 2.11 spring integrations
[ https://issues.apache.org/jira/browse/IGNITE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1786#comment-1786 ] Maxim Muzafarov commented on IGNITE-15896: -- Looks good, please proceed with the merge. > Update extensions docs: the downloads page, 2.11 spring integrations > > > Key: IGNITE-15896 > URL: https://issues.apache.org/jira/browse/IGNITE-15896 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > > Update extensions docs: the downloads page, 2.11 spring integrations -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15923) Remove illegal property in maven-checkstyle-plugin configuration
Aleksandr Polovtcev created IGNITE-15923:
Summary: Remove illegal property in maven-checkstyle-plugin
configuration
Key: IGNITE-15923
URL: https://issues.apache.org/jira/browse/IGNITE-15923
Project: Ignite
Issue Type: Task
Reporter: Aleksandr Polovtcev
Assignee: Aleksandr Polovtcev
maven-checkstyle-plugin configuration in root {{pom.xml}} contains the
following lines:
{code}
fail-if-error
validate
true
true
true
checkstyle-aggregate
{code}
However, {{logViolationsToConsole}} option is only applicable to the {{check}}
goal, the {{checkstyle-aggregate}} goal does not have this property. It should
be removed
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15923) Remove redundant property in maven-checkstyle-plugin configuration
[
https://issues.apache.org/jira/browse/IGNITE-15923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-15923:
-
Summary: Remove redundant property in maven-checkstyle-plugin configuration
(was: Remove illegal property in maven-checkstyle-plugin configuration)
> Remove redundant property in maven-checkstyle-plugin configuration
> --
>
> Key: IGNITE-15923
> URL: https://issues.apache.org/jira/browse/IGNITE-15923
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Trivial
>
> maven-checkstyle-plugin configuration in root {{pom.xml}} contains the
> following lines:
> {code}
>
> fail-if-error
> validate
>
> true
> true
> true
>
>
> checkstyle-aggregate
>
>
> {code}
> However, {{logViolationsToConsole}} option is only applicable to the
> {{check}} goal, the {{checkstyle-aggregate}} goal does not have this
> property. It should be removed
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15923) Remove redundant property in maven-checkstyle-plugin configuration
[
https://issues.apache.org/jira/browse/IGNITE-15923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-15923:
-
Labels: ignite-3 (was: )
> Remove redundant property in maven-checkstyle-plugin configuration
> --
>
> Key: IGNITE-15923
> URL: https://issues.apache.org/jira/browse/IGNITE-15923
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Trivial
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> maven-checkstyle-plugin configuration in root {{pom.xml}} contains the
> following lines:
> {code}
>
> fail-if-error
> validate
>
> true
> true
> true
>
>
> checkstyle-aggregate
>
>
> {code}
> However, {{logViolationsToConsole}} option is only applicable to the
> {{check}} goal, the {{checkstyle-aggregate}} goal does not have this
> property. It should be removed
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15918) Wrong dimension for AveragePutTime and AverageGetTime
[
https://issues.apache.org/jira/browse/IGNITE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15918:
-
Summary: Wrong dimension for AveragePutTime and AverageGetTime (was:
Whorng dimension for AveragePutTime and AverageGetTime)
> Wrong dimension for AveragePutTime and AverageGetTime
> -
>
> Key: IGNITE-15918
> URL: https://issues.apache.org/jira/browse/IGNITE-15918
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Igor Akkuratov
>Priority: Minor
> Labels: .NET, Documentation
>
> After IGNITE-4234 there are wrongs dimensions for metrics AveragePutTime and
> AverageGetTime.
> {code:java}
> ///
> /// The mean time to execute gets.
> ///
> ///
> /// The time in ms.
> ///
> float AverageGetTime { get; }
> ///
> /// The mean time to execute puts.
> ///
> ///
> /// The time in s.
> ///
> float AveragePutTime { get; }{code}
> Return value for getTime in ms, for putTime in s whenever in javadoc there
> are both in µs
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheMetrics.html#getAveragePutTime--
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15890) [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST
[ https://issues.apache.org/jira/browse/IGNITE-15890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15890: --- Fix Version/s: 2.13 > [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST > -- > > Key: IGNITE-15890 > URL: https://issues.apache.org/jira/browse/IGNITE-15890 > Project: Ignite > Issue Type: Test >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: IEP-56 > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > Add ignite version 2.11.0 to Docker file and set it as LATEST -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [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
]
Nikolay Izhikov updated IGNITE-14794:
-
Labels: iep-43 ise (was: iep-43)
> 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.12
>
> 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
> 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}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15890) [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST
[ https://issues.apache.org/jira/browse/IGNITE-15890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444511#comment-17444511 ] Dmitry Pavlov commented on IGNITE-15890: Merged to master https://github.com/apache/ignite/commit/c4f8d04b6f03bef0172e8a306de82743af4524a7 [~RyzhovSV] thank you for contribution. > [ducktests] Add ignite version 2.11.0 to Docker file and set it as LATEST > -- > > Key: IGNITE-15890 > URL: https://issues.apache.org/jira/browse/IGNITE-15890 > Project: Ignite > Issue Type: Test >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: IEP-56 > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > Add ignite version 2.11.0 to Docker file and set it as LATEST -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13510) Getting status of snapshot execution via command line and jmx
[
https://issues.apache.org/jira/browse/IGNITE-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-13510:
-
Labels: iep-43 ise snapshot (was: iep-43 snapshot)
> Getting status of snapshot execution via command line and jmx
> -
>
> Key: IGNITE-13510
> URL: https://issues.apache.org/jira/browse/IGNITE-13510
> Project: Ignite
> Issue Type: Task
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: iep-43, ise, snapshot
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> the control.sh utility immediately relinquishes control
> and without using metricExporter it is impossible to understand whether the
> snapshot completed or not
> Restoring
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:59.523
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Restoring to snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Restoring to snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:59.546
> Execution time: 23 ms
> {code}
> Creating
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:55.368
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> Creating the snapshot with name: snapshot_02052020
> gridCommandHandlerTest1 -> Creating the snapshot with name: snapshot_02052020
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:55.391
> Execution time: 23 ms
> {code}
> No snapshot operation
> {code:java}
> Control utility [ver. 2.12.0-SNAPSHOT#20211004-sha1:77de60a7]
> 2021 Copyright(C) Apache Software Foundation
> User: sega
> Time: 2021-10-07T14:18:58.408
> Command [SNAPSHOT] started
> Arguments: --snapshot status --yes
>
> Status of SNAPSHOT operations:
> gridCommandHandlerTest0 -> No snapshot operation.
> gridCommandHandlerTest1 -> No snapshot operation.
> Command [SNAPSHOT] finished with code: 0
> Control utility has completed execution at: 2021-10-07T14:18:58.439
> Execution time: 31 ms
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-14031) Add Docker images based on Java 11
[ https://issues.apache.org/jira/browse/IGNITE-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov reassigned IGNITE-14031: Assignee: Petr Ivanov > Add Docker images based on Java 11 > -- > > Key: IGNITE-14031 > URL: https://issues.apache.org/jira/browse/IGNITE-14031 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Kadaner >Assignee: Petr Ivanov >Priority: Major > > Since Java 11 support was added in > https://issues.apache.org/jira/browse/IGNITE-11189 it should be possible to > create Docker images as well. > This will allow usage of TLSv1.3 and make > _‑Djdk.tls.client.protocols=TLSv1.2_ JVM parameter unnecessary on thick > clients. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15915) .NET thin: SSL keystore shouldn't be a mandatory parameter
[
https://issues.apache.org/jira/browse/IGNITE-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444521#comment-17444521
]
Ignite TC Bot commented on IGNITE-15915:
{panel:title=Branch: [pull/9566/head] Base: [master] : Possible Blockers
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271512]]
* exe: ClientConnectionTest.TestSslConnectionWithoutClientAuth - History for
base branch is absent.
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6271533]]
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271582]]
* IgniteSpiTestSuite:
TooManyOpenFilesTcpCommunicationSpiTest.testTooManyOpenFilesErr - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271587]]
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryOperationP2PTest.testTxClient - Test has low fail rate in
base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryLongP2PTest.testTxReplicatedClient - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271588]]
* ZookeeperDiscoverySpiTestSuite4: IgniteCachePutRetryAtomicSelfTest.testPutAll
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}SPI (URI Deploy){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271591]]
* IgniteUriDeploymentTestSuite:
GridUriDeploymentMd5CheckSelfTest.testMd5DirectoryCheck - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9566/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Platform .NET (Windows){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6271512]]
* {color:#013220}exe: RawSecureSocketTest.TestHandshake(False) - PASSED{color}
* {color:#013220}exe: RawSecureSocketTest.TestHandshake(True) - PASSED{color}
* {color:#8b}exe: ClientConnectionTest.TestSslConnectionWithoutClientAuth -
FAILED{color}
* {color:#013220}exe: ClientConnectionTest.TestSslConnectionWithClientAuth -
PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6271505]]
* {color:#013220}dll: RawSecureSocketTest.TestHandshake(False) - PASSED{color}
* {color:#013220}dll: RawSecureSocketTest.TestHandshake(True) - PASSED{color}
* {color:#013220}dll: ClientConnectionTest.TestSslConnectionWithoutClientAuth -
PASSED{color}
* {color:#013220}dll: ClientConnectionTest.TestSslConnectionWithClientAuth -
PASSED{color}
{color:#8b}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271580]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
BusyExecutorTest.testReactivationCancellableWontStart - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
BusyExecutorTest.testReactivationWontStart - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6271599&buildTypeId=IgniteTests24Java8_RunAll]
> .NET thin: SSL keystore shouldn't be a mandatory parameter
> --
>
> Key: IGNITE-15915
> URL: https://issues.apache.org/jira/browse/IGNITE-15915
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, SslStreamFactory can't be configured without specifying
> client-side certificates.
> This shouldn't be the case - SSL can be used without any certificates on the
> client.
> Workaround:
> {code}
> class SimpleSslStreamFactory : ISslStreamFactory {
> public SslStream Create(Stream stream, string targetHost)
> {
> var sslStream = new SslStream(stream, false, null, null);
> sslStream.AuthenticateAsClient(targetHost);
> return sslStream;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15923) Remove redundant property in maven-checkstyle-plugin configuration
[
https://issues.apache.org/jira/browse/IGNITE-15923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Ivanov updated IGNITE-15923:
-
Fix Version/s: 3.0.0-alpha4
> Remove redundant property in maven-checkstyle-plugin configuration
> --
>
> Key: IGNITE-15923
> URL: https://issues.apache.org/jira/browse/IGNITE-15923
> Project: Ignite
> Issue Type: Task
>Affects Versions: 3.0.0-alpha4
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Trivial
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> maven-checkstyle-plugin configuration in root {{pom.xml}} contains the
> following lines:
> {code}
>
> fail-if-error
> validate
>
> true
> true
> true
>
>
> checkstyle-aggregate
>
>
> {code}
> However, {{logViolationsToConsole}} option is only applicable to the
> {{check}} goal, the {{checkstyle-aggregate}} goal does not have this
> property. It should be removed
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15923) Remove redundant property in maven-checkstyle-plugin configuration
[
https://issues.apache.org/jira/browse/IGNITE-15923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Ivanov updated IGNITE-15923:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Remove redundant property in maven-checkstyle-plugin configuration
> --
>
> Key: IGNITE-15923
> URL: https://issues.apache.org/jira/browse/IGNITE-15923
> Project: Ignite
> Issue Type: Task
>Affects Versions: 3.0.0-alpha4
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Trivial
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> maven-checkstyle-plugin configuration in root {{pom.xml}} contains the
> following lines:
> {code}
>
> fail-if-error
> validate
>
> true
> true
> true
>
>
> checkstyle-aggregate
>
>
> {code}
> However, {{logViolationsToConsole}} option is only applicable to the
> {{check}} goal, the {{checkstyle-aggregate}} goal does not have this
> property. It should be removed
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15923) Remove redundant property in maven-checkstyle-plugin configuration
[
https://issues.apache.org/jira/browse/IGNITE-15923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Ivanov updated IGNITE-15923:
-
Affects Version/s: 3.0.0-alpha4
> Remove redundant property in maven-checkstyle-plugin configuration
> --
>
> Key: IGNITE-15923
> URL: https://issues.apache.org/jira/browse/IGNITE-15923
> Project: Ignite
> Issue Type: Task
>Affects Versions: 3.0.0-alpha4
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Trivial
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> maven-checkstyle-plugin configuration in root {{pom.xml}} contains the
> following lines:
> {code}
>
> fail-if-error
> validate
>
> true
> true
> true
>
>
> checkstyle-aggregate
>
>
> {code}
> However, {{logViolationsToConsole}} option is only applicable to the
> {{check}} goal, the {{checkstyle-aggregate}} goal does not have this
> property. It should be removed
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to send message to next nod] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Summary: Intermittent [Failed to send message to next nod] exception on
node shutdown (was: Intermittent [Failed to notify direct custom event
listener] exception on node shutdown)
> Intermittent [Failed to send message to next nod] exception on node shutdown
>
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
>
> {+}*Reproducer*{+}:
> Run a cluster with few nodes, on bringing down one of the nodes, the other
> nodes throw this exception intermittently and eventually come down
> +*Actual result*+
> Intermittent exception in one of the nodes:
> {noformat}
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@3a0d7950,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=a452f5c7-4a27-4a5e-be3e-77ddae5d50a3]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)Nov 03, 2021 12:11:00 PM
> org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@67cc413e,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=c2ce7d01-5c5b-4654-8942-bd7ab6b90351]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
> at
> org.apache.ignite.internal.manag
[jira] [Updated] (IGNITE-15886) Intermittent [Failed to send message to next node] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-15886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aggarwal updated IGNITE-15886:
-
Summary: Intermittent [Failed to send message to next node] exception on
node shutdown (was: Intermittent [Failed to send message to next nod]
exception on node shutdown)
> Intermittent [Failed to send message to next node] exception on node shutdown
> -
>
> Key: IGNITE-15886
> URL: https://issues.apache.org/jira/browse/IGNITE-15886
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Gaurav Aggarwal
>Assignee: Mikhail Petrov
>Priority: Major
>
> {+}*Reproducer*{+}:
> Run a cluster with few nodes, on bringing down one of the nodes, the other
> nodes throw this exception intermittently and eventually come down
> +*Actual result*+
> Intermittent exception in one of the nodes:
> {noformat}
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@3a0d7950,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=a452f5c7-4a27-4a5e-be3e-77ddae5d50a3]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2715)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)Nov 03, 2021 12:11:00 PM
> org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to notify direct custom event listener:
> StartRoutineDiscoveryMessage [startReqData=StartRequestData
> [prjPred=com.bfm.libignite.cluster.filter.ClusterGroupFilter@67cc413e,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandlerV2
> [rmtFilterFactoryDep=null, types=0], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=c2ce7d01-5c5b-4654-8942-bd7ab6b90351]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:717)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:526)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2677)
> at
> org.apache.ignite.internal.managers.disc
[jira] [Created] (IGNITE-15924) Java thin client: Type name is not cached on client side for OptimizerMarshaller types
Alex Plehanov created IGNITE-15924:
--
Summary: Java thin client: Type name is not cached on client side
for OptimizerMarshaller types
Key: IGNITE-15924
URL: https://issues.apache.org/jira/browse/IGNITE-15924
Project: Ignite
Issue Type: Bug
Reporter: Alex Plehanov
For JDK marshaller types (for example {{LocalDateTime}} use JDK marshaller)
requested by {{typeId}} type name not cached correctly.
For example, in this fragment, type name requested twice by thin-client (after
each get request), but should be cached after the first request:
{code:java}
try (Ignite srv = Ignition.start(Config.getServerConfiguration())) {
srv.cache(Config.DEFAULT_CACHE_NAME).put(1, LocalDateTime.now());
try (IgniteClient client = Ignition.startClient(new
ClientConfiguration().setAddresses(Config.SERVER))) {
client.cache(Config.DEFAULT_CACHE_NAME).get(1);
client.cache(Config.DEFAULT_CACHE_NAME).get(1);
}
} {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15884) Make TableIndexConfigurationSchema polymorphic
[
https://issues.apache.org/jira/browse/IGNITE-15884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-15884:
---
Epic Link: IGNITE-14904
> Make TableIndexConfigurationSchema polymorphic
> ---
>
> Key: IGNITE-15884
> URL: https://issues.apache.org/jira/browse/IGNITE-15884
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> After introducing polymorphic configuration, it is now possible to split
> {{TableIndexConfigurationSchema}} into different sub-schemas based on the
> index type
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15847) Refactoring of TableDescriptor for SQL Extension API
[ https://issues.apache.org/jira/browse/IGNITE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444549#comment-17444549 ] Taras Ledkov commented on IGNITE-15847: --- [~korlov], the patch is OK with me. > Refactoring of TableDescriptor for SQL Extension API > > > Key: IGNITE-15847 > URL: https://issues.apache.org/jira/browse/IGNITE-15847 > Project: Ignite > Issue Type: Sub-task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: calcite, calcite3-required, ignite-3 > > Currently, TableDescriptor contains a link to TableImpl and methods to > convert from tuple to row and vice versa, thus some refactoring is required -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15924) Java thin client: Type name is not cached on client side for OptimizerMarshaller types
[
https://issues.apache.org/jira/browse/IGNITE-15924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-15924:
---
Description:
For JDK marshaller types (for example {{LocalDateTime}} use JDK marshaller)
type name, requested by {{{}typeId{}}}, is not cached correctly.
For example, in this fragment, type name requested twice by thin-client (after
each get request), but should be cached after the first request:
{code:java}
try (Ignite srv = Ignition.start(Config.getServerConfiguration())) {
srv.cache(Config.DEFAULT_CACHE_NAME).put(1, LocalDateTime.now());
try (IgniteClient client = Ignition.startClient(new
ClientConfiguration().setAddresses(Config.SERVER))) {
client.cache(Config.DEFAULT_CACHE_NAME).get(1);
client.cache(Config.DEFAULT_CACHE_NAME).get(1);
}
} {code}
was:
For JDK marshaller types (for example {{LocalDateTime}} use JDK marshaller)
requested by {{typeId}} type name not cached correctly.
For example, in this fragment, type name requested twice by thin-client (after
each get request), but should be cached after the first request:
{code:java}
try (Ignite srv = Ignition.start(Config.getServerConfiguration())) {
srv.cache(Config.DEFAULT_CACHE_NAME).put(1, LocalDateTime.now());
try (IgniteClient client = Ignition.startClient(new
ClientConfiguration().setAddresses(Config.SERVER))) {
client.cache(Config.DEFAULT_CACHE_NAME).get(1);
client.cache(Config.DEFAULT_CACHE_NAME).get(1);
}
} {code}
> Java thin client: Type name is not cached on client side for
> OptimizerMarshaller types
> --
>
> Key: IGNITE-15924
> URL: https://issues.apache.org/jira/browse/IGNITE-15924
> Project: Ignite
> Issue Type: Bug
>Reporter: Alex Plehanov
>Priority: Major
> Labels: ise
>
> For JDK marshaller types (for example {{LocalDateTime}} use JDK marshaller)
> type name, requested by {{{}typeId{}}}, is not cached correctly.
> For example, in this fragment, type name requested twice by thin-client
> (after each get request), but should be cached after the first request:
> {code:java}
> try (Ignite srv = Ignition.start(Config.getServerConfiguration())) {
> srv.cache(Config.DEFAULT_CACHE_NAME).put(1, LocalDateTime.now());
> try (IgniteClient client = Ignition.startClient(new
> ClientConfiguration().setAddresses(Config.SERVER))) {
> client.cache(Config.DEFAULT_CACHE_NAME).get(1);
> client.cache(Config.DEFAULT_CACHE_NAME).get(1);
> }
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15528) JRaft creates at least 4 threads for every raft group on a leader
[
https://issues.apache.org/jira/browse/IGNITE-15528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444551#comment-17444551
]
Alexey Scherbakov commented on IGNITE-15528:
I've reverted a change which removes assertion in
org.apache.ignite.internal.raft.server.impl.JraftServerImpl#stop
> JRaft creates at least 4 threads for every raft group on a leader
> --
>
> Key: IGNITE-15528
> URL: https://issues.apache.org/jira/browse/IGNITE-15528
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Alexey Scherbakov
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> When we create a raft group on a leader, jraft creates at least 4 threads for
> every raft group: one thread for {{electionTimer}}, {{voteTimer}},
> {{stepDownTimer}}, and {{snapshotTimer}}. To be more precise, every timer is
> an instance of {{HashedWheelTimer}}, which creates one thread:
> {code:java}
> private final Worker worker = new Worker();
> ...
> workerThread = threadFactory.newThread(worker);
> {code}
> This fact leads to restrictions on the number of partitions that might be
> created, as far as every partition is associated with a raft group. For
> example, one table with 1024 partitions leads to at least 4096 threads on a
> single node.
> Changing {{HashedWheelTimer}} to {{DefaultTimer}} with shared pool won't make
> any sense, as far as the workload of the shared executor likely will lead to
> instability of cluster because threads are timer threads (election timer, for
> example).
> A possible solution is to implement batched handling of raft groups requests,
> like {{appendEntriesRequest}}. In this approach, timers could be shared by
> raft groups. There is an issue in original JRaft repo with some close ideas
> https://github.com/sofastack/sofa-jraft/issues/672
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-15897) [Ignite 3] ServiceLoader integration into configuration
[
https://issues.apache.org/jira/browse/IGNITE-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy reassigned IGNITE-15897:
--
Assignee: Roman Puchkovskiy
> [Ignite 3] ServiceLoader integration into configuration
> ---
>
> Key: IGNITE-15897
> URL: https://issues.apache.org/jira/browse/IGNITE-15897
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha3
>Reporter: Ivan Bessonov
>Assignee: Roman Puchkovskiy
>Priority: Major
> Labels: iep-55, ignite-3
> Fix For: 3.0.0-alpha4
>
>
> In order to decouple modules and provide more flexibility, it would be
> helpful to provide certain extension points using standard ServiceLoader Java
> API.
> For example, currently there's an explicit list of configuration roots,
> extensions, validators, etc. in {{org.apache.ignite.internal.app.IgniteImpl}}
> code. This can become a mess and is not extensible.
> New service interface should provide following objects:
> * collection of configuration roots;
> * collection of validators;
> * collection of internal extensions;
> * collection of polymorphic extensions.
> That's probably enough.
> There should be a piece of code in {{runner}} module or somewhere else that
> aggregates this information from all available service loader of given
> interface. Aggregated information can then be used to initialize
> {{{}ConfigurationManager{}}}.
> Local and Distributed roots/extensions should be provided in different
> instances, it's much easier this way for individual developers who will
> implement these services.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15348) Checkstyle should check whitespace after cast token.
[
https://issues.apache.org/jira/browse/IGNITE-15348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444599#comment-17444599
]
Ignite TC Bot commented on IGNITE-15348:
{panel:title=Branch: [pull/9568/head] Base: [master] : Possible Blockers
(94)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272021]]
{color:#d04437}Platform C++ CMake (Linux Clang){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272106]]
{color:#d04437}Cache (Restarts) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272037]]
{color:#d04437}Service Grid (Legacy Mode){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272103]]
{color:#d04437}Cache 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272042]]
{color:#d04437}SPI{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272091]]
{color:#d04437}Service Grid{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272082]]
{color:#d04437}RDD{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272084]]
{color:#d04437}Control Utility{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272059]]
{color:#d04437}Cache 9{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272053]]
{color:#d04437}Basic 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272027]]
{color:#d04437}JDBC Driver{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272070]]
{color:#d04437}Continuous Query 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272057]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272094]]
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272096]]
{color:#d04437}PDS (Compatibility){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272075]]
{color:#d04437}Control Utility (Zookeeper){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272058]]
{color:#d04437}Continuous Query 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272055]]
{color:#d04437}Thin Client: Java{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272079]]
{color:#d04437}Scala (Examples){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272102]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272014]]
{color:#d04437}Binary Objects{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272026]]
{color:#d04437}Cache 6{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272045]]
{color:#d04437}PDS 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272086]]
{color:#d04437}Basic 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272028]]
{color:#d04437}Thin client: Node.js{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272016]]
{color:#d04437}Cache 7{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272046]]
{color:#d04437}Web Sessions{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272092]]
{color:#d04437}Continuous Query 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272056]]
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272052]]
{color:#d04437}Examples{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272104]]
{color:#d04437}PDS (Indexing){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272088]]
{color:#d04437}Data Structures{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272062]]
{color:#d04437}Cache (Failover SSL){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272031]]
{color:#d04437}Cache 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272043]]
{color:#d04437}Cache (Failover) 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272034]]
{color:#d04437}Cache 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272041]]
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6272097]]
{color:#d04437}Queries 2{color} [[tests 0
CANCELLE
[jira] [Assigned] (IGNITE-15924) Java thin client: Type name is not cached on client side for OptimizerMarshaller types
[
https://issues.apache.org/jira/browse/IGNITE-15924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov reassigned IGNITE-15924:
Assignee: Nikolay Izhikov
> Java thin client: Type name is not cached on client side for
> OptimizerMarshaller types
> --
>
> Key: IGNITE-15924
> URL: https://issues.apache.org/jira/browse/IGNITE-15924
> Project: Ignite
> Issue Type: Bug
>Reporter: Alex Plehanov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: ise
>
> For JDK marshaller types (for example {{LocalDateTime}} use JDK marshaller)
> type name, requested by {{{}typeId{}}}, is not cached correctly.
> For example, in this fragment, type name requested twice by thin-client
> (after each get request), but should be cached after the first request:
> {code:java}
> try (Ignite srv = Ignition.start(Config.getServerConfiguration())) {
> srv.cache(Config.DEFAULT_CACHE_NAME).put(1, LocalDateTime.now());
> try (IgniteClient client = Ignition.startClient(new
> ClientConfiguration().setAddresses(Config.SERVER))) {
> client.cache(Config.DEFAULT_CACHE_NAME).get(1);
> client.cache(Config.DEFAULT_CACHE_NAME).get(1);
> }
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-15925) Ignite 3: Make thin client more robust
Igor Sapego created IGNITE-15925: Summary: Ignite 3: Make thin client more robust Key: IGNITE-15925 URL: https://issues.apache.org/jira/browse/IGNITE-15925 Project: Ignite Issue Type: Improvement Components: thin client Affects Versions: 3.0.0-alpha3 Reporter: Igor Sapego Assignee: Igor Sapego There is a ticket (IGNITE-15921) for Ignite 2.x saying about vulnerability of client protocol to OOM attacks. We should take those issues into account when developing Ignite 3. Possibly, we need to conduct additional research here about protocols vulnerabilities and methods of defense. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-14294) .NET: ClientServerCompatibilityTest is flaky
[
https://issues.apache.org/jira/browse/IGNITE-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444609#comment-17444609
]
Ignite TC Bot commented on IGNITE-14294:
{panel:title=Branch: [pull/9567/head] Base: [master] : Possible Blockers
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6271911]]
{color:#d04437}Cache (Restarts) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271927]]
* IgniteCacheRestartTestSuite:
IgniteCacheCreateRestartSelfTest.testStopOriginatingNode - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271932]]
* IgniteCacheTestSuite2:
IgniteCacheServerNodeConcurrentStart.testConcurrentStart - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271981]]
* IgniteSpiTestSuite: TcpCommunicationSpiDropNodesTest.testOneNode - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271984]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryConcurrentStartAndStartStopTest.testMultipleClusters - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271986]]
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryLongP2PTest.testMvccTxReplicatedClient - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271978]]
* IgnitePdsWithIndexingTestSuite:
IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes - Test has low fail rate in
base branch 0,0% and is not flaky
* IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverIncompletedIndex - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271914]]
* IgniteStandByClusterSuite:
IgniteClusterActivateDeactivateTest.testDeactivateFromReadOnlySimple_5_Servers_5_Clients_FromClient
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9567/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=6271998&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: ClientServerCompatibilityTest is flaky
>
>
> Key: IGNITE-14294
> URL: https://issues.apache.org/jira/browse/IGNITE-14294
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ClientServerCompatibilityTest fails for two reasons:
> 1. {{Failed to establish Ignite thin client connection, examine inner
> exceptions for details. (Connection refused 127.0.0.1:10892)}} - check
> process output, is there a different port used for the client connector?
> 2. {{GridUnsafe cannot access class jdk.internal.misc.SharedSecrets}} - we
> should pass {{--add-exports}} and {{--illegal-access=permit}} JVM options
> when running on Java9+, see {{Jvm.IsJava9}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15925) Ignite 3: Make thin client protocol more robust
[ https://issues.apache.org/jira/browse/IGNITE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-15925: - Summary: Ignite 3: Make thin client protocol more robust (was: Ignite 3: Make thin client more robust) > Ignite 3: Make thin client protocol more robust > --- > > Key: IGNITE-15925 > URL: https://issues.apache.org/jira/browse/IGNITE-15925 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > > There is a ticket (IGNITE-15921) for Ignite 2.x saying about vulnerability of > client protocol to OOM attacks. We should take those issues into account when > developing Ignite 3. Possibly, we need to conduct additional research here > about protocols vulnerabilities and methods of defense. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-14807) Calcite. Eliminate usage of deprecated api within Ignite rels and rules
[ https://issues.apache.org/jira/browse/IGNITE-14807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-14807: -- Labels: calcite (was: calcite calcite3-required) > Calcite. Eliminate usage of deprecated api within Ignite rels and rules > --- > > Key: IGNITE-14807 > URL: https://issues.apache.org/jira/browse/IGNITE-14807 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Ivan Daschinsky >Priority: Major > Labels: calcite > Time Spent: 50m > Remaining Estimate: 0h > > Affected rels: > * AbstractIgniteJoin > * IgniteProject > * AbstractIgniteConverterRule > * FilterScanMergeRule -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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 ] Taras Ledkov updated IGNITE-14594: -- Labels: calcite (was: calcite3-required) > 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 >Assignee: Pavel Pereslegin >Priority: Minor > Labels: calcite > Time Spent: 1h 10m > Remaining Estimate: 0h > > 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.20.1#820001)
[jira] [Updated] (IGNITE-13159) Calcite integration. Decorrelator support SOME and ALL operator.
[
https://issues.apache.org/jira/browse/IGNITE-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-13159:
--
Labels: calcite (was: calcite3-required)
> Calcite integration. Decorrelator support SOME and ALL operator.
>
>
> Key: IGNITE-13159
> URL: https://issues.apache.org/jira/browse/IGNITE-13159
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Assignee: Evgeny Stanilovsky
>Priority: Minor
> Labels: calcite
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Now Calcite SqlToRelConverter throws an exception if found a subquery in
> ALL\SOME operator. See SubqueryRewriteRuleTest.testNonAllToSemiAntiJoinRule
> test and find stack trace below.
> We have to either set flag "expand=false" and implement LogicalCorrelate
> converter
> or some rules to overcome the issue.
> However, setting flag "expand=false" makes query pass, but with wrong join
> type (left and inner instead of anti) and moreover it brakes other queries
> due to weird decorrelator behavior. Possibly there is bug in Calcite.
> {code:java}
> Caused by: java.lang.RuntimeException: ALL is only supported if expand =
> falseCaused by: java.lang.RuntimeException: ALL is only supported if expand =
> false at
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.convertExpression(SqlToRelConverter.java:4814)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertWhere(SqlToRelConverter.java:1016)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelectImpl(SqlToRelConverter.java:662)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelect(SqlToRelConverter.java:640)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3384)
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:566)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.rel(IgnitePlanner.java:203)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.optimize(ExecutionServiceImpl.java:618)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareExplain(ExecutionServiceImpl.java:644)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:573)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepare0(ExecutionServiceImpl.java:531)
> ... 16 more
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14589) Calcite engine. Numerous problem with type Decimal
[
https://issues.apache.org/jira/browse/IGNITE-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14589:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. Numerous problem with type Decimal
> --
>
> Key: IGNITE-14589
> URL: https://issues.apache.org/jira/browse/IGNITE-14589
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Vladimir Ermakov
>Priority: Major
> Labels: calcite
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> There are numerous problem with a decimal types:
> * leading and trailing zeros are truncated when converting to string
> * casting to precise scale is not working( {{select cast('0.01' as
> decimal(10, 1)) * 10}} returns 0.1 instead of 0)
> Affected tests:
> {{src/test/sql/types/decimal}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15127) Calcite. Investigate CoreRules.JOIN_COMMUTE[_OUTER] usage.
[ https://issues.apache.org/jira/browse/IGNITE-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-15127: -- Labels: calcite (was: calcite calcite3-required ignite-3) > Calcite. Investigate CoreRules.JOIN_COMMUTE[_OUTER] usage. > -- > > Key: IGNITE-15127 > URL: https://issues.apache.org/jira/browse/IGNITE-15127 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: calcite > Time Spent: 2.5h > Remaining Estimate: 0h > > Looks like join commute rule can dramatically reduce some join costs, > investigation and tests are required. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-14816) Calcite engine. Change TreeMap in sorted IndexSpoolNode to ArrayList
[
https://issues.apache.org/jira/browse/IGNITE-14816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14816:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. Change TreeMap in sorted IndexSpoolNode to ArrayList
>
>
> Key: IGNITE-14816
> URL: https://issues.apache.org/jira/browse/IGNITE-14816
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Pavel Pereslegin
>Priority: Minor
> Labels: calcite
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{IgniteSortedIndexSpool}} assumes that the underlying input is already
> sorted, but the execution node creates {{TreeMap}} to find the rows (see
> {{IndexSpoolNode#createTreeSpool}}). This {{TreeMap}} can be replaced with
> {{ArrayList}} and binary search with the same efficiency for searching and
> lower costs for inserting data.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15203) Calcite. Extract Filter and Project related rules to separate HEP phase
[
https://issues.apache.org/jira/browse/IGNITE-15203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15203:
--
Labels: calcite (was: calcite3-required)
> Calcite. Extract Filter and Project related rules to separate HEP phase
> ---
>
> Key: IGNITE-15203
> URL: https://issues.apache.org/jira/browse/IGNITE-15203
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: calcite
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Currently the query like follow requires too mush time to optimise (> 5
> minutes on my laptop):
> {code:java}
> select * from t1 inner join t2 on t1.id = t2.id where t1.val1 > 0 or t1.val2
> > 10
> {code}
> The reason is that every step of push down of the filter creates one more
> valid plan, that in conjunction with OrToUnion rule and all those Join's
> traits propagation significally boosts the search space.
> We could take an advantage of heuristic planner here to push down filters as
> close to the leaf as possible, whereas pruning all alternative plans.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-13136) Calcite integration. Improve join predicate testing.
[
https://issues.apache.org/jira/browse/IGNITE-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-13136:
--
Labels: calcite ignite-3 (was: calcite calcite3-required ignite-3)
> Calcite integration. Improve join predicate testing.
>
>
> Key: IGNITE-13136
> URL: https://issues.apache.org/jira/browse/IGNITE-13136
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Roman Kondakov
>Assignee: Evgeny Stanilovsky
>Priority: Minor
> Labels: calcite, ignite-3
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> Currently we have to merge joining rows in order to test a join predicate:
> {code:java}
> Row row = handler.concat(left, rightMaterialized.get(rightIdx++));
> if (!cond.test(row))
> continue;
> {code}
> it results in unconditional building a joined row even if it will not be
> emitted to downstream further. To avoid extra GC pressure we need to test the
> join predicate before joining rows:
> {code:java}
> if (!cond.test(left, right))
> continue;
> Row row = handler.concat(left, right);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15031) Calcite engine. Parser fails on REPLACE function
[
https://issues.apache.org/jira/browse/IGNITE-15031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15031:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. Parser fails on REPLACE function
>
>
> Key: IGNITE-15031
> URL: https://issues.apache.org/jira/browse/IGNITE-15031
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{REPLACE}} function is declared at the calcite engine
> ({{SqlStdOperatorTable#REPLACE}})
> but parser fails on the query:
> {{SELECT REPLACE('A', 'B' 'C')}}
> with error: {{Encountered "" at line 1, column 8.}}
> Tests:
> {{function/string/test_replace.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14749) Calcite engine. Create table and use of this table in one statement doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-14749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14749:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. Create table and use of this table in one statement doesn't
> work
>
>
> Key: IGNITE-14749
> URL: https://issues.apache.org/jira/browse/IGNITE-14749
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
>
> If a statement consists of substatements and a table is created in one of
> these substatement and then used by another, preparation of this statement
> failed. For example:
> {code:java}
> executeSql("CREATE TABLE test (val int); INSERT INTO test VALUES (0);");
> {code}
> Failed with:
>
> {noformat}
> Caused by: org.apache.calcite.tools.ValidationException:
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 42 to
> line 1, column 45: Object 'TEST' not found
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.validate(IgnitePlanner.java:180)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareDml(ExecutionServiceImpl.java:597)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:561)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:520)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14808) Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
[
https://issues.apache.org/jira/browse/IGNITE-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14808:
--
Labels: calcite (was: calcite calcite3-required)
> Calcite. RIGHT|FULL Join operations are lost nulls sort ordering.
> -
>
> Key: IGNITE-14808
> URL: https://issues.apache.org/jira/browse/IGNITE-14808
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: calcite
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> queries like
> {noformat}
> FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
> NULLS FIRST
> {noformat} will bring to erroneous results. Also some tests from /sql/join*
> have no ordering thus results are not equal to pattern.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14593) Calcite. Support bang-equal operator
[
https://issues.apache.org/jira/browse/IGNITE-14593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14593:
--
Labels: calcite (was: calcite calcite3-required)
> Calcite. Support bang-equal operator
>
>
> Key: IGNITE-14593
> URL: https://issues.apache.org/jira/browse/IGNITE-14593
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Vladimir Steshin
>Priority: Minor
> Labels: calcite
>
> Looks like it would be helpful to support "!=" syntax, i.e. :
> {code:java}
> UPDATE test SET a=7 WHERE id != 3
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14973) Calcite engine. IgniteLimit is pushed down under Exchange invalid
[
https://issues.apache.org/jira/browse/IGNITE-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14973:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. IgniteLimit is pushed down under Exchange invalid
> -
>
> Key: IGNITE-14973
> URL: https://issues.apache.org/jira/browse/IGNITE-14973
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In complex cases {{IgniteLimit}} is pushed down under Exchange node.
> *Steps to reproduce:*
> {code}
> CREATE TABLE test (a VARCHAR);
> INSERT INTO test VALUES ('aaa'), ('bbb'), ('ccc');
> CREATE TABLE test2 (a VARCHAR, b VARCHAR);
> INSERT INTO test2 VALUES ('blabla', 'b'), ('blabla2', 'c'), ('blabla3', 'd');
> SELECT NULLIF(NULLIF ((SELECT a FROM test ORDER BY a LIMIT 1 offset 1), a),
> b) FROM test2;
> {code}
> *Plan:*
> {code}
> IgniteProject(EXPR$0=[CASE(=(CASE(=($4, $2), null:VARCHAR CHARACTER SET
> "UTF-8", $5), $3), null:VARCHAR CHARACTER SET "UTF-8", CASE(=($4, $2),
> null:VARCHAR CHARACTER SET "UTF-8", $6))])
> IgniteNestedLoopJoin(condition=[true], joinType=[left])
> IgniteNestedLoopJoin(condition=[true], joinType=[left])
> IgniteNestedLoopJoin(condition=[true], joinType=[left])
> IgniteExchange(distribution=[single])
> IgniteIndexScan(table=[[PUBLIC, TEST2]], index=[_key_PK])
> IgniteExchange(distribution=[single])
> IgniteLimit(offset=[1], fetch=[1])
> IgniteIndexScan(table=[[PUBLIC, TEST]], index=[_key_PK],
> requiredColumns=[{2}])
> IgniteExchange(distribution=[single])
> IgniteLimit(offset=[1], fetch=[1])
> IgniteIndexScan(table=[[PUBLIC, TEST]], index=[_key_PK],
> requiredColumns=[{2}])
> IgniteExchange(distribution=[single])
> IgniteLimit(offset=[1], fetch=[1])
> IgniteIndexScan(table=[[PUBLIC, TEST]], index=[_key_PK],
> requiredColumns=[{2}])
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-14597) Calcite engine. Exception when using FIRST
[
https://issues.apache.org/jira/browse/IGNITE-14597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14597:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. Exception when using FIRST
> --
>
> Key: IGNITE-14597
> URL: https://issues.apache.org/jira/browse/IGNITE-14597
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Exception is thrown when running a query {{SELECT FIRST(NULL::DECIMAL)}}
> {code:java}
> class org.apache.ignite.IgniteException: Error at:
> decimal_aggregates.test:10. sql: SELECT FIRST(NULL::DECIMAL)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner$Query.execute(SqlScriptRunner.java:518)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner.run(SqlScriptRunner.java:93)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.ScriptTestRunner$1.run(ScriptTestRunner.java:219)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> plan query.
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:541)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:398)
> at
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:246)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner.sql(SqlScriptRunner.java:111)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner.access$600(SqlScriptRunner.java:51)
> at
> org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner$Query.execute(SqlScriptRunner.java:513)
> ... 3 more
> Caused by: org.apache.calcite.runtime.CalciteContextException: From line 1,
> column 8 to line 1, column 27: Function 'FIRST(NULL :: DECIMAL, 0)' can only
> be used in MATCH_RECOGNIZE
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:467)
> at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:883)
> at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:868)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError(SqlValidatorImpl.java:5043)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateCall(SqlValidatorImpl.java:5574)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.validateCall(IgniteSqlValidator.java:230)
> at org.apache.calcite.sql.SqlCall.validate(SqlCall.java:116)
> at org.apache.calcite.sql.SqlNode.validateExpr(SqlNode.java:273)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateExpr(SqlValidatorImpl.java:4259)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelectList(SqlValidatorImpl.java:4234)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelect(SqlValidatorImpl.java:3474)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.validateSelect(IgniteSqlValidator.java:176)
> at
> org.apache.calcite.sql.validate.SelectNamespace.validateImpl(SelectNamespace.java:60)
> at
> org.apache.calcite.sql.validate.AbstractNamespace.validate(AbstractNamespace.java:84)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace(SqlValidatorImpl.java:1067)
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.validateNamespace(IgniteSqlValidator.java:190)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery(SqlValidatorImpl.java:1041)
> at org.apache.calcite.sql.SqlSelect.validate(SqlSelect.java:232)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validateScopedExpression(SqlValidatorImpl.java:1016)
> at
> org.apache.calcite.sql.validate.SqlValidatorImpl.validate(SqlValidatorImpl.java:724)
>
[jira] [Updated] (IGNITE-15002) Calcite engine. String functions fail on NULL constant
[
https://issues.apache.org/jira/browse/IGNITE-15002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15002:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. String functions fail on NULL constant
> --
>
> Key: IGNITE-15002
> URL: https://issues.apache.org/jira/browse/IGNITE-15002
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The query
> {{select UPPER(NULL), LOWER(NULL)}}
> Functions:
> - UPPER
> - LOWER
> - LEFT
> - RIGHT
> - REPEAT
> - REVERSE
> - SUBSTRING
> fails with exception:
> {code}
> java.lang.RuntimeException: while resolving method 'valueOf[class
> java.lang.String]' in class class java.lang.Void
> at org.apache.calcite.linq4j.tree.Types.lookupMethod(Types.java:323)
> at org.apache.calcite.linq4j.tree.Expressions.call(Expressions.java:445)
> at org.apache.calcite.linq4j.tree.Expressions.call(Expressions.java:457)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ConverterUtils.convert(ConverterUtils.java:229)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ConverterUtils.convert(ConverterUtils.java:175)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexImpTable$AbstractRexCallImplementor.genValueStatement(RexImpTable.java:1962)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexImpTable$AbstractRexCallImplementor.implement(RexImpTable.java:1909)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.visitCall(RexToLixTranslator.java:978)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.visitCall(RexToLixTranslator.java:78)
> at org.apache.calcite.rex.RexCall.accept(RexCall.java:174)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.visitLocalRef(RexToLixTranslator.java:873)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.visitLocalRef(RexToLixTranslator.java:78)
> at org.apache.calcite.rex.RexLocalRef.accept(RexLocalRef.java:75)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.translate(RexToLixTranslator.java:204)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.translate(RexToLixTranslator.java:197)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.translateList(RexToLixTranslator.java:750)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexToLixTranslator.translateProjects(RexToLixTranslator.java:178)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl.compile(ExpressionFactoryImpl.java:300)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl.lambda$scalar$4(ExpressionFactoryImpl.java:263)
> at
> java.base/java.util.concurrent.ConcurrentMap.computeIfAbsent(ConcurrentMap.java:330)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl.scalar(ExpressionFactoryImpl.java:263)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl.project(ExpressionFactoryImpl.java:220)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.LogicalRelImplementor.visit(LogicalRelImplementor.java:202)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.LogicalRelImplementor.visit(LogicalRelImplementor.java:109)
> at
> org.apache.ignite.internal.processors.query.calcite.rel.IgniteProject.accept(IgniteProject.java:89)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.LogicalRelImplementor.visit(LogicalRelImplementor.java:657)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.LogicalRelImplementor.go(LogicalRelImplementor.java:672)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:717)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executePlan(ExecutionServiceImpl.java:657)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executePlans(ExecutionServiceImpl.java:410)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:392)
> at
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProces
[jira] [Updated] (IGNITE-14954) Calcite engine. MONTHNAME, DAYNAME functions fail due to null locale
[
https://issues.apache.org/jira/browse/IGNITE-14954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14954:
--
Labels: calcite (was: calcite3-required)
> Calcite engine. MONTHNAME, DAYNAME functions fail due to null locale
>
>
> Key: IGNITE-14954
> URL: https://issues.apache.org/jira/browse/IGNITE-14954
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The query
> {{SELECT MONTHNAME(CAST('1992-05-31' AS DATE));}}
> fails with exception
> {code}
> class org.apache.ignite.IgniteException: Unexpected exception
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:244)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:68)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.NullPointerException: locale
> at java.base/java.util.Objects.requireNonNull(Objects.java:246)
> at
> java.base/java.time.format.DateTimeFormatter.(DateTimeFormatter.java:1421)
> at
> java.base/java.time.format.DateTimeFormatter.withLocale(DateTimeFormatter.java:1463)
> at
> org.apache.calcite.runtime.SqlFunctions.monthNameWithDate(SqlFunctions.java:2391)
> at SC.execute(Unknown Source)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl$ProjectImpl.apply(ExpressionFactoryImpl.java:387)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ProjectNode.push(ProjectNode.java:63)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:107)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:239)
> ... 4 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-14354) Regression when using SELECT (EXISTS (...))
[
https://issues.apache.org/jira/browse/IGNITE-14354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich reassigned IGNITE-14354:
--
Assignee: (was: Sergey Dorozhkin)
> Regression when using SELECT (EXISTS (...))
> ---
>
> Key: IGNITE-14354
> URL: https://issues.apache.org/jira/browse/IGNITE-14354
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
>Reporter: Lukas Eder
>Priority: Major
>
> This worked as expected in 2.9.1:
>
> {code:java}
> CREATE TABLE t (i int PRIMARY KEY, j int);
> SELECT (EXISTS (SELECT 1 FROM t WHERE t.i = 1));
> {code}
> In version 2.10, I'm getting:
> {code:java}
> SQL Error [1001] [42000]: Failed to parse query. Column "EXISTS1" not found;
> SQL statement:
> SELECT
> (EXISTS1)
> FROM SYSTEM_RANGE(1, 1) __Z0
> LEFT OUTER JOIN PUBLIC.T __Z1
> ON __Z1.I = 1 [42122-197]{code}
> The workaround is to project an asterisk:
> {code:java}
> SELECT (EXISTS (SELECT * FROM t WHERE t.i = 1));{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15915) .NET thin: SSL keystore shouldn't be a mandatory parameter
[
https://issues.apache.org/jira/browse/IGNITE-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444643#comment-17444643
]
Ignite TC Bot commented on IGNITE-15915:
{panel:title=Branch: [pull/9566/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6271533]]
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271582]]
* IgniteSpiTestSuite:
TooManyOpenFilesTcpCommunicationSpiTest.testTooManyOpenFilesErr - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271587]]
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryOperationP2PTest.testTxClient - Test has low fail rate in
base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryLongP2PTest.testTxReplicatedClient - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271588]]
* ZookeeperDiscoverySpiTestSuite4: IgniteCachePutRetryAtomicSelfTest.testPutAll
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}SPI (URI Deploy){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271591]]
* IgniteUriDeploymentTestSuite:
GridUriDeploymentMd5CheckSelfTest.testMd5DirectoryCheck - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9566/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Windows){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6272000]]
* {color:#013220}exe: RawSecureSocketTest.TestHandshake(False) - PASSED{color}
* {color:#013220}exe: RawSecureSocketTest.TestHandshake(True) - PASSED{color}
* {color:#013220}exe: ClientConnectionTest.TestSslConnectionWithoutClientAuth -
PASSED{color}
* {color:#013220}exe: ClientConnectionTest.TestSslConnectionWithClientAuth -
PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6271505]]
* {color:#013220}dll: RawSecureSocketTest.TestHandshake(False) - PASSED{color}
* {color:#013220}dll: RawSecureSocketTest.TestHandshake(True) - PASSED{color}
* {color:#013220}dll: ClientConnectionTest.TestSslConnectionWithoutClientAuth -
PASSED{color}
* {color:#013220}dll: ClientConnectionTest.TestSslConnectionWithClientAuth -
PASSED{color}
{color:#8b}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271580]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
BusyExecutorTest.testReactivationCancellableWontStart - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
BusyExecutorTest.testReactivationWontStart - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6271599&buildTypeId=IgniteTests24Java8_RunAll]
> .NET thin: SSL keystore shouldn't be a mandatory parameter
> --
>
> Key: IGNITE-15915
> URL: https://issues.apache.org/jira/browse/IGNITE-15915
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, SslStreamFactory can't be configured without specifying
> client-side certificates.
> This shouldn't be the case - SSL can be used without any certificates on the
> client.
> Workaround:
> {code}
> class SimpleSslStreamFactory : ISslStreamFactory {
> public SslStream Create(Stream stream, string targetHost)
> {
> var sslStream = new SslStream(stream, false, null, null);
> sslStream.AuthenticateAsClient(targetHost);
> return sslStream;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (IGNITE-15915) .NET thin: SSL keystore shouldn't be a mandatory parameter
[ https://issues.apache.org/jira/browse/IGNITE-15915 ]
Pavel Tupitsyn deleted comment on IGNITE-15915:
-
was (Author: ignitetcbot):
{panel:title=Branch: [pull/9566/head] Base: [master] : Possible Blockers
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271512]]
* exe: ClientConnectionTest.TestSslConnectionWithoutClientAuth - History for
base branch is absent.
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6271533]]
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271582]]
* IgniteSpiTestSuite:
TooManyOpenFilesTcpCommunicationSpiTest.testTooManyOpenFilesErr - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271587]]
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryOperationP2PTest.testTxClient - Test has low fail rate in
base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryLongP2PTest.testTxReplicatedClient - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271588]]
* ZookeeperDiscoverySpiTestSuite4: IgniteCachePutRetryAtomicSelfTest.testPutAll
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}SPI (URI Deploy){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271591]]
* IgniteUriDeploymentTestSuite:
GridUriDeploymentMd5CheckSelfTest.testMd5DirectoryCheck - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9566/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Platform .NET (Windows){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6271512]]
* {color:#013220}exe: RawSecureSocketTest.TestHandshake(False) - PASSED{color}
* {color:#013220}exe: RawSecureSocketTest.TestHandshake(True) - PASSED{color}
* {color:#8b}exe: ClientConnectionTest.TestSslConnectionWithoutClientAuth -
FAILED{color}
* {color:#013220}exe: ClientConnectionTest.TestSslConnectionWithClientAuth -
PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6271505]]
* {color:#013220}dll: RawSecureSocketTest.TestHandshake(False) - PASSED{color}
* {color:#013220}dll: RawSecureSocketTest.TestHandshake(True) - PASSED{color}
* {color:#013220}dll: ClientConnectionTest.TestSslConnectionWithoutClientAuth -
PASSED{color}
* {color:#013220}dll: ClientConnectionTest.TestSslConnectionWithClientAuth -
PASSED{color}
{color:#8b}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271580]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
BusyExecutorTest.testReactivationCancellableWontStart - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
BusyExecutorTest.testReactivationWontStart - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6271599&buildTypeId=IgniteTests24Java8_RunAll]
> .NET thin: SSL keystore shouldn't be a mandatory parameter
> --
>
> Key: IGNITE-15915
> URL: https://issues.apache.org/jira/browse/IGNITE-15915
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, SslStreamFactory can't be configured without specifying
> client-side certificates.
> This shouldn't be the case - SSL can be used without any certificates on the
> client.
> Workaround:
> {code}
> class SimpleSslStreamFactory : ISslStreamFactory {
> public SslStream Create(Stream stream, string targetHost)
> {
> var sslStream = new SslStream(stream, false, null, null);
> sslStream.AuthenticateAsClient(targetHost);
> return sslStream;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15915) .NET thin: SSL keystore shouldn't be a mandatory parameter
[
https://issues.apache.org/jira/browse/IGNITE-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444647#comment-17444647
]
Pavel Tupitsyn commented on IGNITE-15915:
-
Merged to master: 52553241ea2986b966610592db180ac2291ea71a
> .NET thin: SSL keystore shouldn't be a mandatory parameter
> --
>
> Key: IGNITE-15915
> URL: https://issues.apache.org/jira/browse/IGNITE-15915
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, SslStreamFactory can't be configured without specifying
> client-side certificates.
> This shouldn't be the case - SSL can be used without any certificates on the
> client.
> Workaround:
> {code}
> class SimpleSslStreamFactory : ISslStreamFactory {
> public SslStream Create(Stream stream, string targetHost)
> {
> var sslStream = new SslStream(stream, false, null, null);
> sslStream.AuthenticateAsClient(targetHost);
> return sslStream;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15915) .NET thin: SSL keystore shouldn't be a mandatory parameter
[
https://issues.apache.org/jira/browse/IGNITE-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15915:
Fix Version/s: 2.12
> .NET thin: SSL keystore shouldn't be a mandatory parameter
> --
>
> Key: IGNITE-15915
> URL: https://issues.apache.org/jira/browse/IGNITE-15915
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.12, 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, SslStreamFactory can't be configured without specifying
> client-side certificates.
> This shouldn't be the case - SSL can be used without any certificates on the
> client.
> Workaround:
> {code}
> class SimpleSslStreamFactory : ISslStreamFactory {
> public SslStream Create(Stream stream, string targetHost)
> {
> var sslStream = new SslStream(stream, false, null, null);
> sslStream.AuthenticateAsClient(targetHost);
> return sslStream;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15915) .NET thin: SSL keystore shouldn't be a mandatory parameter
[
https://issues.apache.org/jira/browse/IGNITE-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444648#comment-17444648
]
Pavel Tupitsyn commented on IGNITE-15915:
-
Cherry-picked to ignite-2.12: 22ff78d80c9c487cf904854a0e435960a4b0d836
> .NET thin: SSL keystore shouldn't be a mandatory parameter
> --
>
> Key: IGNITE-15915
> URL: https://issues.apache.org/jira/browse/IGNITE-15915
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.12, 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, SslStreamFactory can't be configured without specifying
> client-side certificates.
> This shouldn't be the case - SSL can be used without any certificates on the
> client.
> Workaround:
> {code}
> class SimpleSslStreamFactory : ISslStreamFactory {
> public SslStream Create(Stream stream, string targetHost)
> {
> var sslStream = new SslStream(stream, false, null, null);
> sslStream.AuthenticateAsClient(targetHost);
> return sslStream;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15725) Need to define scenarios related to data rebalancing and identifies possible corner cases
[ https://issues.apache.org/jira/browse/IGNITE-15725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15725: - Epic Link: IGNITE-14209 > Need to define scenarios related to data rebalancing and identifies possible > corner cases > - > > Key: IGNITE-15725 > URL: https://issues.apache.org/jira/browse/IGNITE-15725 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > Need to define scenarios that may lead to data rebalancing. The obvious ones > are joining nodes to the cluster and leaving it. > Also, corner cases should be addressed. For example, how the cluster should > behave when the replica factor is 1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-15836) Refactoring of plan serialization
[ https://issues.apache.org/jira/browse/IGNITE-15836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov resolved IGNITE-15836. --- Assignee: Konstantin Orlov Resolution: Fixed Fixed by IGNITE-15833 > Refactoring of plan serialization > - > > Key: IGNITE-15836 > URL: https://issues.apache.org/jira/browse/IGNITE-15836 > Project: Ignite > Issue Type: Sub-task >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Currently all implementations of IgniteRel interface uses it's class' simple > name as name of the type in serialized form. The problem arises when we try > to deserialize the node. All simple names will be looked in a statically > predifined packages. > We need to provide a way to properly serialize and deserialize user provided > relational nodes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15437) .NET: Thin 3.0: NuGet Multitargeting
[ https://issues.apache.org/jira/browse/IGNITE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-15437: - Priority: Major (was: Blocker) > .NET: Thin 3.0: NuGet Multitargeting > > > Key: IGNITE-15437 > URL: https://issues.apache.org/jira/browse/IGNITE-15437 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Priority: Major > Labels: .NET, iep-78, ignite-3 > Fix For: 3.0 > > > Make a decision on supported .NET versions before the *final release of > Ignite 3.0*, and set up NuGet multitargeting accordingly. > Per IEP-78, we target only netstandard2.1 while in pre-release stage, and > this should be reviewed. > https://cwiki.apache.org/confluence/display/IGNITE/IEP-78+.NET+Thin+Client -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15917) StatisticsViewsPersistenceTest.testEnforceStatisticValues
[
https://issues.apache.org/jira/browse/IGNITE-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444683#comment-17444683
]
Ignite TC Bot commented on IGNITE-15917:
{panel:title=Branch: [pull/9563/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9563/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=6270884&buildTypeId=IgniteTests24Java8_RunAll]
> StatisticsViewsPersistenceTest.testEnforceStatisticValues
> -
>
> Key: IGNITE-15917
> URL: https://issues.apache.org/jira/browse/IGNITE-15917
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> StatisticsViewsPersistenceTest.testEnforceStatisticValues may fail due to
> timeout.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (IGNITE-15917) StatisticsViewsPersistenceTest.testEnforceStatisticValues
[ https://issues.apache.org/jira/browse/IGNITE-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak closed IGNITE-15917. - Ignite Flags: (was: Docs Required,Release Notes Required) > StatisticsViewsPersistenceTest.testEnforceStatisticValues > - > > Key: IGNITE-15917 > URL: https://issues.apache.org/jira/browse/IGNITE-15917 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Trivial > Time Spent: 20m > Remaining Estimate: 0h > > StatisticsViewsPersistenceTest.testEnforceStatisticValues may fail due to > timeout. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-14294) .NET: ClientServerCompatibilityTest is flaky
[
https://issues.apache.org/jira/browse/IGNITE-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444738#comment-17444738
]
Ignite TC Bot commented on IGNITE-14294:
{panel:title=Branch: [pull/9567/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6272780]]
* IgniteSpiTestSuite:
GridRoundRobinLoadBalancingNotPerTaskMultithreadedSelfTest.testMultipleTaskSessionsMultithreaded
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=6272772]]
* dll:
ContinuousQueryTest.TestContinuousQueryWithJavaFilterReceivesOnlyMatchingEvents
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6272782]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryClientDisconnectTest.testDisconnectOnServersLeft_5 - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9567/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=6271998&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: ClientServerCompatibilityTest is flaky
>
>
> Key: IGNITE-14294
> URL: https://issues.apache.org/jira/browse/IGNITE-14294
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ClientServerCompatibilityTest fails for two reasons:
> 1. {{Failed to establish Ignite thin client connection, examine inner
> exceptions for details. (Connection refused 127.0.0.1:10892)}} - check
> process output, is there a different port used for the client connector?
> 2. {{GridUnsafe cannot access class jdk.internal.misc.SharedSecrets}} - we
> should pass {{--add-exports}} and {{--illegal-access=permit}} JVM options
> when running on Java9+, see {{Jvm.IsJava9}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (IGNITE-14294) .NET: ClientServerCompatibilityTest is flaky
[ https://issues.apache.org/jira/browse/IGNITE-14294 ]
Pavel Tupitsyn deleted comment on IGNITE-14294:
-
was (Author: ignitetcbot):
{panel:title=Branch: [pull/9567/head] Base: [master] : Possible Blockers
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6271911]]
{color:#d04437}Cache (Restarts) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271927]]
* IgniteCacheRestartTestSuite:
IgniteCacheCreateRestartSelfTest.testStopOriginatingNode - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271932]]
* IgniteCacheTestSuite2:
IgniteCacheServerNodeConcurrentStart.testConcurrentStart - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271981]]
* IgniteSpiTestSuite: TcpCommunicationSpiDropNodesTest.testOneNode - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271984]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryConcurrentStartAndStartStopTest.testMultipleClusters - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271986]]
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryLongP2PTest.testMvccTxReplicatedClient - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6271978]]
* IgnitePdsWithIndexingTestSuite:
IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes - Test has low fail rate in
base branch 0,0% and is not flaky
* IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverIncompletedIndex - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6271914]]
* IgniteStandByClusterSuite:
IgniteClusterActivateDeactivateTest.testDeactivateFromReadOnlySimple_5_Servers_5_Clients_FromClient
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9567/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=6271998&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: ClientServerCompatibilityTest is flaky
>
>
> Key: IGNITE-14294
> URL: https://issues.apache.org/jira/browse/IGNITE-14294
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ClientServerCompatibilityTest fails for two reasons:
> 1. {{Failed to establish Ignite thin client connection, examine inner
> exceptions for details. (Connection refused 127.0.0.1:10892)}} - check
> process output, is there a different port used for the client connector?
> 2. {{GridUnsafe cannot access class jdk.internal.misc.SharedSecrets}} - we
> should pass {{--add-exports}} and {{--illegal-access=permit}} JVM options
> when running on Java9+, see {{Jvm.IsJava9}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-14294) .NET: ClientServerCompatibilityTest is flaky
[
https://issues.apache.org/jira/browse/IGNITE-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444745#comment-17444745
]
Igor Sapego commented on IGNITE-14294:
--
[~ptupitsyn] looks good to me.
> .NET: ClientServerCompatibilityTest is flaky
>
>
> Key: IGNITE-14294
> URL: https://issues.apache.org/jira/browse/IGNITE-14294
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ClientServerCompatibilityTest fails for two reasons:
> 1. {{Failed to establish Ignite thin client connection, examine inner
> exceptions for details. (Connection refused 127.0.0.1:10892)}} - check
> process output, is there a different port used for the client connector?
> 2. {{GridUnsafe cannot access class jdk.internal.misc.SharedSecrets}} - we
> should pass {{--add-exports}} and {{--illegal-access=permit}} JVM options
> when running on Java9+, see {{Jvm.IsJava9}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (IGNITE-15844) BusyExecutor allow task be executed after deactive/activate.
[ https://issues.apache.org/jira/browse/IGNITE-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak closed IGNITE-15844. - Ignite Flags: (was: Docs Required,Release Notes Required) > BusyExecutor allow task be executed after deactive/activate. > > > Key: IGNITE-15844 > URL: https://issues.apache.org/jira/browse/IGNITE-15844 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Major > Fix For: 2.13 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > Now BusyExecutor allows to schedule and execute task after deactivation if > deactivate/activate completes while task stays in queue. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-14294) .NET: ClientServerCompatibilityTest is flaky
[
https://issues.apache.org/jira/browse/IGNITE-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444971#comment-17444971
]
Pavel Tupitsyn commented on IGNITE-14294:
-
Merged to master: e560cff14c05f717a0a47447faf7f5d387cc6d88
> .NET: ClientServerCompatibilityTest is flaky
>
>
> Key: IGNITE-14294
> URL: https://issues.apache.org/jira/browse/IGNITE-14294
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ClientServerCompatibilityTest fails for two reasons:
> 1. {{Failed to establish Ignite thin client connection, examine inner
> exceptions for details. (Connection refused 127.0.0.1:10892)}} - check
> process output, is there a different port used for the client connector?
> 2. {{GridUnsafe cannot access class jdk.internal.misc.SharedSecrets}} - we
> should pass {{--add-exports}} and {{--illegal-access=permit}} JVM options
> when running on Java9+, see {{Jvm.IsJava9}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
