[jira] [Assigned] (IGNITE-13507) Critical error on tx recovery

2020-11-16 Thread Pavel Vinokurov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Vinokurov reassigned IGNITE-13507:


Assignee: Pavel Vinokurov

> Critical error on tx recovery
> -
>
> Key: IGNITE-13507
> URL: https://issues.apache.org/jira/browse/IGNITE-13507
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7.5
>Reporter: Pavel Vinokurov
>Assignee: Pavel Vinokurov
>Priority: Major
>
> Server node failed because of NullPointerException on tx recovery:
> {code:java}
> [17:15:02,428][SEVERE][sys-#305][] Critical system error detected. Will be 
> handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0, super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteException: Failed to perform tx 
> recovery]]
> class org.apache.ignite.IgniteException: Failed to perform tx recovery
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxRecoveryInitRunnable.run(IgniteTxManager.java:3288)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7186)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:826)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
>   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
>   at 
> org.apache.ignite.internal.IgniteFeatures.nodeSupports(IgniteFeatures.java:212)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxRecoveryInitRunnable.isMvccRecoveryMessageRequired(IgniteTxManager.java:3304)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxRecoveryInitRunnable.run(IgniteTxManager.java:3208)
>   ... 6 more
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13336) .NET: Misleading LINQ exception when expression can't be translated

2020-11-16 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17233139#comment-17233139
 ] 

Ignite TC Bot commented on IGNITE-13336:


{panel:title=Branch: [pull/8459/head] Base: [master] : Possible Blockers 
(51)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 5 Out Of Memory Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=5738544]]
* org.apache.ignite.testsuites.IgniteCacheTestSuite6: 
org.apache.ignite.internal.processors.cache.distributed.IgnitePessimisticTxSuspendResumeTest.
 - History for base branch is absent.
* IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeAndNewCoordinator - 
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite6: 
CacheExchangeMergeTest.testStartCacheOnJoinAndJoinMerge_4_nodes - Test has low 
fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite6: 
GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent - Test 
has low fail rate in base branch 0,0% and is not flaky
* org.apache.ignite.testsuites.IgniteCacheTestSuite6: 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.
 - History for base branch is absent.

{color:#d04437}Control Utility (Zookeeper){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5738594]]

{color:#d04437}Cache (Expiry Policy){color} [[tests 0 Out Of Memory Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=5738529]]

{color:#d04437}Basic 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5738519]]
* IgniteBasicTestSuite: 
MarshallerContextLockingSelfTest.testMultithreadedUpdate - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}Cache 9{color} [[tests 2 Out Of Memory Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=5738547]]
* IgniteCacheTestSuite9: 
IgniteTxCacheWriteSynchronizationModesMultithreadedTest.testMultithreadedPrimarySyncRestart
 - Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite9: 
IgniteTxCacheWriteSynchronizationModesMultithreadedTest.testMultithreadedFullSyncRestart
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5738560]]
* exe: CancellationTest.TestClosures - Test has low fail rate in base branch 
0,0% and is not flaky
* exe: ComputeClientTests.TestExecuteJavaTaskWithTimeout - Test has low fail 
rate in base branch 0,8% and is not flaky

{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5738595]]
* IgniteCoreTest: CacheTestSuiteNativePersistence: TestWal - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}Thin client: Node.js{color} [[tests 35 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5738518]]
* cache configuration operations test suite : create cache - Test has low 
fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : create cache twice - Test has 
low fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : get or create cache - Test 
has low fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : get cache names - Test has 
low fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : destroy cache - Test has low 
fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : create cache with 
configuration - Test has low fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : create cache with wrong args 
- Test has low fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : get or create cache with 
wrong args - Test has low fail rate in base branch 0,0% and is not flaky
* cache configuration operations test suite : get cache with wrong args - 
Test has low fail rate in base branch 0,0% and is not flaky
* sql fields query test suite : get all with page size lazy false - Test 
has low fail rate in base branch 0,0% and is not flaky
* scan query test suite : get all - Test has low fail rate in base branch 
0,0% and is not flaky
... and 24 tests blockers

{panel}
{panel:title=Branch: [pull/8459/head] Base: [master] : New Tests 
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Cache 6{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5738544]]
* {color:#8b}org.apache.ignite.testsuites.IgniteCacheTestSuite6: 
org.apache.ignite.internal.processors.cache.distributed.IgnitePessimisticTxSuspendResumeTest.
 - FAILED{color}
* {color:#8b}org.apache.ignite.testsuites.IgniteCacheTestSuite6: 

[jira] [Created] (IGNITE-13710) Calcite integration. Fix or to union rule logic

2020-11-16 Thread Igor Seliverstov (Jira)
Igor Seliverstov created IGNITE-13710:
-

 Summary: Calcite integration. Fix or to union rule logic
 Key: IGNITE-13710
 URL: https://issues.apache.org/jira/browse/IGNITE-13710
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Igor Seliverstov






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-6267) .NET: Get rid of Doxygen-specific files

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-6267:

Fix Version/s: 2.8

> .NET: Get rid of Doxygen-specific files
> ---
>
> Key: IGNITE-6267
> URL: https://issues.apache.org/jira/browse/IGNITE-6267
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> IGNITE-6253 replaces Doxygen with DocFX.
> Remove Doxygen-specific files:
> * {{Apache.Ignite.dxg}}
> * {{header.html}}
> * {{Package-Info.cs}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-10157) Fix inspections failures in GridTestUtils

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-10157:
-
Fix Version/s: 2.8

> Fix inspections failures in GridTestUtils
> -
>
> Key: IGNITE-10157
> URL: https://issues.apache.org/jira/browse/IGNITE-10157
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fix these fails:
> https://ci.ignite.apache.org/viewLog.html?buildId=2261996=Inspection=IgniteTests24Java8_InspectionsCore



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13701) SQL Indexes,Tables and Schemas views in IEP-35 changed amount, order of columns and content

