About JIRA GEODE-5896

2018-10-22 Thread
Hi,

I am Dong Yang, and my apache account is twosand.  What we are using Gemfire is 
not commonly usage scenario in other company, it's more like a OLTP and OLAP 
mixed scenario. The concept is very similar to using Spark-Gemfire connect, we 
have some server-side function that can shuffle data from server to client as 
stream style. And we encountered the thread lock issue in different 
environments. Before we use Gemfire8 , now we are upgrading to GemFrie9.
About GEODE-5896, it's very important usage for us, and I think the same for 
others if they want using spark to connect to Gemfire. Now we just do some 
patch at client-side the force the meta ready before function executed. But the 
perfect solution should fix some sever-side code.
I can share what I found and where I want to fix, you can review it , resonale 
or not . Fix it by current geode team or I can do it as a contributor.



Dong Yang, Dong [GTSUS Non-J&J
Thanks


Re: About JIRA GEODE-5896

2018-10-22 Thread Udo Kohlmeyer

Hi there Dong Yang,

If you have completed a fix, please submit it via the PR mechanism 
within Github. We will most gladly review and incorporate.


--Udo

On 10/18/18 06:00, Yang, Dong [GTSUS Non-J&J] wrote:

Hi,

I am Dong Yang, and my apache account is twosand.  What we are using Gemfire is 
not commonly usage scenario in other company, it's more like a OLTP and OLAP 
mixed scenario. The concept is very similar to using Spark-Gemfire connect, we 
have some server-side function that can shuffle data from server to client as 
stream style. And we encountered the thread lock issue in different 
environments. Before we use Gemfire8 , now we are upgrading to GemFrie9.
About GEODE-5896, it's very important usage for us, and I think the same for 
others if they want using spark to connect to Gemfire. Now we just do some 
patch at client-side the force the meta ready before function executed. But the 
perfect solution should fix some sever-side code.
I can share what I found and where I want to fix, you can review it , resonale 
or not . Fix it by current geode team or I can do it as a contributor.



Dong Yang, Dong [GTSUS Non-J&J
Thanks





[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #1078 was SUCCESSFUL (with 2456 tests)

2018-10-22 Thread Spring CI

---
Spring Data GemFire > Nightly-ApacheGeode > #1078 was successful.
---
Scheduled
2458 tests in total.

https://build.spring.io/browse/SGF-NAG-1078/





--
This message is automatically generated by Atlassian Bamboo