[jira] [Issue Comment Deleted] (GEODE-2460) Update dependency versions

[ https://issues.apache.org/jira/browse/GEODE-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2460: - Comment: was deleted (was: Commit bc32a76c223d7a2b407fed72595af4056a78e433 in geode's branch refs/heads/G

Review Request 57175: GEODE-4160: upgrade mortbay-jetty-servlet-api dependency

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57175/ --- Review request for geode, Anthony Baker, Jinmei Liao, Jared Stewart, Kevin Dulin

[jira] [Commented] (GEODE-2538) Lucene query with values should not invoke cache loader

[ https://issues.apache.org/jira/browse/GEODE-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889295#comment-15889295 ] ASF subversion and git services commented on GEODE-2538: Commit 8b

[jira] [Resolved] (GEODE-2538) Lucene query with values should not invoke cache loader

[ https://issues.apache.org/jira/browse/GEODE-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-2538. -- Resolution: Fixed Fix Version/s: 1.2.0 > Lucene query with values should not invoke cache loader

[jira] [Commented] (GEODE-1887) Client PROXY region should delegate all operations to server

[ https://issues.apache.org/jira/browse/GEODE-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889321#comment-15889321 ] ASF subversion and git services commented on GEODE-1887: Commit 8a

Re: Build failed in Jenkins: Geode-nightly #762 - adongre, please read

Everything is building fine now, so I'm going to revert that commit. Avinash, go ahead and recommit it after the issue with the sub-class parameterization is fixed and it passes review and precheckin. I don't know of any way to make JUnit Parameterized work with JUnitParams, and I'd recommend not

Re: Build failed in Jenkins: Geode-nightly #762 - adongre, please read

Thanks for the tips, Kirk! I think #2 is something I ought to do more often. On Feb 28, 2017 5:59 PM, "Kirk Lund" wrote: > Everything is building fine now, so I'm going to revert that commit. > > Avinash, go ahead and recommit it after the issue with the sub-class > parameterization is fixed and

Gfsh> Create regions with bad property values?

This works in Geode 1.1.0 where GemFire 8 failed: gfsh> create region --name=Testxxx --type=PARTITION_REDUNDANT_HEAP_LRU --badProperty=badValue Is ignoring bad properties by design? Or a bug? Thanks, Wes Williams

Re: Gfsh> Create regions with bad property values?

We have multiple jira tickets on this waiting to be fixed: https://issues.apache.org/jira/browse/GEODE-1597 https://issues.apache.org/jira/browse/GEODE-2249 On Tue, Feb 28, 2017 at 9:16 PM, Real Wes wrote: > This works in Geode 1.1.0 where GemFire 8 failed: > > gfsh> create region --name=Testxx

Re: gfsh> export cluster-configuration - Reason: null

Is this proper syntax in Geode 1.1.0? If so, let me know and I’ll file a jira... gfsh>export cluster-configuration --zip-file-name=cluster.zip Could not process command due to GemFire error. Error while processing command Reason : null Thanks, Wes > On Mar 1, 2017, at 12:24 AM, Jinmei Lia

Re: gfsh> export cluster-configuration - Reason: null

It is the correct syntax, I just tried it on the tip of develop branch. I know we have tests that covers export cluster-configuration in the pipeline. Please do file a ticket with the logs. gfsh>export cluster-configuration --zip-file-name=test.zip Downloading cluster configuration : /Users/jilia

Re: export logs and stats

+1 for restricting the file extensions and looking at what the user has defined. On Tue, Feb 28, 2017 at 4:46 PM Jinmei Liao wrote: > Yeah, before we were simply looking at System.getProperty("user.dir") to > get all the logs/stats, now I think we should use whatever user defined in > the config

[jira] [Resolved] (GEODE-2489) Tombstone message with keys are sent to peer partitioned region nodes even though no clinets are registered

[ https://issues.apache.org/jira/browse/GEODE-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar resolved GEODE-2489. - Resolution: Fixed > Tombstone message with keys are sent to peer partitioned region nodes

[jira] [Updated] (GEODE-2489) Tombstone message with keys are sent to peer partitioned region nodes even though no clinets are registered

[ https://issues.apache.org/jira/browse/GEODE-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar updated GEODE-2489: Fix Version/s: 1.2.0 > Tombstone message with keys are sent to peer partitioned region nodes

[jira] [Resolved] (GEODE-2490) Tombstone messages are getting processed inline

[ https://issues.apache.org/jira/browse/GEODE-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar resolved GEODE-2490. - Resolution: Fixed > Tombstone messages are getting processed inline >

[jira] [Closed] (GEODE-2490) Tombstone messages are getting processed inline

[ https://issues.apache.org/jira/browse/GEODE-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar closed GEODE-2490. --- > Tombstone messages are getting processed inline > --

[jira] [Updated] (GEODE-2490) Tombstone messages are getting processed inline

[ https://issues.apache.org/jira/browse/GEODE-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar updated GEODE-2490: Fix Version/s: 1.2.0 > Tombstone messages are getting processed inline > ---

<    1   2