2020-11-16 Thread Alexey Goncharuk (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232835#comment-17232835
 ] 

Alexey Goncharuk commented on IGNITE-13701:
---

LGTM

> SQL Indexes,Tables and Schemas views in IEP-35 changed amount, order of 
> columns and content
> ---
>
> Key: IGNITE-13701
> URL: https://issues.apache.org/jira/browse/IGNITE-13701
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://issues.apache.org/jira/browse/IGNITE-12213 broke backward 
> compatibility:
>   * {{CACHE_GROUP_ID}} and {{CACHE_GROUP_NAME}} columns was removed from the 
> {{INDEXES}} view.
>   * {{CACHE_GROUP_ID}} and {{CACHE_GROUP_NAME}} columns was removed from the 
> {{TABLES}} view.
>   * {{SCHEMA_NAME}} column was renamed to {{NAME}} for the {{SCHEMAS}} view.
>   * {{PREDEFINED}} column was added to the {{SCHEMAS}} view.
> Default columns order was changed.
> Also content of {{SCHEMAS}} view has changed in a wrong way: now view 
> contains proxy indexes (it is simply wrapper and implementation detail) and 
> indexes for cache key displays as {{PK}} index (it is incorrect, because 
> {{PK}} index could be only for table and this kind of indexes is 
> implementation detail).
> This behavior should be replaced by previous one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-12402) Example HibernateL2CacheExample

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-12402:
-
Fix Version/s: 2.8

> Example HibernateL2CacheExample
> ---
>
> Key: IGNITE-12402
> URL: https://issues.apache.org/jira/browse/IGNITE-12402
> Project: Ignite
>  Issue Type: Bug
>Reporter: Surkov Aleksandr
>Assignee: Surkov Aleksandr
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is class in examles 
> _org.apache.ignite.examples.datagrid.hibernate.HibernateL2CacheExample_
> If run it, there will be an exception:
> {code:java}
> Exception in thread "main" org.hibernate.MappingException: Could not get 
> constructor for org.hibernate.persister.entity.SingleTableEntityPersister at 
> org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:123)
>  at 
> org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:77)
>  at 
> org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:356) 
> at 
> org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:423)
>  at 
> org.hibernate.boot.internal.MetadataImpl.buildSessionFactory(MetadataImpl.java:170)
>  at 
> org.apache.ignite.examples.datagrid.hibernate.HibernateL2CacheExample.createHibernateSessionFactory(HibernateL2CacheExample.java:236)
>  at 
> org.apache.ignite.examples.datagrid.hibernate.HibernateL2CacheExample.main(HibernateL2CacheExample.java:128)Caused
>  by: org.hibernate.HibernateException: Unable to instantiate default tuplizer 
> [org.hibernate.tuple.entity.PojoEntityTuplizer] at 
> org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:91)
>  at 
> org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:116)
>  at 
> org.hibernate.tuple.entity.EntityMetamodel.(EntityMetamodel.java:388) 
> at 
> org.hibernate.persister.entity.AbstractEntityPersister.(AbstractEntityPersister.java:518)
>  at 
> org.hibernate.persister.entity.SingleTableEntityPersister.(SingleTableEntityPersister.java:124)
>  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.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:96)
>  ... 6 moreCaused by: java.lang.reflect.InvocationTargetException 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.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:88)
>  ... 15 moreCaused by: java.lang.NoClassDefFoundError: 
> javassist/util/proxy/MethodFilter at 
> org.hibernate.bytecode.internal.javassist.BytecodeProviderImpl.getProxyFactoryFactory(BytecodeProviderImpl.java:32)
>  at 
> org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactoryInternal(PojoEntityTuplizer.java:187)
>  at 
> org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:162)
>  at 
> org.hibernate.tuple.entity.AbstractEntityTuplizer.(AbstractEntityTuplizer.java:164)
>  at 
> org.hibernate.tuple.entity.PojoEntityTuplizer.(PojoEntityTuplizer.java:60)
>  ... 20 moreCaused by: java.lang.ClassNotFoundException: 
> javassist.util.proxy.MethodFilter at 
> java.net.URLClassLoader.findClass(URLClassLoader.java:382) at 
> java.lang.ClassLoader.loadClass(ClassLoader.java:424) at 
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at 
> java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 25 more{code}
> This can be fixed if remove
> {code:java}
> test{code}
> for _javassist_ at file
> {code:java}
> examples/pom.xml{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-9017) .NET: Clear cache statistics

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-9017:

Fix Version/s: 2.9

> .NET: Clear cache statistics
> 
>
> Key: IGNITE-9017
> URL: https://issues.apache.org/jira/browse/IGNITE-9017
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.7
>Reporter: Denis Garus
>Assignee: Sergey Stronchinskiy
>Priority: Major
>  Labels: .NET, newbie
> Fix For: 2.9
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> ICache.ClearStatistics, ICluster.ClearStatistics.
> See IGNITE-8705



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-1436) C++: Port to MAC OS.

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-1436:

