[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=15250586#comment-15250586 ] Valentin Kulichenko commented on IGNITE-1248: - Hi Saikat. No problem, I will take a look in

[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:

[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

[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

[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

[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

[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

[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-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=15261610#comment-15261610 ] Valentin Kulichenko commented on IGNITE-3024: - Made a fix in branch {{ignite-3024}} - moved

[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] [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

[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

[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

[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=15291369#comment-15291369 ] Valentin Kulichenko commented on IGNITE-2929: - Hi, feel free to assign tickets to yourself if

[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=15293246#comment-15293246 ] Valentin Kulichenko commented on IGNITE-2929: - Write an email to the dev@ list and ask for

[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=15279433#comment-15279433 ] Valentin Kulichenko commented on IGNITE-3056: - Agree with Semen. Adding new method looks

[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] [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-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] [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

[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:

[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=15266134#comment-15266134 ] Valentin Kulichenko commented on IGNITE-2394: - Hi Alper. Sorry for the delay, I will take a

[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] [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] [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

[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] [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

[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=15299799#comment-15299799 ] Valentin Kulichenko commented on IGNITE-2929: - PR looks good, but there is a discussion on

[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=15299786#comment-15299786 ] Valentin Kulichenko commented on IGNITE-2538: - Looks good. I also added similar override for

[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

[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] [Created] (IGNITE-3588) Cassandra store should use batching in writeAll and deleteAll methods

Valentin Kulichenko created IGNITE-3588: --- Summary: Cassandra store should use batching in writeAll and deleteAll methods Key: IGNITE-3588 URL: https://issues.apache.org/jira/browse/IGNITE-3588

[jira] [Created] (IGNITE-3470) Continuous queries should support EXPIRED events

Valentin Kulichenko created IGNITE-3470: --- Summary: Continuous queries should support EXPIRED events Key: IGNITE-3470 URL: https://issues.apache.org/jira/browse/IGNITE-3470 Project: Ignite

[jira] [Closed] (IGNITE-3602) Hibernate L2 cache should be able to create caches automatically

[ https://issues.apache.org/jira/browse/IGNITE-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-3602. --- > Hibernate L2 cache should be able to create caches automatically >

[jira] [Resolved] (IGNITE-3602) Hibernate L2 cache should be able to create caches automatically

[ https://issues.apache.org/jira/browse/IGNITE-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-3602. - Resolution: Duplicate > Hibernate L2 cache should be able to create caches

[jira] [Updated] (IGNITE-3392) IgniteServices.deploy() method doesn't throw exception in case service initialization throws exception

[ https://issues.apache.org/jira/browse/IGNITE-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3392: Fix Version/s: (was: 1.7) 2.0 > IgniteServices.deploy()

[jira] [Closed] (IGNITE-884) Cache store usability issues

[ https://issues.apache.org/jira/browse/IGNITE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-884. -- > Cache store usability issues > > > Key:

[jira] [Updated] (IGNITE-1840) Exception in eviction manager on startup

[ https://issues.apache.org/jira/browse/IGNITE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1840: Assignee: (was: Valentin Kulichenko) > Exception in eviction manager on

[jira] [Updated] (IGNITE-1995) Local cache is destroyed when close() is called

[ https://issues.apache.org/jira/browse/IGNITE-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1995: Assignee: (was: Valentin Kulichenko) > Local cache is destroyed when close()

[jira] [Resolved] (IGNITE-2783) Frequent deadlock during regular operations

[ https://issues.apache.org/jira/browse/IGNITE-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2783. - Resolution: Duplicate > Frequent deadlock during regular operations >

[jira] [Updated] (IGNITE-2787) Hibernate L2 cache doesn't survive client reconnect

[ https://issues.apache.org/jira/browse/IGNITE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2787: Assignee: (was: Valentin Kulichenko) > Hibernate L2 cache doesn't survive

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

[ https://issues.apache.org/jira/browse/IGNITE-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2928: Assignee: (was: Valentin Kulichenko) > Confusing exception when trying to

[jira] [Updated] (IGNITE-1404) Any distributed cache operation should throw CacheServerNotFoundException if there are no server nodes

[ https://issues.apache.org/jira/browse/IGNITE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1404: Assignee: (was: Valentin Kulichenko) > Any distributed cache operation should

[jira] [Resolved] (IGNITE-1151) Cache operations can throw ClusterTopologyException without wrapping it into CacheException

[ https://issues.apache.org/jira/browse/IGNITE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-1151. - Resolution: Won't Fix > Cache operations can throw ClusterTopologyException

[jira] [Closed] (IGNITE-1151) Cache operations can throw ClusterTopologyException without wrapping it into CacheException

[ https://issues.apache.org/jira/browse/IGNITE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-1151. --- > Cache operations can throw ClusterTopologyException without wrapping it into >

[jira] [Updated] (IGNITE-1122) Cache put hangs if key hashCode is implemented incorrectly

[ https://issues.apache.org/jira/browse/IGNITE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1122: Assignee: (was: Valentin Kulichenko) > Cache put hangs if key hashCode is

[jira] [Commented] (IGNITE-2783) Frequent deadlock during regular operations

[ https://issues.apache.org/jira/browse/IGNITE-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416094#comment-15416094 ] Valentin Kulichenko commented on IGNITE-2783: - This issue was fixed in scope of other

[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency

[ https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2096: Assignee: (was: Valentin Kulichenko) > AtomicConfiguration and

[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency

[ https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2096: Priority: Major (was: Critical) > AtomicConfiguration and CollectionConfiguration

[jira] [Updated] (IGNITE-954) Continuous queries are deployed on client nodes

[ https://issues.apache.org/jira/browse/IGNITE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-954: --- Assignee: (was: Valentin Kulichenko) > Continuous queries are deployed on client

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

[ https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-425: --- Priority: Major (was: Critical) > Introduce transformers for continuous queries >

[jira] [Updated] (IGNITE-884) Cache store usability issues

[ https://issues.apache.org/jira/browse/IGNITE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-884: --- Priority: Major (was: Critical) > Cache store usability issues >

[jira] [Created] (IGNITE-3624) Provide API to get the size of the cache in bytes

Valentin Kulichenko created IGNITE-3624: --- Summary: Provide API to get the size of the cache in bytes Key: IGNITE-3624 URL: https://issues.apache.org/jira/browse/IGNITE-3624 Project: Ignite

[jira] [Resolved] (IGNITE-884) Cache store usability issues

[ https://issues.apache.org/jira/browse/IGNITE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-884. Resolution: Won't Fix > Cache store usability issues >

[jira] [Closed] (IGNITE-2783) Frequent deadlock during regular operations

[ https://issues.apache.org/jira/browse/IGNITE-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2783. --- > Frequent deadlock during regular operations >

[jira] [Closed] (IGNITE-954) Continuous queries are deployed on client nodes

[ https://issues.apache.org/jira/browse/IGNITE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-954. -- > Continuous queries are deployed on client nodes >

[jira] [Resolved] (IGNITE-954) Continuous queries are deployed on client nodes

[ https://issues.apache.org/jira/browse/IGNITE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-954. Resolution: Fixed > Continuous queries are deployed on client nodes >

[jira] [Closed] (IGNITE-27) Performance issue with SQL join query when offheap is enabled.

[ https://issues.apache.org/jira/browse/IGNITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-27. - > Performance issue with SQL join query when offheap is enabled. >

[jira] [Resolved] (IGNITE-27) Performance issue with SQL join query when offheap is enabled.

[ https://issues.apache.org/jira/browse/IGNITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-27. --- Resolution: Won't Fix > Performance issue with SQL join query when offheap is enabled.

[jira] [Updated] (IGNITE-1160) Ignite.deploy(...) method to automatically deploy user code and libraries

[ https://issues.apache.org/jira/browse/IGNITE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1160: Assignee: (was: Valentin Kulichenko) > Ignite.deploy(...) method to

[jira] [Commented] (IGNITE-3470) Continuous queries should support EXPIRED events

[ https://issues.apache.org/jira/browse/IGNITE-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416097#comment-15416097 ] Valentin Kulichenko commented on IGNITE-3470: - Update counter can't be supported for

[jira] [Updated] (IGNITE-1726) Node doesn't fail if SSL configuration is incorrect

[ https://issues.apache.org/jira/browse/IGNITE-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1726: Assignee: (was: Valentin Kulichenko) > Node doesn't fail if SSL configuration

[jira] [Closed] (IGNITE-3470) Continuous queries should support EXPIRED events

[ https://issues.apache.org/jira/browse/IGNITE-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-3470. --- > Continuous queries should support EXPIRED events >

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

[ https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-425: --- Assignee: (was: Valentin Kulichenko) > Introduce transformers for continuous

[jira] [Updated] (IGNITE-955) Local listener in continuous queries should not be mandatory

[ https://issues.apache.org/jira/browse/IGNITE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-955: --- Assignee: (was: Valentin Kulichenko) > Local listener in continuous queries

[jira] [Updated] (IGNITE-1073) Need to add skipOldValue flag to continuous queries

[ https://issues.apache.org/jira/browse/IGNITE-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1073: Assignee: (was: Valentin Kulichenko) > Need to add skipOldValue flag to

[jira] [Updated] (IGNITE-1129) Start system cache for atomics only if atomics are used

[ https://issues.apache.org/jira/browse/IGNITE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1129: Assignee: (was: Valentin Kulichenko) > Start system cache for atomics only if

[jira] [Closed] (IGNITE-940) Need to expose SQL metadata to public API

[ https://issues.apache.org/jira/browse/IGNITE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-940. -- > Need to expose SQL metadata to public API > - > >

[jira] [Updated] (IGNITE-995) Nodes on one host doesn't discover each other if IP finder doesn't explicitly provide port

[ https://issues.apache.org/jira/browse/IGNITE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-995: --- Assignee: (was: Valentin Kulichenko) > Nodes on one host doesn't discover each

[jira] [Updated] (IGNITE-955) Local listener in continuous queries should not be mandatory

[ https://issues.apache.org/jira/browse/IGNITE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-955: --- Priority: Major (was: Critical) > Local listener in continuous queries should not be

[jira] [Commented] (IGNITE-3679) ClassNotFoundException

[ https://issues.apache.org/jira/browse/IGNITE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419400#comment-15419400 ] Valentin Kulichenko commented on IGNITE-3679: - Please paste the whole exception trace, do not

[jira] [Updated] (IGNITE-3680) Document address resolver

[ https://issues.apache.org/jira/browse/IGNITE-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3680: Issue Type: Task (was: Improvement) > Document address resolver >

[jira] [Created] (IGNITE-3680) Document address resolver

Valentin Kulichenko created IGNITE-3680: --- Summary: Document address resolver Key: IGNITE-3680 URL: https://issues.apache.org/jira/browse/IGNITE-3680 Project: Ignite Issue Type:

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

[ https://issues.apache.org/jira/browse/IGNITE-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418132#comment-15418132 ] Valentin Kulichenko commented on IGNITE-3197: - Andrey, I'm a bit confused. If you take a

[jira] [Commented] (IGNITE-3476) Node started within SpringCacheManager does not inject Spring resources

[ https://issues.apache.org/jira/browse/IGNITE-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375845#comment-15375845 ] Valentin Kulichenko commented on IGNITE-3476: - {{SpringTransactionManager}} should be also

[jira] [Created] (IGNITE-3476) Node started within SpringCacheManager does not inject Spring resources

Valentin Kulichenko created IGNITE-3476: --- Summary: Node started within SpringCacheManager does not inject Spring resources Key: IGNITE-3476 URL: https://issues.apache.org/jira/browse/IGNITE-3476

[jira] [Created] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries

Valentin Kulichenko created IGNITE-3487: --- Summary: _key and _val fields should be excluded from 'select * from' queries Key: IGNITE-3487 URL: https://issues.apache.org/jira/browse/IGNITE-3487

[jira] [Closed] (IGNITE-2091) Service Deployment: use service's class String name instead of Class during deployment

[ https://issues.apache.org/jira/browse/IGNITE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2091. --- > Service Deployment: use service's class String name instead of Class during >

[jira] [Resolved] (IGNITE-2091) Service Deployment: use service's class String name instead of Class during deployment

[ https://issues.apache.org/jira/browse/IGNITE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2091. - Resolution: Duplicate > Service Deployment: use service's class String name

[jira] [Created] (IGNITE-3391) Need to be able to customize SQL table name

Valentin Kulichenko created IGNITE-3391: --- Summary: Need to be able to customize SQL table name Key: IGNITE-3391 URL: https://issues.apache.org/jira/browse/IGNITE-3391 Project: Ignite

[jira] [Created] (IGNITE-3392) IgniteServices.deploy() method doesn't throw exception in case service initialization throws exception

Valentin Kulichenko created IGNITE-3392: --- Summary: IgniteServices.deploy() method doesn't throw exception in case service initialization throws exception Key: IGNITE-3392 URL:

[jira] [Updated] (IGNITE-3392) IgniteServices.deploy() method doesn't throw exception in case service initialization throws exception

[ https://issues.apache.org/jira/browse/IGNITE-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3392: Attachment: Test.java > IgniteServices.deploy() method doesn't throw exception in

[jira] [Created] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller

Valentin Kulichenko created IGNITE-3429: --- Summary: org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller Key: IGNITE-3429 URL: https://issues.apache.org/jira/browse/IGNITE-3429

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

[ https://issues.apache.org/jira/browse/IGNITE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2949. - Resolution: Fixed Replaced JCache JAR with Geronimo in master. > Replace JCache

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

[ https://issues.apache.org/jira/browse/IGNITE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2949. --- > Replace JCache API dependency with Geronimo >

[jira] [Updated] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller

[ https://issues.apache.org/jira/browse/IGNITE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3429: Priority: Critical (was: Major) > org.hibernate.cache.spi.CacheKey not properly

[jira] [Comment Edited] (IGNITE-3413) Node is not started if continuous query remote filter class is not found

[ https://issues.apache.org/jira/browse/IGNITE-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367113#comment-15367113 ] Valentin Kulichenko edited comment on IGNITE-3413 at 7/8/16 2:37 AM: -

[jira] [Commented] (IGNITE-3413) Node is not started if continuous query remote filter class is not found

[ https://issues.apache.org/jira/browse/IGNITE-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367113#comment-15367113 ] Valentin Kulichenko commented on IGNITE-3413: - [~al.psc], where is the pull request or a

[jira] [Resolved] (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 resolved IGNITE-2929. - Resolution: Fixed > IgniteContext should not have type parameters >

[jira] [Closed] (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 closed IGNITE-2929. --- > IgniteContext should not have type parameters >

[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=15361678#comment-15361678 ] Valentin Kulichenko commented on IGNITE-2929: - Merged to master. > IgniteContext should not

[jira] [Closed] (IGNITE-3408) Need to provide basic implementation of AddressResolver

[ https://issues.apache.org/jira/browse/IGNITE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-3408. --- > Need to provide basic implementation of AddressResolver >

[jira] [Resolved] (IGNITE-3634) SpringCacheManager should support null values

[ https://issues.apache.org/jira/browse/IGNITE-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-3634. - Resolution: Fixed > SpringCacheManager should support null values >

[jira] [Closed] (IGNITE-3634) SpringCacheManager should support null values

[ https://issues.apache.org/jira/browse/IGNITE-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-3634. --- > SpringCacheManager should support null values >

[jira] [Created] (IGNITE-3635) StackOeverflowError in BinaryObject.toString()

Valentin Kulichenko created IGNITE-3635: --- Summary: StackOeverflowError in BinaryObject.toString() Key: IGNITE-3635 URL: https://issues.apache.org/jira/browse/IGNITE-3635 Project: Ignite

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

[ https://issues.apache.org/jira/browse/IGNITE-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2983. - Resolution: Duplicate > Possible NPE during service proxy invocation >

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

[ https://issues.apache.org/jira/browse/IGNITE-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-3197: Priority: Minor (was: Major) > OverlappingFileLockException in marshaller context

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

[ https://issues.apache.org/jira/browse/IGNITE-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2983. --- > Possible NPE during service proxy invocation >

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