[jira] [Created] (IGNITE-8788) Getting NullPointerException during commit into cassandra, after reconnecting to ignite server

Yashasvi Kotamraju created IGNITE-8788: -- Summary: Getting NullPointerException during commit into cassandra, after reconnecting to ignite server Key: IGNITE-8788 URL: https://issues.apache.org/jira/browse/IGN

[jira] [Updated] (IGNITE-8775) Memory leak in ignite-cassandra module while using RoundRobinPolicy LoadBalancingPolicy

[ https://issues.apache.org/jira/browse/IGNITE-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju updated IGNITE-8775: --- Description: OutOfMemory Exception is observed when encountered with the issue IGNIT

[jira] [Assigned] (IGNITE-8775) Memory leak in ignite-cassandra module while using RoundRobinPolicy LoadBalancingPolicy

[ https://issues.apache.org/jira/browse/IGNITE-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju reassigned IGNITE-8775: -- Assignee: Yashasvi Kotamraju > Memory leak in ignite-cassandra module while u

[jira] [Assigned] (IGNITE-8775) Memory leak in ignite-cassandra module while using RoundRobinPolicy LoadBalancingPolicy

[ https://issues.apache.org/jira/browse/IGNITE-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju reassigned IGNITE-8775: -- Assignee: Igor Rudyak (was: Yashasvi Kotamraju) > Memory leak in ignite-cass

[jira] [Updated] (IGNITE-8775) Memory leak in ignite-cassandra module while using RoundRobinPolicy LoadBalancingPolicy

[ https://issues.apache.org/jira/browse/IGNITE-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju updated IGNITE-8775: --- Description: OutOfMemory Exception is observed when encountered with the issue IGNIT

[jira] [Updated] (IGNITE-8775) Memory leak in ignite-cassandra module while using RoundRobinPolicy LoadBalancingPolicy

[ https://issues.apache.org/jira/browse/IGNITE-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju updated IGNITE-8775: --- Description: OutOfMemory Exception is observed when encountered with the issue IGNIT

[jira] [Created] (IGNITE-8775) Memory leak in ignite-cassandra module while using RoundRobinPolicy LoadBalancingPolicy

Yashasvi Kotamraju created IGNITE-8775: -- Summary: Memory leak in ignite-cassandra module while using RoundRobinPolicy LoadBalancingPolicy Key: IGNITE-8775 URL: https://issues.apache.org/jira/browse/IGNITE-877

[jira] [Commented] (IGNITE-6500) POJO fields of java wrapper type are not retaining null values from Cassandra persistent store, while using ignite's CassandraCacheStoreFactory

[ https://issues.apache.org/jira/browse/IGNITE-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479004#comment-16479004 ] Yashasvi Kotamraju commented on IGNITE-6500: Hi Igor created a new PR with t

[jira] [Commented] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467639#comment-16467639 ] Yashasvi Kotamraju commented on IGNITE-6252: Ticket addressing the Issue in t

[jira] [Created] (IGNITE-8354) Ignite Continuosly refreshes Cassandra Session when there is an Exception in execute method of CassandraSessionImpl

Yashasvi Kotamraju created IGNITE-8354: -- Summary: Ignite Continuosly refreshes Cassandra Session when there is an Exception in execute method of CassandraSessionImpl Key: IGNITE-8354 URL: https://issues.apac

[jira] [Resolved] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju resolved IGNITE-6252. Resolution: Fixed > Cassandra Cache Store Session does not retry if prepare stateme

[jira] [Comment Edited] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433582#comment-16433582 ] Yashasvi Kotamraju edited comment on IGNITE-6252 at 4/12/18 6:00 AM: --

[jira] [Commented] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433582#comment-16433582 ] Yashasvi Kotamraju commented on IGNITE-6252: Hi Igor Sorry. I was looking at

[jira] [Comment Edited] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427115#comment-16427115 ] Yashasvi Kotamraju edited comment on IGNITE-6252 at 4/10/18 6:41 AM: --

[jira] [Commented] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427115#comment-16427115 ] Yashasvi Kotamraju commented on IGNITE-6252: Also whenever session refresh()

[jira] [Reopened] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju reopened IGNITE-6252: The code fix using the condition : *assistant.processedCount() == dataSize* will not w

[jira] [Commented] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426566#comment-16426566 ] Yashasvi Kotamraju commented on IGNITE-6252: *In CassandraSessionImpl.java*  

[jira] [Issue Comment Deleted] (IGNITE-6500) POJO fields of java wrapper type are not retaining null values from Cassandra persistent store, while using ignite's CassandraCacheStoreFactory

[ https://issues.apache.org/jira/browse/IGNITE-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju updated IGNITE-6500: --- Comment: was deleted (was: IGNITE-6500 POJO fields of java wrapper type are not retai

[jira] [Updated] (IGNITE-6500) POJO fields of java wrapper type are not retaining null values from Cassandra persistent store, while using ignite's CassandraCacheStoreFactory

[ https://issues.apache.org/jira/browse/IGNITE-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju updated IGNITE-6500: --- Description: While using ignite's CassandraCacheStoreFactory(part of ignite-cassand

[jira] [Updated] (IGNITE-6500) While using ignite-cassandra-store, POJO field having wrapper type, mapped to Cassandra table are getting initialized to respective default value of primitive type inste

[ https://issues.apache.org/jira/browse/IGNITE-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju updated IGNITE-6500: --- Affects Version/s: 2.1 Fix Version/s: 2.3 > While using ignite-cassandra-stor

[jira] [Assigned] (IGNITE-6500) While using ignite-cassandra-store, POJO field having wrapper type, mapped to Cassandra table are getting initialized to respective default value of primitive type inst

[ https://issues.apache.org/jira/browse/IGNITE-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashasvi Kotamraju reassigned IGNITE-6500: -- Assignee: Yashasvi Kotamraju > While using ignite-cassandra-store, POJO field

[jira] [Created] (IGNITE-6500) While using ignite-cassandra-store, POJO field having wrapper type, mapped to Cassandra table are getting initialized to respective default value of primitive type inste

Yashasvi Kotamraju created IGNITE-6500: -- Summary: While using ignite-cassandra-store, POJO field having wrapper type, mapped to Cassandra table are getting initialized to respective default value of primitive type instead of null if column v