Fix Version/s: 2.9

> C++: Port to MAC OS.
> 
>
> Key: IGNITE-1436
> URL: https://issues.apache.org/jira/browse/IGNITE-1436
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Stephen Darlington
>Priority: Major
>  Labels: cpp
> Fix For: 2.9
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It will require minimal porting of "common" and "utils" stuff.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-12500) IgniteProxy should be injected into non-system types only.

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-12500:
-
Fix Version/s: 2.9

> IgniteProxy should be injected into non-system types only.
> --
>
> Key: IGNITE-12500
> URL: https://issues.apache.org/jira/browse/IGNITE-12500
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
>  Labels: iep-38
> Fix For: 2.9
>
>
> When the Ignite Sandbox is enabled, the GridResourceProxiedIgniteInjector 
> should inject an IgniteProxy into non-system types only.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13312) Methods of interface Binarylizable should not get access to host resources.

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-13312:
-
Fix Version/s: 2.10

> Methods of interface Binarylizable should not get access to host resources.
> ---
>
> Key: IGNITE-13312
> URL: https://issues.apache.org/jira/browse/IGNITE-13312
> Project: Ignite
>  Issue Type: Task
>  Components: security
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
>  Labels: iep-38
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Methods of interface Binarylizable should not get access to host resources on 
> remote nodes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13652) Wrong GitHub link for Apache Ignite With Spring Data/Example

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-13652:
-
Fix Version/s: 2.10

> Wrong GitHub link for Apache Ignite With Spring Data/Example
> 
>
> Key: IGNITE-13652
> URL: https://issues.apache.org/jira/browse/IGNITE-13652
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.9
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
>  Labels: docuentation
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Wrong GihHub link in
> https://ignite.apache.org/docs/latest/extensions-and-integrations/spring/spring-data#example



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13357) .NET: Add includeExpired to ContinuousQuery

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-13357:
-
Fix Version/s: 2.10

> .NET: Add includeExpired to ContinuousQuery
> ---
>
> Key: IGNITE-13357
> URL: https://issues.apache.org/jira/browse/IGNITE-13357
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.10
>
>   Original Estimate: 6h
>  Time Spent: 2h 20m
>  Remaining Estimate: 50m
>
> Add includeExpired flag to ContinuousQuery (thick and thin modes) to track 
> entry expiration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-12588) Failed to run MLeap or Spark examples

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-12588:
-
Fix Version/s: 2.9

> Failed to run MLeap or Spark examples
> -
>
> Key: IGNITE-12588
> URL: https://issues.apache.org/jira/browse/IGNITE-12588
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, spark
>Affects Versions: 2.8
> Environment: Java 8
>  Ubuntu/Win 10
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> New release build comes with missed class 
> org.apache.ignite.ml.mleap.MLeapModelParser
>  Now i can't build any spark examples
> Steps:
>  - Try to mvn clean package -P scala
> Actual:
>  - 
> {code:java}
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[34,34]
>  package org.apache.ignite.ml.mleap does not exist
> [ERROR] 
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,26]
>  cannot find symbol
>   symbol:   class MLeapModelParser
>   location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> [ERROR] 
> /apache-ignite-2.8.0-bin/examples/src/main/spark/org/apache/ignite/examples/ml/mleap/MLeapModelParserExample.java:[45,56]
>  cannot find symbol
>   symbol:   class MLeapModelParser
>   location: class org.apache.ignite.examples.ml.mleap.MLeapModelParserExample
> {code}
>  
> Release build - 
> https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-11282) NullPointerException if transaction enabled and using byte[] for key/value

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-11282:
-
Fix Version/s: 2.8

> NullPointerException if transaction enabled and using byte[] for key/value
> --
>
> Key: IGNITE-11282
> URL: https://issues.apache.org/jira/browse/IGNITE-11282
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Courtney
>Assignee: Igor Akkuratov
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: Screen Shot 2019-02-10 at 15.02.19.png
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> I have debugged this and found the problem is because of hashCode comparison 
> failure. You can see in the screenshot below. 
> {code:java}
> txMap == null ? null : txMap.get(key)
> {code}
> this will fail to get the entry but they the key is in fact in the map, it's 
> the only entry and if a proper array comparison is done e.g. using 
> `Arrays.equals` as shown in the eval window then the key would match. !Screen 
> Shot 2019-02-10 at 15.02.19.png!
> If running without `-ea` then the exception is
> {code:java}
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at 
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at 
> java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
> at 
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632)
> at 
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at 
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at 
> io.hypi.arc.ignite.ArcIgniteUtils.lambda$asFuture$f0cf812f$1(ArcIgniteUtils.java:21)
> at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:215)
> at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:179)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at 
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at 
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at 
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at 
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:300)
> at 
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:287)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at 
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at 
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at 
> 

[jira] [Updated] (IGNITE-12587) ML examples failed on start

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-12587:
-
Fix Version/s: 2.9

