John Blum created GEODE-28:
------------------------------
Summary: Gfsh's 'deploy' command needs enhancements to recognize
Spring Data GemFire Annotated (deployed) Functions.
Key: GEODE-28
URL: https://issues.apache.org/jira/browse/GEODE-28
Project: Geode
Issue Type: Improvement
Components: functions, management & tools
Environment: Apache Geode with Gfsh
Reporter: John Blum
If users want to "define" _Geode_ Functions using [_Spring Data GemFire's_
Function Annotation
support|http://docs.spring.io/spring-data-gemfire/docs/1.6.0.RELEASE/reference/html/#function-annotations],
they are unable to leverage other _Geode_ "features" as a result, such as the
ability to use _Gfsh's_'{{deploy}}' command to deploy JAR files with Function
definitions that may have changed where _Geode_ will "automatically" +detect+
and subsequently +register+ those JAR packaged Function(s).
I have been asked "_what is '_Spring Data GemFire_' going to do to support the
(hot) 'deploy' feature?" However, this is the +wrong+ question.
It is not what SDG can do since this is technically a limitation in _Geode_
(and by extension _GemFire_), since _Geode_ only detects _Geode_-specific types
(in particular, and +only+...
[com.gemstone.gemfire.cache.Function|http://gemfire.docs.pivotal.io/latest/javadocs/japi/com/gemstone/gemfire/cache/execute/Function.html]).
Therefore, the right question is, what can _Geode_ do to recognize additional
types (or rather, meta-data annotated functions) that are not part of the
_Geode_ core types?
In essence, Goede Gfsh's '{{deploy}}' command needs to be enhanced to recognize
SDG-defined POJO Annotated Functions and act accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
