[jira] [Updated] (GEODE-6155) When JSONAssert is on the CLASSPATH of a Geode Server, Gfsh `list members` will throw a NoSuchMethodError

[ https://issues.apache.org/jira/browse/GEODE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6155: - Affects Version/s: 1.6.0 1.7.0 > When JSONAssert is on the CLASSPATH of a Geode Se

[jira] [Created] (GEODE-6157) AssertionError occurs when trying to create (HASH) Index on Invalid Region Entry

John Blum created GEODE-6157: Summary: AssertionError occurs when trying to create (HASH) Index on Invalid Region Entry Key: GEODE-6157 URL: https://issues.apache.org/jira/browse/GEODE-6157 Project: Geode

[jira] [Updated] (GEODE-6157) AssertionError occurs when trying to create (HASH) Index on Invalid Region Entry

[ https://issues.apache.org/jira/browse/GEODE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6157: - Labels: HashIndex Indexes JavaAssertions OQL Querying (was: ) > AssertionError occurs when trying to cre

[jira] [Updated] (GEODE-6157) AssertionError occurs when trying to create (HASH) Index on Invalid Region Entry

[ https://issues.apache.org/jira/browse/GEODE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6157: - Affects Version/s: 1.6.0 1.7.0 > AssertionError occurs when trying to create (HASH

[jira] [Created] (GEODE-6155) When JSONAssert is on the CLASSPATH of a Geode Server, Gfsh `list members` will throw a NoSuchMethodError

John Blum created GEODE-6155: Summary: When JSONAssert is on the CLASSPATH of a Geode Server, Gfsh `list members` will throw a NoSuchMethodError Key: GEODE-6155 URL: https://issues.apache.org/jira/browse/GEODE-6155

[jira] [Comment Edited] (GEODE-6152) Client PROXY Regions may return the same Object instance on get(key) and cause Thread-safety issues

[ https://issues.apache.org/jira/browse/GEODE-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710918#comment-16710918 ] John Blum edited comment on GEODE-6152 at 12/10/18 9:48 PM: T

[jira] [Comment Edited] (GEODE-6152) Client PROXY Regions may return the same Object instance on get(key) and cause Thread-safety issues

[ https://issues.apache.org/jira/browse/GEODE-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711104#comment-16711104 ] John Blum edited comment on GEODE-6152 at 12/10/18 9:50 PM: T

[jira] [Comment Edited] (GEODE-6152) Client PROXY Regions may return the same Object instance on get(key) and cause Thread-safety issues

[ https://issues.apache.org/jira/browse/GEODE-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711104#comment-16711104 ] John Blum edited comment on GEODE-6152 at 12/10/18 9:49 PM: T

[jira] [Commented] (GEODE-6032) Entire object is serialized again (and again) when Delta.hasDelta() returns false and client is using PROXY Region

[ https://issues.apache.org/jira/browse/GEODE-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715628#comment-16715628 ] John Blum commented on GEODE-6032: -- [~agingade] - Well, you can argue you that, but then

[jira] [Comment Edited] (GEODE-6032) Entire object is serialized again (and again) when Delta.hasDelta() returns false and client is using PROXY Region

[ https://issues.apache.org/jira/browse/GEODE-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715628#comment-16715628 ] John Blum edited comment on GEODE-6032 at 12/10/18 10:00 PM: -

[jira] [Commented] (GEODE-6032) Entire object is serialized again (and again) when Delta.hasDelta() returns false and client is using PROXY Region

[ https://issues.apache.org/jira/browse/GEODE-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715664#comment-16715664 ] John Blum commented on GEODE-6032: -- [~agingade] - In terms of the items you listed for s

[jira] [Comment Edited] (GEODE-6032) Entire object is serialized again (and again) when Delta.hasDelta() returns false and client is using PROXY Region

[ https://issues.apache.org/jira/browse/GEODE-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715664#comment-16715664 ] John Blum edited comment on GEODE-6032 at 12/10/18 10:18 PM: -

[jira] [Commented] (GEODE-6032) Entire object is serialized again (and again) when Delta.hasDelta() returns false and client is using PROXY Region

[ https://issues.apache.org/jira/browse/GEODE-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717772#comment-16717772 ] John Blum commented on GEODE-6032: -- My final comment on this issue (BUG, IMO)... If we

[jira] [Comment Edited] (GEODE-6032) Entire object is serialized again (and again) when Delta.hasDelta() returns false and client is using PROXY Region

[ https://issues.apache.org/jira/browse/GEODE-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717772#comment-16717772 ] John Blum edited comment on GEODE-6032 at 12/11/18 7:09 PM: M

[jira] [Commented] (GEODE-6430) GFSH simply hangs when the objects queried are not resolvable on the classpath.

[ https://issues.apache.org/jira/browse/GEODE-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772423#comment-16772423 ] John Blum commented on GEODE-6430: -- Note, the Server eventually spit out... {code:java}

[jira] [Created] (GEODE-6430) GFSH simply hangs when the objects queried are not resolvable on the classpath.

John Blum created GEODE-6430: Summary: GFSH simply hangs when the objects queried are not resolvable on the classpath. Key: GEODE-6430 URL: https://issues.apache.org/jira/browse/GEODE-6430 Project: Geode

[jira] [Commented] (GEODE-6430) GFSH simply hangs when the objects queried are not resolvable on the classpath.

[ https://issues.apache.org/jira/browse/GEODE-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772428#comment-16772428 ] John Blum commented on GEODE-6430: -- It should also be noted, that if some of the applica

[jira] [Commented] (GEODE-6430) GFSH simply hangs when the objects queried are not resolvable on the classpath.

[ https://issues.apache.org/jira/browse/GEODE-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772430#comment-16772430 ] John Blum commented on GEODE-6430: -- And, of course, if everything is present, then I see

[jira] [Comment Edited] (GEODE-6430) GFSH simply hangs when the objects queried are not resolvable on the classpath.

[ https://issues.apache.org/jira/browse/GEODE-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772428#comment-16772428 ] John Blum edited comment on GEODE-6430 at 2/19/19 11:13 PM: I

[jira] [Created] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS

John Blum created GEODE-6540: Summary: Allow the cache XSD to be resolvable through HTTPS Key: GEODE-6540 URL: https://issues.apache.org/jira/browse/GEODE-6540 Project: Geode Issue Type: Improvem

[jira] [Updated] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS

[ https://issues.apache.org/jira/browse/GEODE-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6540: - Priority: Critical (was: Major) > Allow the cache XSD to be resolvable through HTTPS > -

[jira] [Updated] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS

[ https://issues.apache.org/jira/browse/GEODE-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6540: - Affects Version/s: 1.8.0 > Allow the cache XSD to be resolvable through HTTPS > -

[jira] [Updated] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS

[ https://issues.apache.org/jira/browse/GEODE-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6540: - Labels: CacheXML HTTP HTTPS XSD (was: ) > Allow the cache XSD to be resolvable through HTTPS > -

[jira] [Commented] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS

[ https://issues.apache.org/jira/browse/GEODE-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797584#comment-16797584 ] John Blum commented on GEODE-6540: -- It should be noted that the {{cache-1.0.xsd}} (http

[jira] [Comment Edited] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS

[ https://issues.apache.org/jira/browse/GEODE-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797584#comment-16797584 ] John Blum edited comment on GEODE-6540 at 3/20/19 9:31 PM: --- It

[jira] [Comment Edited] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS

[ https://issues.apache.org/jira/browse/GEODE-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797584#comment-16797584 ] John Blum edited comment on GEODE-6540 at 3/20/19 9:28 PM: --- It

[jira] [Updated] (GEODE-6700) Reduce verbose and unnecessary log output

[ https://issues.apache.org/jira/browse/GEODE-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6700: - Labels: Log4j Logging (was: ) > Reduce verbose and unnecessary log output >

[jira] [Created] (GEODE-6700) Reduce verbose and unnecessary log output

John Blum created GEODE-6700: Summary: Reduce verbose and unnecessary log output Key: GEODE-6700 URL: https://issues.apache.org/jira/browse/GEODE-6700 Project: Geode Issue Type: Wish

[jira] [Updated] (GEODE-6700) Reduce verbose and unnecessary log output

[ https://issues.apache.org/jira/browse/GEODE-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6700: - Description: When starting an Apache Geode {{ClientCache}} application with the following Log4j configur

[jira] [Updated] (GEODE-6700) Reduce verbose and unnecessary log output

[ https://issues.apache.org/jira/browse/GEODE-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-6700: - Description: When starting an Apache Geode {{ClientCache}} application with the following Log4j configur

[jira] [Commented] (GEODE-2083) Geode should call Declarable.init() when the SecurityManager component implements Declarable.

[ https://issues.apache.org/jira/browse/GEODE-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832914#comment-16832914 ] John Blum commented on GEODE-2083: -- Any more thoughts/progress on this issue? I definit

[jira] [Commented] (GEODE-7200) Geode should not try to prefill any declared Pool (e.g. DEFAULT, or otherwise) if a client is running in a local-only capacity

[ https://issues.apache.org/jira/browse/GEODE-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206506#comment-17206506 ] John Blum commented on GEODE-7200: -- If the client is running completely in LOCAL-only mo

[jira] [Comment Edited] (GEODE-7200) Geode should not try to prefill any declared Pool (e.g. DEFAULT, or otherwise) if a client is running in a local-only capacity

[ https://issues.apache.org/jira/browse/GEODE-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206506#comment-17206506 ] John Blum edited comment on GEODE-7200 at 10/2/20, 8:40 PM: I

[jira] [Comment Edited] (GEODE-7200) Geode should not try to prefill any declared Pool (e.g. DEFAULT, or otherwise) if a client is running in a local-only capacity

[ https://issues.apache.org/jira/browse/GEODE-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206506#comment-17206506 ] John Blum edited comment on GEODE-7200 at 10/2/20, 8:40 PM: I

[jira] [Created] (GEODE-8618) OQL Grammar specification in docs is incomplete

John Blum created GEODE-8618: Summary: OQL Grammar specification in docs is incomplete Key: GEODE-8618 URL: https://issues.apache.org/jira/browse/GEODE-8618 Project: Geode Issue Type: Improvement

[jira] [Updated] (GEODE-8286) The Geode JVM Shutdown Hook should not be enabled by default

[ https://issues.apache.org/jira/browse/GEODE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8286: - Priority: Minor (was: Major) > The Geode JVM Shutdown Hook should not be enabled by default > --

[jira] [Updated] (GEODE-8618) OQL Grammar specification in docs is incomplete

[ https://issues.apache.org/jira/browse/GEODE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8618: - Priority: Minor (was: Major) > OQL Grammar specification in docs is incomplete > ---

[jira] [Updated] (GEODE-8618) OQL Grammar specification in docs is incomplete

[ https://issues.apache.org/jira/browse/GEODE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8618: - Description: For example, there are no rules for the {{ORDER BY}} and {{LIMIT}} clauses. Referring to th

[jira] [Updated] (GEODE-8286) The Geode JVM Shutdown Hook should not be enabled by default

[ https://issues.apache.org/jira/browse/GEODE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8286: - Priority: Critical (was: Minor) > The Geode JVM Shutdown Hook should not be enabled by default > ---

[jira] [Updated] (GEODE-8618) OQL grammar specification in docs is incomplete

[ https://issues.apache.org/jira/browse/GEODE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8618: - Summary: OQL grammar specification in docs is incomplete (was: OQL Grammar specification in docs is inco

[jira] [Updated] (GEODE-8618) OQL grammar specification in docs is incomplete

[ https://issues.apache.org/jira/browse/GEODE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8618: - Component/s: docs > OQL grammar specification in docs is incomplete > ---

[jira] [Commented] (GEODE-8618) OQL grammar specification in docs is incomplete

[ https://issues.apache.org/jira/browse/GEODE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219953#comment-17219953 ] John Blum commented on GEODE-8618: -- The doc also does not specify the grammar for {{GROU

[jira] [Created] (GEODE-8699) Expose the OQL Parser as a public API

John Blum created GEODE-8699: Summary: Expose the OQL Parser as a public API Key: GEODE-8699 URL: https://issues.apache.org/jira/browse/GEODE-8699 Project: Geode Issue Type: Wish Compon

[jira] [Updated] (GEODE-126) Provide pre-canned Geode Functions out-of-the-box for useful, common Geode operations.

[ https://issues.apache.org/jira/browse/GEODE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-126: Priority: Minor (was: Major) > Provide pre-canned Geode Functions out-of-the-box for useful, common Geode

[jira] [Assigned] (GEODE-167) Leverage the @ConditionalIgnore annotation and corresponding JUnit Rule to setup conditional test exclusions in the test suite based on timestamp or complex condition imp

[ https://issues.apache.org/jira/browse/GEODE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum reassigned GEODE-167: --- Assignee: (was: John Blum) > Leverage the @ConditionalIgnore annotation and corresponding JUnit R

[jira] [Updated] (GEODE-2083) Geode should call Declarable.init() when the SecurityManager component implements Declarable.

[ https://issues.apache.org/jira/browse/GEODE-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-2083: - Issue Type: Bug (was: Improvement) > Geode should call Declarable.init() when the SecurityManager compon

[jira] [Updated] (GEODE-7382) ReflectionBasedAutoSerializer should consider using the greediest application domain object type constructor it can find to satisfy the values of the domain object

[ https://issues.apache.org/jira/browse/GEODE-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-7382: - Summary: ReflectionBasedAutoSerializer should consider using the greediest application domain object type

[jira] [Updated] (GEODE-7376) AsyncEventQueueFactory.pauseEventDispatching() & AsyncEventQueue.resumeEventDispatching() is missing from the API Javadoc

[ https://issues.apache.org/jira/browse/GEODE-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-7376: - Priority: Minor (was: Major) > AsyncEventQueueFactory.pauseEventDispatching() & > AsyncEventQueue.resum

[jira] [Updated] (GEODE-7382) ReflectionBasedAutoSerializer should use the greediest domain object constructor it can find to satisfy the values of the domain object

[ https://issues.apache.org/jira/browse/GEODE-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-7382: - Summary: ReflectionBasedAutoSerializer should use the greediest domain object constructor it can find to

[jira] [Updated] (GEODE-7797) Deprecate old Apache Geode logging properties

[ https://issues.apache.org/jira/browse/GEODE-7797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-7797: - Priority: Minor (was: Major) > Deprecate old Apache Geode logging properties > -

[jira] [Updated] (GEODE-8235) Server should not be required to have an available PDX type registry for ClientCache applications

[ https://issues.apache.org/jira/browse/GEODE-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8235: - Priority: Critical (was: Major) > Server should not be required to have an available PDX type registry f

[jira] [Updated] (GEODE-8254) JSONFormatter cannot parse JSON Arrays

[ https://issues.apache.org/jira/browse/GEODE-8254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8254: - Issue Type: Bug (was: Improvement) > JSONFormatter cannot parse JSON Arrays > --

[jira] [Updated] (GEODE-8235) Server should not be required to have an available PDX type registry for ClientCache applications

[ https://issues.apache.org/jira/browse/GEODE-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8235: - Priority: Major (was: Critical) > Server should not be required to have an available PDX type registry f

[jira] [Updated] (GEODE-8255) JSONFormatter does not properly generate the @type metadata field

[ https://issues.apache.org/jira/browse/GEODE-8255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8255: - Priority: Critical (was: Major) > JSONFormatter does not properly generate the @type metadata field > --

[jira] [Updated] (GEODE-8256) The Jackson ObjectMapper used by a PdxInstance does not properly handle Java 8 Types

[ https://issues.apache.org/jira/browse/GEODE-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8256: - Priority: Critical (was: Major) > The Jackson ObjectMapper used by a PdxInstance does not properly handl

[jira] [Updated] (GEODE-8257) The Jackson ObjectMapper used by a PdxInstance cannot handle typed JSON Objects

[ https://issues.apache.org/jira/browse/GEODE-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8257: - Priority: Critical (was: Major) > The Jackson ObjectMapper used by a PdxInstance cannot handle typed JSO

[jira] [Updated] (GEODE-8258) Cannot implement PdxInstance and store in a Region

[ https://issues.apache.org/jira/browse/GEODE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8258: - Issue Type: Bug (was: Improvement) > Cannot implement PdxInstance and store in a Region > --

[jira] [Updated] (GEODE-8618) OQL grammar specification in docs is incomplete

[ https://issues.apache.org/jira/browse/GEODE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8618: - Issue Type: Bug (was: Improvement) > OQL grammar specification in docs is incomplete > -

[jira] [Updated] (GEODE-8618) OQL grammar specification in docs is incomplete

[ https://issues.apache.org/jira/browse/GEODE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8618: - Priority: Major (was: Minor) > OQL grammar specification in docs is incomplete > ---

[jira] [Updated] (GEODE-8286) The Geode JVM Shutdown Hook should not be enabled by default

[ https://issues.apache.org/jira/browse/GEODE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8286: - Issue Type: Bug (was: Improvement) > The Geode JVM Shutdown Hook should not be enabled by default >

[jira] [Commented] (GEODE-3096) Refactor and unify GFSH http clients

[ https://issues.apache.org/jira/browse/GEODE-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187190#comment-16187190 ] John Blum commented on GEODE-3096: -- Regarding... {quote}Use one single ShellCommandContr

[jira] [Updated] (GEODE-8254) JSONFormatter cannot parse JSON Arrays

[ https://issues.apache.org/jira/browse/GEODE-8254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8254: - Description: The Apache Geode [JSONFormatter|https://geode.apache.org/releases/latest/javadoc/org/apache

[jira] [Commented] (GEODE-7201) Useless and unhelpful Exception inappropriately logged at ERROR

[ https://issues.apache.org/jira/browse/GEODE-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561627#comment-17561627 ] John Blum commented on GEODE-7201: -- This does not only affect Spring! This is easy enou

<    1   2   3   4   5