> ML examples failed on start
> ---
>
> Key: IGNITE-12587
> URL: https://issues.apache.org/jira/browse/IGNITE-12587
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.8
> Environment: Java 8
> Linux/Win
>Reporter: Stepan Pilschikov
>Assignee: Alexey Zinoviev
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> New release build comes with lost data sets for ML 2.8
> Steps:
> - Try to run any ML examples used MLSandboxDatasets 
> (org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample
>  for examples)
> Actual:
> - FileNotFoundException
> {code}
> Exception in thread "main" java.io.FileNotFoundException: 
> modules/ml/src/main/resources/datasets/boston_housing_dataset.txt
>   at 
> org.apache.ignite.ml.util.SandboxMLCache.fillCacheWith(SandboxMLCache.java:119)
>   at 
> org.apache.ignite.examples.ml.environment.TrainingWithCustomPreprocessorsExample.main(TrainingWithCustomPreprocessorsExample.java:62)
> {code}
> Release build - 
> https://ci.ignite.apache.org/viewLog.html?buildId=4957767=Releases_ApacheIgniteMain_ReleaseBuild=artifacts_Releases_ApacheIgniteMain=ignite-2.8



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13143) Persistent store defragmentation

2020-11-16 Thread Maxim Muzafarov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-13143:
-
Fix Version/s: 2.10

> Persistent store defragmentation
> 
>
> Key: IGNITE-13143
> URL: https://issues.apache.org/jira/browse/IGNITE-13143
> Project: Ignite
>  Issue Type: New Feature
>  Components: persistence
>Reporter: Sergey Chugunov
>Priority: Major
>  Labels: IEP-47, important
> Fix For: 2.10
>
>
> Persistent store enables users to store data of their caches in a durable 
> fashion on disk still benefiting from in-memory nature of Apache Ignite. Data 
> of caches is stored in files created for every primary or backup partition 
> assigned to that node and in an additional file for all user indexes.
> Files in filesystem are allocated lazily (only if some data is actually 
> stored to particular partition) and grow automatically when more data is 
> added to the cache. But the problem is that files cannot shrink even if all 
> data is removed.
> This umbrella ticket covers all other tasks needed to implement simple yet 
> effective approach to defragmentation. Detailed discussion could be found in 
> [IEP-47|https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation]
>  and in corresponding [dev-list 
> discussion|http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-IEP-47-Native-persistence-defragmentation-td47717.html]
>  but core ideas are as follows:
>  # Defragmentation is performed in a special _maintenance_ mode when node 
> starts, provides access to some APIs like metrics or JMX management but 
> doesn't join the cluster.
>  # It is performed by copying all data from all partitions on node to new 
> files with automatic compaction. After successful copy old partition files 
> are deleted.
>  # Metrics on progress of the operation are provided to the user.
>  # Operation is fault-tolerant and in case of node failure proceeds after 
> node restart.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13701) SQL Indexes,Tables and Schemas views in IEP-35 changed amount, order of columns and content

2020-11-16 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232813#comment-17232813
 ] 

Ignite TC Bot commented on IGNITE-13701:


{panel:title=Branch: [pull/8451/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8451/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=5733162buildTypeId=IgniteTests24Java8_RunAll]

> SQL Indexes,Tables and Schemas views in IEP-35 changed amount, order of 
> columns and content
> ---
>
> Key: IGNITE-13701
> URL: https://issues.apache.org/jira/browse/IGNITE-13701
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://issues.apache.org/jira/browse/IGNITE-12213 broke backward 
> compatibility:
>   * {{CACHE_GROUP_ID}} and {{CACHE_GROUP_NAME}} columns was removed from the 
> {{INDEXES}} view.
>   * {{CACHE_GROUP_ID}} and {{CACHE_GROUP_NAME}} columns was removed from the 
> {{TABLES}} view.
>   * {{SCHEMA_NAME}} column was renamed to {{NAME}} for the {{SCHEMAS}} view.
>   * {{PREDEFINED}} column was added to the {{SCHEMAS}} view.
> Default columns order was changed.
> Also content of {{SCHEMAS}} view has changed in a wrong way: now view 
> contains proxy indexes (it is simply wrapper and implementation detail) and 
> indexes for cache key displays as {{PK}} index (it is incorrect, because 
> {{PK}} index could be only for table and this kind of indexes is 
> implementation detail).
> This behavior should be replaced by previous one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13709) Control.sh API - status

2020-11-16 Thread Ivan Bessonov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Bessonov updated IGNITE-13709:
---
Description: 
_Prerequisites:_ command can be sent to nodes in maintenance mode and in normal 
operations as well.
 
_Command output:_
 # For node in normal operations:
defragmentation is scheduled for caches: 


 # For node in maintenance mode executing defragmentation:
defragmentation is completed for the caches:
    cache0 - size before/after: 200GB/150GB, time took: 15 mins 42 secs
defragmentation is in progress for cache:
    cache1 - partitions processed/all: 177/512, time elapsed: 7 mins 11 secs
awaiting defragmentation: cache2, cache3, cache4.


 # For node in maintenance mode for other reason:
no defragmentation is scheduled for the node, the node is in maintenance to 
perform tasks: 

