[jira] [Updated] (GEODE-2851) REST API can not execute functions with dot in the function ID
[
https://issues.apache.org/jira/browse/GEODE-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dodge updated GEODE-2851:
-
Description:
Following the examples at
(.../developing/function_exec/function_execution.html) we created a function
that returned the class name as the function ID. After deploying the JAR
containing that function using gfsh, we could successfully execute that
function via gfsh:
{code}
gfsh>execute function --id=cheezypizza.DeleteFunction
Execution summary
Member ID/Name | Function Execution Result
--- | -
10.32.104.55(rest-server:1878):1025 | Hello, world!
{code}
However, executing that function via a POST to
http://35.165.170.9:8080/gemfire-api/v1/functions/cheezypizza.DeleteFunction
fails, apparently because it stops reading the function ID at the '.' given
{color:red}Caused by: org.apache.geode.cache.execute.FunctionException:
Function named cheezypizza is not registered to FunctionService{color}:
{code}
org.apache.geode.rest.internal.web.exception.GemfireRestException: Server has
encountered error while executing the function!
at
org.apache.geode.rest.internal.web.controllers.FunctionAccessController.execute(FunctionAccessController.java:223)
at
org.apache.geode.rest.internal.web.controllers.FunctionAccessController$$FastClassBySpringCGLIB$$b1783d32.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:69)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
at
org.apache.geode.rest.internal.web.controllers.FunctionAccessController$$EnhancerBySpringCGLIB$$225e498c.execute()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:114)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738)
at
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:115)
at
[jira] [Created] (GEODE-2851) REST API can not execute functions with dot in the function ID
Michael Dodge created GEODE-2851:
Summary: REST API can not execute functions with dot in the
function ID
Key: GEODE-2851
URL: https://issues.apache.org/jira/browse/GEODE-2851
Project: Geode
Issue Type: Bug
Components: rest (dev)
Reporter: Michael Dodge
Following the examples at
(.../developing/function_exec/function_execution.html) we created a function
that returned the class name as the function ID. After deploying the JAR
containing that function using gfsh, we could successfully execute that
function via gfsh:
{code}
gfsh>execute function --id=cheezypizza.DeleteFunction
Execution summary
Member ID/Name | Function Execution Result
--- | -
10.32.104.55(rest-server:1878):1025 | Hello, world!
{code}
However, executing that function via a POST to
http://35.165.170.9:8080/gemfire-api/v1/functions/cheezypizza.DeleteFunction
fails, apparently because it stops reading the function ID at the '.' given
{color:red}Caused by: org.apache.geode.cache.execute.FunctionException:
Function named cheezypizza is not registered to FunctionService{color}:
{code}
org.apache.geode.rest.internal.web.exception.GemfireRestException: Server has
encountered error while executing the function!
at
org.apache.geode.rest.internal.web.controllers.FunctionAccessController.execute(FunctionAccessController.java:223)
at
org.apache.geode.rest.internal.web.controllers.FunctionAccessController$$FastClassBySpringCGLIB$$b1783d32.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:69)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
at
org.apache.geode.rest.internal.web.controllers.FunctionAccessController$$EnhancerBySpringCGLIB$$225e498c.execute()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:114)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738)
at
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
[jira] [Created] (GEODE-2849) REST API does not support LIKE matching with ad hoc queries
Michael Dodge created GEODE-2849: Summary: REST API does not support LIKE matching with ad hoc queries Key: GEODE-2849 URL: https://issues.apache.org/jira/browse/GEODE-2849 Project: Geode Issue Type: Bug Components: rest (dev) Reporter: Michael Dodge The REST API supports both named and unnamed (a.k.a. ad hoc) queries. Named queries support additional behaviors such as binding query parameters (e.g., $1) via the body of the POST and LIKE matching (e.g., WHERE foo LIKE 'bar%'). Ad hoc queries have no mechanism for supplying bind parameters but should still be able to use LIKE matching as it requires no additional data from the caller. We have observed errors (with somewhat obscure error messages) when using an HTTP GET with an URL like this: http://35.165.170.9:8080/gemfire-api/v1/queries/adhoc?q=SELECT%20*%20FROM%20/orderrequests%20WHERE%20PizzaType%20LIKE%20"%25oni; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2839) Enhance OQL portions of REST API developer documentation
Michael Dodge created GEODE-2839:
Summary: Enhance OQL portions of REST API developer documentation
Key: GEODE-2839
URL: https://issues.apache.org/jira/browse/GEODE-2839
Project: Geode
Issue Type: Improvement
Components: docs
Reporter: Michael Dodge
The documentation for querying has excellent coverage of OQL
(developing/query_additional/query_language_features.html) however it is
difficult to get to that coverage from the REST API developer documentation,
e.g., rest_apps/rest_queries.html, rest_apps/post_create_query.html.
* Some functionality differs between ad hoc ("unnamed") queries and created
("named") queries, in particular whether the "LIKE 'foo%'" construct is
supported, and those differences are not obvious.
* Whilst OQL syntax is discussed in the REST API documentation, there are no
hyperlinks to the OQL documentation.
* The REST API documentation contains a few example of OQL use yet the OQL
documentation has more complete examples.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (GEODE-2834) Query with WHERE clause unable to return values that include single-quotes inside strings
Michael Dodge created GEODE-2834:
Summary: Query with WHERE clause unable to return values that
include single-quotes inside strings
Key: GEODE-2834
URL: https://issues.apache.org/jira/browse/GEODE-2834
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Michael Dodge
If one was to create a region and insert JSON values via the REST API and one
of those values happened to include a single-quote character inside a string,
e.g.,:
{
"PizzaType":"meat lover's",
"Quantity":"1"
}
And then one was to execute a query using gfsh, e.g.:
gfsh>query --query="SELECT * FROM /orderrequests o WHERE o.PizzaType LIKE
'meat%'"
Then one would see an error as follows:
Error getting bean properties Expected a ',' or '}' at 26 [character 27 line 1]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (GEODE-2819) HTTP status code 414 is not documented
Michael Dodge created GEODE-2819: Summary: HTTP status code 414 is not documented Key: GEODE-2819 URL: https://issues.apache.org/jira/browse/GEODE-2819 Project: Geode Issue Type: Bug Components: rest (dev) Reporter: Michael Dodge Whilst consuming the REST API to do a "put all", we built a URI that is too long and thus got a 414 HTTP status code. The documentation that we are using (https://geode.apache.org/docs/guide/11/rest_apps/put_multiple_values_for_keys.html) does not specify what constitutes "too long" and does not include 414 in the Error Codes table at the bottom of the page. The former would be nice; the latter seems necessary. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2763) Remove of nonSingleHopsCount stat in client
Michael Dodge created GEODE-2763: Summary: Remove of nonSingleHopsCount stat in client Key: GEODE-2763 URL: https://issues.apache.org/jira/browse/GEODE-2763 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge A pre-existing issue (GEODE-2017) required the removal of the nonSingleHopsCount statistic in the clients. Whilst marked for the native client as well, it was not addressed in the native client. It should be. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2733) Crash during initialization using Xcode 8.3
[ https://issues.apache.org/jira/browse/GEODE-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949691#comment-15949691 ] Michael Dodge commented on GEODE-2733: -- I have independently verified that rolling back to Xcode 8.2.1 fixes the problem. > Crash during initialization using Xcode 8.3 > --- > > Key: GEODE-2733 > URL: https://issues.apache.org/jira/browse/GEODE-2733 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Dodge > > Circa 27 March 2017, Apple released the macOS 10.12.4 and Xcode 8.3 updates. > After applying those updates, all native client executables (e.g., unit > tests, integration tests, quickstarts) crashes with a SIGSEGV/EXC_BAD_ACCESS > with pthread_mutex_lock() which is part of the initialization of the ACE > libraries. We don't know whether it's caused by an incompatibility between > ACE and the 10.12.4 runtimes (e.g., a struct has changed in size) or if it's > an actual bug in the runtimes. Mike Martell found a bug that has already been > filed with Apple about Emacs crashing with pthread-related problems after > this update, so our current theory is that there's a problem in the pthreads > library from Apple. > UPDATE: Dave Barnes installed just macOS 10.12.4 and has had no problems. > Thus, it appears that Xcode 8.3 is the culprit. Anecdotal evidence suggests > that Xcode 8.3 has other problems, too, which may or may not be related to > the crashes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2733) Crash during initialization using Xcode 8.3
[ https://issues.apache.org/jira/browse/GEODE-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge updated GEODE-2733: - Description: Circa 27 March 2017, Apple released the macOS 10.12.4 and Xcode 8.3 updates. After applying those updates, all native client executables (e.g., unit tests, integration tests, quickstarts) crashes with a SIGSEGV/EXC_BAD_ACCESS with pthread_mutex_lock() which is part of the initialization of the ACE libraries. We don't know whether it's caused by an incompatibility between ACE and the 10.12.4 runtimes (e.g., a struct has changed in size) or if it's an actual bug in the runtimes. Mike Martell found a bug that has already been filed with Apple about Emacs crashing with pthread-related problems after this update, so our current theory is that there's a problem in the pthreads library from Apple. UPDATE: Dave Barnes installed just macOS 10.12.4 and has had no problems. Thus, it appears that Xcode 8.3 is the culprit. Anecdotal evidence suggests that Xcode 8.3 has other problems, too, which may or may not be related to the crashes. was:Circa 27 March 2017, Apple released the macOS 10.12.4 and Xcode 8.3 updates. After applying those updates, all native client executables (e.g., unit tests, integration tests, quickstarts) crashes with a SIGSEGV/EXC_BAD_ACCESS with pthread_mutex_lock() which is part of the initialization of the ACE libraries. We don't know whether it's caused by an incompatibility between ACE and the 10.12.4 runtimes (e.g., a struct has changed in size) or if it's an actual bug in the runtimes. Mike Martell found a bug that has already been filed with Apple about Emacs crashing with pthread-related problems after this update, so our current theory is that there's a problem in the pthreads library from Apple. Summary: Crash during initialization using Xcode 8.3 (was: Crash during initialization using macOS 10.12.4 and Xcode 8.3) > Crash during initialization using Xcode 8.3 > --- > > Key: GEODE-2733 > URL: https://issues.apache.org/jira/browse/GEODE-2733 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Dodge > > Circa 27 March 2017, Apple released the macOS 10.12.4 and Xcode 8.3 updates. > After applying those updates, all native client executables (e.g., unit > tests, integration tests, quickstarts) crashes with a SIGSEGV/EXC_BAD_ACCESS > with pthread_mutex_lock() which is part of the initialization of the ACE > libraries. We don't know whether it's caused by an incompatibility between > ACE and the 10.12.4 runtimes (e.g., a struct has changed in size) or if it's > an actual bug in the runtimes. Mike Martell found a bug that has already been > filed with Apple about Emacs crashing with pthread-related problems after > this update, so our current theory is that there's a problem in the pthreads > library from Apple. > UPDATE: Dave Barnes installed just macOS 10.12.4 and has had no problems. > Thus, it appears that Xcode 8.3 is the culprit. Anecdotal evidence suggests > that Xcode 8.3 has other problems, too, which may or may not be related to > the crashes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2733) Crash during initialization using macOS 10.12.4 and Xcode 8.3
Michael Dodge created GEODE-2733: Summary: Crash during initialization using macOS 10.12.4 and Xcode 8.3 Key: GEODE-2733 URL: https://issues.apache.org/jira/browse/GEODE-2733 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge Circa 27 March 2017, Apple released the macOS 10.12.4 and Xcode 8.3 updates. After applying those updates, all native client executables (e.g., unit tests, integration tests, quickstarts) crashes with a SIGSEGV/EXC_BAD_ACCESS with pthread_mutex_lock() which is part of the initialization of the ACE libraries. We don't know whether it's caused by an incompatibility between ACE and the 10.12.4 runtimes (e.g., a struct has changed in size) or if it's an actual bug in the runtimes. Mike Martell found a bug that has already been filed with Apple about Emacs crashing with pthread-related problems after this update, so our current theory is that there's a problem in the pthreads library from Apple. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2713) Function execution can lead to passing the address of a stack variable
Michael Dodge created GEODE-2713: Summary: Function execution can lead to passing the address of a stack variable Key: GEODE-2713 URL: https://issues.apache.org/jira/browse/GEODE-2713 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge In ThinClientRegion::executeFunctionSH(), the address of a stack variable (the result collector lock) is passed to the workers. If an exception occurs with any of the workers, the function will return, causing the stack variable to be destructed. Since the workers have the raw address, it is now a dangling pointer situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2701) Building instructions do not correctly specify that JDK is required
Michael Dodge created GEODE-2701: Summary: Building instructions do not correctly specify that JDK is required Key: GEODE-2701 URL: https://issues.apache.org/jira/browse/GEODE-2701 Project: Geode Issue Type: Bug Components: docs Reporter: Michael Dodge The build instructions (BUILDING.md and user guide) do not correctly that the JDK is required for building the geode-native code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2636) Update exemplary code to follow library renaming
[ https://issues.apache.org/jira/browse/GEODE-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2636: Assignee: Michael Dodge > Update exemplary code to follow library renaming > > > Key: GEODE-2636 > URL: https://issues.apache.org/jira/browse/GEODE-2636 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Dodge >Assignee: Michael Dodge > > The work done for GEODE-2508 needs to be accommodated in the template and > quickstart code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2636) Update exemplary code to follow library renaming
Michael Dodge created GEODE-2636: Summary: Update exemplary code to follow library renaming Key: GEODE-2636 URL: https://issues.apache.org/jira/browse/GEODE-2636 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge The work done for GEODE-2508 needs to be accommodated in the template and quickstart code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2598) Verify buffer allocation behavior of apache::geode::client::DataOutput
Michael Dodge created GEODE-2598: Summary: Verify buffer allocation behavior of apache::geode::client::DataOutput Key: GEODE-2598 URL: https://issues.apache.org/jira/browse/GEODE-2598 Project: Geode Issue Type: Test Components: native client Reporter: Michael Dodge The class apache::geode::client::DataOutput manages some internal buffers that contribute to the return values of getBufferLength() and getRemainingBufferLength(). The behavior appears to differ between platforms and is not immediately obvious from external observation. This behavior should be unit-tested to ensure that it does not regress. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2578) Query string limited to 64 KiB
[ https://issues.apache.org/jira/browse/GEODE-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2578: Assignee: Michael Dodge > Query string limited to 64 KiB > -- > > Key: GEODE-2578 > URL: https://issues.apache.org/jira/browse/GEODE-2578 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Dodge >Assignee: Michael Dodge > > The serialization of query strings uses a 16-bit unsigned integer to > represent the length of the query string. Query strings with more than 65535 > characters are silently truncated. Use of a 32-bit unsigned integer to > represent the length would greatly increase the size of query strings that > may be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2578) Query string limited to 64 KiB
Michael Dodge created GEODE-2578: Summary: Query string limited to 64 KiB Key: GEODE-2578 URL: https://issues.apache.org/jira/browse/GEODE-2578 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge The serialization of query strings uses a 16-bit unsigned integer to represent the length of the query string. Query strings with more than 65535 characters are silently truncated. Use of a 32-bit unsigned integer to represent the length would greatly increase the size of query strings that may be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2516) Script to Run Quickstarts not exectable
[ https://issues.apache.org/jira/browse/GEODE-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876923#comment-15876923 ] Michael Dodge commented on GEODE-2516: -- If memory serves, there is some wackiness in CMake that makes it challenging to successfully alter the executable permissions on files. At one time I think there were comments in the CMakeLists.txt files that explained it. > Script to Run Quickstarts not exectable > --- > > Key: GEODE-2516 > URL: https://issues.apache.org/jira/browse/GEODE-2516 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell > > The runcpp.sh script for running the native client quickstarts is not > executable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2478) Replace gf with geode
[ https://issues.apache.org/jira/browse/GEODE-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868674#comment-15868674 ] Michael Dodge commented on GEODE-2478: -- clicache/src/gf_defs.hpp clicache/src/gf_includes.hpp clicache/src/gfclicache.vcxproj.filters cppcache/include/geode/gf_base.hpp cppcache/include/geode/gf_types.hpp > Replace gf with geode > - > > Key: GEODE-2478 > URL: https://issues.apache.org/jira/browse/GEODE-2478 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Dodge > > The substring "gf" still occurs in some places in the native client codebase. > It ought to be replaced with "geode" or "geode-native", whichever makes more > sense on a case-by-case basis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2476) Replace gfcpp with geode
Michael Dodge created GEODE-2476: Summary: Replace gfcpp with geode Key: GEODE-2476 URL: https://issues.apache.org/jira/browse/GEODE-2476 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Dodge The substring "gfcpp" still occurs in some places in the native client codebase. It ought to be replaced with "geode" or "geode-native", whichever makes more sense on a case-by-case basis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2476) Replace gfcpp with geode
[ https://issues.apache.org/jira/browse/GEODE-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2476: Assignee: Michael Dodge > Replace gfcpp with geode > > > Key: GEODE-2476 > URL: https://issues.apache.org/jira/browse/GEODE-2476 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Dodge >Assignee: Michael Dodge > > The substring "gfcpp" still occurs in some places in the native client > codebase. It ought to be replaced with "geode" or "geode-native", whichever > makes more sense on a case-by-case basis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2376) Remove stack dump comment from ThinClientPoolDM.cpp
[ https://issues.apache.org/jira/browse/GEODE-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2376: Assignee: Michael Dodge > Remove stack dump comment from ThinClientPoolDM.cpp > --- > > Key: GEODE-2376 > URL: https://issues.apache.org/jira/browse/GEODE-2376 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Michael Dodge >Priority: Minor > > For some strange reason there is a stack dump embedded in the source. There > is no comment on the relevance to the section of code. > See around line 506. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2439) Replace all non-standard types in all public includes / API
[ https://issues.apache.org/jira/browse/GEODE-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862007#comment-15862007 ] Michael Dodge commented on GEODE-2439: -- The following appear to be the includes that could cause problems under cppcache/include/gfcpp: #include #include #include #include #include #include #include #include #include > Replace all non-standard types in all public includes / API > --- > > Key: GEODE-2439 > URL: https://issues.apache.org/jira/browse/GEODE-2439 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Ernest Burghardt > > research other non-standard types in API, ACE_Time -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2462) Unify quick starts and examples
[ https://issues.apache.org/jira/browse/GEODE-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge updated GEODE-2462: - Issue Type: New Feature (was: Bug) > Unify quick starts and examples > --- > > Key: GEODE-2462 > URL: https://issues.apache.org/jira/browse/GEODE-2462 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Michael Dodge >Assignee: Michael Dodge > > Currently, there exists both src/quickstart and examples under the native > root. It is unclear what the difference is or what value-add the examples > directories brings. The exemplary code under src/quickstart and examples > ought to be unified, without duplicates, of course. Given that src/quickstart > has more code, it should be the single location of exemplary code for the > native libraries. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2462) Unify quick starts and examples
[ https://issues.apache.org/jira/browse/GEODE-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2462: Assignee: Michael Dodge > Unify quick starts and examples > --- > > Key: GEODE-2462 > URL: https://issues.apache.org/jira/browse/GEODE-2462 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Dodge >Assignee: Michael Dodge > > Currently, there exists both src/quickstart and examples under the native > root. It is unclear what the difference is or what value-add the examples > directories brings. The exemplary code under src/quickstart and examples > ought to be unified, without duplicates, of course. Given that src/quickstart > has more code, it should be the single location of exemplary code for the > native libraries. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2462) Unify quick starts and examples
Michael Dodge created GEODE-2462: Summary: Unify quick starts and examples Key: GEODE-2462 URL: https://issues.apache.org/jira/browse/GEODE-2462 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge Currently, there exists both src/quickstart and examples under the native root. It is unclear what the difference is or what value-add the examples directories brings. The exemplary code under src/quickstart and examples ought to be unified, without duplicates, of course. Given that src/quickstart has more code, it should be the single location of exemplary code for the native libraries. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2446) Remove "c" client
[ https://issues.apache.org/jira/browse/GEODE-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2446: Assignee: Michael Dodge > Remove "c" client > - > > Key: GEODE-2446 > URL: https://issues.apache.org/jira/browse/GEODE-2446 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Assignee: Michael Dodge > > under src/ the "cclient" module is obsolete/old code that should be removed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2377) Fix run-unit-tests target
[ https://issues.apache.org/jira/browse/GEODE-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856957#comment-15856957 ] Michael Dodge commented on GEODE-2377: -- If the original concern was lack of output from the unit tests, pass -DCTEST_UNITTEST_VERBOSITY=-V to cmake during the original generation of the make files. > Fix run-unit-tests target > - > > Key: GEODE-2377 > URL: https://issues.apache.org/jira/browse/GEODE-2377 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Ernest Burghardt >Assignee: Michael Dodge > > The run-unit-tests target is not running the unit tests and you must do the > following to run the tests... > $ cd build/cppcache/test/ > $ ./gfcppcache_unittests -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2441) Remove PDXAutoSerializer
[ https://issues.apache.org/jira/browse/GEODE-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856908#comment-15856908 ] Michael Dodge commented on GEODE-2441: -- Perhaps move the relevant code to a user-contributed portion of the repo? > Remove PDXAutoSerializer > - > > Key: GEODE-2441 > URL: https://issues.apache.org/jira/browse/GEODE-2441 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Ernest Burghardt > > Remove PDXAutoSerializer utility that generates PDX serialization C++ source > that you can include in your project to (de)serialize your C++ classes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2438) Correct references to non-existent JAR files
Michael Dodge created GEODE-2438: Summary: Correct references to non-existent JAR files Key: GEODE-2438 URL: https://issues.apache.org/jira/browse/GEODE-2438 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge The method KillJavaProcesses() in src/clicache/integration-test/CacheHelperN.cs refers to geode.jar. Sadly, no JAR file called geode.jar exists in the GEODE installation so KillJavaProcesses() does not work. For purposes of identifying GEODE server processes, geode-core-*.jar is probably the better choice. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2411) Remove references to Gemfire from include guards
[ https://issues.apache.org/jira/browse/GEODE-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2411: Assignee: Michael Dodge > Remove references to Gemfire from include guards > > > Key: GEODE-2411 > URL: https://issues.apache.org/jira/browse/GEODE-2411 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Dodge >Assignee: Michael Dodge > > Many of the macro definitions used as include guards in the C++ header files > refer to Gemfire. These references should be replaced at least with > references to Geode but preferably using pragmas instead of defines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2411) Remove references to Gemfire from include guards
Michael Dodge created GEODE-2411: Summary: Remove references to Gemfire from include guards Key: GEODE-2411 URL: https://issues.apache.org/jira/browse/GEODE-2411 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Dodge Many of the macro definitions used as include guards in the C++ header files refer to Gemfire. These references should be replaced at least with references to Geode but preferably using pragmas instead of defines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2316) Replace GemFire namespace with Geode namespace
[ https://issues.apache.org/jira/browse/GEODE-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2316: Assignee: Michael Dodge > Replace GemFire namespace with Geode namespace > -- > > Key: GEODE-2316 > URL: https://issues.apache.org/jira/browse/GEODE-2316 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Dodge >Assignee: Michael Dodge > Fix For: 1.1.0 > > > For the code under cppcache, replace gemfire with apache::geode::client. > For the code under clicache, replace GemStone.GemFire.Cache.Generic and > GemStone.GemFire.Cache with Apache.Geode.Client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2306) Update native client BUILDING.md to reflect changes for Geode
[ https://issues.apache.org/jira/browse/GEODE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2306: Assignee: Michael Dodge > Update native client BUILDING.md to reflect changes for Geode > - > > Key: GEODE-2306 > URL: https://issues.apache.org/jira/browse/GEODE-2306 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Michael Dodge > Fix For: 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2246) Invalid class cast in function execution
[ https://issues.apache.org/jira/browse/GEODE-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2246: Assignee: Michael Dodge > Invalid class cast in function execution > > > Key: GEODE-2246 > URL: https://issues.apache.org/jira/browse/GEODE-2246 > Project: Geode > Issue Type: Bug > Components: functions >Reporter: Michael Dodge >Assignee: Michael Dodge > > In some situations (e.g., running a certain version of the native client > quickstarts) a ClassCastException is thrown inside ExecuteFunction66.run() at > line 391 of ExecuteFunction66.java: > final DistributionManager newDM = (DistributionManager) dm; > The variable dm is an instance of the interface > org.apache.geode.distributed.internal.DM. The class > org.apache.geode.distributed.internal.DistributionManager implements DM but > not all implementers of DM extend DistributionManager, e.g., > org.apache.geode.distributed.internal.LonerDistributionManager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
