[ 
https://issues.apache.org/jira/browse/GEODE-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942403#comment-15942403
 ] 

Shrumit Mehta commented on GEODE-2658:
--------------------------------------

Hi Hitesh,

I've had a look at the RedisAdapter code that you've pointed me to. 

I've also had a look at the code at org/apache/geode/cache/execute which seems 
to be what is used for Functions.

My understanding is that we have to implement Functions which can be executed 
using the REST API like so: "/gemfire-api/v1/functions/...". This project would 
involve writing Functions following in the footsteps of the RedisAdapter code.

I am definitely interested in making a Proposal for this project. I just wanted 
to know about a few more things:

1. Are we aiming to implement only the functions listed in the Description? Are 
there priorities/core requirements in that list?

2. Are we aiming for an improvement in performance (or other metrics) when we 
use Functions compared to using the RedisAdapter?

3. There are 3rd party wrapper libraries which can expose the Redis API though 
HTTP. Can you elaborate on the utility of this project? In what scenarios would 
a user prefer using Functions instead of RedisAdapter?

4. I will be following the generic Apache Proposal format. Is there anything 
specific that you're looking for in the Proposal?

Thanks,
Shrumit

> Provide Developer friendly api on Geode
> ---------------------------------------
>
>                 Key: GEODE-2658
>                 URL: https://issues.apache.org/jira/browse/GEODE-2658
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Hitesh Khamesra
>              Labels: GSoC2017
>
> Geode provides basic java concurrent map apis in distributed environment.
> These apis are not enough for application. Thus we need some utility api 
> based on Redis.
> 1. Update Counter Atomically.
> 2. Update object field atomically
> 3. Append new field to object
> 4. Fetch object field
> 5. Append new event to list (pop, push, range)
> 6. Append new member to set
> 7. Atomic Get and set
> 8. Atomic bit operations on value objects   
> 9. Set expiration on key
> 10. Merge objects  
> I will add more description later.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to