> Control.sh API - status
> ---
>
> Key: IGNITE-13709
> URL: https://issues.apache.org/jira/browse/IGNITE-13709
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Labels: IEP-47
>
> _Prerequisites:_ command can be sent to nodes in maintenance mode and in 
> normal operations as well.
>  
> _Command output:_
>  # For node in normal operations:
> defragmentation is scheduled for caches: 
>  # For node in maintenance mode executing defragmentation:
> defragmentation is completed for the caches:
>     cache0 - size before/after: 200GB/150GB, time took: 15 mins 42 secs
> defragmentation is in progress for cache:
>     cache1 - partitions processed/all: 177/512, time elapsed: 7 mins 11 secs
> awaiting defragmentation: cache2, cache3, cache4.
>  # For node in maintenance mode for other reason:
> no defragmentation is scheduled for the node, the node is in maintenance to 
> perform tasks: 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13709) Control.sh API - status

2020-11-16 Thread Ivan Bessonov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Bessonov updated IGNITE-13709:
---
Labels: IEP-47  (was: )

> Control.sh API - status
> ---
>
> Key: IGNITE-13709
> URL: https://issues.apache.org/jira/browse/IGNITE-13709
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Labels: IEP-47
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (IGNITE-13709) Control.sh API - status

2020-11-16 Thread Ivan Bessonov (Jira)
Ivan Bessonov created IGNITE-13709:
--

 Summary: Control.sh API - status
 Key: IGNITE-13709
 URL: https://issues.apache.org/jira/browse/IGNITE-13709
 Project: Ignite
  Issue Type: Sub-task
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13697) Control.sh API - schedule & cancel

2020-11-16 Thread Ivan Bessonov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Bessonov updated IGNITE-13697:
---
Description: 
 
 From original draft by [~sergeychugunov]:
  
 Schedule
 *control.sh defragmentation schedule nodes 
nodeConsistentId0[,nodeConsistentId1] [caches cacheName0,cacheName1,cacheName2]*
  
 Optional list of caches is passed to perform defragmentation for a particular 
set of caches. By default all caches are defragmented.
  
 _Prerequisites_: command is sent to node in normal operations, node in 
maintenance mode should not accept it

_Command output:_
 Defragmentation is successfully scheduled on nodes , on next 
restart the following caches will be defragmented: .
 Cancel
 *control.sh defragmentation cancel nodeHost nodePort [cache cacheName0]*

_Prerequisites_: command is sent to node in maintenance mode or in normal mode

_Command output:_
 Defragmentation is already completed for caches: 
 Defragmentation is cancelled for caches: ; all intermediate files 
are cleaned up.
  
 *Note:* Caches list for cancel command will not be implemented here.

  was:
 
>From original draft by [~sergeychugunov]:
 
Schedule
*control.sh defragmentation schedule nodes 
nodeConsistentId0[,nodeConsistentId1] [caches cacheName0,cacheName1,cacheName2]*
 
Optional list of caches is passed to perform defragmentation for a particular 
set of caches. By default all caches are defragmented.
 
_Prerequisites_: command is sent to node in normal operations, node in 
maintenance mode should not accept it

_Command output:_
Defragmentation is successfully scheduled on nodes , on next 
restart the following caches will be defragmented: .
Cancel
*control.sh defragmentation cancel nodeHost nodePort [cache cacheName0]*

_Prerequisites_: command is sent to node in maintenance mode, node in normal 
operations should not accept it.

_Command output:_
Defragmentation is already completed for caches: 
Defragmentation is cancelled for caches: ; all intermediate files 
are cleaned up.
 
*Note:* Caches list for cancel command will not be implemented here.


> Control.sh API - schedule & cancel
> --
>
> Key: IGNITE-13697
> URL: https://issues.apache.org/jira/browse/IGNITE-13697
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Labels: IEP-47
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
>  
>  From original draft by [~sergeychugunov]:
>   
>  Schedule
>  *control.sh defragmentation schedule nodes 
> nodeConsistentId0[,nodeConsistentId1] [caches 
> cacheName0,cacheName1,cacheName2]*
>   
>  Optional list of caches is passed to perform defragmentation for a 
> particular set of caches. By default all caches are defragmented.
>   
>  _Prerequisites_: command is sent to node in normal operations, node in 
> maintenance mode should not accept it
> _Command output:_
>  Defragmentation is successfully scheduled on nodes , on next 
> restart the following caches will be defragmented: .
>  Cancel
>  *control.sh defragmentation cancel nodeHost nodePort [cache cacheName0]*
> _Prerequisites_: command is sent to node in maintenance mode or in normal mode
> _Command output:_
>  Defragmentation is already completed for caches: 
>  Defragmentation is cancelled for caches: ; all intermediate 
> files are cleaned up.
>   
>  *Note:* Caches list for cancel command will not be implemented here.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13336) .NET: Misleading LINQ exception when expression can't be translated

2020-11-16 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232767#comment-17232767
 ] 

Ignite TC Bot commented on IGNITE-13336:


{panel:title=Branch: [pull/8459/head] Base: [master] : Possible Blockers 
(26)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests 4 TIMEOUT , Out Of Memory 
Error , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5737641]]
* IgniteCacheRestartTestSuite: 
GridCachePartitionedOptimisticTxNodeRestartTest.testRestartWithTxPutAllTenNodesTwoBackups
 - Test has low fail rate in base branch 3,6% and is not flaky
* IgniteCacheRestartTestSuite: 
GridCachePartitionedOptimisticTxNodeRestartTest.testRestartWithTxTenNodesTwoBackups
 - Test has low fail rate in base branch 3,6% and is not flaky
