[jira] [Commented] (IGNITE-4800) Lucene query may fails with NPE.

[ https://issues.apache.org/jira/browse/IGNITE-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114878#comment-16114878 ] Dmitriy Pavlov commented on IGNITE-4800: Could you please check failures on TC in master

[jira] [Commented] (IGNITE-5851) Automatically activate cluster if baseline topology is reached

[ https://issues.apache.org/jira/browse/IGNITE-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114872#comment-16114872 ] Dmitriy Pavlov commented on IGNITE-5851: See also design proposal

[jira] [Updated] (IGNITE-4181) The several runs of ServicesExample causes NPE

[ https://issues.apache.org/jira/browse/IGNITE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Sorokin updated IGNITE-4181: Fix Version/s: (was: 2.2) 2.1 > The several runs of ServicesExample

[jira] [Commented] (IGNITE-5926) Puts on near cache hangs

[ https://issues.apache.org/jira/browse/IGNITE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114848#comment-16114848 ] vinay commented on IGNITE-5926: --- This is just a thought that near caches will mostly have very frequent

[jira] [Created] (IGNITE-5947) ClassCastException when two-dimensional array is fetched from cache

Valentin Kulichenko created IGNITE-5947: --- Summary: ClassCastException when two-dimensional array is fetched from cache Key: IGNITE-5947 URL: https://issues.apache.org/jira/browse/IGNITE-5947

[jira] [Updated] (IGNITE-5947) ClassCastException when two-dimensional array is fetched from cache

[ https://issues.apache.org/jira/browse/IGNITE-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-5947: Attachment: TestMain.java > ClassCastException when two-dimensional array is

[jira] [Updated] (IGNITE-5946) Ignite WebSessions: Flaky failure for WebSessionSelfTest.testClientReconnectRequest() and subclasses

[ https://issues.apache.org/jira/browse/IGNITE-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5946: --- Description: Success rate on Teamcity is ~63%

[jira] [Updated] (IGNITE-3663) Failed test: Sporadic failures to WebSessionSelfTest.testSessionRenewalDuringLogin()

[ https://issues.apache.org/jira/browse/IGNITE-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-3663: --- Labels: Muted_test (was: ) > Failed test: Sporadic failures to >

[jira] [Created] (IGNITE-5946) Ignite WebSessions: Flaky failure for WebSessionSelfTest.testClientReconnectRequest() and subclasses

Dmitriy Pavlov created IGNITE-5946: -- Summary: Ignite WebSessions: Flaky failure for WebSessionSelfTest.testClientReconnectRequest() and subclasses Key: IGNITE-5946 URL:

[jira] [Updated] (IGNITE-5549) Ignite Cache Failover2: test suite hands up from CacheAsyncOperationsFailoverTxTest.testAsyncFailover()

[ https://issues.apache.org/jira/browse/IGNITE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5549: --- Attachment: ThreadDump0.log > Ignite Cache Failover2: test suite hands up from >

[jira] [Updated] (IGNITE-5549) Ignite Cache Failover2: test suite hands up from CacheAsyncOperationsFailoverTxTest.testAsyncFailover()

[ https://issues.apache.org/jira/browse/IGNITE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5549: --- Priority: Critical (was: Major) > Ignite Cache Failover2: test suite hands up from >

[jira] [Updated] (IGNITE-5549) Ignite Cache Failover2: test suite hands up from CacheAsyncOperationsFailoverTxTest.testAsyncFailover()

[ https://issues.apache.org/jira/browse/IGNITE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5549: --- Affects Version/s: 2.1 > Ignite Cache Failover2: test suite hands up from >

[jira] [Updated] (IGNITE-5549) Ignite Cache Failover2: test suite hands up for more than 2 hours

[ https://issues.apache.org/jira/browse/IGNITE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5549: --- Description: Timeout came from CacheAsyncOperationsFailoverTxTest.testAsyncFailover() test:

[jira] [Updated] (IGNITE-5549) Ignite Cache Failover2: test suite hands up from CacheAsyncOperationsFailoverTxTest.testAsyncFailover() t

[ https://issues.apache.org/jira/browse/IGNITE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5549: --- Summary: Ignite Cache Failover2: test suite hands up from

[jira] [Updated] (IGNITE-5549) Ignite Cache Failover2: test suite hands up from CacheAsyncOperationsFailoverTxTest.testAsyncFailover()

[ https://issues.apache.org/jira/browse/IGNITE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5549: --- Fix Version/s: 2.2 > Ignite Cache Failover2: test suite hands up from >

[jira] [Updated] (IGNITE-5549) Ignite Cache Failover2: test suite hands up from CacheAsyncOperationsFailoverTxTest.testAsyncFailover()

[ https://issues.apache.org/jira/browse/IGNITE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5549: --- Summary: Ignite Cache Failover2: test suite hands up from

[jira] [Updated] (IGNITE-5945) Flaky failure in IgniteCache 5: IgniteCacheAtomicProtocolTest.testPutReaderUpdate2

[ https://issues.apache.org/jira/browse/IGNITE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5945: --- Labels: MakeTeamcityGreenAgain (was: ) > Flaky failure in IgniteCache 5: >

[jira] [Created] (IGNITE-5945) Flaky failure in IgniteCache 5: IgniteCacheAtomicProtocolTest.testPutReaderUpdate2

Dmitriy Pavlov created IGNITE-5945: -- Summary: Flaky failure in IgniteCache 5: IgniteCacheAtomicProtocolTest.testPutReaderUpdate2 Key: IGNITE-5945 URL: https://issues.apache.org/jira/browse/IGNITE-5945

[jira] [Commented] (IGNITE-4931) Safe way for deactivate cluster

[ https://issues.apache.org/jira/browse/IGNITE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114579#comment-16114579 ] Dmitriy Pavlov commented on IGNITE-4931: Following tests were muted with link to this issue:

[jira] [Updated] (IGNITE-4931) Safe way for deactivate cluster

[ https://issues.apache.org/jira/browse/IGNITE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-4931: --- Labels: MakeTeamcityGreenAgain Muted_test (was: ) > Safe way for deactivate cluster >

[jira] [Updated] (IGNITE-5841) Ignite SPI Suite: testReconnectAfterFailTopologyChanged() test failure with assertions

[ https://issues.apache.org/jira/browse/IGNITE-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5841: --- Affects Version/s: 2.1 > Ignite SPI Suite: testReconnectAfterFailTopologyChanged() test

[jira] [Updated] (IGNITE-5841) Ignite SPI Suite: testReconnectAfterFailTopologyChanged() test failure with assertions

[ https://issues.apache.org/jira/browse/IGNITE-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5841: --- Fix Version/s: 2.2 > Ignite SPI Suite: testReconnectAfterFailTopologyChanged() test failure

[jira] [Updated] (IGNITE-5944) Ignite 1.9 can't be started with configured IGFS and Hadoop secondary system

[ https://issues.apache.org/jira/browse/IGNITE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Cherkasov updated IGNITE-5944: -- Attachment: pradeep-config.xml IGFSExample.java > Ignite 1.9 can't be

[jira] [Updated] (IGNITE-5944) Ignite 1.9 can't be started with configured IGFS and Hadoop secondary system

[ https://issues.apache.org/jira/browse/IGNITE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Cherkasov updated IGNITE-5944: -- Description: (was: I can't run example) > Ignite 1.9 can't be started with

[jira] [Updated] (IGNITE-5944) Ignite 1.9 can't be started with configured IGFS and Hadoop secondary system

[ https://issues.apache.org/jira/browse/IGNITE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Cherkasov updated IGNITE-5944: -- Description: I can't run example > Ignite 1.9 can't be started with configured IGFS

[jira] [Resolved] (IGNITE-5944) Ignite 1.9 can't be started with configured IGFS and Hadoop secondary system

[ https://issues.apache.org/jira/browse/IGNITE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Cherkasov resolved IGNITE-5944. --- Resolution: Cannot Reproduce it works fine with 2.0.0 > Ignite 1.9 can't be started

[jira] [Created] (IGNITE-5944) Ignite 1.9 can't be started with configured IGFS and Hadoop secondary system

Mikhail Cherkasov created IGNITE-5944: - Summary: Ignite 1.9 can't be started with configured IGFS and Hadoop secondary system Key: IGNITE-5944 URL: https://issues.apache.org/jira/browse/IGNITE-5944

[jira] [Comment Edited] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

[ https://issues.apache.org/jira/browse/IGNITE-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114538#comment-16114538 ] Taras Ledkov edited comment on IGNITE-5384 at 8/4/17 3:47 PM: -- Looks like we

[jira] [Commented] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

[ https://issues.apache.org/jira/browse/IGNITE-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114538#comment-16114538 ] Taras Ledkov commented on IGNITE-5384: -- Looks like we must not implement date conversion explicitly

[jira] [Commented] (IGNITE-5842) ODBC: Make sure ODBC driver works correctly with RazorSQL.

[ https://issues.apache.org/jira/browse/IGNITE-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114531#comment-16114531 ] Igor Sapego commented on IGNITE-5842: - Found and fixed one more issue - IGNITE-5939 > ODBC: Make

[jira] [Commented] (IGNITE-5939) ODBC: SQLColAttributes should work with legacy attribute codes.

[ https://issues.apache.org/jira/browse/IGNITE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114528#comment-16114528 ] ASF GitHub Bot commented on IGNITE-5939: Github user isapego closed the pull request at:

[jira] [Updated] (IGNITE-5941) Index with long name stores incorrect

[ https://issues.apache.org/jira/browse/IGNITE-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-5941: -- Attachment: LongIndexNameTest.java > Index with long name stores incorrect >

[jira] [Commented] (IGNITE-4800) Lucene query may fails with NPE.

[ https://issues.apache.org/jira/browse/IGNITE-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114484#comment-16114484 ] ASF GitHub Bot commented on IGNITE-4800: Github user asfgit closed the pull request at:

[jira] [Commented] (IGNITE-5939) ODBC: SQLColAttributes should work with legacy attribute codes.

[ https://issues.apache.org/jira/browse/IGNITE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114482#comment-16114482 ] Pavel Tupitsyn commented on IGNITE-5939: [~isapego] looks good to me. > ODBC: SQLColAttributes

[jira] [Resolved] (IGNITE-5795) @AffinityKeyMapped ignored if QueryEntity used

[ https://issues.apache.org/jira/browse/IGNITE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin resolved IGNITE-5795. -- Resolution: Workaround I discussed this with [~vozerov] and confirmed we do not want

[jira] [Resolved] (IGNITE-5505) @AffinityKeyMapped annotation is ignored if class names are configured on BinaryConfiguration

[ https://issues.apache.org/jira/browse/IGNITE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin resolved IGNITE-5505. -- Resolution: Workaround See the comment above with a workaround provided >

[jira] [Commented] (IGNITE-5505) @AffinityKeyMapped annotation is ignored if class names are configured on BinaryConfiguration

[ https://issues.apache.org/jira/browse/IGNITE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114470#comment-16114470 ] Alexey Kukushkin commented on IGNITE-5505: -- I discussed this with [~vozerov] again and confirmed

[jira] [Updated] (IGNITE-5943) Communication. Server node may reject client connection during massive clients join

[ https://issues.apache.org/jira/browse/IGNITE-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-5943: - Description: There is a race between a client join discovery event on server nodes and

[jira] [Updated] (IGNITE-5943) Communication. Server node may reject client connection during massive clients join

[ https://issues.apache.org/jira/browse/IGNITE-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-5943: - Summary: Communication. Server node may reject client connection during massive clients

[jira] [Created] (IGNITE-5943) Communication. We could reject client connection while it has received EVT_NODE_JOINED

Eduard Shangareev created IGNITE-5943: - Summary: Communication. We could reject client connection while it has received EVT_NODE_JOINED Key: IGNITE-5943 URL: https://issues.apache.org/jira/browse/IGNITE-5943

[jira] [Created] (IGNITE-5942) Python3 pylibmc does not work with Ignite memcache mode

Mikhail Cherkasov created IGNITE-5942: - Summary: Python3 pylibmc does not work with Ignite memcache mode Key: IGNITE-5942 URL: https://issues.apache.org/jira/browse/IGNITE-5942 Project: Ignite

[jira] [Updated] (IGNITE-5938) Implement WAL logs compaction and compression after checkpoint

[ https://issues.apache.org/jira/browse/IGNITE-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-5938: --- Labels: Mak (was: ) > Implement WAL logs compaction and compression after

[jira] [Updated] (IGNITE-5938) Implement WAL logs compaction and compression after checkpoint

[ https://issues.apache.org/jira/browse/IGNITE-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-5938: --- Labels: (was: Mak) > Implement WAL logs compaction and compression after

[jira] [Updated] (IGNITE-5941) Index with long name stores incorrect

[ https://issues.apache.org/jira/browse/IGNITE-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-5941: -- Affects Version/s: 2.1 > Index with long name stores incorrect >

[jira] [Updated] (IGNITE-5931) .NET: Incorrect conflicting type error

[ https://issues.apache.org/jira/browse/IGNITE-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-5931: --- Priority: Critical (was: Major) > .NET: Incorrect conflicting type error >

[jira] [Commented] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[ https://issues.apache.org/jira/browse/IGNITE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114413#comment-16114413 ] Igor Seliverstov commented on IGNITE-5918: -- [~yzhdanov], [~vozerov], could you look at the

[jira] [Commented] (IGNITE-5931) .NET: Incorrect conflicting type error

[ https://issues.apache.org/jira/browse/IGNITE-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114414#comment-16114414 ] Pavel Tupitsyn commented on IGNITE-5931: Another related problem: {{AffinityKeyMappedAttribute}}

[jira] [Commented] (IGNITE-5658) Optimizations for data streamer

[ https://issues.apache.org/jira/browse/IGNITE-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114411#comment-16114411 ] Igor Seliverstov commented on IGNITE-5658: -- [~yzhdanov], could you look at the changes? >

[jira] [Resolved] (IGNITE-1577) IlligateStateException when removing index during stop

[ https://issues.apache.org/jira/browse/IGNITE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-1577. - Resolution: Won't Fix Doesn't appear to be a problem. > IlligateStateException when

[jira] [Closed] (IGNITE-1577) IlligateStateException when removing index during stop

[ https://issues.apache.org/jira/browse/IGNITE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1577. --- > IlligateStateException when removing index during stop >

[jira] [Commented] (IGNITE-5939) ODBC: SQLColAttributes should work with legacy attribute codes.

[ https://issues.apache.org/jira/browse/IGNITE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114402#comment-16114402 ] ASF GitHub Bot commented on IGNITE-5939: GitHub user isapego opened a pull request:

[jira] [Commented] (IGNITE-5382) SQL: frequent switch between schemas cause severe slowdown

[ https://issues.apache.org/jira/browse/IGNITE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114398#comment-16114398 ] Vladimir Ozerov commented on IGNITE-5382: - [~skalashnikov], IMO this approach is prone to leaks.

[jira] [Comment Edited] (IGNITE-425) Introduce transformers for continuous queries

[ https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109140#comment-16109140 ] Nikolay Izhikov edited comment on IGNITE-425 at 8/4/17 1:50 PM: PR -

[jira] [Commented] (IGNITE-5912) [Redis] EXPIRE/PEXPIRE on keys

[ https://issues.apache.org/jira/browse/IGNITE-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114346#comment-16114346 ] Roman Shtykh commented on IGNITE-5912: -- Hi [~anovikov], Thanks for checking the pr. Modified as you

[jira] [Assigned] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

[ https://issues.apache.org/jira/browse/IGNITE-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-5384: Assignee: Taras Ledkov > JDBC Driver: implement ResultSet#getDate(int, Calendar) >

[jira] [Updated] (IGNITE-5939) ODBC: SQLColAttributes should work with legacy attribute codes.

[ https://issues.apache.org/jira/browse/IGNITE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-5939: Description: According to

[jira] [Created] (IGNITE-5939) ODBC: SQLColAttributes should work with legacy attribute codes.

Igor Sapego created IGNITE-5939: --- Summary: ODBC: SQLColAttributes should work with legacy attribute codes. Key: IGNITE-5939 URL: https://issues.apache.org/jira/browse/IGNITE-5939 Project: Ignite

[jira] [Resolved] (IGNITE-5921) Reduce contention for free list access

[ https://issues.apache.org/jira/browse/IGNITE-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov resolved IGNITE-5921. -- Resolution: Duplicate > Reduce contention for free list access >

[jira] [Commented] (IGNITE-5921) Reduce contention for free list access

[ https://issues.apache.org/jira/browse/IGNITE-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114335#comment-16114335 ] Igor Seliverstov commented on IGNITE-5921: -- All works are done in scope of IGNITE-5658 > Reduce

[jira] [Resolved] (IGNITE-3656) JdbcConnection.setTransactionIsolation should not throw an exception

[ https://issues.apache.org/jira/browse/IGNITE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-3656. - Resolution: Duplicate > JdbcConnection.setTransactionIsolation should not throw an

[jira] [Commented] (IGNITE-4762) Support transactional updates in JDBC driver

[ https://issues.apache.org/jira/browse/IGNITE-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114333#comment-16114333 ] Vladimir Ozerov commented on IGNITE-4762: - NB: no TX support (or at least atomic updates) was

[jira] [Commented] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[ https://issues.apache.org/jira/browse/IGNITE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114324#comment-16114324 ] ASF GitHub Bot commented on IGNITE-5918: GitHub user gvvinblade opened a pull request:

[jira] [Assigned] (IGNITE-5658) Optimizations for data streamer

[ https://issues.apache.org/jira/browse/IGNITE-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov reassigned IGNITE-5658: Assignee: Igor Seliverstov (was: Yakov Zhdanov) > Optimizations for data

[jira] [Commented] (IGNITE-5658) Optimizations for data streamer

[ https://issues.apache.org/jira/browse/IGNITE-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114321#comment-16114321 ] ASF GitHub Bot commented on IGNITE-5658: GitHub user gvvinblade opened a pull request:

[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion

[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114310#comment-16114310 ] Ryabov Dmitrii commented on IGNITE-602: --- Thx for answer, [~agura]. Should I add hashcode only when

[jira] [Comment Edited] (IGNITE-3479) Coordinator(s) for global transaction ordering

[ https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114262#comment-16114262 ] Semen Boikov edited comment on IGNITE-3479 at 8/4/17 12:30 PM: --- This

[jira] [Assigned] (IGNITE-5938) Implement WAL logs compaction and compression after checkpoint

[ https://issues.apache.org/jira/browse/IGNITE-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin reassigned IGNITE-5938: -- Assignee: Dmitriy Govorukhin > Implement WAL logs compaction and compression

[jira] [Created] (IGNITE-5938) Implement WAL logs compaction and compression after checkpoint

Alexey Goncharuk created IGNITE-5938: Summary: Implement WAL logs compaction and compression after checkpoint Key: IGNITE-5938 URL: https://issues.apache.org/jira/browse/IGNITE-5938 Project:

[jira] [Updated] (IGNITE-3484) MVCC data structure for getAll operation

[ https://issues.apache.org/jira/browse/IGNITE-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-3484: - Description: Need implement some data structure to store/get multiple entry versions: -

[jira] [Commented] (IGNITE-5382) SQL: frequent switch between schemas cause severe slowdown

[ https://issues.apache.org/jira/browse/IGNITE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114290#comment-16114290 ] Sergey Kalashnikov commented on IGNITE-5382: [~vozerov] When thread closes its connection or

[jira] [Updated] (IGNITE-3484) MVCC data structure for getAll operation

[ https://issues.apache.org/jira/browse/IGNITE-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-3484: - Summary: MVCC data structure for getAll operation (was: MVCC for cache data structures) > MVCC

[jira] [Comment Edited] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion

[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114287#comment-16114287 ] Andrey Gura edited comment on IGNITE-602 at 8/4/17 12:13 PM: - Hi, [~SomeFire]

[jira] [Updated] (IGNITE-5936) Cleanup of not needed and committed versions

[ https://issues.apache.org/jira/browse/IGNITE-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-5936: - Description: At first committed data is stored in separate data structure.Need implement some

[jira] [Created] (IGNITE-5937) Mvcc data structure for SQL queries

Semen Boikov created IGNITE-5937: Summary: Mvcc data structure for SQL queries Key: IGNITE-5937 URL: https://issues.apache.org/jira/browse/IGNITE-5937 Project: Ignite Issue Type: Sub-task

[jira] [Updated] (IGNITE-5936) Cleanup of not needed and committed versions

[ https://issues.apache.org/jira/browse/IGNITE-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-5936: - Summary: Cleanup of not needed and committed versions (was: Cleanup of not needed versions) >

[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion

[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114287#comment-16114287 ] Andrey Gura commented on IGNITE-602: Hi, [~SomeFire] I think we can improve a couple of things in

[jira] [Updated] (IGNITE-5932) Integrate communication with coordinator in tx protocol

[ https://issues.apache.org/jira/browse/IGNITE-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-5932: - Description: Need integrate communication with coordinator in transactions protocol: - reading

[jira] [Resolved] (IGNITE-5290) Events might be missed during concurrent CQ registration and cache operations

[ https://issues.apache.org/jira/browse/IGNITE-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Tikhonov resolved IGNITE-5290. -- Resolution: Fixed Fixed by 42293fa sboikov on 29.05.2017 at

[jira] [Created] (IGNITE-5936) Cleanup of not needed versions

Semen Boikov created IGNITE-5936: Summary: Cleanup of not needed versions Key: IGNITE-5936 URL: https://issues.apache.org/jira/browse/IGNITE-5936 Project: Ignite Issue Type: Sub-task

[jira] [Commented] (IGNITE-5931) .NET: Incorrect conflicting type error

[ https://issues.apache.org/jira/browse/IGNITE-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114273#comment-16114273 ] Pavel Tupitsyn commented on IGNITE-5931: Another problem is that we return

[jira] [Commented] (IGNITE-5382) SQL: frequent switch between schemas cause severe slowdown

[ https://issues.apache.org/jira/browse/IGNITE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114270#comment-16114270 ] Vladimir Ozerov commented on IGNITE-5382: - [~skalashnikov], [~al.psc], any reason why we add

[jira] [Created] (IGNITE-5935) Integrate mvcc support in tx recovery protocol

Semen Boikov created IGNITE-5935: Summary: Integrate mvcc support in tx recovery protocol Key: IGNITE-5935 URL: https://issues.apache.org/jira/browse/IGNITE-5935 Project: Ignite Issue Type:

[jira] [Comment Edited] (IGNITE-5233) JDBC thin Driver: implement metadata support

[ https://issues.apache.org/jira/browse/IGNITE-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114231#comment-16114231 ] Taras Ledkov edited comment on IGNITE-5233 at 8/4/17 11:32 AM: --- I've

[jira] [Created] (IGNITE-5934) Integrate mvcc support in sql query protocol

Semen Boikov created IGNITE-5934: Summary: Integrate mvcc support in sql query protocol Key: IGNITE-5934 URL: https://issues.apache.org/jira/browse/IGNITE-5934 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-5930) Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers

[ https://issues.apache.org/jira/browse/IGNITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ksenia Rybakova updated IGNITE-5930: Affects Version/s: (was: 1.9) 2.1 > Long running transactions

[jira] [Created] (IGNITE-5933) Integrate mvcc support in cache.getAll protocol

Semen Boikov created IGNITE-5933: Summary: Integrate mvcc support in cache.getAll protocol Key: IGNITE-5933 URL: https://issues.apache.org/jira/browse/IGNITE-5933 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-5930) Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers

[ https://issues.apache.org/jira/browse/IGNITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ksenia Rybakova updated IGNITE-5930: Attachment: ignite-base-load-config.xml run-load.xml

[jira] [Commented] (IGNITE-3479) Coordinator(s) for global transaction ordering

[ https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114262#comment-16114262 ] Semen Boikov commented on IGNITE-3479: -- This assumes following tasks: - implement coordinator

[jira] [Assigned] (IGNITE-3479) Coordinator(s) for global transaction ordering

[ https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-3479: Assignee: Semen Boikov > Coordinator(s) for global transaction ordering >

[jira] [Created] (IGNITE-5932) Integrate communication with coordinator in tx protocol

Semen Boikov created IGNITE-5932: Summary: Integrate communication with coordinator in tx protocol Key: IGNITE-5932 URL: https://issues.apache.org/jira/browse/IGNITE-5932 Project: Ignite

[jira] [Created] (IGNITE-5931) .NET: Incorrect conflicting type error

Pavel Tupitsyn created IGNITE-5931: -- Summary: .NET: Incorrect conflicting type error Key: IGNITE-5931 URL: https://issues.apache.org/jira/browse/IGNITE-5931 Project: Ignite Issue Type: Bug

[jira] [Updated] (IGNITE-5930) Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers

[ https://issues.apache.org/jira/browse/IGNITE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ksenia Rybakova updated IGNITE-5930: Description: Load config: - CacheRandomOperation benchmark - Caches: atomic partitioned

[jira] [Created] (IGNITE-5930) Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers

Ksenia Rybakova created IGNITE-5930: --- Summary: Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers Key: IGNITE-5930 URL: https://issues.apache.org/jira/browse/IGNITE-5930

[jira] [Created] (IGNITE-5929) Add application name to query

Alexey Kuznetsov created IGNITE-5929: Summary: Add application name to query Key: IGNITE-5929 URL: https://issues.apache.org/jira/browse/IGNITE-5929 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-5648) NOT NULL constraint support for CREATE TABLE operator

[ https://issues.apache.org/jira/browse/IGNITE-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5648: Fix Version/s: (was: 2.3) 2.2 > NOT NULL constraint support for

[jira] [Updated] (IGNITE-3478) Transactional SQL (mvcc)

[ https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-3478: - Summary: Transactional SQL (mvcc) (was: Transactional SQL) > Transactional SQL (mvcc) >

[jira] [Commented] (IGNITE-5233) JDBC thin Driver: implement metadata support

[ https://issues.apache.org/jira/browse/IGNITE-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114231#comment-16114231 ] Taras Ledkov commented on IGNITE-5233: -- I've re-merged patch with master. [~vozerov], please review

[jira] [Updated] (IGNITE-3479) Coordinator(s) for global transaction ordering

[ https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-3479: - Summary: Coordinator(s) for global transaction ordering (was: Global transaction ordering) >

[jira] [Assigned] (IGNITE-3478) Transactional SQL

[ https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-3478: Assignee: Semen Boikov (was: Sergi Vladykin) > Transactional SQL > - > >

[jira] [Commented] (IGNITE-5912) [Redis] EXPIRE/PEXPIRE on keys

[ https://issues.apache.org/jira/browse/IGNITE-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114229#comment-16114229 ] Andrey Novikov commented on IGNITE-5912: Hi [~roman_s], I reviewed your pull request and found

  1   2   >