[jira] [Updated] (IGNITE-17299) .NET: The constructor to deserialize an object of type 'System.OrdinalCaseSensitiveComparer' was not found
[
https://issues.apache.org/jira/browse/IGNITE-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-17299:
Release Note: .NET: Fixed StringComparer serialization.
> .NET: The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found
> --
>
> Key: IGNITE-17299
> URL: https://issues.apache.org/jira/browse/IGNITE-17299
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.13
> Environment: NET 5.0, Apache Ignite 2.13, Newtonsoft.Json 13.0.1
>Reporter: Vadim Alekseev
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.14
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We have a model created with Nswag. The model has additional properties, by
> which all unknown fields are parsed.
> {code:java}
> private System.Collections.Generic.IDictionary
> _additionalProperties = new System.Collections.Generic.Dictionary object>();
> [Newtonsoft.Json.JsonExtensionData]
> public System.Collections.Generic.IDictionary
> AdditionalProperties
> {
> get { return _additionalProperties; }
> set { _additionalProperties = value; }
> } {code}
> If the nested model is saved in additional properties, it is saved as
> KeyValuePair. The object is a JArray containing a JObject.
> When writing data to the cache, everything is fine. But when retrieving data
> from the cache an error occurs:
>
> *The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found.*
>
> Stack Trace:
> {code:java}
> at
> Apache.Ignite.Core.Impl.Common.SerializableTypeDescriptor.get_SerializationCtorUninitialized()
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadSerializationInfo(BinaryReader
> reader, IEnumerable`1 fieldNames, Type type, ICollection`1 dotNetFields)
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1688(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1682(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1293(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
>
[jira] [Commented] (IGNITE-17299) .NET: The constructor to deserialize an object of type 'System.OrdinalCaseSensitiveComparer' was not found
[
https://issues.apache.org/jira/browse/IGNITE-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584586#comment-17584586
]
Pavel Tupitsyn commented on IGNITE-17299:
-
Cherry-picked to ignite-2.14: 35688da9d40671d2a04afa69dad4807117a46cce
> .NET: The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found
> --
>
> Key: IGNITE-17299
> URL: https://issues.apache.org/jira/browse/IGNITE-17299
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.13
> Environment: NET 5.0, Apache Ignite 2.13, Newtonsoft.Json 13.0.1
>Reporter: Vadim Alekseev
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.14
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We have a model created with Nswag. The model has additional properties, by
> which all unknown fields are parsed.
> {code:java}
> private System.Collections.Generic.IDictionary
> _additionalProperties = new System.Collections.Generic.Dictionary object>();
> [Newtonsoft.Json.JsonExtensionData]
> public System.Collections.Generic.IDictionary
> AdditionalProperties
> {
> get { return _additionalProperties; }
> set { _additionalProperties = value; }
> } {code}
> If the nested model is saved in additional properties, it is saved as
> KeyValuePair. The object is a JArray containing a JObject.
> When writing data to the cache, everything is fine. But when retrieving data
> from the cache an error occurs:
>
> *The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found.*
>
> Stack Trace:
> {code:java}
> at
> Apache.Ignite.Core.Impl.Common.SerializableTypeDescriptor.get_SerializationCtorUninitialized()
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadSerializationInfo(BinaryReader
> reader, IEnumerable`1 fieldNames, Type type, ICollection`1 dotNetFields)
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1688(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1682(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1293(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
[jira] [Commented] (IGNITE-17299) .NET: The constructor to deserialize an object of type 'System.OrdinalCaseSensitiveComparer' was not found
[
https://issues.apache.org/jira/browse/IGNITE-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584584#comment-17584584
]
Ignite TC Bot commented on IGNITE-17299:
{panel:title=Branch: [pull/10214/head] Base: [master] : Possible Blockers
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746717]]
{color:#d04437}Cache 5{color} [[tests 2 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746716]]
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= OPTIMISTIC, Concurrency = SERIALIZABLE, Started from = CLIENT] - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= PESSIMISTIC, Concurrency = READ_COMMITTED, Started from = FAILED] - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Basic 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746703]]
{color:#d04437}Cache 12{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746711]]
* IgniteCacheTestSuite12:
GracefulShutdownTest.testRollingRestartEmulationReplicatedCache - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746769]]
* IgnitePdsTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_1000_500_8_16
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746782]]
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746777]]
* IgniteCoreTest: CacheTestSuiteNativePersistence: TestWal - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10214/head] Base: [master] : New Tests
(463)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Windows){color} [[tests
234|https://ci.ignite.apache.org/viewLog.html?buildId=6747003]]
* {color:#013220}exe: Int32,System.String]) - PASSED{color}
* {color:#013220}exe: Queue`1[System.Int64]) - PASSED{color}
* {color:#013220}exe: Single,System.Double]) - PASSED{color}
* {color:#013220}exe: String,System.String]) - PASSED{color}
* {color:#013220}exe:
BasicSerializableObjectsTest.TestAllSerializableSystemTypes([0, 0]) -
PASSED{color}
* {color:#013220}exe: KeyNotFoundExceptioncolon The given key was not
present in the dictionary.) - PASSED{color}
* {color:#013220}exe: List`1[System.Single]) - PASSED{color}
* {color:#013220}exe: LinkedList`1[System.Int32]) - PASSED{color}
* {color:#013220}exe: Collections.DictionaryEntry) - PASSED{color}
* {color:#013220}exe: Collections.Comparer) - PASSED{color}
* {color:#013220}exe: HashSet`1[System.Int32]) - PASSED{color}
... and 223 new tests
{color:#8b}Platform .NET (Core Linux){color} [[tests
229|https://ci.ignite.apache.org/viewLog.html?buildId=6747005]]
* {color:#013220}dll:
TestAllSerializableSystemTypes(System.AccessViolationException - PASSED{color}
* {color:#013220}dll: RuntimeBinder.RuntimeBinderInternalCompilerException -
PASSED{color}
* {color:#013220}dll:
TestAllSerializableSystemTypes(System.AppDomainUnloadedException - PASSED{color}
* {color:#013220}dll: TestAllSerializableSystemTypes(System.AggregateException
- PASSED{color}
* {color:#013220}dll: RuntimeBinder.RuntimeBinderException - PASSED{color}
* {color:#013220}dll: Collections.Hashtable) - PASSED{color}
* {color:#013220}dll: Stack`1[System.Int32]) - PASSED{color}
* {color:#013220}dll: Serialization.JsonPropertyCollection) - PASSED{color}
* {color:#013220}dll: Collection`1[System.Int32]) - PASSED{color}
* {color:#013220}dll: String,System.String]) - PASSED{color}
* {color:#013220}dll: Int32,System.String]) - PASSED{color}
... and 218 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6746812buildTypeId=IgniteTests24Java8_RunAll]
> .NET: The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found
> --
>
> Key: IGNITE-17299
> URL: https://issues.apache.org/jira/browse/IGNITE-17299
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.13
> Environment: NET 5.0, Apache Ignite 2.13, Newtonsoft.Json 13.0.1
>Reporter: Vadim Alekseev
>Assignee: Pavel Tupitsyn
>
[jira] (IGNITE-17299) .NET: The constructor to deserialize an object of type 'System.OrdinalCaseSensitiveComparer' was not found
[ https://issues.apache.org/jira/browse/IGNITE-17299 ]
Pavel Tupitsyn deleted comment on IGNITE-17299:
-
was (Author: ignitetcbot):
{panel:title=Branch: [pull/10214/head] Base: [master] : Possible Blockers
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746717]]
{color:#d04437}Platform .NET (Windows){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6746781]]
* exe: CancellationTest.TestJavaTask - Test has low fail rate in base branch
0,0% and is not flaky
* exe: Serialization.JsonPropertyCollection) - History for base branch is
absent.
* exe: BasicSerializableObjectsTest.TestAllSerializableSystemTypes(0) - History
for base branch is absent.
* exe: BasicSerializableObjectsTest.TestAllSerializableSystemTypes((0, 0)) -
History for base branch is absent.
{color:#d04437}Cache 5{color} [[tests 2 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746716]]
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= OPTIMISTIC, Concurrency = SERIALIZABLE, Started from = CLIENT] - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= PESSIMISTIC, Concurrency = READ_COMMITTED, Started from = FAILED] - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Basic 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746703]]
{color:#d04437}Cache 12{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746711]]
* IgniteCacheTestSuite12:
GracefulShutdownTest.testRollingRestartEmulationReplicatedCache - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746769]]
* IgnitePdsTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_1000_500_8_16
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746782]]
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746777]]
* IgniteCoreTest: CacheTestSuiteNativePersistence: TestWal - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10214/head] Base: [master] : New Tests
(465)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Windows){color} [[tests
236|https://ci.ignite.apache.org/viewLog.html?buildId=6746781]]
* {color:#013220}exe: Int32,System.String]) - PASSED{color}
* {color:#013220}exe: Queue`1[System.Int64]) - PASSED{color}
* {color:#013220}exe: Single,System.Double]) - PASSED{color}
* {color:#013220}exe: String,System.String]) - PASSED{color}
* {color:#013220}exe:
BasicSerializableObjectsTest.TestAllSerializableSystemTypes([0, 0]) -
PASSED{color}
* {color:#013220}exe: KeyNotFoundExceptioncolon The given key was not
present in the dictionary.) - PASSED{color}
* {color:#013220}exe: List`1[System.Single]) - PASSED{color}
* {color:#013220}exe: LinkedList`1[System.Int32]) - PASSED{color}
* {color:#013220}exe: Collections.DictionaryEntry) - PASSED{color}
* {color:#013220}exe: Collections.Comparer) - PASSED{color}
* {color:#013220}exe: HashSet`1[System.Int32]) - PASSED{color}
... and 225 new tests
{color:#8b}Platform .NET (Core Linux){color} [[tests
229|https://ci.ignite.apache.org/viewLog.html?buildId=6746780]]
* {color:#013220}dll:
TestAllSerializableSystemTypes(System.AccessViolationException - PASSED{color}
* {color:#013220}dll: RuntimeBinder.RuntimeBinderInternalCompilerException -
PASSED{color}
* {color:#013220}dll:
TestAllSerializableSystemTypes(System.AppDomainUnloadedException - PASSED{color}
* {color:#013220}dll: TestAllSerializableSystemTypes(System.AggregateException
- PASSED{color}
* {color:#013220}dll: RuntimeBinder.RuntimeBinderException - PASSED{color}
* {color:#013220}dll: Collections.Hashtable) - PASSED{color}
* {color:#013220}dll: Stack`1[System.Int32]) - PASSED{color}
* {color:#013220}dll: Serialization.JsonPropertyCollection) - PASSED{color}
* {color:#013220}dll: Collection`1[System.Int32]) - PASSED{color}
* {color:#013220}dll: String,System.String]) - PASSED{color}
* {color:#013220}dll: Int32,System.String]) - PASSED{color}
... and 218 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6746812buildTypeId=IgniteTests24Java8_RunAll]
> .NET: The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found
>
[jira] [Commented] (IGNITE-17299) .NET: The constructor to deserialize an object of type 'System.OrdinalCaseSensitiveComparer' was not found
[
https://issues.apache.org/jira/browse/IGNITE-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584583#comment-17584583
]
Pavel Tupitsyn commented on IGNITE-17299:
-
Merged to master: f6e2ebe8e62b3e442bda2a70f19544261b3c0cfa
> .NET: The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found
> --
>
> Key: IGNITE-17299
> URL: https://issues.apache.org/jira/browse/IGNITE-17299
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.13
> Environment: NET 5.0, Apache Ignite 2.13, Newtonsoft.Json 13.0.1
>Reporter: Vadim Alekseev
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.14
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We have a model created with Nswag. The model has additional properties, by
> which all unknown fields are parsed.
> {code:java}
> private System.Collections.Generic.IDictionary
> _additionalProperties = new System.Collections.Generic.Dictionary object>();
> [Newtonsoft.Json.JsonExtensionData]
> public System.Collections.Generic.IDictionary
> AdditionalProperties
> {
> get { return _additionalProperties; }
> set { _additionalProperties = value; }
> } {code}
> If the nested model is saved in additional properties, it is saved as
> KeyValuePair. The object is a JArray containing a JObject.
> When writing data to the cache, everything is fine. But when retrieving data
> from the cache an error occurs:
>
> *The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found.*
>
> Stack Trace:
> {code:java}
> at
> Apache.Ignite.Core.Impl.Common.SerializableTypeDescriptor.get_SerializationCtorUninitialized()
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadSerializationInfo(BinaryReader
> reader, IEnumerable`1 fieldNames, Type type, ICollection`1 dotNetFields)
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1688(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1682(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1293(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
>
[jira] [Commented] (IGNITE-17299) .NET: The constructor to deserialize an object of type 'System.OrdinalCaseSensitiveComparer' was not found
[
https://issues.apache.org/jira/browse/IGNITE-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584389#comment-17584389
]
Ignite TC Bot commented on IGNITE-17299:
{panel:title=Branch: [pull/10214/head] Base: [master] : Possible Blockers
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746717]]
{color:#d04437}Platform .NET (Windows){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6746781]]
* exe: CancellationTest.TestJavaTask - Test has low fail rate in base branch
0,0% and is not flaky
* exe: Serialization.JsonPropertyCollection) - History for base branch is
absent.
* exe: BasicSerializableObjectsTest.TestAllSerializableSystemTypes(0) - History
for base branch is absent.
* exe: BasicSerializableObjectsTest.TestAllSerializableSystemTypes((0, 0)) -
History for base branch is absent.
{color:#d04437}Cache 5{color} [[tests 2 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746716]]
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= OPTIMISTIC, Concurrency = SERIALIZABLE, Started from = CLIENT] - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= PESSIMISTIC, Concurrency = READ_COMMITTED, Started from = FAILED] - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Basic 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746703]]
{color:#d04437}Cache 12{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746711]]
* IgniteCacheTestSuite12:
GracefulShutdownTest.testRollingRestartEmulationReplicatedCache - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746769]]
* IgnitePdsTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_1000_500_8_16
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6746782]]
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6746777]]
* IgniteCoreTest: CacheTestSuiteNativePersistence: TestWal - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10214/head] Base: [master] : New Tests
(465)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Windows){color} [[tests
236|https://ci.ignite.apache.org/viewLog.html?buildId=6746781]]
* {color:#013220}exe: Int32,System.String]) - PASSED{color}
* {color:#013220}exe: Queue`1[System.Int64]) - PASSED{color}
* {color:#013220}exe: Single,System.Double]) - PASSED{color}
* {color:#013220}exe: String,System.String]) - PASSED{color}
* {color:#013220}exe:
BasicSerializableObjectsTest.TestAllSerializableSystemTypes([0, 0]) -
PASSED{color}
* {color:#013220}exe: KeyNotFoundExceptioncolon The given key was not
present in the dictionary.) - PASSED{color}
* {color:#013220}exe: List`1[System.Single]) - PASSED{color}
* {color:#013220}exe: LinkedList`1[System.Int32]) - PASSED{color}
* {color:#013220}exe: Collections.DictionaryEntry) - PASSED{color}
* {color:#013220}exe: Collections.Comparer) - PASSED{color}
* {color:#013220}exe: HashSet`1[System.Int32]) - PASSED{color}
... and 225 new tests
{color:#8b}Platform .NET (Core Linux){color} [[tests
229|https://ci.ignite.apache.org/viewLog.html?buildId=6746780]]
* {color:#013220}dll:
TestAllSerializableSystemTypes(System.AccessViolationException - PASSED{color}
* {color:#013220}dll: RuntimeBinder.RuntimeBinderInternalCompilerException -
PASSED{color}
* {color:#013220}dll:
TestAllSerializableSystemTypes(System.AppDomainUnloadedException - PASSED{color}
* {color:#013220}dll: TestAllSerializableSystemTypes(System.AggregateException
- PASSED{color}
* {color:#013220}dll: RuntimeBinder.RuntimeBinderException - PASSED{color}
* {color:#013220}dll: Collections.Hashtable) - PASSED{color}
* {color:#013220}dll: Stack`1[System.Int32]) - PASSED{color}
* {color:#013220}dll: Serialization.JsonPropertyCollection) - PASSED{color}
* {color:#013220}dll: Collection`1[System.Int32]) - PASSED{color}
* {color:#013220}dll: String,System.String]) - PASSED{color}
* {color:#013220}dll: Int32,System.String]) - PASSED{color}
... and 218 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6746812buildTypeId=IgniteTests24Java8_RunAll]
> .NET: The constructor to deserialize an object of type
>
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584361#comment-17584361 ] Anton Kurbanov commented on IGNITE-12852: - [~tledkov], I've created ticket for that: https://issues.apache.org/jira/browse/IGNITE-17573 > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17573) SQL COPY command should support all RFC4180 compatible CSV files
Anton Kurbanov created IGNITE-17573: --- Summary: SQL COPY command should support all RFC4180 compatible CSV files Key: IGNITE-17573 URL: https://issues.apache.org/jira/browse/IGNITE-17573 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 2.13 Reporter: Anton Kurbanov Assignee: Anton Kurbanov https://www.rfc-editor.org/rfc/rfc4180 Currently there are no ways to handle CSV files with optional header with column names and with line breaks in fields content. SQL COPY command must correctly process all RFC compatible files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12622: - Fix Version/s: 2.15 (was: 2.14) > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Ivan Rakov >Assignee: Ivan Rakov >Priority: Major > Labels: IEP-80 > Fix For: 2.15 > > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-16944) Implement Topology REST API group
[ https://issues.apache.org/jira/browse/IGNITE-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr resolved IGNITE-16944. Resolution: Duplicate > Implement Topology REST API group > - > > Key: IGNITE-16944 > URL: https://issues.apache.org/jira/browse/IGNITE-16944 > Project: Ignite > Issue Type: Task > Components: rest >Reporter: Aleksandr >Priority: Major > Labels: ignite-3 > > h3. Topology REST API > Provide information about cluster topology. > ||Method||Path||Parameters||Description|| > |GET|/management/v1/topology/| |Return cluster topology > information(consistent ID, ID, address, status).| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-16944) Implement Topology REST API group
[ https://issues.apache.org/jira/browse/IGNITE-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584314#comment-17584314 ] Aleksandr commented on IGNITE-16944: Already implemented in IGNITE-17092 > Implement Topology REST API group > - > > Key: IGNITE-16944 > URL: https://issues.apache.org/jira/browse/IGNITE-16944 > Project: Ignite > Issue Type: Task > Components: rest >Reporter: Aleksandr >Priority: Major > Labels: ignite-3 > > h3. Topology REST API > Provide information about cluster topology. > ||Method||Path||Parameters||Description|| > |GET|/management/v1/topology/| |Return cluster topology > information(consistent ID, ID, address, status).| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584241#comment-17584241 ] Taras Ledkov edited comment on IGNITE-12852 at 8/24/22 1:11 PM: [~antkr] 1. I guess this patch could me merged because it fixes significant functionality for users. 2. Agreed. I guess we can introduce one or more parse option to tune parser behavior. However, checking that the number of fields in the rows is the same looks good. was (Author: tledkov): @[~antkr] 1. I guess this patch could me merged because it fixes significant functionality for users. 2. Agreed. I guess we can introduce one or more parse option to tune parser behavior. However, checking that the number of fields in the rows is the same looks good. > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584241#comment-17584241 ] Taras Ledkov commented on IGNITE-12852: --- @[~antkr] 1. I guess this patch could me merged because it fixes significant functionality for users. 2. Agreed. I guess we can introduce one or more parse option to tune parser behavior. However, checking that the number of fields in the rows is the same looks good. > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17299) .NET: The constructor to deserialize an object of type 'System.OrdinalCaseSensitiveComparer' was not found
[
https://issues.apache.org/jira/browse/IGNITE-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584239#comment-17584239
]
Igor Sapego commented on IGNITE-17299:
--
[~ptupitsyn] Approved. Left a single comment though.
> .NET: The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found
> --
>
> Key: IGNITE-17299
> URL: https://issues.apache.org/jira/browse/IGNITE-17299
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.13
> Environment: NET 5.0, Apache Ignite 2.13, Newtonsoft.Json 13.0.1
>Reporter: Vadim Alekseev
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have a model created with Nswag. The model has additional properties, by
> which all unknown fields are parsed.
> {code:java}
> private System.Collections.Generic.IDictionary
> _additionalProperties = new System.Collections.Generic.Dictionary object>();
> [Newtonsoft.Json.JsonExtensionData]
> public System.Collections.Generic.IDictionary
> AdditionalProperties
> {
> get { return _additionalProperties; }
> set { _additionalProperties = value; }
> } {code}
> If the nested model is saved in additional properties, it is saved as
> KeyValuePair. The object is a JArray containing a JObject.
> When writing data to the cache, everything is fine. But when retrieving data
> from the cache an error occurs:
>
> *The constructor to deserialize an object of type
> 'System.OrdinalCaseSensitiveComparer' was not found.*
>
> Stack Trace:
> {code:java}
> at
> Apache.Ignite.Core.Impl.Common.SerializableTypeDescriptor.get_SerializationCtorUninitialized()
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadSerializationInfo(BinaryReader
> reader, IEnumerable`1 fieldNames, Type type, ICollection`1 dotNetFields)
> at
> Apache.Ignite.Core.Impl.Binary.SerializableSerializer.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1688(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1682(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String
> fieldName) at lambda_method1293(Closure , Object , IBinaryReader ) at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride) at
> Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
> typeOverride) at
>
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584216#comment-17584216 ] Anton Kurbanov commented on IGNITE-12852: - [~tledkov] So, the two major points we are currently missing from the RFC are: ability to parse optional CSV file header and fields with linebreaks. I absolutely agree that we must support both of them, please let me know your opinion whether: 1. should it be implemented as part of this ticket or as a separate issue? 2. we may think of some cumbersome corner case, like: — in current implementation we have relaxed requirements on number of fields in the record, RFC4180 explicitly requires that a number of fields in each row should be the same — this may lead to delayed detection of whether the row is on multiple lines or the record is broken as we may potentially lookup for enclosing bracket until the unknown place in the file which may be even not found, a simple example would be a single column CSV file (something like dictionary) with broken record in the very beginning with the linebreak. so the question is that do we want to commit to RFC or leave this option as a flag and attempt to introduce some fail-fast option? > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17432) ignitevisorcmd can't run in jdk17 env
[ https://issues.apache.org/jira/browse/IGNITE-17432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584203#comment-17584203 ] Taras Ledkov commented on IGNITE-17432: --- Chetty-picked to [ignite-2.14|https://github.com/apache/ignite/commit/3c733733db3516f032e2396c6d28cf831485aa67] > ignitevisorcmd can't run in jdk17 env > - > > Key: IGNITE-17432 > URL: https://issues.apache.org/jira/browse/IGNITE-17432 > Project: Ignite > Issue Type: Bug > Components: cli >Affects Versions: 2.13 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Minor > Fix For: 2.14 > > Attachments: > 0001-IGNITE-17432-ignitevisorcmd-can-t-run-in-jdk17-env.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Unrecognized VM option 'MaxPermSize=128M' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17317) Test IgnitePdsBinaryMetadataAsyncWritingTest.testNodeIsStoppedOnExceptionDuringStoringMetadata is flaky on TC
[
https://issues.apache.org/jira/browse/IGNITE-17317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584177#comment-17584177
]
Taras Ledkov commented on IGNITE-17317:
---
[~sergeychugunov], looks like resolved
[commit|https://github.com/apache/ignite/commit/7aca244b68d81fa1f891d8f767be2a53b29438a3].
Please resolve the issue
> Test
> IgnitePdsBinaryMetadataAsyncWritingTest.testNodeIsStoppedOnExceptionDuringStoringMetadata
> is flaky on TC
> -
>
> Key: IGNITE-17317
> URL: https://issues.apache.org/jira/browse/IGNITE-17317
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Test history is available here: [TC
> link|https://ci.ignite.apache.org/test/-1717009344468901983?currentProjectId=IgniteTests24Java8=%3Cdefault%3E]
> Test fails on a cache put operation before a condition being verified is
> reached:
> {code:java}
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [2]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1260)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2111)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1347)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:870)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsBinaryMetadataAsyncWritingTest.testNodeIsStoppedOnExceptionDuringStoringMetadata(IgnitePdsBinaryMetadataAsyncWritingTest.java:257)
> {code}
> There is also a stack trace in logs indicating there is some problem when
> writing to WAL:
> {code:java}
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [2]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1260)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2111)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1347)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:870)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsBinaryMetadataAsyncWritingTest.testNodeIsStoppedOnExceptionDuringStoringMetadata(IgnitePdsBinaryMetadataAsyncWritingTest.java:257)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2428)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [2]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:401)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:3213)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$500(GridDhtAtomicCache.java:145)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:305)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:300)
> at
>
[jira] [Updated] (IGNITE-17306) Speedup runtime classes compilation speed for configuration
[ https://issues.apache.org/jira/browse/IGNITE-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-17306: --- Labels: iep-55 ignite-3 (was: ignite-3) > Speedup runtime classes compilation speed for configuration > --- > > Key: IGNITE-17306 > URL: https://issues.apache.org/jira/browse/IGNITE-17306 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: iep-55, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > There are a few places in presto that for too slow, we can easily optimize > them > (Nothing will be committed if there's no visible difference in tests duration) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17306) Speedup runtime classes compilation speed for configuration
[ https://issues.apache.org/jira/browse/IGNITE-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-17306: --- Epic Link: IGNITE-14904 > Speedup runtime classes compilation speed for configuration > --- > > Key: IGNITE-17306 > URL: https://issues.apache.org/jira/browse/IGNITE-17306 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > There are a few places in presto that for too slow, we can easily optimize > them > (Nothing will be committed if there's no visible difference in tests duration) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
"\{clientType}.ActiveSessions" metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800 and local port 1024
3) Start jdbc or thin client with connecting to proxy server
{code:java}
ClientConfiguration cfg = new
ClientConfiguration().setAddresses("127.0.0.1:1024");
IgniteClient igniteClient = Ignition.startClient(cfg);
IgniteClient igniteClient2 = Ignition.startClient(cfg); {code}
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
"\{clientType}.ActiveSessions" metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> "\{clientType}.ActiveSessions" metrics no decrease in case when we use
> thin/jdbc client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
>
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800 and local port 1024
> 3) Start jdbc or thin client with connecting to proxy server
> {code:java}
> ClientConfiguration cfg = new
> ClientConfiguration().setAddresses("127.0.0.1:1024");
> IgniteClient igniteClient = Ignition.startClient(cfg);
> IgniteClient igniteClient2 = Ignition.startClient(cfg); {code}
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16319) Replace DataLoaderApplication with DataGenerationApplication
[
https://issues.apache.org/jira/browse/IGNITE-16319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-16319:
--
Fix Version/s: (was: 2.14)
> Replace DataLoaderApplication with DataGenerationApplication
>
>
> Key: IGNITE-16319
> URL: https://issues.apache.org/jira/browse/IGNITE-16319
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Sergey Korotkov
>Priority: Minor
> Labels: ducktests
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Currently, two application exists in ducktape for one purpose - generate some
> data and put it in the cluster.
> We should remove {{DataLoaderApplication}} and use
> {{DataGenerationApplication}} instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-17570) Extend documentation about defining of indices
[
https://issues.apache.org/jira/browse/IGNITE-17570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semyon Danilov resolved IGNITE-17570.
-
Resolution: Fixed
LGTM. Thank you for the contribution, merged to the master branch.
> Extend documentation about defining of indices
> --
>
> Key: IGNITE-17570
> URL: https://issues.apache.org/jira/browse/IGNITE-17570
> Project: Ignite
> Issue Type: Task
>Reporter: Igor Gusev
>Assignee: Igor Gusev
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://ignite.apache.org/docs/latest/SQL/indexes#configuring-index-inline-size]
> add information about PK_INLINE_SIZE, AFFINITY_INDEX_INLINE_SIZE parameters
> within WITH section. For example:
>
> {code:java}
> {{CREATE TABLE IF NOT EXISTS TABLE1 (
> id varchar(15),
> col varchar(100),
> PRIMARY KEY(id) ) WITH "PK_INLINE_SIZE=19,AFFINITY_INDEX_INLINE_SIZE=20"}}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13578) Update ignite-kafka dependencies to get rid of reported CVEs
[ https://issues.apache.org/jira/browse/IGNITE-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584148#comment-17584148 ] Taras Ledkov commented on IGNITE-13578: --- Cleanup release version because work on the the issue looks like not so active. > Update ignite-kafka dependencies to get rid of reported CVEs > > > Key: IGNITE-13578 > URL: https://issues.apache.org/jira/browse/IGNITE-13578 > Project: Ignite > Issue Type: Bug > Components: integrations >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The libraries to update: > connect-api-2.1.1.jar > kafka-clients-2.1.1.jar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13578) Update ignite-kafka dependencies to get rid of reported CVEs
[ https://issues.apache.org/jira/browse/IGNITE-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-13578: -- Fix Version/s: (was: 2.14) > Update ignite-kafka dependencies to get rid of reported CVEs > > > Key: IGNITE-13578 > URL: https://issues.apache.org/jira/browse/IGNITE-13578 > Project: Ignite > Issue Type: Bug > Components: integrations >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The libraries to update: > connect-api-2.1.1.jar > kafka-clients-2.1.1.jar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17537) Make units of 'timeout' and 'duration' more explicit in control.sh --tx output
[
https://issues.apache.org/jira/browse/IGNITE-17537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julia Bakulina reassigned IGNITE-17537:
---
Assignee: Julia Bakulina
> Make units of 'timeout' and 'duration' more explicit in control.sh --tx output
> --
>
> Key: IGNITE-17537
> URL: https://issues.apache.org/jira/browse/IGNITE-17537
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh
>Affects Versions: 2.13
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Trivial
> Labels: ise, newbie
>
> Execution of {{control.sh --tx}} command produces output of matching
> transactions, eg.:
> {quote}Matching transactions:
> Tx: [xid=fdc4d720281--0fd8-0177--0012, label=null,
> state=ACTIVE, startTime=2022-07-06 05:05:07.432,
> {*}{color:#ff}duration=778{color}{*}, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, topVer=AffinityTopologyVersion [topVer=199,
> minorTopVer=0], {*}{color:#ff}timeout=4{color}{*}, ...]
> {quote}
> But, from the above line it is unclear, that in fact, duration is printed in
> seconds [1], while timeout is printed in milliseconds.
> We can improve output in one of the following ways:
> # Explicitly append unit for seconds and milliseconds.
> # Print duration and timeout in same units: both in seconds or both in
> milliseconds.
> Links:
> #
> https://github.com/apache/ignite/blob/bf9a460eccd07701cacac2a414c65707243350f1/modules/core/src/main/java/org/apache/ignite/internal/visor/tx/VisorTxInfo.java#L286
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17559) IgniteSetClientTests.TestCopyToInvalidArguments fails on Windows
[
https://issues.apache.org/jira/browse/IGNITE-17559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584141#comment-17584141
]
Pavel Tupitsyn commented on IGNITE-17559:
-
[~tledkov] cherry-picked to ignite-2.14:
5102d1d278fe80254517e70b97f3ca020f700b2a
> IgniteSetClientTests.TestCopyToInvalidArguments fails on Windows
>
>
> Key: IGNITE-17559
> URL: https://issues.apache.org/jira/browse/IGNITE-17559
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.14
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/test/-420042244593401280?currentProjectId=IgniteTests24Java8=%3Cdefault%3E
> {code}
> Expected string length 75 but was 79. Strings differ at index 29.
> Expected: "...r required. (Parameter 'arrayIndex')\nActual value was -1."
> But was: "...r required.\r\nParameter name: arrayIndex\r\nActual value was
> -1."
> -^
>at
> Apache.Ignite.Core.Tests.Client.DataStructures.IgniteSetClientTests.TestCopyToInvalidArguments()
> in
> C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Client\DataStructures\IgniteSetClientTests.cs:line
> 219
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17358) Metric exporter configuration for Ignite 3
[ https://issues.apache.org/jira/browse/IGNITE-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov reassigned IGNITE-17358: --- Assignee: Kirill Gusakov > Metric exporter configuration for Ignite 3 > -- > > Key: IGNITE-17358 > URL: https://issues.apache.org/jira/browse/IGNITE-17358 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Chudov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > Should be designed a way to configure metric exporters in Ignite > configuration. Different types of exporters should be supported, including > ones that work according to push and pull models. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-15455) Support statistics SQL commands on Calcite
[ https://issues.apache.org/jira/browse/IGNITE-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582912#comment-17582912 ] Ivan Daschinsky edited comment on IGNITE-15455 at 8/24/22 8:02 AM: --- [~alexpl] [~tedkov] Could you please review patch if you din't mind? was (Author: ivandasch): [~alexpl] [~taras.ledkov] Could you please review patch if you din't mind? > Support statistics SQL commands on Calcite > -- > > Key: IGNITE-15455 > URL: https://issues.apache.org/jira/browse/IGNITE-15455 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.13 >Reporter: Alexander Belyak >Assignee: Ivan Daschinsky >Priority: Major > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Time Spent: 40m > Remaining Estimate: 0h > > Need to support ANALYZE, REFRESH and DROP commands similar (or exact) the > same, as they works in 2.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-15455) Support statistics SQL commands on Calcite
[ https://issues.apache.org/jira/browse/IGNITE-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584099#comment-17584099 ] Ivan Daschinsky edited comment on IGNITE-15455 at 8/24/22 8:02 AM: --- [~tledkov] Thanks for your review, merged to master. was (Author: ivandasch): [~tledkov] Thanks for your review, merged to master. > Support statistics SQL commands on Calcite > -- > > Key: IGNITE-15455 > URL: https://issues.apache.org/jira/browse/IGNITE-15455 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.13 >Reporter: Alexander Belyak >Assignee: Ivan Daschinsky >Priority: Major > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Time Spent: 40m > Remaining Estimate: 0h > > Need to support ANALYZE, REFRESH and DROP commands similar (or exact) the > same, as they works in 2.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-6785) Affinity field name forced to be upper-case
[
https://issues.apache.org/jira/browse/IGNITE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-6785:
-
Fix Version/s: (was: 2.14)
> Affinity field name forced to be upper-case
> ---
>
> Key: IGNITE-6785
> URL: https://issues.apache.org/jira/browse/IGNITE-6785
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1, 2.8
>Reporter: Denis A. Magda
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: newbie, usability
> Attachments: SqlAffinityKeyTest.java, sql_bug.zip
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If an SQL schema and cache is created with CREATE TABLE command and a user
> wants to use key-value APIs creating its own custom key class, then (at
> least) the key class's affinity field forced to be written in upper-case.
> Steps to reproduce using the project attached:
> * start a node with {{./ignite.sh ../examples/config/example-ignite.xml}}.
> * create {{City}} table using {{ignite_world.sql}}. SQLline is one of the
> quickest ways: https://apacheignite-sql.readme.io/docs/sqlline
> * Run {{KeyValueDataProcessing}} to catch the exception below
> {noformat}
> Exception in thread "main" class
> org.apache.ignite.binary.BinaryObjectException: Binary type has different
> affinity key fields [typeName=demo.model.CityKey,
> affKeyFieldName1=COUNTRYCODE, affKeyFieldName2=countryCode]
> at
> org.apache.ignite.internal.binary.BinaryUtils.mergeMetadata(BinaryUtils.java:987)
> {noformat}
> If fact {{CityKey}} names the affinity field in the same way as in CREATE
> TABLE - {{countryCode}}.
> Next, run {{KeyValueBinaryDataProcessing}} to spot another weird thing:
> * BinaryObject key accepts `countryCode` as the affinity field name.
> * If to print our a binary object value then all the fields are in the
> upper-case (they were not defined this way in CREATE TABLE):
> {noformat}
> demo.model.City [idHash=1613627715, hash=-1386587499, DISTRICT=Noord-Holland,
> POPULATION=711200, NAME=Amsterdam]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17562) Sql. Implement cascade drop for indices.
[ https://issues.apache.org/jira/browse/IGNITE-17562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-17562: --- Epic Link: IGNITE-17304 > Sql. Implement cascade drop for indices. > > > Key: IGNITE-17562 > URL: https://issues.apache.org/jira/browse/IGNITE-17562 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > As for now, dropping table doesn't force cascading index drop. > Thus we have to drop indices manually before dropping the table. > Let's force cascading index drop when table is dropped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17563) Sql. Add nulls ordering support to CREATE INDEX command.
[ https://issues.apache.org/jira/browse/IGNITE-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-17563: --- Epic Link: IGNITE-17304 > Sql. Add nulls ordering support to CREATE INDEX command. > > > Key: IGNITE-17563 > URL: https://issues.apache.org/jira/browse/IGNITE-17563 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > As of now, CreateIndexCommand support only asc/desc ordering. > Let's support NULLS FIRST/LAST ordering as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13348) Creating IgniteAtomicLong from the client node may hang.
[
https://issues.apache.org/jira/browse/IGNITE-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584079#comment-17584079
]
Taras Ledkov commented on IGNITE-13348:
---
[~slava.koptilin], does the issue really "in progress" more than one year?
I see that we move it from release to release several times.
Should it be scheduled for a specific release or is it worth cleanup the fix
version?
> Creating IgniteAtomicLong from the client node may hang.
>
>
> Key: IGNITE-13348
> URL: https://issues.apache.org/jira/browse/IGNITE-13348
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.14
>
> Attachments: DataStructuresInitializationTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like, the data structure processor does not properly initialize when
> a client node connects to a cluster that changes its own state (state
> transition from the inactive state to active).
> reproducer attached.
> *UPDATE*
> It seems to me, the root cause of the issue is that {{joinFut}} is always
> completed with {{false}}.
> {code:java|title=GridClusterStateProcessor.java}
> /** {@inheritDoc} */
> @Override public void onStateFinishMessage(ChangeGlobalStateFinishMessage
> msg) {
> DiscoveryDataClusterState discoClusterState = globalState;
> if (msg.requestId().equals(discoClusterState.transitionRequestId())) {
> ...
> TransitionOnJoinWaitFuture joinFut = this.joinFut;
> if (joinFut != null)
> joinFut.onDone(false);
> ...
> }
> else
> U.warn(log, "Received state finish message with unexpected ID: "
> + msg);
> }
> {code}
> On the other hand, this value is used to determine the state of the cluster
> when a new node joins the cluster
> {code:java|title=IgniteKernal.java}
> public void start(
> DiscoveryLocalJoinData joinData = ctx.discovery().localJoin();
> IgniteInternalFuture transitionWaitFut =
> joinData.transitionWaitFuture();
> ...
> boolean active;
> if (transitionWaitFut != null) {
> if (log.isInfoEnabled()) {
> log.info("Join cluster while cluster state transition is
> in progress, waiting when transition finish.");
> }
> active = transitionWaitFut.get();
> }
> else
> active = joinData.active();
> startTimer.finishGlobalStage("Await transition");
> ...
> }
> {code}
> User list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-node-hangs-while-IgniteAtomicLong-is-created-tp33537.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15647:
--
Fix Version/s: 2.15
(was: 2.14)
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.15
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[
https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584050#comment-17584050
]
Taras Ledkov commented on IGNITE-12852:
---
[~antkr], the patch is OK with me.
What doyou think about CSV that contains values with line separator, e.g:
{code}
ID, Comment, LikesCount
0, "Single line comment", 28
1. "Multiple
line
comment", 42
{code}
Looks like it isn't supported now.
May be we have to file issues to implement Ignite CSV parser according with
[RFC-4180|https://www.rfc-editor.org/rfc/rfc4180]?
> Comma in field is not supported by COPY command
> ---
>
> Key: IGNITE-12852
> URL: https://issues.apache.org/jira/browse/IGNITE-12852
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: YuJue Li
>Assignee: Anton Kurbanov
>Priority: Critical
> Fix For: 2.14
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a));
>
> a.csv:
> 1,"a,b",2
>
> COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV;
>
> The copy command fails because there is a comma in the second field,but this
> is a fully legal and compliant CSV format
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17338) Implement RocksDB based hash index storage
[
https://issues.apache.org/jira/browse/IGNITE-17338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-17338:
---
Ignite Flags: (was: Docs Required,Release Notes Required)
> Implement RocksDB based hash index storage
> --
>
> Key: IGNITE-17338
> URL: https://issues.apache.org/jira/browse/IGNITE-17338
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Please see IGNITE-17318 for partial description of what needs to be achieved.
> I expect that hash index records will have the following structure:
> {code:java}
> [ indexId | partitionId | hash | tuple | rowId ] -> []{code}
> Fixed-length prefix should cover indexId, partitionId and hash value.
> Searching rows effectively becomes a scan, but this is fine.
> Hashing must be performed internally, hash function already presents
> somewhere in the code.
> Is far as I understand, PK is going to be implemented as a secondary hash
> index.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17559) IgniteSetClientTests.TestCopyToInvalidArguments fails on Windows
[
https://issues.apache.org/jira/browse/IGNITE-17559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584029#comment-17584029
]
Taras Ledkov commented on IGNITE-17559:
---
[~ptupitsyn], please cherry-pick the patch to the {{ignite-2.14}} branch if
need. Otherwise, lets change fix version to 2.15.
> IgniteSetClientTests.TestCopyToInvalidArguments fails on Windows
>
>
> Key: IGNITE-17559
> URL: https://issues.apache.org/jira/browse/IGNITE-17559
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.14
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/test/-420042244593401280?currentProjectId=IgniteTests24Java8=%3Cdefault%3E
> {code}
> Expected string length 75 but was 79. Strings differ at index 29.
> Expected: "...r required. (Parameter 'arrayIndex')\nActual value was -1."
> But was: "...r required.\r\nParameter name: arrayIndex\r\nActual value was
> -1."
> -^
>at
> Apache.Ignite.Core.Tests.Client.DataStructures.IgniteSetClientTests.TestCopyToInvalidArguments()
> in
> C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Client\DataStructures\IgniteSetClientTests.cs:line
> 219
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-15455) Support statistics SQL commands on Calcite
[ https://issues.apache.org/jira/browse/IGNITE-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584021#comment-17584021 ] Taras Ledkov commented on IGNITE-15455: --- [~ivandasch], the patch is OK with me. > Support statistics SQL commands on Calcite > -- > > Key: IGNITE-15455 > URL: https://issues.apache.org/jira/browse/IGNITE-15455 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.13 >Reporter: Alexander Belyak >Assignee: Ivan Daschinsky >Priority: Major > Labels: calcite2-required, calcite3-required > Fix For: 2.14 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to support ANALYZE, REFRESH and DROP commands similar (or exact) the > same, as they works in 2.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