* IgniteCacheRestartTestSuite: 
GridCachePartitionedOptimisticTxNodeRestartTest.testRestartWithTxSixNodesTwoBackups
 - Test has low fail rate in base branch 3,6% and is not flaky
* IgniteCacheRestartTestSuite: 
GridCachePartitionedOptimisticTxNodeRestartTest.testRestartWithTxEightNodesTwoBackups
 - Test has low fail rate in base branch 3,6% and is not flaky

{color:#d04437}MVCC Cache 8{color} [[tests 0 Out Of Memory Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=5737686]]

{color:#d04437}Queries 2{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5737609]]

{color:#d04437}MVCC Queries{color} [[tests 0 Out Of Memory Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=5737629]]

{color:#d04437}JDBC Driver{color} [[tests 7 Out Of Memory Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=5737606]]
* IgniteJdbcDriverTestSuite: JdbcConnectionSelfTest.testDefaults - Test has low 
fail rate in base branch 0,0% and is not flaky
* IgniteJdbcDriverTestSuite: JdbcConnectionSelfTest.testNodeId - Test has low 
fail rate in base branch 0,0% and is not flaky
* IgniteJdbcDriverTestSuite: JdbcConnectionSelfTest.testCustomCache - Test has 
low fail rate in base branch 0,0% and is not flaky
* IgniteJdbcDriverTestSuite: JdbcConnectionSelfTest.testCustomPort - Test has 
low fail rate in base branch 0,0% and is not flaky
* org.apache.ignite.jdbc.suite.IgniteJdbcDriverTestSuite: 
org.apache.ignite.qa.query.WarningOnBigQueryResultsTest. - History for base 
branch is absent.
* IgniteJdbcDriverTestSuite: 
JdbcThinConnectionPropertiesTest.testNamePrefixDriverPropertyInfo - Test has 
low fail rate in base branch 0,0% and is not flaky
* IgniteJdbcDriverTestSuite: 
JdbcThinConnectionPropertiesTest.testPrefixedPropertiesApplicable - Test has 
low fail rate in base branch 0,0% and is not flaky

{color:#d04437}MVCC PDS 4{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit 
Code |https://ci.ignite.apache.org/viewLog.html?buildId=5737691]]

{color:#d04437}MVCC Cache 9{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5737687]]

{color:#d04437}PDS (Indexing){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5737659]]
* IgnitePdsWithIndexingCoreTestSuite: 
IgnitePdsBinaryMetadataAsyncWritingTest.testPutRequestFromServerCompletesIfMetadataWriteHangOnBackup
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cache (Deadlock Detection){color} [[tests 1 TIMEOUT , Out Of 
Memory Error , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5737633]]
* TxDeadlockDetectionTestSuite: 
TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}MVCC Cache 2{color} [[tests 2 TIMEOUT , Out Of Memory Error , 
Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5737680]]
* IgniteCacheMvccTestSuite2: 
GridCacheDhtPreloadUnloadSelfTest.testUnloadZeroBackupsTwoNodes - Test has low 
fail rate in base branch 0,0% and is not flaky
* IgniteCacheMvccTestSuite2: 
GridCacheDhtPreloadUnloadSelfTest.testUnloadOneBackupTwoNodes - Test has low 
fail rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5737665]]
* exe: CacheTest.TestCacheWithExpirationDoesNotAffectKeepBinarySettings - Test 
has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Start Nodes{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5737612]]
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - Test has low fail 
rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/8459/head] Base: [master] : New Tests 
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=5737666]]
* {color:#013220}dll: CacheLinqTest.TestInvokeThrowsNotSupportedException - 
PASSED{color}
* {color:#013220}dll: 

[jira] [Updated] (IGNITE-12509) CACHE_REBALANCE_STOPPED event raises for wrong caches in case of specified RebalanceDelay

2020-11-16 Thread Yaroslav Molochkov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yaroslav Molochkov updated IGNITE-12509:

Fix Version/s: (was: 2.9.1)
   (was: 2.10)

> CACHE_REBALANCE_STOPPED event raises for wrong caches in case of specified 
> RebalanceDelay
> -
>
> Key: IGNITE-12509
> URL: https://issues.apache.org/jira/browse/IGNITE-12509
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Rakov
>Assignee: Yaroslav Molochkov
>Priority: Major
>  Labels: 2.9.1-rc, newbie
> Attachments: RebalanceDelayTest.java
>
>
> Steps to reproduce:
> 1. Start in-memory cluster with 2 server nodes
> 2. Start 3 caches with different rebalance delays (e.g. 5, 10 and 15 seconds) 
> and upload some data
> 3. Start localListener for EVT_CACHE_REBALANCE_STOPPED event on one of the 
> nodes.
> 4. Start one more server node.
> 5. Wait for 5 seconds, till rebalance delay is reached.
> 6. EVT_CACHE_REBALANCE_STOPPED event received 3 times (1 for each cache), but 
> in fact only 1 cache was rebalanced. The same happens for the rest of the 
> caches.
> As result on rebalance finish we're getting event for each cache 
> [CACHE_COUNT] times, instead of 1.
> Reproducer attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-12509) CACHE_REBALANCE_STOPPED event raises for wrong caches in case of specified RebalanceDelay

2020-11-16 Thread Yaroslav Molochkov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yaroslav Molochkov updated IGNITE-12509:

Labels: newbie  (was: 2.9.1-rc newbie)

> CACHE_REBALANCE_STOPPED event raises for wrong caches in case of specified 
> RebalanceDelay
> -
>
> Key: IGNITE-12509
> URL: https://issues.apache.org/jira/browse/IGNITE-12509
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Rakov
>Assignee: Yaroslav Molochkov
>Priority: Major
>  Labels: newbie
> Attachments: RebalanceDelayTest.java
>
>
> Steps to reproduce:
> 1. Start in-memory cluster with 2 server nodes
> 2. Start 3 caches with different rebalance delays (e.g. 5, 10 and 15 seconds) 
> and upload some data
> 3. Start localListener for EVT_CACHE_REBALANCE_STOPPED event on one of the 
> nodes.
> 4. Start one more server node.
> 5. Wait for 5 seconds, till rebalance delay is reached.
> 6. EVT_CACHE_REBALANCE_STOPPED event received 3 times (1 for each cache), but 
> in fact only 1 cache was rebalanced. The same happens for the rest of the 
> caches.
> As result on rebalance finish we're getting event for each cache 
> [CACHE_COUNT] times, instead of 1.
> Reproducer attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-13708) Add thin client support for Spring Transactions.

