[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2018-02-02 Thread Saleem Akbar (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350096#comment-16350096 ] Saleem Akbar commented on COLLECTIONS-599: -- Thanks :-) > HashEntry array object naming

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2018-02-01 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349105#comment-16349105 ] Gary Gregory commented on COLLECTIONS-599: -- The fix has been committed to git master. I

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2018-02-01 Thread Saleem Akbar (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348998#comment-16348998 ] Saleem Akbar commented on COLLECTIONS-599: -- I also came across this problem (in my scenario

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2017-11-06 Thread mingleizhang (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241348#comment-16241348 ] mingleizhang commented on COLLECTIONS-599: -- I suspect that whether this issue belongs to a

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2017-11-06 Thread mingleizhang (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241347#comment-16241347 ] mingleizhang commented on COLLECTIONS-599: -- I suspect that whether this issue belongs to a

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2017-11-06 Thread mingleizhang (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241304#comment-16241304 ] mingleizhang commented on COLLECTIONS-599: -- Hi, [~garydgregory] I would think this change

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2017-11-06 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240470#comment-16240470 ] Gary Gregory commented on COLLECTIONS-599: -- Hi [~mingleizhang], Please feel free to provide

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2017-11-05 Thread mingleizhang (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239959#comment-16239959 ] mingleizhang commented on COLLECTIONS-599: -- Does anyone give me a permission that can

[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming data initialized with double the size during deserialization

2016-12-02 Thread Tejas Patel (JIRA)
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714952#comment-15714952 ] Tejas Patel commented on COLLECTIONS-599: - Possible fix would be calculating threshold before