[jira] [Commented] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect

[ https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190250#comment-15190250 ] Valentin Kulichenko commented on IGNITE-2765: - Anton, I reviewed the changes

[jira] [Created] (IGNITE-2796) NPE during rebalancing

Valentin Kulichenko created IGNITE-2796: --- Summary: NPE during rebalancing Key: IGNITE-2796 URL: https://issues.apache.org/jira/browse/IGNITE-2796 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2797) Prepare and finish future never time out

Valentin Kulichenko created IGNITE-2797: --- Summary: Prepare and finish future never time out Key: IGNITE-2797 URL: https://issues.apache.org/jira/browse/IGNITE-2797 Project: Ignite Issue

[jira] [Updated] (IGNITE-2798) 'Transaction has already been completed' in restart tests

[ https://issues.apache.org/jira/browse/IGNITE-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2798: Description: When running transaction tests with node restarts (e.g. {{IgniteCache

[jira] [Created] (IGNITE-2798) 'Transaction has already been completed' in restart tests

Valentin Kulichenko created IGNITE-2798: --- Summary: 'Transaction has already been completed' in restart tests Key: IGNITE-2798 URL: https://issues.apache.org/jira/browse/IGNITE-2798 Project: Ignit

[jira] [Resolved] (IGNITE-2735) Interrupt all acquires on local node after ignite.close

[ https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2735. - Resolution: Fixed > Interrupt all acquires on local node after ignite.close > ---

[jira] [Commented] (IGNITE-2735) Interrupt all acquires on local node after ignite.close

[ https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190464#comment-15190464 ] Valentin Kulichenko commented on IGNITE-2735: - Yes, makes sense. Merged chang

[jira] [Closed] (IGNITE-2735) Interrupt all acquires on local node after ignite.close

[ https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2735. --- > Interrupt all acquires on local node after ignite.close > -

[jira] [Commented] (IGNITE-2796) NPE during rebalancing

[ https://issues.apache.org/jira/browse/IGNITE-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191420#comment-15191420 ] Valentin Kulichenko commented on IGNITE-2796: - Not really, I just saw this in

[jira] [Created] (IGNITE-2822) Continuous query local listener can be notified with empty list of events

Valentin Kulichenko created IGNITE-2822: --- Summary: Continuous query local listener can be notified with empty list of events Key: IGNITE-2822 URL: https://issues.apache.org/jira/browse/IGNITE-2822

[jira] [Assigned] (IGNITE-2795) Cache query cursor do not create value copy

[ https://issues.apache.org/jira/browse/IGNITE-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-2795: --- Assignee: Valentin Kulichenko > Cache query cursor do not create value copy

[jira] [Commented] (IGNITE-2831) Support advertised address for use with EC2 service discovery

[ https://issues.apache.org/jira/browse/IGNITE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193906#comment-15193906 ] Valentin Kulichenko commented on IGNITE-2831: - This can be achieved by implem

[jira] [Commented] (IGNITE-2829) Unable to cache two beans with same class name but different package

[ https://issues.apache.org/jira/browse/IGNITE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194385#comment-15194385 ] Valentin Kulichenko commented on IGNITE-2829: - Kranthi, I believe this is al

[jira] [Commented] (IGNITE-2831) Support advertised address for use with EC2 service discovery

[ https://issues.apache.org/jira/browse/IGNITE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194401#comment-15194401 ] Valentin Kulichenko commented on IGNITE-2831: - {{AddressResolver}} in this ca

[jira] [Comment Edited] (IGNITE-2831) Support advertised address for use with EC2 service discovery

[ https://issues.apache.org/jira/browse/IGNITE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194401#comment-15194401 ] Valentin Kulichenko edited comment on IGNITE-2831 at 3/14/16 11:45 PM:

[jira] [Created] (IGNITE-2832) CacheJdbcPojoStoreFactory.dataSource property should be replaced with Factory

Valentin Kulichenko created IGNITE-2832: --- Summary: CacheJdbcPojoStoreFactory.dataSource property should be replaced with Factory Key: IGNITE-2832 URL: https://issues.apache.org/jira/browse/IGNITE-2832

[jira] [Commented] (IGNITE-2798) 'Transaction has already been completed' in restart tests

[ https://issues.apache.org/jira/browse/IGNITE-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194752#comment-15194752 ] Valentin Kulichenko commented on IGNITE-2798: - Dmitry, Is it possible not to

[jira] [Commented] (IGNITE-2829) Unable to cache two beans with same class name but different package

[ https://issues.apache.org/jira/browse/IGNITE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196243#comment-15196243 ] Valentin Kulichenko commented on IGNITE-2829: - There is no particular date no

[jira] [Resolved] (IGNITE-2829) Unable to cache two beans with same class name but different package

[ https://issues.apache.org/jira/browse/IGNITE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2829. - Resolution: Duplicate > Unable to cache two beans with same class name but differ

[jira] [Closed] (IGNITE-2829) Unable to cache two beans with same class name but different package

[ https://issues.apache.org/jira/browse/IGNITE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2829. --- > Unable to cache two beans with same class name but different package >

[jira] [Commented] (IGNITE-2797) Prepare and finish future never time out

[ https://issues.apache.org/jira/browse/IGNITE-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198851#comment-15198851 ] Valentin Kulichenko commented on IGNITE-2797: - I also noticed a bug in timeou

[jira] [Closed] (IGNITE-2853) Job processor should be stopped earlier than service processor

[ https://issues.apache.org/jira/browse/IGNITE-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2853. --- > Job processor should be stopped earlier than service processor > --

[jira] [Updated] (IGNITE-2797) Prepare and finish future never time out

[ https://issues.apache.org/jira/browse/IGNITE-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2797: Attachment: TxTest2.java > Prepare and finish future never time out > -

[jira] [Commented] (IGNITE-2708) Need to validate that SPIs are started only once

[ https://issues.apache.org/jira/browse/IGNITE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202396#comment-15202396 ] Valentin Kulichenko commented on IGNITE-2708: - Hi, is there any reason why it

[jira] [Created] (IGNITE-2853) Job processor should be stopped earlier than service processor

Valentin Kulichenko created IGNITE-2853: --- Summary: Job processor should be stopped earlier than service processor Key: IGNITE-2853 URL: https://issues.apache.org/jira/browse/IGNITE-2853 Project:

[jira] [Created] (IGNITE-2852) TreeMap can't be converted to portable

Valentin Kulichenko created IGNITE-2852: --- Summary: TreeMap can't be converted to portable Key: IGNITE-2852 URL: https://issues.apache.org/jira/browse/IGNITE-2852 Project: Ignite Issue T

[jira] [Created] (IGNITE-2854) Need to implement deadlock detection

Valentin Kulichenko created IGNITE-2854: --- Summary: Need to implement deadlock detection Key: IGNITE-2854 URL: https://issues.apache.org/jira/browse/IGNITE-2854 Project: Ignite Issue Typ

[jira] [Commented] (IGNITE-1071) IgniteCache.metrics() method returns local metrics

[ https://issues.apache.org/jira/browse/IGNITE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198357#comment-15198357 ] Valentin Kulichenko commented on IGNITE-1071: - Anton, I would look through al

[jira] [Resolved] (IGNITE-2853) Job processor should be stopped earlier than service processor

[ https://issues.apache.org/jira/browse/IGNITE-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2853. - Resolution: Fixed Fixed in master. > Job processor should be stopped earlier tha

[jira] [Created] (IGNITE-2881) SPI queries not working

Valentin Kulichenko created IGNITE-2881: --- Summary: SPI queries not working Key: IGNITE-2881 URL: https://issues.apache.org/jira/browse/IGNITE-2881 Project: Ignite Issue Type: Bug

[jira] [Updated] (IGNITE-2881) SPI queries not working

[ https://issues.apache.org/jira/browse/IGNITE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2881: Attachment: SpiQueryTest.java > SPI queries not working > --- >

[jira] [Updated] (IGNITE-2735) Interrupt all acquires on local node after ignite.close

[ https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2735: Fix Version/s: (was: 1.5.0.final) 1.6 > Interrupt all acquir

[jira] [Updated] (IGNITE-2735) Interrupt all acquires on local node after ignite.close

[ https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2735: Affects Version/s: (was: 1.6) 1.5.0.final > Interrupt al

[jira] [Commented] (IGNITE-2708) Need to validate that SPIs are started only once

[ https://issues.apache.org/jira/browse/IGNITE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209145#comment-15209145 ] Valentin Kulichenko commented on IGNITE-2708: - I see your point. To make it s

[jira] [Created] (IGNITE-2893) Atomic structures should not use transactions

Valentin Kulichenko created IGNITE-2893: --- Summary: Atomic structures should not use transactions Key: IGNITE-2893 URL: https://issues.apache.org/jira/browse/IGNITE-2893 Project: Ignite

[jira] [Updated] (IGNITE-2893) Atomic structures should not use transactions

[ https://issues.apache.org/jira/browse/IGNITE-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2893: Labels: newbie (was: ) > Atomic structures should not use transactions > -

[jira] [Created] (IGNITE-2894) Binary object inside of Externalizable still serialized with OptimizedMarshaller

Valentin Kulichenko created IGNITE-2894: --- Summary: Binary object inside of Externalizable still serialized with OptimizedMarshaller Key: IGNITE-2894 URL: https://issues.apache.org/jira/browse/IGNITE-2894

[jira] [Created] (IGNITE-2928) Confusing exception when trying to execute DELETE query

Valentin Kulichenko created IGNITE-2928: --- Summary: Confusing exception when trying to execute DELETE query Key: IGNITE-2928 URL: https://issues.apache.org/jira/browse/IGNITE-2928 Project: Ignite

[jira] [Created] (IGNITE-2929) IgniteContext should not have type parameters

Valentin Kulichenko created IGNITE-2929: --- Summary: IgniteContext should not have type parameters Key: IGNITE-2929 URL: https://issues.apache.org/jira/browse/IGNITE-2929 Project: Ignite

[jira] [Updated] (IGNITE-640) Implement IgniteMultimap data structures

[ https://issues.apache.org/jira/browse/IGNITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-640: --- Assignee: (was: Konstantin Margorin) > Implement IgniteMultimap data structures >

[jira] [Assigned] (IGNITE-2942) Use getOrStart in IgniteContext instead of current try-catch structure

[ https://issues.apache.org/jira/browse/IGNITE-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-2942: --- Assignee: Valentin Kulichenko > Use getOrStart in IgniteContext instead of c

[jira] [Created] (IGNITE-2949) Replace JCache API dependency with Geronimo

Valentin Kulichenko created IGNITE-2949: --- Summary: Replace JCache API dependency with Geronimo Key: IGNITE-2949 URL: https://issues.apache.org/jira/browse/IGNITE-2949 Project: Ignite Is

[jira] [Created] (IGNITE-2951) Cluster is unstable when there are more than 500 clients

Valentin Kulichenko created IGNITE-2951: --- Summary: Cluster is unstable when there are more than 500 clients Key: IGNITE-2951 URL: https://issues.apache.org/jira/browse/IGNITE-2951 Project: Ignite

[jira] [Commented] (IGNITE-2951) Cluster is unstable when there are more than 500 clients

[ https://issues.apache.org/jira/browse/IGNITE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231103#comment-15231103 ] Valentin Kulichenko commented on IGNITE-2951: - The following is done: * Remo

[jira] [Resolved] (IGNITE-2951) Cluster is unstable when there are more than 500 clients

[ https://issues.apache.org/jira/browse/IGNITE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2951. - Resolution: Fixed > Cluster is unstable when there are more than 500 clients > --

[jira] [Closed] (IGNITE-2951) Cluster is unstable when there are more than 500 clients

[ https://issues.apache.org/jira/browse/IGNITE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2951. --- > Cluster is unstable when there are more than 500 clients >

[jira] [Commented] (IGNITE-1102) IgniteSpringBean should have getConfiguration() method

[ https://issues.apache.org/jira/browse/IGNITE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234306#comment-15234306 ] Valentin Kulichenko commented on IGNITE-1102: - Yes, that's exactly what I sug

[jira] [Comment Edited] (IGNITE-1102) IgniteSpringBean should have getConfiguration() method

[ https://issues.apache.org/jira/browse/IGNITE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234306#comment-15234306 ] Valentin Kulichenko edited comment on IGNITE-1102 at 4/10/16 10:14 PM:

[jira] [Created] (IGNITE-2975) Load balancer does not survive client reconnect

Valentin Kulichenko created IGNITE-2975: --- Summary: Load balancer does not survive client reconnect Key: IGNITE-2975 URL: https://issues.apache.org/jira/browse/IGNITE-2975 Project: Ignite

[jira] [Commented] (IGNITE-2708) Need to validate that SPIs are started only once

[ https://issues.apache.org/jira/browse/IGNITE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237366#comment-15237366 ] Valentin Kulichenko commented on IGNITE-2708: - Hi Ryan, did you have any prog

[jira] [Created] (IGNITE-2983) Possible NPE during service proxy invocation

Valentin Kulichenko created IGNITE-2983: --- Summary: Possible NPE during service proxy invocation Key: IGNITE-2983 URL: https://issues.apache.org/jira/browse/IGNITE-2983 Project: Ignite I

[jira] [Resolved] (IGNITE-3022) Unable to start Ignite Node on AWS

[ https://issues.apache.org/jira/browse/IGNITE-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-3022. - Resolution: Duplicate Duplicate of IGNITE-2758 > Unable to start Ignite Node on

[jira] [Closed] (IGNITE-3022) Unable to start Ignite Node on AWS

[ https://issues.apache.org/jira/browse/IGNITE-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-3022. --- > Unable to start Ignite Node on AWS > -- > >

[jira] [Created] (IGNITE-3024) Possible deadlock in services when Spring is used

Valentin Kulichenko created IGNITE-3024: --- Summary: Possible deadlock in services when Spring is used Key: IGNITE-3024 URL: https://issues.apache.org/jira/browse/IGNITE-3024 Project: Ignite

[jira] [Created] (IGNITE-3027) TcpDiscoveryImpl.registerLocalNodeAddress() has an infinite loop

Valentin Kulichenko created IGNITE-3027: --- Summary: TcpDiscoveryImpl.registerLocalNodeAddress() has an infinite loop Key: IGNITE-3027 URL: https://issues.apache.org/jira/browse/IGNITE-3027 Projec

[jira] [Commented] (IGNITE-1248) Add a method to retrieve Spring application context

[ https://issues.apache.org/jira/browse/IGNITE-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250586#comment-15250586 ] Valentin Kulichenko commented on IGNITE-1248: - Hi Saikat. No problem, I will

[jira] [Created] (IGNITE-3055) IgniteDataStreamer can't be timed out

Valentin Kulichenko created IGNITE-3055: --- Summary: IgniteDataStreamer can't be timed out Key: IGNITE-3055 URL: https://issues.apache.org/jira/browse/IGNITE-3055 Project: Ignite Issue Ty

[jira] [Created] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

Valentin Kulichenko created IGNITE-3056: --- Summary: Service implementation class is required even if it's not expected to be deployed on current node Key: IGNITE-3056 URL: https://issues.apache.org/jira/brows

[jira] [Updated] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3056: Component/s: managed services > Service implementation class is required even if it

[jira] [Updated] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3056: Affects Version/s: 1.5.0.final > Service implementation class is required even if i

[jira] [Updated] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3056: Flags: Important > Service implementation class is required even if it's not expect

[jira] [Updated] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3056: Labels: community customer important (was: ) > Service implementation class is req

[jira] [Updated] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3056: Fix Version/s: 1.6 > Service implementation class is required even if it's not expe

[jira] [Assigned] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-3056: --- Assignee: Valentin Kulichenko > Service implementation class is required eve

[jira] [Updated] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3056: Description: Currently the service instance is deserialized as part of {{GridServic

[jira] [Created] (IGNITE-3057) Optimize transactions that do not acquire any locks

Valentin Kulichenko created IGNITE-3057: --- Summary: Optimize transactions that do not acquire any locks Key: IGNITE-3057 URL: https://issues.apache.org/jira/browse/IGNITE-3057 Project: Ignite

[jira] [Commented] (IGNITE-3024) Possible deadlock in services when Spring is used

[ https://issues.apache.org/jira/browse/IGNITE-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261610#comment-15261610 ] Valentin Kulichenko commented on IGNITE-3024: - Made a fix in branch {{ignite-

[jira] [Created] (IGNITE-3073) Possible thread starvation due to rebalancing

Valentin Kulichenko created IGNITE-3073: --- Summary: Possible thread starvation due to rebalancing Key: IGNITE-3073 URL: https://issues.apache.org/jira/browse/IGNITE-3073 Project: Ignite

[jira] [Commented] (IGNITE-2394) Cache loading from storage is called on client nodes

[ https://issues.apache.org/jira/browse/IGNITE-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266134#comment-15266134 ] Valentin Kulichenko commented on IGNITE-2394: - Hi Alper. Sorry for the delay,

[jira] [Commented] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node

[ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279433#comment-15279433 ] Valentin Kulichenko commented on IGNITE-3056: - Agree with Semen. Adding new m

[jira] [Closed] (IGNITE-1661) memory leak

[ https://issues.apache.org/jira/browse/IGNITE-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-1661. --- > memory leak > --- > > Key: IGNITE-1661 > URL: h

[jira] [Updated] (IGNITE-3152) Client node's addresses are registered in IP finder

[ https://issues.apache.org/jira/browse/IGNITE-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3152: Attachment: Test.java > Client node's addresses are registered in IP finder > -

[jira] [Created] (IGNITE-3152) Client node's addresses are registered in IP finder

Valentin Kulichenko created IGNITE-3152: --- Summary: Client node's addresses are registered in IP finder Key: IGNITE-3152 URL: https://issues.apache.org/jira/browse/IGNITE-3152 Project: Ignite

[jira] [Created] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections

Valentin Kulichenko created IGNITE-3153: --- Summary: TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections Key: IGNITE-3153 URL: https://issues.apache.org/jira/browse/IGNITE-3153

[jira] [Created] (IGNITE-3164) Add an option to send resulting value instead of entry processor in transactional cache

Valentin Kulichenko created IGNITE-3164: --- Summary: Add an option to send resulting value instead of entry processor in transactional cache Key: IGNITE-3164 URL: https://issues.apache.org/jira/browse/IGNITE-3

[jira] [Updated] (IGNITE-3164) Add an option to send resulting value instead of entry processor in transactional cache

[ https://issues.apache.org/jira/browse/IGNITE-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3164: Description: In some cases user can't guarantee that EP behaves consistently on all

[jira] [Created] (IGNITE-3175) BigDecimal fields are not supported if query is executed from IgniteRDD

Valentin Kulichenko created IGNITE-3175: --- Summary: BigDecimal fields are not supported if query is executed from IgniteRDD Key: IGNITE-3175 URL: https://issues.apache.org/jira/browse/IGNITE-3175

[jira] [Updated] (IGNITE-2929) IgniteContext should not have type parameters

[ https://issues.apache.org/jira/browse/IGNITE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2929: Assignee: (was: Valentin Kulichenko) > IgniteContext should not have type param

[jira] [Assigned] (IGNITE-2929) IgniteContext should not have type parameters

[ https://issues.apache.org/jira/browse/IGNITE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-2929: --- Assignee: Valentin Kulichenko > IgniteContext should not have type parameter

[jira] [Commented] (IGNITE-2929) IgniteContext should not have type parameters

[ https://issues.apache.org/jira/browse/IGNITE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291369#comment-15291369 ] Valentin Kulichenko commented on IGNITE-2929: - Hi, feel free to assign ticket

[jira] [Commented] (IGNITE-2929) IgniteContext should not have type parameters

[ https://issues.apache.org/jira/browse/IGNITE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293246#comment-15293246 ] Valentin Kulichenko commented on IGNITE-2929: - Write an email to the dev@ lis

[jira] [Closed] (IGNITE-2538) RDD.isEmpty method should be overriden in IgniteRDD to use IgniteCache API

[ https://issues.apache.org/jira/browse/IGNITE-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2538. --- > RDD.isEmpty method should be overriden in IgniteRDD to use IgniteCache API > --

[jira] [Commented] (IGNITE-2538) RDD.isEmpty method should be overriden in IgniteRDD to use IgniteCache API

[ https://issues.apache.org/jira/browse/IGNITE-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299786#comment-15299786 ] Valentin Kulichenko commented on IGNITE-2538: - Looks good. I also added simil

[jira] [Resolved] (IGNITE-2538) RDD.isEmpty method should be overriden in IgniteRDD to use IgniteCache API

[ https://issues.apache.org/jira/browse/IGNITE-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2538. - Resolution: Fixed > RDD.isEmpty method should be overriden in IgniteRDD to use Ig

[jira] [Commented] (IGNITE-2929) IgniteContext should not have type parameters

[ https://issues.apache.org/jira/browse/IGNITE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299799#comment-15299799 ] Valentin Kulichenko commented on IGNITE-2929: - PR looks good, but there is a

[jira] [Created] (IGNITE-3194) BinaryObjectException when web session attribute schema is changed

Valentin Kulichenko created IGNITE-3194: --- Summary: BinaryObjectException when web session attribute schema is changed Key: IGNITE-3194 URL: https://issues.apache.org/jira/browse/IGNITE-3194 Proj

[jira] [Commented] (IGNITE-1192) Provide integration with Spring Data

[ https://issues.apache.org/jira/browse/IGNITE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300015#comment-15300015 ] Valentin Kulichenko commented on IGNITE-1192: - Hi Juan, Can you please provi

[jira] [Created] (IGNITE-3197) OverlappingFileLockException in marshaller context

Valentin Kulichenko created IGNITE-3197: --- Summary: OverlappingFileLockException in marshaller context Key: IGNITE-3197 URL: https://issues.apache.org/jira/browse/IGNITE-3197 Project: Ignite

[jira] [Commented] (IGNITE-3204) java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

[ https://issues.apache.org/jira/browse/IGNITE-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301919#comment-15301919 ] Valentin Kulichenko commented on IGNITE-3204: - {{ignite-indexing}} module dep

[jira] [Commented] (IGNITE-2680) Terminating running SQL queries

[ https://issues.apache.org/jira/browse/IGNITE-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302320#comment-15302320 ] Valentin Kulichenko commented on IGNITE-2680: - I think we also add an ability

[jira] [Created] (IGNITE-3209) Need to wait for affinity assignment change during affinityCall failover

Valentin Kulichenko created IGNITE-3209: --- Summary: Need to wait for affinity assignment change during affinityCall failover Key: IGNITE-3209 URL: https://issues.apache.org/jira/browse/IGNITE-3209

[jira] [Created] (IGNITE-3215) IgniteRDD should be able to work with BinaryObjects

Valentin Kulichenko created IGNITE-3215: --- Summary: IgniteRDD should be able to work with BinaryObjects Key: IGNITE-3215 URL: https://issues.apache.org/jira/browse/IGNITE-3215 Project: Ignite

[jira] [Created] (IGNITE-3216) Need to deduplicate addresses registered in the IP finder

Valentin Kulichenko created IGNITE-3216: --- Summary: Need to deduplicate addresses registered in the IP finder Key: IGNITE-3216 URL: https://issues.apache.org/jira/browse/IGNITE-3216 Project: Ignit

[jira] [Assigned] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections

[ https://issues.apache.org/jira/browse/IGNITE-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-3153: --- Assignee: Valentin Kulichenko > TcpDiscoveryZookeeperIpFinder doesn't proper

[jira] [Commented] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections

[ https://issues.apache.org/jira/browse/IGNITE-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306883#comment-15306883 ] Valentin Kulichenko commented on IGNITE-3153: - Thanks, Roman! I added the tra

[jira] [Updated] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections

[ https://issues.apache.org/jira/browse/IGNITE-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3153: Description: The exception below is possible when client reconnects and ZooKeeper I

[jira] [Created] (IGNITE-3230) External addresses are not registered in IP finder

Valentin Kulichenko created IGNITE-3230: --- Summary: External addresses are not registered in IP finder Key: IGNITE-3230 URL: https://issues.apache.org/jira/browse/IGNITE-3230 Project: Ignite

[jira] [Commented] (IGNITE-3175) BigDecimal fields are not supported if query is executed from IgniteRDD

[ https://issues.apache.org/jira/browse/IGNITE-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310895#comment-15310895 ] Valentin Kulichenko commented on IGNITE-3175: - I'm reopening the ticket, beca

[jira] [Commented] (IGNITE-3175) BigDecimal fields are not supported if query is executed from IgniteRDD

[ https://issues.apache.org/jira/browse/IGNITE-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312119#comment-15312119 ] Valentin Kulichenko commented on IGNITE-3175: - I also don't see {{java.lang.C

[jira] [Assigned] (IGNITE-3215) IgniteRDD should be able to work with BinaryObjects

[ https://issues.apache.org/jira/browse/IGNITE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-3215: --- Assignee: Valentin Kulichenko > IgniteRDD should be able to work with Binary

<    1   2   3   4   5   6   7   8   9   10   >