2020-11-16 Thread Mikhail Petrov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Petrov reassigned IGNITE-13708:
---

Assignee: Mikhail Petrov

> Add thin client support for Spring Transactions.
> 
>
> Key: IGNITE-13708
> URL: https://issues.apache.org/jira/browse/IGNITE-13708
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
>
> It's needed to add thin client support for Spring Transactions. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13336) .NET: Misleading LINQ exception when expression can't be translated

2020-11-16 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232687#comment-17232687
 ] 

Ignite TC Bot commented on IGNITE-13336:


{panel:title=Branch: [pull/8459/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8459/head] Base: [master] : New Tests 
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=5733197]]
* {color:#013220}dll: CacheLinqTest.TestInvokeThrowsNotSupportedException - 
PASSED{color}
* {color:#013220}dll: 
CacheLinqTestSqlEscapeAll.TestInvokeThrowsNotSupportedException - PASSED{color}
* {color:#013220}dll: 
CacheLinqTestSimpleName.TestInvokeThrowsNotSupportedException - PASSED{color}

{color:#8b}Platform .NET{color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=5733195]]
* {color:#013220}exe: CacheLinqTest.TestInvokeThrowsNotSupportedException - 
PASSED{color}
* {color:#013220}exe: CacheLinqTest.TestInvokeThrowsNotSupportedException - 
PASSED{color}
* {color:#013220}exe: CacheLinqTest.TestInvokeThrowsNotSupportedException - 
PASSED{color}

{panel}
[TeamCity *- Run :: .NET* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5733200buildTypeId=IgniteTests24Java8_RunAllNet]

> .NET: Misleading LINQ exception when expression can't be translated
> ---
>
> Key: IGNITE-13336
> URL: https://issues.apache.org/jira/browse/IGNITE-13336
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.8.1
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Minor
>  Labels: .NET
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The following program results in a cryptic exception, when the problem is 
> simply lack of Expression<> wrapper around the query filter:
> {code}
> class Program
> {
> private static readonly IIgnite Ignite = Ignition.Start();
> static void Main(string[] args)
> {
> var cache = GetCache();
> cache["1"] = new Foo();
> var res = Where2(e => e.Value.X == 0);
> Console.WriteLine(res);
> }
> public static ICache GetCache()
> {
> var cacheName = typeof(T).Name;
> var cfg = new CacheConfiguration(cacheName, new 
> QueryEntity(typeof(T)));
> return Ignite.GetOrCreateCache(cfg);
> }
> public static List Where2(Func, bool> 
> query)
> {
> var queryResult = GetCache().AsCacheQueryable().Where(x => 
> query(x));
> return queryResult.Select(x => x.Value).ToList();
> }
> }
> public class Foo
> {
> [QuerySqlField] public int X { get; set; }
> }
> {code}
> We should throw a better exception that says "LINQ expression can't be 
> translated to SQL because of ..."



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-2292) .NET: Add ability to build .NET platform from Maven

2020-11-16 Thread Pavel Tupitsyn (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-2292:
--

Assignee: Pavel Tupitsyn

> .NET: Add ability to build .NET platform from Maven
> ---
>
> Key: IGNITE-2292
> URL: https://issues.apache.org/jira/browse/IGNITE-2292
> Project: Ignite
>  Issue Type: Task
>  Components: general, platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .net
>
> Currently build procedure looks as follows:
> 1) Java is built from Maven
> 2) .NET is built manually using modules/platforms/dotnet/mkbuild.cmd
> 3) Docs fo Java, .NET and CPP are built form Maven
> Looks like we should intergrate .NET buld into Maven process so that user can 
> build the whole product with a single command. E.g.:
> {code}mvn clean package [java_build_args] -Dignite.net.docs=true 
> -Dignite.net.build =true -Dignite.net.build.x86=true 
> -Dignite.net.build.x86.javaHome=[path to x86 JDK]{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-6599) .NET: IgniteConfiguration.ClusterName

2020-11-16 Thread Peter Ivanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ivanov reassigned IGNITE-6599:


Assignee: Pavel Tupitsyn  (was: Peter Ivanov)

> .NET: IgniteConfiguration.ClusterName
> -
>
> Key: IGNITE-6599
> URL: https://issues.apache.org/jira/browse/IGNITE-6599
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, newbie
>
> Propagate from Java: IGNITE-6597



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-6599) .NET: IgniteConfiguration.ClusterName

2020-11-16 Thread Peter Ivanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ivanov reassigned IGNITE-6599:


Assignee: Peter Ivanov  (was: Pavel Tupitsyn)

> .NET: IgniteConfiguration.ClusterName
> -
>
> Key: IGNITE-6599
> URL: https://issues.apache.org/jira/browse/IGNITE-6599
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Peter Ivanov
>Priority: Minor
>  Labels: .NET, newbie
>
> Propagate from Java: IGNITE-6597



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-6599) .NET: IgniteConfiguration.ClusterName

2020-11-16 Thread Peter Ivanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ivanov reassigned IGNITE-6599:


Assignee: Pavel Tupitsyn  (was: Peter Ivanov)

> .NET: IgniteConfiguration.ClusterName
> -
>
> Key: IGNITE-6599
> URL: https://issues.apache.org/jira/browse/IGNITE-6599
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, newbie
>
> Propagate from Java: IGNITE-6597



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-6599) .NET: IgniteConfiguration.ClusterName

2020-11-16 Thread Peter Ivanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ivanov reassigned IGNITE-6599:


Assignee: Peter Ivanov  (was: Pavel Tupitsyn)

> .NET: IgniteConfiguration.ClusterName
> -
>
> Key: IGNITE-6599
> URL: https://issues.apache.org/jira/browse/IGNITE-6599
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Peter Ivanov
>Priority: Minor
>  Labels: .NET, newbie
>
> Propagate from Java: IGNITE-6597



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-12489) Error during purges by expiration: Unknown page type

2020-11-16 Thread Alexey Goncharuk (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232646#comment-17232646
 ] 

Alexey Goncharuk commented on IGNITE-12489:
---

The changes look good to me, thanks for tackling this issue!

> Error during purges by expiration: Unknown page type
> 
>
> Key: IGNITE-12489
> URL: https://issues.apache.org/jira/browse/IGNITE-12489
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7, 2.7.6
>Reporter: Ruslan Kamashev
>Assignee: Nikita Tolstunov
>Priority: Blocker
> Fix For: 2.10
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> {{*logger*}}
> {code:java}
> org.apache.ignite.internal.processors.cache.GridCacheIoManager
> {code}
> {{*message*}}
> {code:java}
> Failed to process message [senderId=969d56ba-4b46-40cf-886e-ac445cf6a95d, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest]{code}
> {{*thread*}}
> {code:java}
> sys-stripe-19-#20{code}
> {{*trace*}}
> {code:java}
> java.lang.IllegalStateException: Unknown page type: 1 pageId: 00010303117d
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.io(BPlusTree.java:5058)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$200(BPlusTree.java:90)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5330)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5566)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpiredInternal(GridCacheOffheapManager.java:2232)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpired(GridCacheOffheapManager.java:2157)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.expire(GridCacheOffheapManager.java:845)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:207)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:888)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessageProcessed(GridCacheIoManager.java:1103)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1076)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>   at java.lang.Thread.run(Thread.java:748)
>   Dec 23, 2019 @ 18:28:28.457 {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13336) .NET: Misleading LINQ exception when expression can't be translated

2020-11-16 Thread Pavel Tupitsyn (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232620#comment-17232620
 ] 

Pavel Tupitsyn commented on IGNITE-13336:
-

[~gurustron] looks good to me.

Please make sure to get a TeamCity "visa" before merging.

> .NET: Misleading LINQ exception when expression can't be translated
> ---
>
> Key: IGNITE-13336
> URL: https://issues.apache.org/jira/browse/IGNITE-13336
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.8.1
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Minor
>  Labels: .NET
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The following program results in a cryptic exception, when the problem is 
> simply lack of Expression<> wrapper around the query filter:
> {code}
> class Program
> {
> private static readonly IIgnite Ignite = Ignition.Start();
> static void Main(string[] args)
> {
> var cache = GetCache();
> cache["1"] = new Foo();
> var res = Where2(e => e.Value.X == 0);
> Console.WriteLine(res);
> }
> public static ICache GetCache()
> {
> var cacheName = typeof(T).Name;
> var cfg = new CacheConfiguration(cacheName, new 
> QueryEntity(typeof(T)));
> return Ignite.GetOrCreateCache(cfg);
> }
> public static List Where2(Func, bool> 
> query)
> {
> var queryResult = GetCache().AsCacheQueryable().Where(x => 
> query(x));
> return queryResult.Select(x => x.Value).ToList();
> }
> }
> public class Foo
> {
> [QuerySqlField] public int X { get; set; }
> }
> {code}
> We should throw a better exception that says "LINQ expression can't be 
> translated to SQL because of ..."



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (IGNITE-13708) Add thin client support for Spring Transactions.

2020-11-16 Thread Mikhail Petrov (Jira)
Mikhail Petrov created IGNITE-13708:
---

 Summary: Add thin client support for Spring Transactions.
 Key: IGNITE-13708
 URL: https://issues.apache.org/jira/browse/IGNITE-13708
 Project: Ignite
  Issue Type: Improvement
Reporter: Mikhail Petrov


It's needed to add thin client support for Spring Transactions. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)